Handover and RFSU: what transfers, and what it costs to prove it.

1. What RFSU means

Ready for start-up declares that a subsystem has been commissioned and is safe to be put into service. It is issued per subsystem, and on most projects it is the point at which care, custody and control transfer from the contractor to the operator.

That transfer is the substance of the milestone. After it, the operator carries responsibility for the subsystem's condition, its permits and its safe operation. Which is why the operator will not accept it on assertion — they will want the record chain beneath it.

2. The certificate chain

Each certificate depends on the layer below it, and none of them are independent claims:

1. ITRs — individual checks signed against tags.
2. Walkdown — physical verification of the subsystem against documentation.
3. Punch status — blocking items cleared, carried items visible.
4. Mechanical completion — the subsystem is built and statically inspected.
5. Commissioning records — B-ITRs and procedure sign-offs proving function.
6. RFSU — safe and ready for service; custody transfers.
7. Final handover — after start-up and performance testing, with the full dossier issued.

A certificate issued without its layer is worth very little at audit, which is why certificate management enforces the prerequisites rather than trusting them.

3. What goes in the handover dossier

Contents vary by contract and jurisdiction, but a subsystem dossier normally contains:

• The certificate itself, signed by all required parties.
• All completed ITRs for the tags in the subsystem, with their attachments.
• The walkdown record and the punch list, with status of every item.
• Preservation history for equipment in scope.
• Vendor documentation, calibration certificates and material certificates.
• As-built markups and any approved deviations or concessions.

The volume is the point. A single subsystem dossier can run to thousands of pages, and a facility carries hundreds of subsystems.

4. Why dossier assembly overruns

Assembly overruns because it is treated as a phase rather than a by-product. If records were signed on paper and filed by date, then building a per-subsystem dossier means locating every document for every tag in that subsystem — a search problem multiplied by hundreds of subsystems.

When records are captured against the tag and subsystem from the beginning, the dossier is a query rather than a project. That is the single largest schedule difference between paper-based and digital completions.

5. RFSU is not final acceptance

RFSU transfers custody so the operator can start up. Final acceptance normally comes later, after performance testing has demonstrated contractual criteria and after remaining Category B punch has been closed out. Warranty periods, retention release and liquidated damages usually key off final acceptance rather than RFSU.

Both dates matter commercially, and both are conditional on evidence that has to exist in retrievable form. Treating handover as a document exercise at the end is how projects lose months at exactly the point where there is no float left.