Your Client Already Told You Exactly What the Job Is. You Just Lost It on the Way Home.

Why the site walkthrough is the most underused document in construction — and what to do about it.

— -

Here’s something I’ve seen happen on job after job, and I’d bet you’ve lived through it yourself.

You do a walkthrough. An hour, maybe ninety minutes. The client walks you through every room, points at things, tells you what she wants. It’s a great conversation — she’s been thinking about this for two years and she has opinions about everything. You take notes, you take photos, you get the full picture.

You drive home. You record a quick voice memo in the car to capture the stuff that wasn’t in the notes.

Three or four days later — because that’s when you can actually sit down and write the estimate — you open the notepad, pull up the photos, hit play on the voice memo, and start trying to reconstruct what was actually decided in that walkthrough.

And that’s when it falls apart a little.

Not catastrophically. Just… a little. You’re not sure which window wall she meant for the vanity. You don’t remember whether the kitchen island conversation was in scope or a “we’ll talk about it later.” The niche light — was that a recessed fixture or a puck light? You think recessed, but you’re not positive.

So you make calls. Reasonable ones. You’ve been doing this long enough to fill in the gaps.

And then three weeks later she calls and asks why the island isn’t in the proposal.

— -

## The Thing Nobody Names

The problem isn’t that you forgot. The problem is that the walkthrough was never captured in a format that could be used.

Think about what a walkthrough actually is. It’s the single most information-dense moment in the entire project lifecycle. The client is standing in the room, pointing at the exact thing she’s talking about, with full context, full intent, and two years of pent-up specificity. Everything that matters about the scope — every finish, every layout decision, every “keep this, move that, I definitely don’t want X” — comes out in that conversation.

And then you write it down in observation order on a yellow notepad.

Which means you later have to convert it from “what I saw, roughly in the order I walked the rooms” into “what this job actually costs, organized by trade and quantity.” That conversion is reconstruction work. It’s not estimating. It’s archaeology.

The estimate doesn’t take long because pricing is hard. It takes long because you’re rebuilding the scope from incomplete notes before you can price a single thing.

— -

## What the Notes Actually Capture

Let me show you the gap with one sentence.

Client says: ”I want a frameless walk-in shower, floor-to-ceiling tile, and a niche with a light in it.”

What goes in the notes: frameless shower, floor to ceiling, niche w/ light

What that sentence actually contains:

1. Frameless glass enclosure — spec and size TBD

2. Floor tile — SF calculation needed

3. Wall tile — 3 walls, floor to ceiling, SF calculation needed

4. Shower niche — location, size, waterproofing

5. Electrical rough-in for a recessed fixture in a wet-rated area

Five line items in one sentence. The note captured the concept. The estimate needs the items.

This isn’t a note-taking problem. You can’t write five line items in real time while she’s already moved on to the next thing. The walkthrough moves fast. That’s fine. That’s how it should work.

The problem is what happens to that information between the walkthrough and the estimate. It lives in a format — casual notes, photos, voice memos — that requires reconstruction before it can be used. And reconstruction takes time, introduces error, and creates the gaps that turn into change orders later.

— -

## The Flag Problem Is Bigger Than the Line Item Problem

Here’s what actually costs money: not the items you got wrong, but the items that were ambiguous and you didn’t know it.

The niche light — you priced it as a puck light because that’s what most people want, and you weren’t sure. She had a recessed fixture in mind. Different rough-in. Different coordination with the electrician. Not a huge deal on its own, but it’s a conversation you have mid-job instead of before the contract.

The kitchen island — you noted it as “client may want to revisit.” Accurate. But when she calls asking why it’s not in the proposal, you’re now having a scope conversation with a client who signed three weeks ago and assumed it was included. That conversation is harder than it needed to be.

The hall bathroom layout — you’re pretty sure she said keep it as-is. But she might have said that as a question, not a decision. If the toilet moves later, that’s a plumbing relo that wasn’t in the estimate.

Every one of these is a flag — something that came up in the walkthrough but wasn’t resolved enough to price with confidence. The problem isn’t that flags exist. Every job has them. The problem is that most of them aren’t identified as flags until the estimator is sitting at a desk trying to price something he’s not sure about.

The walkthrough is when the client is most available to answer these questions. She’s in the room. She’s engaged. She’ll give you a clean answer in thirty seconds. By the time you’re writing the estimate four days later, getting that answer requires a call, a wait, an email thread.

— -

## What Happens When You Treat the Recording as the Document

Here’s the shift that changes things.

Instead of treating the walkthrough as a source of notes to be converted later, treat the recording of the walkthrough as the primary document — and process it into line items before you start estimating.

A forty-five-minute walkthrough recording, processed systematically, produces:

• Every finish specification she mentioned, organized by room and trade

• Every layout decision — what moves, what stays, what gets demolished

• Every scope boundary — what’s in, what’s explicitly out, what’s “we’ll talk about it”

• A list of flagged items: things that came up but weren’t fully resolved, each with a specific question that needs a quick client answer before the estimate is final

That last one is the piece most estimators don’t have. Not “I’m not sure about the niche light” as a vague feeling — but “client mentioned recessed fixture in niche, wet-rated application — confirm fixture type and switch location before pricing electrical.”

Specific flag. Specific question. One quick call and it’s resolved before the proposal goes out.

The estimate you send at the end of that process is cleaner than anything built from notes. Every scope boundary is documented. Every ambiguity either resolved or explicitly flagged. The client reads it and feels understood — because everything she said in that walkthrough is reflected in what you sent back.

— -

## The Practical Version

You don’t need a new system for this. You need one habit change.

Record the walkthrough. Not just a voice memo in the car — the actual conversation, in the room, while she’s talking. Most phones do this. Most clients are fine with it when you tell them it’s so you don’t miss anything.

That recording is your document. Process it — or have it processed — into line items before you open the estimating template. Every item she mentioned becomes a line item or a flag. Every flag gets a specific question written next to it.

Then price from the line items. Not from the notes. Not from memory. From a structured document that was built from the actual conversation.

You’ll spend less time reconstructing. You’ll write cleaner proposals. You’ll have fewer “why isn’t X in the estimate” calls. And you’ll catch the ambiguities while they’re still cheap to resolve — before the contract, not after.

The scope was in that conversation the whole time. That’s where it lives. Treat the recording like the document it already is.

— -

• *TIM processes recorded walkthroughs, client calls, and voice memos into structured takeoffs — line items organized by trade, flags on every ambiguity, ready to price.*