Handover
Construction handover pack support
A handover pack is painful because it is assembled at the end from information produced across the whole job, by people who have already moved to the next one. The work is not really compilation, it is retrieval. Aldbry changes where the information comes from, so the pack is built from records captured as the work happened rather than chased afterwards.
Why it hurts
The information exists, scattered
Almost nothing in a handover pack is genuinely new. It is a retrieval problem wearing a compilation problem's clothes.
01
Produced months before it is needed
Test certificates, inspection records and as-built information created throughout the job, filed inconsistently, wanted all at once.
02
By people who have left
Subcontractors demobilised, staff moved to the next project. Chasing them is slow and the answers get thinner.
03
Against a date that does not move
Handover is contractual. The pack competes with finishing the work, and it usually loses until the last fortnight.
04
Judged on completeness, not effort
A pack missing one certificate is incomplete. The ninety that are present earn nothing.
What we do
Change where the information comes from
- Capture upstreamSite diaries, inspection evidence and subcontractor records captured as the work happens, so the pack is assembled from what already exists.
- Index against the jobRecords filed and indexed as they are produced, which is what turns retrieval from a search into a lookup.
- Gaps surfaced earlyMissing certificates and records identified while the trade is still on site, rather than in the fortnight before handover.
- Acceptance stays with peopleWhether the pack is complete, and whether the works are ready, is a judgement your team makes.
Being straight about it
Being straight about what is live
Handover Packs is a Corvleo module in development, not a live one. Inspections and Quality, Progress Reporting and Handover Packs are in development. We do not describe a module as live until it is running on a real site. We will not describe it otherwise to make this page read better.
What is available today is the upstream half, and it is the half that decides how bad handover is. Site Diaries, RAMS Assurance and Subcontractor Onboarding are live on UK construction sites with a small number of contractors. Those three capture the records a handover pack is later assembled from, which is why getting them right during the job is worth more than any amount of effort at the end.
Where you want the compilation itself taken on now, we do that as a managed service rather than as software. Our managed AI services page sets out how that works, and it is a monthly retainer scoped to your workflows.
Common questions
Questions about construction handover pack
Will it work with our CDE and existing systems?
Yes, that is the design intention: Corvleo works alongside a Common Data Environment and feeds records into it rather than replacing it. Your CDE is the filing system, where documents are stored, controlled and shared. Corvleo sits a layer underneath, producing and checking the documentation in the first place, so what lands in the CDE is clean and consistent. In practice we also work inside the tools your teams already use day to day, such as Microsoft 365 or Google Workspace, SharePoint or shared drives, and your project platforms where they allow integration.
How much does it cost to start?
Two things cost nothing and the first paid step is £3,500. The free RAMS pack check reviews one subcontractor pack and returns a report, and the Construction Admin Cost Calculator gives you a headline cost of your own admin in a couple of minutes. The AI Opportunity Audit is a £3,500 fixed fee, credited against implementation if you proceed within 30 days, and the roadmap is yours to keep whether or not you take it further. Beyond that, AI training is half or full-day sessions, implementation is a fixed-fee setup with an optional retainer, and managed services are a monthly retainer scoped to your workflows. See the audit for what it covers.
What goes into a construction handover pack?
What the people who operate and later work on the structure need, which in practice means operation and maintenance information, as-built drawings and information, test and commissioning records, certificates and warranties, asset information where the client will run the building from it, and the health and safety file required under CDM 2015. The exact contents are set by the contract and the client, and they vary more than people expect. The common thread is that almost all of it is produced during the job rather than at the end, which is why the assembly is a retrieval exercise.
Can you assemble a handover pack for a project already finishing?
Yes, though the honest answer is that it will be harder and slower than starting earlier, because the work becomes chasing rather than compiling. Where records exist but are scattered, indexing and cross-checking them against what the contract requires is straightforward and we do it as a managed service. Where records were never created, no amount of assembly will produce them, and the useful output is a clear list of what is genuinely missing so you can decide what to recreate and what to disclose.
Next step
Start before the last fortnight.
Book a short call about the records your current projects are producing, and what handover will need from them.