Reading a Job Before You Touch It

Why this matters

Two techs can stand in the same room and see two different jobs. One sees the task on the work order. The other sees the task, plus the three things around it that decide how the task actually goes. Reading a job is the skill of seeing the second version. It is what separates a tech who hits his estimate from one who is always "almost done."

What reading a job actually means

Reading a job is forming an accurate mental model of the work before you commit a tool or a price to it. It is not psychic. It is pattern recognition built from paying attention: this kind of space, this age of system, this condition, this customer, usually means these complications. You build the library by walking a lot of jobs and noticing, every time, where reality differed from the work order.

The goal is to answer four questions before you start: What am I really being asked to do? What is in my way? What can I not see? Who am I doing it for?

The four reads

Read the scope. What is the actual finished state the customer expects? Strip the job back to the outcome. "Fix the leak" might mean replace one part, or it might mean the part is fine and the real failure is upstream. The stated task is a clue, not the scope.

Read the obstacles. Everything between you and the work. Access, the carry, things that must be moved or protected, other systems crowding the space, a tight or awkward position to work in. Obstacles are where labor estimates die. A two-hour task in an open garage is a half-day task in a packed crawlspace.

Read the unknowns. What is hidden, and how much does it matter if your guess is wrong. Behind the wall, under the slab, inside the unit, above the ceiling. You cannot see it, so you assess the odds: how old is the building, what does the visible portion suggest, what is the typical failure for this setup. Name your unknowns out loud so they become allowances, not surprises.

Read the customer. Their priorities and their tolerances. The one who watches every move, the one who wants it cheap above all, the one who will add "while you're here" tasks, the one who is hiding the real budget. The customer shapes the job as much as the building does.

Signals that the job is not what it looks like

Train yourself to flag these on every site:

• A previous repair, patch, or workaround. Someone was here before and either could not or would not do it right. Find out why.
• A mismatch between the age of the building and the age of a component. New part on old everything else means the old everything else is the next failure.
• Corrosion, staining, brittleness, or smell. These are the building telling you about water, heat, or time that the customer did not mention.
• The customer downplaying something. "Oh, it's always done that" is often the actual problem.
• An access path that does not obviously work. If you cannot picture material getting in and debris getting out, you have not finished reading the job.

Calibrate bigger vs smaller

Every job is either bigger than it looks, smaller than it looks, or about right. Most are not about right. The bias to watch: jobs in bad condition, tight access, or with hidden systems trend bigger; jobs that sound dramatic on the phone but are clean and accessible in person often trend smaller. Reading well means catching both, because over-scoping loses you the bid and under-scoping loses you the margin.

Write the read down

A read that lives only in your head does not transfer to the estimate, the dispatcher, or the tech who actually runs the job. Capture it: a few photos, the obstacles, the unknowns you are pricing as allowances, the customer note. The point of reading a job is to change how it gets priced and planned. If nothing downstream changes, you read it for nothing.

References

• Trade-standard estimating and scope-verification practice.
• OSHA jobsite hazard assessment guidance (pre-work walkthrough).
• See related: The Site Walk Before You Quote; The Real Problem vs The Stated Problem; Scoping the Hidden-Conditions Risk.