Note
Stage Billing Through a Site Handover
When a site manager gives notice, the immediate concern is coverage: who goes to site tomorrow. The billing concern arrives six weeks later.
The person who ran the site held a working picture of where the project stood: which stages had been accepted but not yet invoiced, what was agreed verbally with the main contractor’s engineer, when the retention amounts would become releasable, which material orders were still open. A handover that covers site coverage but not billing status sets the incoming manager up to discover the gaps after a billing cycle has already closed.
This piece covers what needs to transfer, how to do it in half a day when the project is documented, and what to do when it is not.
What actually leaves with the outgoing site manager?
Not the project folder. That usually stays. What leaves is the context that makes it usable: the knowledge that turns a set of documents into a working picture of where the project stands.
Four things in particular:
Accepted-but-not-invoiced stages. Acceptance and billing rarely happen on the same day. A stage accepted on the 10th and a billing cutoff on the 25th still leaves two weeks for the invoice to go out. If nobody flags the stage at handover, the cutoff passes and the stage waits another month.
Verbal scope agreements. When a main contractor’s engineer changes a detail on site and the crew adjusts, that instruction may never have made it into a written variation record. The person who was there when it happened is the only record.
Retention tracking context. The release conditions are in the contract. Whether all stages feeding the retention pool have been properly accepted and closed is knowledge that accumulates across months. The number is easy to read. The path to it is not.
Open material orders. A fabrication or delivery order placed but not yet confirmed is invisible to anyone who did not place it.
These four are where missed billing after a handover comes from: not gaps in the project file, but gaps in the working knowledge that sits on top of it.
What does a complete handover document contain?
A one-page project status snapshot is the minimum a handover should produce. Every stage from the BOQ listed with a current status: accepted and invoiced, accepted and not yet invoiced, in progress, not yet started. This single page eliminates the most common post-handover error, which is a stage that was accepted but never billed because the incoming manager had no way of knowing acceptance had happened.
Three supporting files complete the picture:
The acceptance folder. One signed acceptance form per accepted stage. If any form is missing, the handover is when that surfaces. Tracking it down while the outgoing manager is still available takes a day. Six months later, when a missing form holds up a retention release, it can take much longer.
The variation log. A list of every instruction outside the original scope: date, who gave it, whether it has been priced, whether it has been billed. If the log does not exist, the handover is when reconstruction begins. Anything not recoverable gets noted as a gap.
The material date list. Open orders, expected delivery dates, and which stages depend on each delivery. The incoming manager cannot chase a delivery they do not know exists.
How long should a complete handover take?
When the project runs on a documented timeline with billing stages as pins on the same line as the work, a handover takes roughly three hours: one hour reviewing the timeline and walking through the status snapshot together, one hour on site moving zone by zone with the incoming manager, and one hour going through the acceptance folder and the variation log.
When the project does not have a documented timeline, the same handover runs between two days and two weeks and still leaves gaps. The things not written down cannot be retrieved from a folder. The difference between the three-hour handover and the two-week handover is not effort. It is where the knowledge lived during the project.
A worked example: five zones, two weeks notice
A fit-out subcontract covers five zones across two floors. The site manager gives two weeks’ notice at the end of week eight. Zones 1 through 3 are accepted; zone 2 was accepted on 18 August and not yet invoiced. Zone 4 is in progress, zone 5 not started.
The handover document shows zone 2 as accepted and awaiting invoice, with the signed form on file. It also shows a tile order for zone 4 with an expected delivery of 2 September.
The incoming manager enters week nine knowing zone 2 needs an invoice before the September billing cutoff, and that the zone 4 materials need confirming with the supplier before the install bar can start.
Without the handover document, zone 2 appears in October when someone asks why the count is short. The tile order goes unchecked, the delivery slips, and zone 4’s acceptance moves to the following billing period.
How do you stop billing knowledge from concentrating in one person?
The answer is not continuous documentation. That ask rarely survives a busy site.
The answer is two questions, same time each week: which stages changed status this week, and are there any open items that need to move before the next billing date. Twenty minutes. Across eight weeks, that habit produces a project file a new manager can read in an hour.
When the file is current, a handover is a transfer. When it is not, it is a reconstruction, and the cost shows up as billing stages discovered too late for the current period.
FAQ
What should the outgoing site manager prepare before their last day?
Draft the status snapshot first, covering every stage from the BOQ. Then confirm that every accepted stage has a signed form in the folder. Then document any verbal scope agreements or variation instructions not formally recorded. That sequence covers the three most common post-handover billing gaps before the incoming manager arrives. The site walk confirms what the document describes.
What if the site manager leaves without completing the handover?
Start with the main contractor’s commercial team. Ask for a payment summary showing which stages have been invoiced and what is outstanding. Compare against the BOQ. The difference between what has been invoiced and what the contract covers is where accepted-but-not-billed stages hide. It takes longer than a proper handover, but the information is recoverable.
How far in advance should handover preparation begin?
With a two-week notice period, draft the status snapshot in the first week and review it with the incoming manager in the second. The site walk should happen at least three days before the outgoing manager’s last day. A handover started in the final 48 hours can transfer the folder. It rarely transfers the context.
If you want to look at where the billing stages stand on a current project before a handover creates the urgency to find out, a 45-minute call is a good place to start. We open the project file together and put a status on every stage.