The Rush Job Request: Say Yes for a Fair Premium or No Well (4 Templates)

"I know this is short notice. Is there any chance you could have it done by Friday?" The rush request arrives flattering and dangerous in the same breath. Flattering, because they came to you. Dangerous, because every option costs something: the free yes that torches your schedule and teaches customers that deadlines are negotiable, the resentful yes that poisons the job, the clumsy no that loses a good customer. The businesses that handle it well all share one habit: they decided their answer before the email arrived. Here is the policy worth deciding, the fair maths of rush fees, plus four templates for the moment itself.

The rush fee is the honest price of disruption

Start with the reframe that unlocks everything: a rush fee is not a penalty for the customer, it is the true cost of the exception they are asking for. Meeting their Friday means your evening, another customer bumped, materials at premium prices or express shipping you absorb. Charging for that is not opportunism, it is accounting. And the fee performs a second service nobody mentions: it filters real urgency from casual impatience. A customer with a genuine emergency pays 50 percent extra without blinking. One who suddenly discovers next month is fine after all has just told you the deadline was soft. Now you know.

The common ladder across trades and services runs 25 to 100 percent on top of the normal price. A squeeze that costs you an evening sits near 25. Weekend work or bumping scheduled customers justifies 50. Drop everything, tonight, is fairly double. Set your ladder once, calmly, write it into your quotes and apply it to everyone, because a rush fee invented per customer under pressure stops being policy and starts being a mood.

The written yes, even at speed

Urgency is exactly when paperwork gets skipped and exactly when it must not be. Before the rushed work starts, one confirmation email: the scope, the deadline, the total including the rush fee and what the customer must provide by when. They answer with one word. Three minutes, total. Skip it and the classic rush disasters queue up: the fee that surprises the invoice, the scope that grows mid sprint, the customer whose own late photos or approvals quietly erase the deadline you are still being held to. That last clause, "the Friday date holds provided I have your [input] by Wednesday noon", is the single most protective sentence in rush work. If the job then grows anyway, the variation rules from the extra cost guide apply at double speed.

Rush request templates

Four for the answers you will actually give. Swap the brackets and send fast, because in rush conversations the reply speed is part of the answer.

The no is a service too

The instinct is to treat a declined rush job as a lost customer. The reality of ordinary business life says otherwise. What loses customers is the slow maybe: the two days of silence while you agonise, which burn exactly the hours they needed to find another option. A same day no with the best realistic alternative is remembered as good service, because you respected the one resource they were short of. The craft of the warm refusal is the same one covered in how to say no in an email: decline the request, keep the relationship. And when the rushed work is done and delivered, the momentum is perfect for the review ask, because nobody writes a warmer review than the customer whose emergency you just handled.

Deciding well at the worst moment

Rush requests arrive at the busiest possible time by definition. That is precisely when policy beats improvisation: the fee ladder decided in calm, the input deadline clause ready, the confirmation email a habit. The writing itself is the last bottleneck, a reply that must be fast, warm and exact while the workshop waits. That is the job ReciteMail does: it learns your voice from emails you have already sent, then turns "yes to the Friday cabinet job, 50 percent rush so 900 total, need her measurements by Wednesday noon or the date moves, warm" into the finished reply in seconds. It runs on your PC, never connects to your inbox and nothing sends without you. See how it fits the trades.

Common questions

Should you charge a rush fee for urgent work?

Yes, whenever the deadline forces you to treat the job as an exception: working evenings, bumping other customers or paying premiums for materials and shipping. The fee is not a punishment, it is the honest price of disruption. Stating it plainly filters real emergencies from casual impatience. A customer whose need is genuine pays it without resentment. One who drops the urgency the moment it costs something has just told you the deadline was soft, which is also useful to know.

How much should a rush fee be?

Common practice across trades and services runs from 25 to 100 percent on top of the normal price, scaled to how much the deadline disrupts. A squeeze that costs you an evening sits near 25 percent. Weekend work, bumped customers or premium material costs justify 50. A genuine drop everything emergency can fairly double the price. Set your ladder once, write it down and apply it to everyone, because a rush fee invented per customer stops being policy and starts being a mood.

How do you decline a rush job without losing the customer?

Fast, warmly and with the best realistic alternative in the same email. The no is not the damaging part, every reasonable customer knows calendars fill. What damages is a slow maybe that burns their remaining time to find someone else. Reply the same day: I cannot do Friday without shortchanging the work, here is the earliest date I can do properly. If it helps, here is a smaller version I could manage by your date. A fast honest no with options is remembered as good service.

Should you get rush terms in writing before starting?

Always, even when the clock is screaming. One confirmation email with the scope, the rushed deadline, the total including the rush fee and what the customer must provide by when, answered with a one word yes, takes three minutes. Skipping it because things are urgent is how rush jobs end in disputes: the fee surprises the invoice, the scope grows mid sprint or the customer's late input erases the deadline you are being held to. The more urgent the job, the more the written yes protects both sides.

← Back to the blog