Can We Take This Work? A Capacity Decision Tree

Why this matters

The most damaging word in a busy shop is an automatic "yes." A new job comes in, saying yes feels like growth, so you say yes - and then you blow a promise date, push an existing customer, or send a crew into work you are not set up for. Overcommitting does not look like failure in the moment; it looks like a full schedule. It shows up later as missed dates, burned-out techs, and angry customers you already had. Knowing how to decide whether you can actually take a job - before you promise it - is a core operating skill, and it is mostly about being honest with yourself about real capacity, not the capacity you wish you had.

Start here: what is your true open capacity?

Before you can answer "can we take this," you have to know what is genuinely open. Real capacity is not "hours in the week." It is the hours left after existing committed jobs, realistic drive time between them, and a buffer for the inevitable jobs that run long or blow up.

• Look at what is already promised, not what is loosely penciled. A confirmed job is committed capacity, gone.
• Subtract drive time and setup, which eat a real chunk of every field day and are the thing owners forget when they eyeball the calendar.
• Keep a buffer. A schedule packed to one hundred percent has no room for the callback, the runover, the sick tech - and one of those happens almost every week. A shop with zero slack is a shop that misses dates.

If you do not know your true open capacity, every "yes" is a guess, and guesses run optimistic.

First branch: do you have the hours?

With real open capacity in hand, ask the simplest question: do the hours exist in the window the customer needs?

• If yes, comfortably: the hours are not the problem. Move to the skills branch.
• If yes, but only by packing tight against your buffer: this is a yellow light. You can fit it, but you are spending your slack, which means the next surprise blows a date. Take it only if you can move the promise date out to rebuild buffer, or if it is worth the risk.
• If no: the hours are not there. Do not promise it into a window that does not exist. Skip to the "no room" options below.

Second branch: do you have the right skills and tools?

Hours are necessary but not sufficient. Having time on the calendar does not mean having the right time - the tech with the skill, the certification, the equipment the job needs.

• Does this job need a skill only one person has, and is that person available in the window? If the work is gated on a single specialist who is already booked, the open hours are the wrong hours. You do not really have capacity for this job.
• Is it work you are actually set up to do well? Taking a job outside your wheelhouse to fill the schedule is how shops end up with callbacks, re-dos, and a bad review on work they should never have accepted. A job you can do at full quality beats a job you can merely fit.

If the skills or tools are not there in the window, treat it like a "no room" case even if raw hours exist.

Third branch: at what cost to existing commitments?

Now the question owners skip: if you take this, what does it cost the customers you already promised? New work is only free if it fits in genuinely open space. The moment it forces you to bump, delay, or rush an existing job, it is not additive - it is robbing one customer to serve another.

• Does taking this push an existing confirmed job? Then you are trading a kept promise for a new one. Almost never worth it; the customer you already have is worth more than the one you are courting.
• Does it force the crew into overtime or a rushed pace that drives quality down or burns people out? That is a cost too, just a delayed one.

A "yes" that quietly breaks an existing promise is the worst kind, because you lose a customer you already won to chase one you have not.

If there is no room: your real options

When the honest answer is "we cannot take this on the terms asked," you still have moves better than a false yes:

• Offer a realistic date. Most customers will wait if you tell them the truth up front. A later date you keep beats a sooner date you miss.
• Put it on a managed backlog and tell them where they stand, rather than promising into thin air.
• Refer it out if it is outside your skills or your window entirely. A good referral protects your reputation; a botched job you should not have taken destroys it.
• Decline cleanly. "We are not the right shop for this right now" is a complete, professional answer.

The discipline is simple to state and hard to hold: never promise capacity you do not have. A truthful "not until next week" keeps a customer. A hopeful "yes, today" that you miss loses two - the one you disappointed and the one you bumped.

References

• See related: Promise Date vs Realistic Date - Scheduling Discipline
• See related: Backlog - When the Schedule Is Full Decision Tree
• Capacity planning, standard operations-management practice
• U.S. Small Business Administration guidance on managing customer commitments and workload