Skip to content

MRB · MDR · Final Turnover Pack

The handover dossier

The dossier is assembled by hand in the last weeks of a job, from folders and inboxes, by the people who can least afford the time.

How it works

  1. 01

    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.

  2. 02

    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.

  3. 03

    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.

  4. 04

    Compile and seal

    One action produces the ordered, paginated, indexed pack, sealed and verifiable.

What it covers

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.

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.