RIT · GDL
Document generation
The process end to end, in the product: sources mobilised, sourced generation, automated check, block-by-block expert validation, export in the expected format, Audit Pack.
The NEXA impact
3
departments on the same core
3
reporting processes in production
To document
cycle time saved
Document generation industrialises a process your teams already run: it produces the deliverable, cites its sources, blocks validation when evidence is insufficient, and leaves an exportable Audit Pack. The expert remains the signatory.
This process’s figures will be published with their source and methodology note once the reference set is arbitrated. No unverified number goes live.
Capabilities
Generation linked to its sources
Every assertion in the deliverable is linked to the passage that justifies it. The link is clickable, the excerpt viewable without leaving the screen. A deliverable without sources is not publishable.
An automated check before the human
An evaluator model scores each block’s compliance, consistency and substantiation before a reviewer sees it. The expert lands on a pre-sorted document, not a blank page.
Block-by-block validation
The expert validates or corrects block by block, never the whole document. Every validation carries an identity and a timestamp. When evidence is missing, the button is disabled and the reason displayed.
Product visual coming soon
Export in the existing process format
DOCX, PDF or console. The output format is your process’s, not the tool’s. Your template nomenclature is respected — a deliverable that needs reformatting has gained nothing.
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
- Analysts, management controllers, actuaries, lawyers, quality leads
- Validators
- Process owner, designated approver
- Data mobilised
- Internal documents, warehouses, business referentials, authorised external sources
- Integrations
- IT connectors, SDK, export to the destination tool
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
ROI at our clients
GROUPAMA GAN VIE
Stake
Three departments produced their reporting separately, with heterogeneous controls and long cycles.
Goal
Position the core centrally to multiply processes with a single evidence chain.
3 departments on the same core
3 reporting processes in production
Published indicators are orders of magnitude measured in client context, not contractual guarantees. No logo, name or figure is published without the client’s explicit consent.
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 →Put this process into production.
A demo on your own documents, not on a demo dataset.