Handover feels like an ending. The work is accepted, the final invoice is paid, the contractor packs up, and the people who ran the job move on to the next thing. But the building, machine, system or process that was handed over is only beginning its working life. Some of its problems will not appear for years. Some of its promised benefits will only arrive if someone keeps working at them. And some of its obligations, such as maintenance, monitoring, permits and eventual disposal, will continue long after anyone remembers the project.
Two kinds of trouble follow. The first is hidden defects: a flaw that could not be seen at completion and appears years later, when the original team has gone, the warranty has expired and nobody can find the drawings. The second is orphaned obligations and benefits: the energy saving that quietly disappears after a service visit, the monitoring requirement nobody knew about, the end-of-life cost that never appeared in the business case.
This article explains why handover does not end responsibility, how to separate four different kinds of closure, what records to keep for the long tail, and how a small business can make sure each continuing obligation and benefit has an owner. It is general information. Rights and time limits for defect claims depend on the contract, the type of work and state law, so get legal advice when a defect appears, and check permit and licence conditions with the relevant authority.
Four kinds of closure
Businesses often treat a job as finished on a single date. In practice, there are four different points, and they may be years apart:
| Closure point | What it means | Typical owner |
|---|---|---|
| Project closure | The people delivering the work have finished what they were engaged to do | The project lead or contractor |
| Acceptance | The output meets agreed conditions and passes to its owner | The business owner or operations |
| Benefit realisation | The intended savings, capacity or improvements are actually happening | Whoever runs the asset day to day |
| Liability closure | Remaining obligations have been met and no longer need active management | Often nobody, unless assigned |
The common mistake is collapsing all four into the handover date. A job can be finished, accepted and paid for while its benefits have not yet been realised and its obligations have barely begun.
Hidden defects outlive warranties
A latent defect is a flaw that was not apparent at completion or during the defects period. Some only show after repeated loading, weather, settlement, temperature cycling, vibration or years of operation. By the time they appear:
- the people who designed and built the work may have left;
- the contractor may have restructured or stopped trading;
- records may be archived or lost;
- the operating team knows the symptom, but not the original design assumptions.
The defect becomes harder to diagnose exactly when it becomes more expensive. And a later failure is not automatically the builder’s fault. It may come from design, construction, materials, the way the asset has been used or maintained, later alterations, or several of these together. Working out which requires evidence created during the original project.
Several legal paths may be relevant: the contract, warranties, statutory obligations for building work, negligence, consumer protections and insurance. Which applies, and for how long, depends on the circumstances and the law in your state. Time limits vary and can run for many years. A lawyer can advise once a problem appears, but only the business can make sure the evidence still exists.
Keep the records the future will need
Projects tend to archive records for administrative convenience. A better approach starts from the question: if this failed in eight years, what would we need to know? For work that matters, keep:
- design drawings and calculations, including the loads or conditions the design assumed;
- as-built drawings showing what was actually constructed or installed;
- material certificates and test results;
- inspection records, approvals and certificates;
- approved changes and deviations, with the reasons;
- the defect list and how each item was resolved;
- warranties, manuals, maintenance schedules and supplier details;
- commissioning records and initial performance readings.
Store them where they will survive staff changes, a move of premises and a change of software. Record where they are in your asset list, so whoever is responsible in five years can find them.
Benefits need owners after the project ends
The same thinking applies to the good things a project was meant to deliver. Suppose a business installs heat recovery on its refrigeration plant to pre-heat water and cut gas use. The project delivers the equipment. The saving still depends on commissioning quality, settings, maintenance, production patterns and someone checking the result.
If nobody owns the benefit after handover, the business may report the project as a success without ever knowing whether the expected value arrived. Each significant benefit needs:
- a baseline: what things looked like before;
- a measure: what will be tracked;
- a target: what was promised;
- a review date: when someone will check;
- an owner with authority to act if performance drifts.
Handover transfers risk, so treat it that way
Handover moves control of the asset, and with it many responsibilities. The receiving owner needs to accept, knowingly:
- maintenance obligations and service schedules;
- monitoring or reporting required by permits, licences or agreements;
- operating controls and safe operating procedures;
- remaining risks and any known defects;
- records and data;
- contingency arrangements;
- the budget to do all of this.
A signature on a completion certificate is weak evidence if the people taking over do not have the knowledge, time or money to meet those obligations. A useful question at handover is: what must remain true after this job closes for the intended outcome to last? It exposes the dependencies the project team was quietly carrying.
The business case should see the whole life
Some costs only appear after delivery: energy and water, maintenance, monitoring, waste, insurance, regulatory reporting, replacement, decommissioning, site restoration and disposal. A project can look attractive if analysis stops at commissioning and much less so over its whole life.
Not every future cost can be forecast precisely. That is not a reason to ignore them. Distinguish three groups:
- known future obligations, such as scheduled replacements or permit conditions;
- uncertain liabilities, such as possible remediation;
- consequences that cannot yet be reliably valued.
The buying for the whole life of equipment article covers how to compare options on lifetime cost rather than purchase price.
Accountability should move, not disappear
Making the project lead responsible for outcomes years after handover is unrealistic; they have no control once the job ends. The opposite failure is just as common: nobody is responsible because the project has closed. The answer is staged accountability:
- During design, surface long-term consequences and lifetime costs.
- During delivery, create the controls, records and handover arrangements needed later.
- At handover, the receiving owner formally accepts remaining obligations and benefits.
- During operation, someone checks that performance continues and obligations are met.
- At end of life, decommissioning or restoration may become a new project.
A one-page handover sheet
A simple sheet completed before the final payment does most of the work. It does not need special software; a shared document linked to your asset list is enough.
| Section | What to record |
|---|---|
| Continuing obligations | Maintenance, servicing, inspections, monitoring, sampling, reporting, permit and licence conditions, each with an owner and a first due date |
| Expected benefits | Each promised saving or improvement, its baseline, how it will be measured, the target and a review date |
| Known issues | Open defects, agreed workarounds and anything accepted “for now” |
| Warranties and support | What is covered, for how long, who to contact and what voids the cover |
| Records | Where drawings, test results, certificates, manuals and commissioning data are kept |
| End of life | Expected replacement or disposal, and any restoration obligations |
Ask the people taking over the asset to read it and sign it, and keep a copy with the asset records. If the job involved supplier inspections and tests, the records produced under an inspection and test plan are exactly the evidence a future investigation will need, so file them with the sheet.
A worked example
This is an illustration. A food manufacturer completes an extension to its factory: a new floor slab for a packing area, a refrigeration plant with heat recovery to pre-heat wash-down water, and a new pre-treatment pit for wastewater under its trade waste agreement with the local water utility. The builder finishes on time, the defects period of twelve months passes without major issues, and the project is closed.
Over the next four years, three problems emerge:
- Hidden defect. Cracks appear along the forklift route in the new slab. The builder points out that the defects period ended long ago. The owner needs to know what loads the slab was designed for, what concrete strength was specified and achieved, and whether forklift traffic has changed. The as-built drawings and concrete test results are on the former project manager’s laptop, which was replaced two years earlier. Reconstructing the history costs more than the first engineering inspection.
- Disappearing benefit. The heat recovery was expected to save about $14,000 a year in gas. When the owner finally compares bills, actual savings in the most recent year were about $5,000. A refrigeration technician had changed settings during a service, and nobody was tracking the saving.
- Missed obligation. The trade waste agreement requires regular pit cleaning and periodic sampling. The project team assumed operations knew; operations assumed the contractor had set it up. After several months without cleaning, the business receives a warning from the utility.
None of these was a failure of the project as delivered. Each was a failure of what happened after closure.
For its next project, the business uses a one-page handover sheet. It lists every continuing obligation with a named owner and a date, every expected benefit with a baseline and a review date, and where every critical record is stored. Records are kept in a shared folder linked to the asset list, not on individual devices.
How this applies to a small Australian business
- Treat handover as a transfer of risk, not an administrative step.
- Use a one-page handover sheet listing obligations, benefits, owners, dates and record locations.
- Keep design, construction and test records for significant work, stored where they will survive staff and system changes.
- Give each expected benefit a baseline, measure and review date.
- Check permit, licence and agreement conditions that continue after the job, and who will meet them.
- Include whole-of-life costs in the original decision.
- Get legal advice promptly if a hidden defect appears; time limits apply and vary.
- Talk to your insurer about whether any policies respond to defects or resulting damage.
Signals worth watching
- Records held on personal devices or by the contractor only.
- Benefits reported as achieved but never measured.
- Obligations nobody can name an owner for.
- Projects closed with known issues described as “operational matters”.
- Maintenance schedules that exist on paper but not in anyone’s calendar.
- Business cases that stop at commissioning.
Common mistakes
- Collapsing four kinds of closure into one date.
- Archiving records for convenience rather than future need.
- Assuming the expiry of a defects period ends all responsibility, on either side.
- Assuming benefits arrive automatically once the equipment is installed.
- Leaving continuing obligations unassigned.
- Ignoring end-of-life costs when choosing between options.
Frequently asked questions
How long should we keep project records? For significant work, at least as long as the asset is in use and claims could be made. Ask your lawyer about time limits that apply to your type of work and state.
Who should own benefits after handover? The person who runs the asset or process day to day, with authority to adjust it. Not the project lead, who has moved on.
Does the builder remain responsible after the defects period? It depends on the contract, the nature of the defect and the law. Do not assume either way; get advice.
What belongs on a handover sheet? Continuing obligations, owners and dates; expected benefits, baselines and review dates; known defects; warranties; and where every critical record is kept.
Is this only relevant for buildings? No. The same applies to machines, software systems, processes and any work with a long working life.
Questions to ask
- Which of our recent projects have obligations that continue after closure, and who owns them?
- Could we find the design and test records for our most important assets?
- Which promised benefits have we actually measured since handover?
- What permit or agreement conditions did our last project create?
- What will this asset cost to maintain, operate and eventually remove?
- What must remain true for the outcome to last?
Bringing it together
A project ends at handover, but what it creates keeps producing risks, costs and benefits for years. Separate project closure, acceptance, benefit realisation and liability closure, because they rarely happen on the same day. Keep the records a future investigation will need, stored where they will survive. Give every continuing obligation and every expected benefit a named owner, a measure and a date. Include whole-of-life costs in the original decision. Responsibility should move from the project team to the people who run the asset, not disappear when the last invoice is paid.
Source: KEVOS notes, drawing on teaching material on defects, latent defects and contract closure, and on environmental project management material on lifecycle accountability after project handover. Examples and figures in this article are illustrations. This article is general information, not legal advice.
