Journal/Playbook

The register you hand over is the one you kept

An Excel export, 2,300 photos named IMG_4471 onwards and an inspection PDF that references neither. The handover pack goes wrong because it is assembled. If the register during the build was the register, handover is a filter and a print button.

A two-colour risograph poster of a fanned stack of report sheets in section, one sheet pulled out with its edge in orange, a line-drawn key ring beside it
WP
Will PrinmanCo-founder
14 October 2026·6 min read

Handover on a sixty-unit building. The client's representative wants the defect register. What she gets is an Excel file exported on the Thursday, a folder of 2,300 photos named IMG4471 to IMG6770, and a PDF of the pre-completion inspection with green ticks and red crosses that does not reference the Excel file at all.

She asks a reasonable question: for the twelve items still open on level 9, which photo is which, and who said they were still open. The site manager, who knows the answer to all twelve, is on another job by the following Monday.

The handover register is not a document you produce. It is the register you kept, printed.

That is the whole argument, and I will spend the rest of this post on why it is harder than it sounds.

The handover pack goes wrong because it is assembled. Somebody sits down in the last week and builds a document out of parts that were never connected: the spreadsheet that lived on the site manager's laptop, the photos that lived on three phones, the inspection that lived in a checklist app, the emails to trades that lived in Outlook. Assembly is where the twelve items on level 9 lose their photos, because the photos were only ever connected to the rows in one person's memory.

If the register during the build was the register, with the photo on the defect, the inspection raising the defect, the email on the defect's trail, then the handover pack is a filter and a print button. Nothing is assembled, so nothing is lost in assembly.

What the client actually needs, in order

Not the whole register. The whole register is yours. The client needs four things, and they want them at four different levels of detail, which is why one export never satisfies anyone.

A count they can trust. Open, ready to inspect, closed, by level. If their count and yours differ by nine, the handover meeting is about the nine and nothing else.

A per-unit view. The purchaser of 9.07 does not care about the building. They care about the three things in 9.07, with photos, in language that does not say "backcharge".

The evidence behind each closed item. Not for every item, but for any item they choose to ask about. Before photo, after photo, who verified it, when.

And the open list, as a live thing, because the twelve items on level 9 are not finished at handover and the client is about to inherit chasing them.

Four reports from one register

In IssuesId these are four reports off the same data, and the point of saying so is that they cannot disagree with each other.

The Executive Summary is the count: project health and numbers, for the handover meeting and the steering committee. The Door Sheet is one page per location, which is the walk-through and the per-room sign-off; you print level 9 and walk it with the client's rep, ticking rooms. The Purchaser Report is one page per defect with photos, written for the purchaser rather than the trade, which is the pack 9.07's buyer gets at settlement. And the Client Defect Summary is the client's own view, client-worded, respecting whatever visibility the project gives clients, which they can generate themselves from their own login without asking you.

Behind all four, Internal Detailed is the version you keep: every note, every photo, every drawing, every email. You do not send it. You have it, for the day a tribunal asks.

Every one of these is composed the same way. Pick the report, pick the scope, narrow it, and the match count tells you how many defects you are about to print before you print them. Which means the nine-item argument is over before the meeting, because both of you can see where the nine went: closed on Thursday, after her export.

The photos are on the defects, or they are nowhere

This is the part that has to be true during the build for any of the above to work at handover, and it is the part most teams skip.

A photo taken on a phone and uploaded later to a folder is not evidence of anything in particular. The same photo taken against the defect, in the room, with its original device timestamp kept and a pin on the fault, is the defect. When the trade marks their work complete they have to attach a photo of the finished work, so every closed item carries its before and its after without anyone collecting them. How do you prove a defect was fixed is the longer version of that.

Photo-heavy report layouts stop at twenty photos per defect. We put that cap in on purpose. Past twenty, nobody reads the report, including the person who asked for it.

The inspection that raised the defect is on the defect too

The pre-completion inspection in the story above was a PDF of ticks and crosses that did not reference the register. Thirty-one crosses on level 9, typed into the register on a Thursday night by a tired site manager, two of which never made it. An inspection that cannot raise a defect is a form is the whole post about that.

In IssuesId a No on a checklist raises the defect and links it to the question. When the defect closes, the question flips back to Yes on its own. So at handover the inspection and the register agree, because they are the same thing viewed twice, and the client's rep can go from "the inspection failed the shower screen in 9.07" to the defect, its trade, its photos and its close-out in two clicks instead of a search of a photo folder.

Handover is a change of role, not a change of system

The twelve open items on level 9 do not disappear at handover. Somebody has to chase them for the next twelve months, and in most buildings that somebody is now the owners corporation or a facilities manager with a different spreadsheet.

The alternative is to leave the register where it is and change who is in it. The committee or the FM takes the client seat. Residents get a QR card at handover that logs them into their own portal, so the dripping mixer in month three arrives as a record against 9.07 rather than an email to the info@ inbox. The builder's trades keep receiving work the way they did during the build, by email link, no login. The owner's side closes; the trade never could. Who is responsible for defects after practical completion sets out who holds what once the keys change hands.

The honest list

The pack described here is what we produce. The thing it depends on is boring and happens eleven months earlier: that the register during the build was the register, photos on the defects, inspections raising them, emails on the trail. Get that right and handover is a Friday afternoon. Get it wrong and no report template in the world will find the twelve photos on level 9.

If you are still assembling, the defect register template carries the columns the client will ask about, and the anatomy of the report itself is at what should a construction defect report include.

IssuesId