The short answer
- A rush job displaces other work — that is its real cost
- Check blanks and artwork before agreeing to anything
- Never move a committed job without telling that customer
- Keep deliberate slack in the schedule so rushes fit
- Rushes cause most quality failures; skip nothing that matters
The phone rings at three o'clock on a Wednesday and somebody needs a hundred shirts by Friday. The answer is not automatically no, and it is not automatically yes either — it depends on things you can check in ten minutes.
What a rush actually costs
The real costs
- Other jobs pushed back, sometimes past their dates
- Overtime, or work displaced into evenings
- Rush freight on blanks
- Setup disruption — a changeover that was not planned
- Higher spoilage under time pressure
- Attention taken from everything else that day
The displacement is the cost that matters and the one never counted. A rush accepted by delaying two other jobs has moved the problem rather than solved it, and those customers did not agree to it.
There is no spare capacity. A rush job is always paid for by somebody else's delivery date.
Deciding
Say yes when
- The schedule has genuine room
- It is a repeat — artwork and screens exist
- Blanks are confirmed in stock and can arrive in time
- It is a valued account and the disruption is manageable
- The rush premium reflects the disruption
- Nothing committed has to move
Say no when the honest answer is that you would have to gamble. A rush accepted on a hope that blanks arrive is a rush that fails publicly, and a failed rush costs more goodwill than a declined one.
Where you decline, offer what you can — a partial delivery on the date with the balance following, or a different garment that is in stock. Most customers under pressure will take a workable alternative over a flat refusal, and the pricing side is covered in pricing rush jobs.
Checking feasibility
Before agreeing, check the three things that actually decide it. This takes minutes and prevents most rush failures.
The three checks
- Blanks: in stock, in every size, arriving in time
- Artwork: print-ready, or fixable today
- Capacity: a real slot, not an optimistic one
Blanks are the usual failure. A garment showing available nationally may be split across warehouses, and a size missing from the nearest one adds a day — which is why live availability is worth more on a rush than on anything else.
Artwork is the second. A customer in a hurry frequently sends a poor file, and the time to discover that is before committing to the date rather than at eight the next morning.
Protecting the schedule
Rules worth holding
- Never move a committed job without telling that customer
- Keep deliberate slack rather than booking to capacity
- Cap how many rushes you accept in a week
- One person owns the schedule and approves changes
- Record what was displaced, so the pattern is visible
Deliberate slack is the structural answer. A schedule booked to the last hour has no capacity for anything unexpected, and unexpected things happen weekly — which is the argument in a schedule that survives a bad week.
Telling the displaced customer is not optional. A silently delayed job produces a complaint from somebody who did nothing wrong, and that costs more than the rush earned.
Running it
Preparation is everything
- Stage the whole job before the press is free
- Confirm artwork approved and screens made
- Ink mixed and matched in advance
- Blanks received, counted and checked
- Everyone told what is happening and when
- Finishing and dispatch arranged, not assumed
Dispatch is the step most often forgotten on a rush. A job finished at five that misses the carrier collection has not saved anybody anything, and the collection time should be checked before the schedule is built around it.
Quality under pressure
Rush jobs produce most of the quality failures in a decorating shop, because the checks are the first things to be dropped.
Never skip
- Cure verification — an undercured rush fails in the wash
- The first-off check against the proof
- Spelling on names and numbers
- Counting the finished order
- Written approval, even if brief
Cure is the one that must never go. It takes a minute, it is invisible if wrong, and a rush order that fails after delivery destroys the goodwill the rush was meant to build — the checks are in cure checks that catch problems.
Tell the customer what the compressed timeline means for them as well. A rush leaves no room for a revision, so the artwork they send is the artwork that gets printed, and saying that plainly prevents an approval cycle that the schedule cannot absorb.
What you can reasonably reduce is scope rather than checks: fewer colours, a simpler placement, an in-stock garment. Those are honest ways to make a date; skipping verification is not.
Reducing them
Fewer rushes over time
- Publish lead times clearly, everywhere
- Price rushes properly — it filters the unnecessary ones
- Remind seasonal customers before their season
- Set store closing dates that leave real production time
- Keep artwork on file so repeats are fast by default
- Hold stock of your highest-volume garments
The seasonal reminder does most of the work. A large share of rush jobs are annual events that the customer simply left late, and a message six weeks earlier converts an emergency into an ordinary order.
Charge the premium consistently rather than case by case. A rush rate applied to some customers and waived for others stops being a rate and becomes a negotiation, and the customers who push hardest are the ones who will rush you most often.
Where lead times, stock and job status are visible in one system, the feasibility check that decides a rush takes a minute rather than a round of phone calls — which is often the difference between taking profitable urgent work and turning it away because nobody could answer quickly enough. The rest of the production archive assumes a rush was checked before it was promised.


