Busy-Season Overtime vs Turn-Away Work Decision Tree

Why this matters

At the peak of demand, every shop hits the same fork: push the crew into overtime to take more work, or turn some work away. Get it wrong in one direction and you burn out your team and bleed quality. Get it wrong in the other and you leave good money and good customers on the table. This walks the decision from the simplest checks to the hard trade-offs, so you choose on purpose instead of just defaulting to "say yes to everything."

Start here: is the extra work even worth taking?

Not all overflow work deserves overtime. Filter before you fatigue.

• If the marginal job is low-margin, far away, or a poor fit, decline it regardless of capacity. Overtime spent on bad work is a double loss.
• If the job is profitable, fits your trade, and serves a customer worth keeping, it is a real candidate. Continue.

Can you create capacity without overtime first?

Overtime should be the lever you pull after the cheaper ones, not the first.

• If there is idle time, slow dispatch, or process drag in your normal day, tighten that first. You may find the capacity you need without a single extra hour.
• If you can defer genuinely non-urgent work out of the spike, do that and free the slots for the urgent jobs.
• If a subcontractor can absorb the overflow at acceptable quality, that may beat grinding your own crew.
• If none of those close the gap and the work is worth taking, overtime is now on the table. Move on.

How deep into fatigue is your crew already?

This is the branch most owners skip, and it is the most important.

• If the team is fresh and the surge is short and clearly bounded, moderate overtime is fine and often welcome for the extra pay. Proceed within a sane ceiling.
• If the crew is already deep into a long grind, more overtime buys you less and costs you more. Tired techs work slower, make mistakes, and create callbacks and safety risks that erase the gain. At this point, turning work away is the higher-return choice. Continue to the trade-off.

Weigh the true cost of overtime against the cost of declining

Both choices cost something. Compare them honestly.

If the overtime is short and the crew is rested, the revenue usually justifies it. If the overtime is sustained and the crew is spent, the hidden costs of callbacks, mistakes, and lost techs usually outweigh the extra revenue, and turning work away is the disciplined call.

If you turn work away, do it well

Declining work is a skill, not a failure. How you do it decides whether you keep the customer.

• If you ghost them or give a vague brush-off, you lose them to a competitor for good.
• If you offer a real future date, a referral, or a clear explanation, many customers wait or come back. A clean "I cannot do it justice this week, but I can have you on the books for next Tuesday" protects the relationship even as you decline today.

Protect the customers who carry your slow season

One more filter before you turn anyone away.

• If the work is for a loyal, recurring customer who counts on you, stretch further to serve them, even if it means declining a new one-time job instead. The relationships that feed your slow months are worth protecting in your busy ones.
• If the work is a one-time price-shopper and your crew is maxed, that is the right job to defer or decline.

Final check before you decide

Run the chain: the work is worth taking, you have exhausted cheaper capacity, you have honestly read your crew's fatigue, you have weighed real overtime cost against the cost of declining, and you have protected your core customers. Then choose. The right answer is not always more overtime, and it is not always saying no. It is the one the whole tree points to for this specific job and this specific week.

References

• OSHA, guidance on worker fatigue and extended-hour workloads
• SBA, capacity-planning and staffing guidance for small businesses
• Trade-standard practice for peak-demand scheduling and crew management
• See related: Surviving the Demand Surge Without Burning Out; The Seasonal Hire Decision Tree