Hand over and close out
Finish the job cleanly: work the punch list to zero, confirm every inspection passed and no…
Pull together the operation and maintenance manual: collect the as-built drawings, product data, test and commissioning certificates and warranties, check the set is complete against the required index and issue it to the client at handover.
5 steps across the platform - what you do at each one, and why it matters.
Gather the as-built drawings and the product data sheets for what was actually installed, one place per system, and make sure each file reflects the final built state rather than an early design version.

Why: The operator will run the building from these documents for years. An as-built that still shows the design intent, not what the trades actually fitted, sends a maintenance team to the wrong valve on the wrong floor.
Pull in the test, inspection and commissioning certificates and the warranties for each system, and tie every one back to the equipment and the trade that signed it off.
Why: These certificates are the proof that the systems were tested and left working, and the warranties are what the client leans on when something fails. A missing certificate at handover often blocks occupation.
Run the assembled manual against the required contents index for the handover, mark off what is present, and chase the trades for the last missing drawings, data sheets and certificates before you close it.
Why: A handover manual is judged complete or not against the agreed index, not against how thick it looks. Finding the gaps yourself, before the client does, is what keeps the acceptance and the final payment on track.
Issue the complete manual to the client by a formal transmittal at handover, record the date and what was in the set, and keep the acknowledgement that they received it.
Why: Handing over the manual formally, with a dated record of exactly what was included, is what discharges your obligation to provide it. A pile of files with no transmittal behind it is easy to dispute months later.
Produce a short report that lists what the handover set contained, when it was issued and any items still to follow, and keep it with the project record.
Why: A clear summary of what was handed over, and what was still outstanding on the day, is the evidence you point back to if a document is ever queried. It closes the loop on the whole handover cleanly.
5 / 184 platform modules
Finish the job cleanly: work the punch list to zero, confirm every inspection passed and no…
Pull the as-built record together, prove the quality file has no gaps, then issue an operat…
Walk the finished works with the client, record what passes and what does not against the a…