Estimating

You Walked the Site on Tuesday. You're Writing the Estimate on Sunday.

The walkthrough is the single best moment in the estimating process. The owner is on-site, conditions are visible, every relevant detail exists in one place. Five days later, none of those inputs are as good as they were.

TIM Editorial·June 2026·7 min read

It is Sunday afternoon. He has 47 photos from Tuesday's walkthrough open on his laptop — taken in the order that made sense at the time, which is not the order that makes sense for building an estimate. He has a voice memo from the drive back. He has a page and a half from the yellow notepad he keeps in his truck.

He is trying to build a $140,000 proposal from these materials.

The kitchen notes are solid. He spent most of the walkthrough there, and the scope is clear in his head. The primary bath is thinner. He remembers the tile was going to be large format, but looking at the photos he cannot tell if it was 24x24 or 24x48 — and it matters, because the waste factor is different and the layout pattern the client described works differently at each size. He remembers the client mentioned something about the shower valve, but he is not sure if she wanted to replace the full valve or just the trim kit. That is a $400 difference in materials and about two hours of plumber time.

He makes a call on both. He goes with 24x24. He prices the trim kit. He moves on.

He will not find out he guessed wrong until week six, when the tile order comes in and the foreman calls to say the layout is off.

The Moment When All the Right Information Exists

The walkthrough is the single best moment in the entire estimating process. The owner is on-site. The conditions are visible. The client is present to answer questions. Every relevant detail about the project — substrate condition, existing rough-in locations, scope boundaries, material preferences, site access constraints — exists in one place at one time.

Five days later, none of those inputs are as good as they were on Tuesday.

Memory decays and competes with everything that has happened since — two site visits, a subcontractor call, a client dispute on a different job, an unexpected material delivery, a Thursday evening finishing last week's estimate. Photos capture what the phone was pointed at, not what needs to be priced. The voice memo requires replaying twenty minutes of audio to find the forty-five seconds about the mudroom. The yellow notepad has shorthand that made sense on Tuesday and requires interpretation by Sunday.

The estimate gets built anyway. It goes out. It is usually close enough to win jobs. And it contains, on average, six to eight assumptions that were guesses rather than recorded facts — each one a future cost variance waiting for a specific moment in the project to reveal itself.

What Specifically Gets Lost in the Gap

The categories where the walkthrough-to-estimate gap causes the most problems are consistent across the businesses where it happens.

Four categories that consistently surface problems:

  • Substrate and condition notes. The owner walked the subfloor in the second bathroom. It felt soft in one corner — not soft enough to flag immediately, but something to account for in demo and prep pricing. Not in the notes because he was mid-conversation with the client when he felt it. The estimate includes standard prep. The subfloor condition shows up in week two when the tile setter calls to say there is a problem.
  • Client selections in progress. The countertop was "probably quartz, leaning toward something she showed me on her phone." He uses the mid-range allowance that has worked on similar jobs. The client selects at the high end. The overage surfaces at the supplier invoice three weeks into the project.
  • Scope boundaries that were not confirmed. During the walkthrough, the client gestured toward the adjacent hallway and said "while you're doing all this, it might be worth looking at the hallway too." The owner nodded. He is not sure if that was a request that should be in the proposal or casual conversation. He leaves it out. The client asks about it when the proposal comes in.
  • Subcontractor coordination items. He was going to ask about the island pendant situation — three pendants on a single circuit or individual circuits — because the answer affects the electrical quote by $600. He forgot to ask. He assumes single circuit. He is right three times out of four. This is not that time.

What Contractors Try First

The natural response to this problem is to take better notes. More detail on the walkthrough. A more comprehensive checklist. Some owners carry a two-page form. Some record video. Some send a detailed follow-up email to the client after the walkthrough to confirm what was discussed.

Each of these helps. None of them solve the underlying problem.

Better notes require a structured format to be useful for estimating. A page of observations recorded in the order they were noticed — "tile in main bath, client wants white, check structural beam in kitchen, pendant question, mudroom maybe, subfloor soft corner near door" — still requires interpretation and reconstruction when the estimate is being built. The quality of the raw notes is not the constraint. The constraint is the gap between observing and recording, and between recording and translating those records into estimate line items.

Video records what is on screen, not what the owner is thinking. The footage of the subfloor corner does not capture the softness he felt underfoot. Client confirmation emails are valuable for scope clarity. They do not capture the owner's in-the-moment observations about the work required to execute the scope.

The problem is not the quantity of information captured. The problem is the format. Information captured in observation format has to be converted into estimate format before it is useful. That conversion happens Sunday afternoon, from memory, five days after the site visit. Something is always lost in the translation.

What a Structured Intake Captures Instead

The walkthrough that produces a reliable estimate is not longer. It is differently organized.

Instead of observing and then converting, the intake captures information in the categories the estimate requires. Not "notes about the bathroom" but "tile: format, finish, pattern, approximate square footage, substrate condition visible, any subfloor concerns." Not "general impressions of the kitchen" but "demo scope, rough-in locations confirmed, ceiling height, island: yes/no, pendant: single or individual circuits, countertop: material direction, allowance tier, confirmation needed before proposal."

Each category maps to a line item or a decision in the estimate. By the end of the walkthrough, the estimate categories are populated with actual information rather than waiting for a Sunday afternoon reconstruction.

The questions that could not be answered on-site are flagged explicitly: "countertop tier — confirm with client before proposal goes out." They are not assumptions. They are open items that require a five-minute call before the estimate is finalized. That call happens Monday morning with current context rather than Sunday afternoon with five-day-old memory.

The tile format question — 24x24 or 24x48 — is not a Sunday afternoon guess. It is a Tuesday afternoon note, or a flagged question answered in a brief client text on Wednesday, before the estimate is started.

What Changes Downstream

An estimate built from a complete intake is a different document from an estimate built from reconstruction.

The assumptions are visible. The items confirmed on-site are recorded as confirmed. The items that required a follow-up call are recorded as confirmed once the call happened. The items that remain genuinely unknown are stated explicitly as allowances with noted uncertainty, rather than hidden as guesses that look like decisions.

The surprises that surface in week two — the subfloor condition, the tile format, the scope boundary question — do not surface in week two. They surface before the proposal goes out, when they are still questions rather than problems.

The estimate review time decreases. The owner reviewing his own estimate on a Sunday afternoon spends less of that time reconstructing context and more of it actually reviewing numbers. The items he is uncertain about are marked, not buried.

And over time, the estimate becomes a teaching document. Each completed intake, compared to the actual project conditions encountered, reveals which categories are consistently underestimated and which are consistently accurate. The soft subfloor corner that was missed on Tuesday and cost $1,800 in week two becomes a line item on every future bathroom estimate — not because the owner added it from memory, but because the intake structure flagged it as a category and the project record confirmed its cost.

The Tile Was 24x24 or 24x48

The difference between those two sizes, on the bathroom the owner was pricing, was $340 in material cost and about $600 in installation labor due to the layout complexity of the larger format. The client had mentioned the size during the walkthrough. The owner had looked at the sample she showed him. He did not write it down because he was in the middle of measuring the wall height.

By Sunday he could not remember.

He estimated 24x24. The client had selected 24x48. The tile was ordered, delivered, and staged before the discrepancy was discovered. Reordering the correct tile added eleven days to the schedule and a conversation with the client about why the project was starting late.

The cost of not writing down one number, five days before the estimate was due, was eleven days and a client conversation the owner did not want to have.

Most estimates have a version of this. The question is not whether the walkthrough captures perfect information — it will not. The question is whether the capture process is structured enough to flag the decisions that require a confirmed answer, and distinguish them from the items that are safely assumed.

That distinction exists when the intake is built to produce it. It does not exist when the intake is a yellow notepad and 47 photos in the order the phone was pointed.

Tracking whether the estimate held once the project ran?

The next piece in this series covers how to measure the gap between quoted margin and actual margin — and which line items are responsible.

You Quoted 22% Margin. What Did You Actually Make? →

Related

Frequently asked questions

How should contractors capture information during a site walkthrough for estimating?

The most effective site capture for estimating purposes organizes information by estimate category rather than by observation order. Instead of general notes, the intake captures specific answers to specific questions that map directly to estimate line items: substrate condition, rough-in locations, client selection tiers, scope boundaries confirmed versus discussed, items requiring follow-up before the proposal is finalized. This format reduces the reconstruction work required when the estimate is written and makes open items visible rather than hidden as assumptions.

Why do construction estimates have errors even after a thorough site visit?

The primary cause is the gap between the site visit and when the estimate is written. Memory decays, competing priorities intervene, and the mental context that existed on-site is partially lost by the time the estimator sits down to price the work. Information captured in observation format — notes, photos, voice memos — requires conversion into estimate format before it is useful, and something is typically lost in that conversion. The gap is not a discipline problem; it is a structural consequence of how most contractors organize the walkthrough-to-estimate process.

What is a construction estimate intake process?

An estimate intake process is a structured method for capturing the information required to build an accurate proposal during or immediately after the site visit. A well-designed intake captures information in the categories the estimate requires — by trade, by phase, by decision type — rather than in observation order. It distinguishes between items that are confirmed on-site and items that require follow-up before the proposal can be finalized. When the intake is complete, the estimate can be built from recorded information rather than from memory.

How do contractors reduce surprises that happen after the estimate is accepted?

Most project surprises trace back to assumptions made during the estimating process that were not confirmed at the time. A structured site intake reduces surprises by making open items explicit — flagging them as questions requiring a client call or a subcontractor confirmation before the proposal goes out, rather than converting them into assumptions that look like decisions. The surprises that surface in week two as cost variances are often the questions that were not asked during the walkthrough or in the days immediately following it.

See how TIM handles the estimating function

Built for service businesses with 5 to 15 employees. First month complimentary.

See TIM's pricing