Surprise Jobsite Conditions Are a Systems Problem

Surprise Jobsite Conditions Are a Systems Problem

by Bruce Baker | Jul 31, 2026

You send a crew to a relatively basic job. They pull a cover plate and find previous work that never should have passed. Wiring nobody would sign off on. A structure sitting on three inches of slab. A relief valve that should have been swapped years ago. Nobody mentioned it. The salesman was on site for hours and said nothing.

Now your tech is standing there deciding whether to keep going, stop and call, or eat the extra work to keep the customer happy. Every one of those choices costs you.

I have spent more than 20 years advising owners in construction and the skilled trades. Surprise jobsite conditions feel like bad luck. They are not. They are a systems problem, and once you treat them that way, they stop bleeding your margin.

Why surprise conditions are a systems problem, not bad luck

Field crews find things that were undisclosed at the start of a job. Old workmanship that fails code. Missing safety infrastructure. A snake in the condensing unit. These are not rare events. They are the normal texture of the work.

Here is the trap. When there is no system for handling them, every discovery becomes an on-the-spot judgment call made by whoever happens to be holding the wrench. Some techs stop and document. Some push through and absorb the cost. Some flag it three days later when the paperwork lands on your desk.

That inconsistency is the real problem. You cannot price, schedule, or protect margin when the same situation gets handled five different ways depending on who showed up.

What it costs when you ignore it

The cost compounds quietly.

  • Scope creep eats hours you never billed for.
  • Jobs run weeks behind because a discovery stalls the schedule and nobody replans.
  • Safety risk climbs when a hazard gets worked around instead of documented and addressed.
  • Your relationship with the customer sours when a change order shows up as a surprise to them too.
  • Your best people burn out from making stressful calls that were never their job to make.

I worked with a residential construction company that was winning work but bleeding it back out. A large share of jobs ran behind, and overhead drifted past budget before anyone caught it. The fix was not working harder. It was a weekly operating rhythm, a short KPI review, site walks, and a post-mortem on every completed job so the same mistakes stopped repeating. Surprise conditions were a big part of what had been slipping through.

The fix: a discovery, document, decide routine

You do not need software. You need a repeatable routine every crew follows the moment they find something the job did not account for. Call it discovery, document, decide.

Discovery on arrival

Before the real work starts, the crew does a short walk and looks for the obvious red flags: previous poor workmanship, structural issues, missing safety infrastructure, anything that changes the scope or the risk. Five minutes up front saves you a stalled afternoon.

Document before you touch it

Photo first, always. A quick photo and a one-line note in whatever channel you already use. This does two things. It protects you from being blamed for the prior mess, and it gives you the evidence you need to bill the change or walk away clean.

Decide with a clear rule

Your crew should know the threshold without calling you. Something like: anything that adds more than a set number of hours, or anything that is a safety hazard, stops the work and triggers a call and a change order. Below that, document and proceed. Write the rule down so it is the same every time.

The point is not the exact numbers. The point is that the decision is made by the system, not by the mood of the person on site.

An honest caveat

A routine will not catch everything. Some conditions are honestly buried and nobody finds them until the wall is open. The house sinking on a three-inch slab is not something a five-minute walk reveals.

What the system does is handle the discoverable ninety percent consistently, and give you a documented, defensible process for the rest. That is the honest promise. Fewer surprises, and a clean paper trail for the ones you cannot prevent.

There is also a real cost to building the routine: it slows the first few jobs down while the crew learns it. That is a fair trade for stopping the same losses every week after.

Where coaching fits

If you are trying to build a company that runs on rhythm and documented process instead of your own reactions, that is the work we do at Workplaces. I run a Business Building Program and leadership development for owners across construction and the trades, helping them build a self-managing company where the crew follows the system whether or not the owner is on site.

The same discipline that turns surprise jobsite conditions into billable scope is the discipline that lets you step back from being the bottleneck. Whether you are scaling an existing shop or figuring out how to start a construction company without money, systems are the cheapest asset you can build, because they cost time up front and pay back on every job after.

One concrete next step

This week, write one sentence and give it to every crew: “If you find something the job did not account for, photo it, and if it is a safety issue or adds more than X hours, stop and call before you proceed.”

That single rule, applied every time, is where the margin stops leaking. Build what compounds.