Add-on module
The handover dossier
The handover dossier (MRB/MDR) that builds itself as you work.
For those who hand over a job with its full documentation.
What changes
The dossier is put together by hand in the last weeks, from folders and email.
You see what's missing while there's still time, then seal it.
How it works
- 1
Declare what the dossier must contain
- 2
Watch it fill as the work happens
- 3
See what is missing while it can still be fixed
- 4
Compile and seal
What's included
- Contract-driven index
- Live completeness
- Pulls from every contributor
- Ordered and paginated
- Sealed
- Reproducible
Part of the platform, always included
Details
The steps, explained
- Declare what the dossier must contain. The index comes from the contract — client requirements, code requirements, and what the notified body will want to see.
- Watch it fill as the work happens. Every certificate, report, test result and sign-off produced during the job lands against its slot. Completeness is visible in week two, not week fifty.
- See what is missing while it can still be fixed. The gap list is the useful output. A missing MTR found in month three is an email; found on handover day it is a delay.
- Compile and seal. One action produces the ordered, paginated, indexed pack, sealed and verifiable.
All the features
- Contract-driven index. The structure follows the client's requirement, not a fixed template.
- Live completeness. What is in, what is missing, and who owes it.
- Pulls from every contributor. Welding, NDT, inspection, materials, calibration, nonconformances.
- Ordered and paginated. Section numbering, running index, cross-references that resolve.
- Sealed. The pack and its documents carry a seal a third party can check.
- Reproducible. The same pack can be regenerated later and shown to be the same pack.
In depth
Why this is the wedge
Ask anyone who has delivered a large fabrication contract what the worst part was. It is rarely the welding.
It is the fortnight before handover, when a small group of people reconstruct months of evidence from shared drives, email attachments and a filing cabinet, against a client index that does not quite match how any of it was filed.
It is expensive, it is unbillable, and it happens at the exact moment when the margin on the job is already decided.
The reason it is painful is structural: the evidence is produced continuously and collected once, at the end. Collect it continuously instead and the compilation stops being a project. That is the whole idea, and everything else in the platform exists to feed it.
Want to see it on your own work?
Bring us a real case: in thirty minutes we show you what it becomes in Worgify.