AI for Small Business

Architecture Project Handover Documentation: What to Include and How to Present It

Updated on November 18, 2026
8 min read

Architecture project handover documentation is the set of records and guides that lets a client run, maintain and insure the building you designed. Most of it comes from other people, so the studio's real job is to collect it, check it and present it in an order the client can follow.

TL;DR: A handover pack has three layers: a short user guide for the people who occupy the building, a quick-start page for whoever manages it, and the full operation and maintenance (O&M) file underneath. The contractor supplies most of the content (as-built information, manuals, warranties, certificates), and the studio checks it and sets the structure. Start collecting at the beginning of construction, not at Practical Completion. AI can read the incoming files and draft the client-facing pages, and DocsAura, an AI document design tool, turns the finished DOCX or PDF into a designed page in about two minutes.

Architecture Project Handover Documentation: What the Pack Contains

Handover is the point where responsibility for the building moves to the client. In the RIBA Plan of Work 2020, the Building Manual, including the Health and Safety File and Fire Safety Information, is a Stage 5 information exchange, and handover and close-out follow it as Stage 6.^1 In the US, the contractor's obligations sit in the AIA A201-2017 General Conditions: Section 3.11 requires the contractor to keep an updated set of documents recording the work as constructed.^2

Across both systems, a pack usually holds these items:

The studio does not write most of this. The RIBA Plan for Use Guide says the contractor holds primary responsibility for assembling the as-built information, while under the UK's CDM regulations the client and designers must make sure it is in place and fit for purpose.^3 The AIA's own guidance makes the same split visible: A201 puts record documents with the contractor, and B101-2017 lets an architect offer as-constructed record drawings only as a supplemental service, built from the contractor's mark-ups, with the architect not responsible for their accuracy or completeness.^2 Check which side of that line your agreement puts you on before you promise anything.

Who Supplies What

Item Usually comes from Studio's role
Record drawings Contractor mark-ups (or a paid supplemental service) Check against the design, flag gaps
O&M manuals, warranties Contractor and subcontractors Check completeness and order
Test and commissioning certificates Installers, engineers, inspectors Check they exist and match the installed systems
Health and safety and fire information Principal contractor and designers Confirm it is in the pack
User guide and quick-start page Studio Write and design
Cover summary and index Studio Write and design

The last two rows belong to you, and they decide whether the client uses the rest.

Give the Client Three Layers, Not One Binder

The RIBA Plan for Use Guide warns against daunting the people who manage a new building with a heavy Building Manual and recommends prioritising information into three elements: a simple User Guide for every occupant interface in the building, a quick-start guide for building managers that can double as an emergency services grab pack (meter locations, emergency shut-offs, an overview of the whole building), and the detailed, well-indexed O&M Guide that sits below the surface for reference.^3

That structure works for a house as well as an office. For a residential client, the user guide covers heating controls, the boiler, ventilation and the hot-water tank. The quick-start page names the stopcock, the consumer unit and the gas isolation valve. The O&M file stays in the cloud folder and rarely gets opened.

The Engine Shed, a building conservation centre for Historic Environment Scotland, shows the user layer at work. The team produced a graphical building user guide with face-to-face training and training films. The guide sits beside the O&M manuals and summarises what affects day-to-day running, and staff feedback on it was positive.^3

The user guide and quick-start page are the two documents a studio writes itself, and they are the ones a client might still read three years later.

Start Collecting Before Practical Completion

Time is where handover gets expensive. The Plan for Use Guide says that where a component's make or type has been named, information for the Building Manual should be compiled at the beginning of Stage 5 or even earlier and issued in draft, and that the Log Book required under the Building Regulations can be developed from Stage 1 as a running summary of the design intent for building services. It also notes that much time is wasted extracting as-built information from subcontractors.^3

A workable routine:

  1. Write the requirements into the tender and specification. State what each trade must supply, in what format, and by when.
  2. Keep a handover tracker from the first site meeting. One row per item: who owes it, when it was promised, whether it arrived.
  3. Check each item as it arrives. Does the warranty name the right product and address? Does the certificate match what was installed?
  4. Draft the user guide and quick-start page while the building is still a site. Update them when the services are commissioned.
  5. Schedule training before and after handover. The Plan for Use Guide recommends sessions on both sides of handover and suggests filming training, even on a phone, to cope with absenteeism and information overload.^3
  6. Review the asset schedule before the end of the Defects Liability Period. The client needs to know every listed system is in good order and has a service contract.^3

The last item prevents a common muddle. The Plan for Use Guide observes that many clients fail to distinguish between operation (owner or occupier), defects (the main contractor), routine maintenance (maintenance contractors) and Aftercare, where unexpected issues can fall between the first three.^3 A one-page responsibilities table in the pack answers the question the client will ask at the first problem: who do I call?

For the site-visit side of this routine, see our guide on how to write an architect site visit report clients understand. The care instructions that follow handover are covered in how to use AI to create aftercare instructions.

What we found when we read 3 handover guides

We read three public handover guides, two written for architects (Layer's architect handoff guide and Planman's guide to handover problems) and one for interior designers (The Little Design Corner's client handover folder), and tallied what each covers. Two of the three list as-built or record drawings. Two of the three tell the reader to prepare the pack early rather than at completion. None of the three gives the client a plain-language summary page or index, and none mentions AI. A fourth guide could not be read because its page did not load without a browser, so it is left out of the count. The gap is the front of the pack: every guide lists what to collect, and none says how to present it.

Where AI Helps With Handover Documents

AI earns its place on the reading and drafting around the pack. The drawings, the O&M content and the certificates come from specialists, and nothing in this workflow changes that.

Review every output. A wrong shut-off location in a quick-start page is a safety issue. Handover files also hold client contact details, access arrangements and security information, so sort them before uploading anything: our guide on whether it is safe to upload architecture client documents to AI sorts studio paperwork into green, amber and red.

Present the Front of the Pack

The cover summary, user guide and quick-start page are the pages the client reads, so they should look as good as the building. A studio that spends weeks on a stair detail can easily lose its last evening to formatting a Word document into something presentable. Time is the problem here, because the design sense is already in the studio.

DocsAura, an AI document design tool, takes a DOCX or PDF you already wrote and returns a designed HTML page you can export or share by link. It does not produce drawings and does not connect to CAD or BIM software. Once the text is final, the designed version of the user guide, quick-start page and cover summary takes about two minutes, and the O&M file stays as the contractor delivered it.

Try It on One Document You Already Have

Pick one handover-style page you have written, such as a heating guide, a maintenance schedule or a contacts list. Drop it into DocsAura, the AI document design tool, with no setup and nothing to install, and read what comes back in about two minutes. If the page suits your next handover, keep it. If not, you have lost two minutes.

Turn voice notes and screenshots into beautiful documents.

Status updates, proposals, case studies, SOPs — generated in minutes, not hours.

Try DocsAura Free
Published on November 18, 2026.
Dominik Szafrański
Dominik Szafrański
Founder

After years of freelancer and agency work—spending countless hours on proposals, case studies, and client documentation—Dominik decided to build a tool that helps agencies and freelancers create professional client documents in minutes, not hours.