Spotting the Job That Will Go Sideways: A Decision Tree

Why this matters

Some jobs are doomed before you write the quote, and the signs are usually visible during the walk if you know to look. A job that goes sideways does not just lose money on that ticket. It eats your week, sours the customer, and pulls you off the next three jobs. Catching it early lets you price the risk, exclude it, or walk away. This is a sorting tool: run the checks from the cheapest, most common warning sign to the deeper ones.

Start here

Before anything else, ask one question: can you clearly picture the finished job, start to end, with no question marks? If yes, the job is probably fine. If you keep hitting a blank spot - a thing you cannot see, a number you do not know, a customer answer that does not add up - that blank spot is where it goes sideways. Work the branches below to find it.

Branch 1: The customer signals (most common)

If the customer is vague about the budget or dodges the question, there is usually a number they are not telling you, and it is lower than the job needs. Pin down the real budget before pricing, or expect a fight over every line.

If the customer has already had two or three people out for this, ask why none of them got hired or finished. Either the job is genuinely hard, the price keeps coming in over their head, or they are difficult to satisfy. All three predict trouble.

If the customer keeps adding "and while you're here," scope creep has already started. Scope it formally now or it will balloon mid-job. (See: Scope Creep Starts at the Estimate.)

If the customer downplays a visible problem, believe your eyes, not their summary. "It's always done that" is frequently the actual failure you are about to inherit.

Branch 2: The condition signals

If you see a previous repair, patch, or workaround, find out who did it and why it did not hold. A botched prior job means the underlying problem is still there and now it is tangled with someone else's mistake.

If a single new component sits in an old system, the rest of the system is the next failure. Your clean repair may expose three more.

If you find corrosion, water staining, rot, or a strong smell, the building is reporting damage the customer did not. This is the classic hidden-conditions trap. Either investigate it now or write a clear exclusion for what you cannot see.

If the structure is old and you cannot inspect the part that matters, assume the worst case is on the table and price an allowance for it.

Branch 3: The access and logistics signals

If you cannot picture material getting in and debris getting out, stop and solve that before you quote. A buried access path can double the labor and is almost never in the first estimate.

If the work area is packed, occupied, or fragile, the time to move, protect, and replace everything is real labor. Count it.

If the job needs another trade, a permit, an inspection, or a part with a long lead time, your schedule now depends on someone you do not control. Build slack and make the dependency explicit to the customer.

Branch 4: The gut signal

If something feels off and you cannot name it, do not override it. The uneasy feeling is your pattern recognition firing before your conscious mind catches up. Slow down, walk the space again, and find the thing your gut already noticed. It is usually one of the signals above that you skimmed past.

What to do once you have spotted it

You have three honest options, in order of preference:

  1. Price the risk in. Add the allowance, the contingency, the access penalty. Tell the customer plainly why.
  2. Exclude it. Write what is not covered and what triggers a change order, so the surprise has a paper trail.
  3. Decline it. Some jobs are not worth winning. A clean "we're not the right shop for this" beats a job that goes sideways and takes your reputation with it.

The one option that always loses is pretending you did not see the signal.

References

  • Trade-standard risk assessment and scope-exclusion practice.
  • OSHA jobsite hazard assessment guidance.
  • See related: Scope Creep Starts at the Estimate; Scoping the Hidden-Conditions Risk; The Job Bigger Than It Looks.