Part of How to Run a Remote Construction Walkthrough — Remote stakeholder walkthroughs

Capturing a Decision Made on a Walkthrough

The most expensive sentence on a jobsite is "we agreed to that on the walkthrough." Make the agreement survive the walk.

Walkthroughs generate decisions. Somebody looks at a wall, says move it six inches, and everyone nods. Six weeks later there is a disagreement about whether that conversation happened, what exactly was agreed, and who was going to pay for it.

The walkthrough was recorded. That helps less than people assume, because a decision buried at minute thirty-one of a ninety-minute video is not findable by anyone who was not there.

Recording is not capture

A recording is evidence a decision happened. It is not a record of the decision.

The gap matters. Nobody scrubs an hour and a half of footage to settle a question about a doorway. They ask the person who was there, who remembers it slightly differently from the other person who was there, and now you are back to memory — with a video file nobody watched sitting in the folder.

Capture means: the decision exists somewhere findable, in words, with the walkthrough as backup. Both halves. The recording without the note is unfindable. The note without the recording is one party's account.

Say it out loud, on the walk

The cheapest habit in this whole article: when a decision gets made, mark it verbally, in the moment.

"Okay — decision: the outlet moves to the north wall, next to the door. That's a change from the drawing." Ten seconds. Now the recording has an audible marker, the timestamp is findable, and — the part that matters most — everyone standing there just heard the decision stated back and had a chance to say no.

Half the disputes I have seen were not about what was decided. They were about two people leaving a conversation with different understandings of it, neither aware of the mismatch. Saying it back out loud kills that at the source, before it becomes a change order.

Name who decided, too. "Owner's call, confirmed on the walk." Six weeks later, the question is usually who authorized it, not what it was.

The note that goes out within the hour

Immediately afterward, while the walk is fresh: a short list.

  • What was decided, in one sentence per item
  • Who made the call
  • Where it sits in the recording — roughly the time, and which area
  • What happens next, and who owns it

Send it to everyone who was on the walk, including the people who joined remotely, and ask them to correct anything wrong. Silence after a written summary is worth vastly more than agreement remembered from a conversation. A correction that arrives the same afternoon costs nothing; the same correction six weeks later is a change order and an argument.

That list is also what makes the recording usable. With it, the video becomes a searchable archive — you know what you are looking for and roughly where. Without it, the file is an unindexed hour.

Remote attendance makes this better, not worse

The reflex is to assume a decision is weaker when half the parties were on a phone. In practice it is usually stronger.

People joining remotely tend to ask more explicit questions, because they cannot lean over and point. That forces the decision to be stated in words rather than gestures — and words are what survive. A walkthrough where the owner, architect, and sub are all on one feed tends to produce cleaner decisions than one where three people nod at a wall.

It also means the decision is witnessed by everyone at once, rather than relayed afterward by whoever was on site. Relay is where most of the drift happens.

The same discipline that runs a punch list live and closes it at the wall applies to any decision on any walk: state it, agree it in the moment, write it down the same day.

Keep the record where it stays reachable and access is controlled rather than forwarded around — that is the security page — and the walkthrough stops being an event people remember differently and starts being a document.

InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.

More in this series

Part 4 · August 19, 2026 · 5 min read

Run the Punch List Live and Close It at the Wall

Punch does not eat schedule because the items are hard. It eats schedule because the dispute loop runs through email. Run the disposition pass live instead.

Part 6 · September 23, 2026 · 4 min read

Walking a Change Order Live

Rot behind the sheathing, an owner two hours away, a crew standing still. Run the walk live, show the condition, and get the yes on the recording.

Other topics

Show someone the inspection instead of describing it.

Fifteen minutes, a phone and a real site. That is the whole demonstration.