The Go/No-Go on a Questionable Job Decision Tree

Why this matters

Not every job is worth taking. Some look fine on the phone and turn out to be a money pit, a liability trap, or a customer who will never be satisfied. The cheapest bad job is the one you decline before you start it. Saying no to the wrong job protects the schedule, the crew, and the cash you would otherwise sink into a loss. This tree is a pre-commit gate: a structured way to read the warning signs at the estimate stage and decide go, no-go, or go-only-if before you ever quote a price.

Start here: is it safe and legal for you to do?

The first gate is non-negotiable, and a no here ends it.

• If the work requires a license, trade, or permit you do not hold, it is a no-go as scoped. Refer it or partner up; do not stretch past your lane.
• If the conditions are unsafe to work in and the customer will not let you correct them (no shutoff access, refusing to clear a hazard, demanding a known-unsafe method), no-go.
• If completing it as the customer wants would mean violating code, no-go. Your license follows the violation.

Clear this gate before anything else. Money does not buy back a job you should never have touched.

Read the customer signals

Many bad jobs are bad customers, not bad work. Watch for the patterns.

• Pressure to skip permits, inspections, or proper method to save fees: tells you how the rest of the job will go.
• A history of firing the last few contractors, or a story where every prior pro was "incompetent": you are likely next.
• Refusal to sign anything, resistance to a written scope, or wanting everything verbal: removes your protection on purpose.
• Haggling that targets the labor and safety steps, not just the total: they are buying corners.

One yellow flag is normal. A cluster of these is a no-go or a heavily-protected go.

Assess the unknowns and access

Questionable jobs are often questionable because you cannot see what you are quoting.

• If too much of the work is hidden (behind walls, underground, inside a sealed system) and the customer will not authorize exploratory work, you are pricing blind. Either scope it as time-and-materials with a conditions clause, or no-go.
• If access is genuinely impractical (no way to get equipment in, working space that is unsafe or impossible), that is a real constraint, not a detail.
• If the prior work is so poor that you would be inheriting its defects, decide whether you can isolate your scope from theirs. If not, the failures will land on you.

When the unknowns are large but bounded and the customer will share risk, this becomes a "go-if" rather than a no-go.

Decision matrix: go, go-if, or no-go

What "go-if" looks like in writing

Most questionable jobs are not pure no-gos; they are go-if-protected. The protections that turn a risky job into an acceptable one:

• A conditions clause stating the price assumes no concealed defects and that hidden conditions bill separately.
• Time-and-materials or allowances for the genuinely unknown portions instead of a fixed price you cannot stand behind.
• A written, signed scope that defines exactly what you are and are not responsible for, explicitly excluding the prior work's defects.
• A deposit or progress terms that keep you from financing the job.

If the customer accepts the protections, proceed. If they reject every one of them, they have told you it is a no-go.

How to say no cleanly

Declining well protects your reputation. Be brief, honest, and non-judgmental: the job is outside your scope, or it carries risk you cannot price responsibly, and you would rather refer them than do it wrong. Offer a referral where you can. Document that you declined and why. A clean no costs you one job; a bad yes can cost you several.

References

• State licensing-board scope-of-work and contractor-conduct rules
• OSHA general-duty standard on refusing unsafe work conditions
• Trade-standard practice on contract scope, exclusions, and conditions clauses
• See related: The Conditions Clause: Protect the Quote; Reading the Prior Work, Good or Bad