In a firm of one, a sloppy record is recoverable, because the person who captured it is the person writing it up and the gaps get filled from memory.
The moment there are three of you, that stops being true. The grad writes up the director's walk. The senior reviews something a junior captured in the rain. Someone is on leave and their job still has to go out on Thursday. At that point the record has to carry itself, and most records cannot.
This is what makes the difference.
1. Say who you are, once
Thirty seconds of context at the start of the capture, before you start walking, is worth more than anything else on this list.
Jimmy, Tuesday morning, number 14 Curzon Street. Pre-purchase walk for the buyer's solicitor. Main concern is the rear extension, the agent mentioned movement. Weather is dry, has been for about a week.
Whoever picks this up now knows the job, the audience, the brief, and the weather, which they would otherwise have to guess at or ask you about.
The weather line matters more than it looks. Half the interpretation of damp depends on it, and the person at the desk has no idea what it was doing on site.
2. Say what you are unsure about
The single most useful sentence to a reviewer is the one that flags your own uncertainty.
I am not confident about this one. It reads like historic movement to me but I would want someone to look at the render on the return before we commit to that.
A junior who does this is doing the job correctly, not admitting weakness. A record that surfaces its soft spots lets a reviewer spend their attention where it is needed instead of re-checking everything at equal weight.
Firms that punish this get records that sound confident and are not, which is the expensive failure.
3. Separate the observation from the conclusion
When one person captures and another writes, this is where it goes wrong most often.
Staining to the ceiling, roughly a metre across, darker at the edges. My read is the shower above rather than the roof, because the roof was redone last year.
Observation, then interpretation, then the reason for the interpretation. Now the writer can keep your conclusion, or overrule it, and either way they know what you actually saw. If you only say “shower leak above”, they have to take it or discard it whole.
4. Name the deliverable as you go
Say out loud which output each finding belongs to.
That is one for the schedule, not the report.
This does not go to the client, it is a note for our file.
Nobody else can infer this reliably, and getting it wrong in either direction is bad. Internal caveats leaking into a client report is the kind of mistake that costs a relationship.
5. Do not go quiet on the interesting part
The most common failure in team handover is also the most human one. You find the thing that matters, you get absorbed in looking at it, and you stop narrating for ninety seconds.
The person writing it up gets ninety seconds of silent footage of the one defect that carries the job.
If you notice yourself concentrating, that is the cue to start talking.
6. Close with the shape of the write-up
Before you get in the car:
Three actions. Ceiling in the main bathroom, the gate post, and the smoke seal on the riser door. Everything else is fair wear.
You have just given the writer their structure and a checkable count. If they end up with five actions, one of you has misread something, and they will know to come back and ask.
The one that quietly breaks it
Adding context in a separate place.
The email you send afterwards, the note in the job management system, the thing you said in the corridor. All of it is real context and none of it is attached to the walk. Six months later the capture and the commentary have drifted into different systems, and the record no longer explains itself.
If it belongs to the walk, say it during the walk. That is the whole rule.
Where the tooling helps
Handover is the case that made us treat the footage and the narration as one object rather than two files. What the reviewer gets is a structured summary with action items where every line traces back to the exact frame and the words behind it, so checking a junior's read takes seconds rather than a second pass of the whole walk. It stays searchable later, which is what makes an archived job useful to whoever inherits it.
The draft is never sign-ready. The reviewer reads it, corrects it, and signs it, and stays the author of record.
But the habits above are worth adopting before any of that. They are what turn a capture into something a colleague can actually use.

