PROCESS · DOCUMENT KNOWLEDGE
Requirements matching
Requirement by requirement: the answer found in your documentation, the coverage level, and the gap when there is one.
The NEXA impact
Minutes
to produce a complete analysis
1 to 2 months
for the same work by hand
Share of requirements covered on the first pass
What matters is not the matches : it is the gaps. The process matches every requirement : regulatory, contractual, customer : to your documented answer, scores the coverage and surfaces what is missing. The expert decides; the trace remains.
Published indicators are orders of magnitude measured in client context, not contractual guarantees. Every figure was cleared by the client concerned before going live.
Indicators shown without a value are still being arbitrated: no unverified figure, and none borrowed from another process, goes live.
Capabilities
Two referentials, one matching
The requirements plan on one side, your documented answers on the other. The platform builds the matching line by line and materialises the links : and the holes.
A reasoned decision per requirement
Every match carries a reasoned decision: covered, partial, gap. The justification cites passages on both sides. Nothing is declared compliant without a reference.
Expert validation per requirement
The expert confirms or corrects each decision, with identity and timestamp. Confirmed gaps feed the action plan.
The exportable file
The whole matching : requirements, answers, decisions, validations : exports as a dated file, defensible in quality review or client audit.
Export du dossier d’audit : période, périmètre, format
One family in a structured portfolio.
How the process unfolds
Six steps, six evidence artefacts. That is what separates a critical process from text generation.
Ingestion & context
Sources selected, access scope applied, personal data detected before execution.
Generation
The engine produces a proposal. Every assertion is linked to its source.
Automated check
The AI judge scores compliance, consistency and substantiation, block by block.
Expert validation
Draft → Reviewed → Approved. Three separate roles: operator, reviewer, approver.
Governed feedback
The expert’s feedback is typed, attributed, versioned and replayed on the next process.
Capitalisation
The validated pattern serves the next process, which starts faster and costs less.
Users and data
- Users
- Quality leads, compliance, tender-response teams
- Validators
- Quality lead, domain expert
- Data mobilised
- Requirements books, internal referentials, manuals, procedures
- Integrations
- Document connectors, matching-file export
Controls and guardrails
- Substantiation threshold configurable per process
- Validation disabled when evidence is insufficient
- Personal-data detection before execution
- Column contract enforced: any gap is rejected
- Runs replayable on an auditor’s request
- Audit Pack exportable over the chosen period
The trace this process leaves
Transparence
The trace this process leaves
Run Receipt, Evidence Panel in the interface, exportable Audit Pack and replay on demand.
See the evidence chain →Gouvernance
What this process consumes and returns
Cost per run, tokens, CO₂ footprint, number of uses, acceptance rate and ROI configured by the process owner.
See the Cockpit →Simulateur ROI
What a process estate costs, and returns
Compare the three paths on your volumes, then simulate what a process returns: break-even, kinds of value, Cost per Run.
Open the simulator →Put this process into production.
A demo on your own documents, not on a demo dataset.