A design handover is the controlled transfer of a design, with the information needed to act on it, from the people who produced it to the people who will build, check or operate it. Done well, it has a defined package, a named sender, a named reviewer, a recorded acceptance and a route for changes. Done badly, it is an email with a zip file and a hope that nobody asks questions. This guide sets out how the process works on UK construction and engineering projects, using RIBA, IStructE, CDM 2015 and RICS guidance.
TL;DR
- Handover is not one event. It happens at every stage gateway, and again at Practical Completion when the building passes to the client.
- A good package states what is issued, the assumptions behind it, the risks that remain and what is still open.
- Name a sender and a competent reviewer, and hold a short walkthrough with the receiving team before sign-off.
- After handover, every change goes through a register, an impact check, an authorisation and a reissue of affected drawings.
- Overflow capacity can prepare and check handover packages, provided the output is review-ready and aligned to UK standards.
Table of Contents
- What a design handover is and where it sits in the UK project timeline
- What a handover package should contain
- Who prepares, checks and accepts
- A practical handover process, step by step
- How to check a handover is complete and understood
- Design change control after handover
- The design change order process: record, authorise, track
- Higher-risk buildings: stricter change rules
- Common handover failures and how to avoid them
- Perspective: what we see from the engineering desk
- Get handover-ready packages without hiring
- FAQ
- Sources
What a design handover is and where it sits in the UK project timeline
The words “handover”, “transfer” and “handoff” are used loosely. On UK projects there are two distinct meanings, and mixing them up causes most of the confusion.
Design handover between parties or stages. Responsibility for design information passes from one team to another: from architect to structural engineer, from concept to technical design, from the designer to the contractor’s design team. The RIBA Plan of Work 2020 frames this well: a crucial goal at the end of each stage is to capture everything the client needs to sign off that stage, because the information delivered becomes the basis for the next stage.
Building handover at completion. The same RIBA document explains that Stage 5 runs from the contractor taking possession of the site to Practical Completion, and Stage 6 starts with the handover of the building to the client. Handover activities set out in the Plan for Use Strategy may begin during Stage 5. The RIBA Plan of Work template adds that there is no design work in Stage 5 other than responding to site queries, so anything the contractor needs must be in the package before construction starts.
The IStructE Structural Plan of Work 2020 describes the end of its Stage 5 in similar terms: Practical Completion and handover from the construction team to the client, typically with the Health and Safety File information and handover documentation.
One caution on contracts. The RIBA Plan of Work is not a contractual document. It defines outcomes for each stage but not who must deliver them, so your appointment documents have to say who hands over what, and when.

Where design responsibility changes hands
The most sensitive transfer for engineers is the point where design responsibility moves, for example from a client’s designer to a design-and-build contractor. Contracts set this point explicitly, and the transition period can end at a defined RIBA stage. Whatever the contract says, treat the moment of transfer as a formal issue: a dated, revisioned package, not a conversation.
What a handover package should contain
The package depends on the stage. A Stage 3 to Stage 4 handover is mostly drawings, calculations and coordination information. A completion handover is mostly records and manuals. Across both, a few elements keep recurring.
For completion, the IStructE guidance says handover documentation typically requires the Health and Safety File information. It may also include the Building Manual, asset information (such as a schedule of design life of elements and life to first maintenance), design loading drawings for the finished structure and information on how the structure was designed for demolition.
For handover into construction, the CDM 2015 guidance on pre-construction information is a useful model. Pre-construction information should include existing information as well as design information for construction. It should identify unusual remaining risks, list key assumptions and decisions made and clarify sequencing requirements. Those four items are exactly what a receiving engineer or contractor wants and rarely gets.
| Package element | What it should state | Typical owner |
|---|---|---|
| Issue register | Every drawing, calculation and specification with revision and status | Sender’s document controller |
| Design basis | Codes, loads, materials, ground assumptions, Eurocode parts and National Annexes used | Lead designer |
| Calculations | Review-ready, indexed, cross-referenced to drawings | Designing engineer, checked by a second engineer |
| Drawings and models | Current revision, with CAD or BIM files in the agreed format | Technician or BIM coordinator |
| Residual risks | Hazards that design could not remove, and how they are to be managed | Designer, collated by the Principal Designer |
| Open items | What is not yet resolved and who owns each item | Project lead |
| Sequencing constraints | Temporary stability, propping, loading restrictions | Designer, with the temporary works coordinator |
If the project works to ISO 19650, tie the package to the information requirements set in the BIM Execution Plan. Our note on ISO 19650 BIM execution plans for UK projects covers how that agreement keeps file formats and naming from becoming a handover argument.
Who prepares, checks and accepts
Handover fails when everyone assumes someone else is responsible. Assign three roles explicitly.
- Sender. The lead designer or project engineer who assembles the package and signs the issue. On a CDM project, the Principal Designer compiles the health and safety file at completion and hands it to the client, according to the CDM 2015 guidance summarised in the IStructE and CITB material.
- Reviewer. A named person on the receiving side who can interpret the package. Complys is not needed here; the principle is simple: the receiving principal contractor or contractor should name a reviewer with the competence to understand the design assumptions, plan construction methods and manage residual hazards.
- Acceptor. The person with authority to say the package is adequate for the next stage, often the project manager or client’s representative.
The CITB guidance notes that the principal contractor may raise questions and may identify ambiguous or missing information, and that the Principal Designer must respond, either directly or by going back to the client or the designers. Build that response loop into your programme. A handover with no time allowed for queries is a handover that will be reopened on site.
A practical handover process, step by step
- Agree the handover points early. The Get It Right Initiative recommends a project-specific plan of work for each discipline before any design starts, so everyone knows what is passed on and when. Put the gateways in the programme.
- Freeze the issue. Choose a cut-off. Anything produced after it goes into the next revision, not into the package by stealth.
- Run an internal check. A second engineer confirms that calculations match drawings, that loads on the drawings match loads in the calculations, and that the model matches the 2D sheets.
- Compile the package against the template. Use the issue register, design basis, risk and open-items list from the table above. Use a standard matrix where one exists for your discipline, which helps prevent gaps or duplication.
- Write a cover note. One page: what is issued, what has changed since the last issue, assumptions, residual risks, open items and who to call.
- Hold a walkthrough. Thirty to sixty minutes with the receiving team, screen shared, drawings open. This is where misunderstandings surface cheaply.
- Record acceptance. The acceptor signs off, or lists conditions. File the signed record with the package.
- Open the query channel. Nominate one inbox or log for questions and log every answer against the relevant drawing.
How to check a handover is complete and understood
Completeness is about content. Understanding is about people. You need both checks.
The Get It Right Initiative states that great care is needed at design gateways so the information communicated is clear, accurate and suited to its audience. It also says a design review workshop with those receiving the information, including the supply chain, helps the “passing of the baton” and helps define outstanding work for designers. That workshop is the step most teams skip, and the one that most often prevents rework.

Learning from gate reviews on large projects
Large programmes formalise this. Crossrail’s Design Gates Process subjected all designs to a three-stage review, at roughly 20%, 60% and 100% design completion (Issue for Construction). The gates were not a direct review of the design itself but a review of evidence of progress, completion and assurance activity. Teams presented evidence against twelve criteria, including coordination, constructability, design for safety, management of risks and conformance to standards.
You do not need twelve criteria on a two-storey extension. You can borrow the idea, though: ask for evidence, not reassurance. A short checklist of five or six criteria (requirements met, standards followed, coordination done, risks recorded, constructability reviewed, open items owned) applied at each handover gives the same discipline at a fraction of the effort.
Design change control after handover
Once a design is handed over, it will still change. Site conditions, client requests and supply issues all see to that. Change control is what stops those changes from eroding the design.
RICS guidance on change control and management defines change control as the process that can lead to altering the timescale, cost or scope of the project. When a change is proposed, the responsible person should identify the reason, investigate impacts on costs, timescales and locations, mitigate risks and maximise opportunities, then review and accept or reject it.
The Scottish Government’s change control guidance adds useful practice that applies well beyond public projects. A change request can come from anyone on the project, but it should enter through a single point, usually the project manager, on a Change Request Form. It should never go straight to the contractor without passing through the control process.
A workable engineering version looks like this:
- Raise. Anyone submits the request with the reason and the affected drawings or calculations.
- Assess. The designer checks structural, civil and coordination effects. The cost and programme effect is assessed alongside.
- Decide. The authorised person approves, rejects or defers. Delegated authority levels should already be defined in the project execution plan.
- Implement. Calculations, drawings, models and specifications are revised and reissued with new revision codes.
- Close. The register is updated and the change is communicated to everyone who needs to know.
The design change order process: record, authorise, track
A change order is the paperwork that turns an approved change into an instruction. RICS says a change management process should register each change on a suitable register with a discrete number, distribute and file copies of the documents, include change board minutes, and follow up to ensure every affected drawing and specification is updated and reissued. It also notes that variations should generally be agreed before any final account is settled.
The Scottish Government guidance lists the documents to maintain: a document control register, a Change Request Form, a Change Control Register, and a cost plan and programme recording the effect of changes. In practice:
- Give every change a unique number that appears on the request, the order, the revised drawings and the cost record.
- Record who approved it and under what delegated authority.
- Never issue a revised drawing without a revision note that cites the change number.
- Review the register at each project meeting so that nothing stays pending without an owner.
This is also where document control earns its keep. If you are short of people to maintain registers and revision histories, see how we approach engineering document control with embedded remote engineers.
Higher-risk buildings: stricter change rules
In England, higher-risk buildings carry stronger obligations. CIBSE Journal notes that supporting documents under the Building Regulations (Higher-Risk Building Procedures) (England) 2023 include a change control plan, and that a rigorous process must be followed for changes to the approved design on site. Major changes need reapproval by the Building Safety Regulator, and previously approved documents must be updated as part of the golden thread so design decisions stay traceable. If your project falls in this category, build that traceability into the package from the first issue rather than retrofitting it.
Common handover failures and how to avoid them
- Unstated assumptions. The receiving engineer designs against a ground condition or load that the sender never confirmed. Fix: a design basis page in every package.
- Drawings and calculations out of step. Fix: the internal cross-check before issue.
- No named reviewer. Questions sit unanswered. Fix: name one person per side.
- Changes made verbally on site. Fix: one entry point and a register.
- Models and PDFs disagree. Fix: issue both from the same revision and say so in the cover note. Our comparison of 2D CAD and BIM explains how that choice affects what you hand over.
- Temporary works forgotten. Sequencing constraints belong in the package. See our guidance on temporary works coordination under BS 5975.
Perspective: what we see from the engineering desk
We work as embedded remote engineers inside UK consultancies, so we see handovers from both sides: the package we receive and the package we return.
Our view is that most handover problems are capacity problems in disguise. The senior engineer who should be writing the cover note, cross-checking the calculations against the drawings and running the walkthrough is also finishing another job. The handover is rushed, and the rework appears three weeks later.
That is why we build review-ready outputs: indexed calculations aligned to UK standards and Eurocodes, drawings and models issued from the same revision, and a clear list of assumptions and open items. Your team keeps the client relationship and the sign-off. We take on the preparation and the checking workload that makes a clean handover possible, with NDA protection and a project kick-off within 48 hours.
Used this way, outsourced capacity does not dilute responsibility. It gives your lead engineer the time to do the part of handover that only they can do.
Mohammed
Get handover-ready packages without hiring
If your team is stretched at the point where designs must be issued, our remote engineering support embeds qualified civil and structural engineers in your workflow. They prepare calculations, drawings and BIM coordination, and they assemble review-ready packages aligned to UK standards and Eurocodes. You retain the client relationship throughout.

For a sense of how this works in practice, read how we handle calculation and drawing support through review or structural drawing and calculation coordination. To discuss capacity for your next issue, start from our home page.
FAQ
What is the difference between design handover and design handoff?
They describe the same idea of passing a design to the next party. “Handoff” is common in software and UX, while UK construction usually says handover, tied to stage gateways and to completion. In engineering the package also carries calculations, risks and records, not only drawings.
When should a design handover take place?
At the end of each project stage, when the information needed for client sign-off has been captured, and again at Practical Completion, when the building passes to the client. Under the RIBA Plan of Work 2020, building handover tasks bridge Stages 5 and 6. Any point where design responsibility moves between organisations should also be treated as a formal handover.
Who is responsible for the health and safety file at handover?
Under CDM 2015, the Principal Designer compiles the health and safety file at project completion and hands it to the client, according to the guidance summarised by the IStructE. Designers must supply the information it needs, so agree early what each party will contribute.
What should a design change request include?
The reason for the change, the drawings and calculations affected, an assessment of cost, time and location impacts, and the approver. Submit it through a single entry point such as the project manager. It should be numbered, entered on the change register and closed only when affected documents are reissued.
Can outsourced engineers prepare a handover package?
Yes, provided the brief names the package contents, the standards and the reviewer. Embedded engineers can prepare calculations, drawings and models and compile the issue register, while your lead engineer signs off and presents the package to the receiving team.
Sources
- RIBA Plan of Work 2020 Overview
- RIBA Plan of Work 2020 Template
- IStructE Structural Plan of Work 2020: Overview and Guidance
- CITB CDM 2015: Principal designers
- Get It Right Initiative: Design gateways
- Crossrail Learning Legacy: Design Gates Process
- RICS: Change control and management
- Scottish Government: Change control in construction projects
- CIBSE Journal: The narrow gate, gaining design approval for higher-risk buildings


Leave a Reply