Your best customer calls on a Wednesday. A line is down, they need twelve brackets by Friday, and they will pay what it takes.
You say yes. Of course you say yes. They are a good customer, it is good money, and saying no to a rush is how you stop being the shop they call first.
By Friday the brackets are out the door and the customer is happy. It feels like a win.
Then Monday comes, and two other jobs are late.
The rush is not the problem
Rush work is part of running a job shop. Some of your best margins come from it, and some of your best customers stayed with you because of the week you pulled them out of a hole.
The problem is not the rush. It is the yes nobody checked.
On Wednesday you knew the brackets needed about fourteen hours. What you did not know, standing at the phone, was that Thursday and Friday were already full. Nobody had added up the week. So the rush went in on top, the welder stayed on it, and the two jobs that were meant to ship Friday slid into next week.
What the rush really cost
Here is the sum most shops never do.
The rush job paid well. Say it carried a healthy premium on those fourteen hours. That premium is real.
But the two jobs that slipped did not get cheaper to make. They just got later. One customer called twice to ask where their parts were. The other had to push back their own assembly, and the next RFQ they sent went to two other shops as well as you.
Then there is the catch-up. Someone worked Saturday at time and a half to get the week back. The premium on the rush job quietly paid for that Saturday, and not much else.
None of this shows up on the rush job's invoice. It shows up later, spread across other jobs and other customers, where nobody connects it to the yes on Wednesday.
Why the whiteboard cannot tell you
Most small shops plan the week on a whiteboard, a spreadsheet or in the owner's head. All three hold the list of jobs. None of them hold the sum.
A whiteboard shows you that five jobs are due this week. It does not show you that those five jobs need 118 hours and your shop has about 100. You find that out on Thursday afternoon, when the work is not getting done.
So when the rush call comes in, the real answer to "can we fit it in?" is "I think so." And "I think so" is how two other jobs end up late.
Know your ceiling first
The fix starts with one number: how many hours your shop can actually run in a day.
Not the hours on the clock. The hours that turn into work. Three people on eight-hour days is twenty-four hours on paper, but setups, breaks, cleanup and hunting for material all take a slice. At 85% you have about twenty. Pick a number you believe, even a rough one, and adjust it as you learn.
Once you have it, every day on the schedule has a ceiling. Add up the work booked on that day and you can see straight away whether it fits.
Ask three questions before you say yes
When a rush comes in, look at the week and ask:
- Which days does it land on? Put the hours where the work will really happen, not just on the due date.
- Does it push those days over? If they were already full, something else has to move.
- What moves, and who do I call? Pick the job that can slip with the least damage, and call that customer today, not on Friday.
You will still say yes to most rushes. The difference is that the customer whose job moves hears it from you, early, with a new date. That is a very different phone call from the one where they chase you.
Price the rush for what it moves
If a rush pushes other work around, the premium has to cover that: the overtime, the weekend shift, the job that ships late. Plenty of shops charge a flat rush premium without ever checking what it has to pay for. Once you can see what a rush actually moves, you can price it with confidence.
What this looks like in Quotara
This is the problem the schedule in Quotara is built to show.
You tell Quotara how many hours your shop can run in a day, once, in Settings. The schedule adds up the work booked on each day and shades it red when it goes over, so you see the overloaded day before it arrives. Each job also gets a projected finish date at its current pace, and the jobs heading for late are called out.
When you mark a job rush, it pins to the top of the work order list, the floor and the schedule, highlighted in red, so the whole team sees it first without being told. Clear the flag and it drops back into line.
The hours behind all of it come from the floor, where your team clocks in on each step from a phone or a shared tablet. So the schedule shows what is really happening, not just what was meant to happen.
Try it on next week
Before the next rush call, take ten minutes. Add up the hours booked for next week, day by day, and set them against your real daily ceiling.
If there is room, great. You can say yes on the phone and mean it.
If there is not, you just found out on a quiet Sunday instead of a busy Thursday.
Try Quotara free for 14 days. No credit card required.