Rush Fees: How to Price Urgent Work Without Wrecking Your Week

A client emails on Thursday asking for a project delivered by Monday morning. Say yes at your normal rate, and you're the one who eats the weekend. A rush fee is how you get paid for that trade — and done right, it protects your schedule instead of just padding an invoice.

Quick answer

A freelance rush fee typically runs 25% to 100% — sometimes more, for the most extreme turnarounds — on top of your normal rate. The number scales with how compressed the deadline is: a 25% floor is common for shaving a few days off a standard timeline, while sub-48-hour or same-day work often justifies doubling your rate. What actually makes something a "rush job" isn't the calendar date. It's whether the request pushes something you've already committed to. That's a different problem than a client who cancels mid-project (see kill fees for that scenario), but the pricing logic rhymes: you're charging for disruption, not just hours.

Step-by-step: setting a rush fee that actually protects your week

Step 1 — Define what counts as a rush job for you

Under-48-hours is the line most freelancers draw, but the real test is simpler: does saying yes bump something already on your calendar? A quiet week with open capacity isn't a rush job, even if the client calls it one. A booked week where this request means working Saturday is.

Step 2 — Calculate from displacement cost, not a round number

Instead of picking a percentage out of the air, work backward from what the rush actually costs you. One useful formula sets the fair minimum as whichever is higher: your normal project price, or your normal hourly rate times the hours the rush takes, plus whatever it genuinely displaces. That last part matters. If a rush job pushes another client's work to next week and that client still gets paid on schedule, you haven't lost that revenue — just delayed it. The real cost is the incremental one: an evening you didn't plan to work, a subcontractor you had to bring in, or the admin overhead of re-shuffling two calendars instead of one. If you don't bill hourly at all, the same logic applies to value-based pricing — price the outcome, not the clock, and the rush premium still reflects genuine disruption rather than a guess.

Step 3 — Use a tiered structure so it's consistent

A flat "everything gets +50%" policy is easy to explain, but it doesn't match how differently rush jobs actually hit your week. A tiered structure holds up better under scrutiny from both you and the client:

• ~25% — the work fits in normal hours, but you have to reschedule something else to make room
• ~50% — the work disrupts your established process, like doing something yourself that you'd normally hand to a subcontractor
• ~100% — the work requires nights, weekends, or otherwise personal time — the same logic behind overtime pay for employees

This is the same instinct behind a rate card for out-of-scope work: price the disruption ahead of time, so you're not negotiating from scratch every time a request lands.

Step 4 — Put it in writing before the first rush request

Rush terms belong in the contract or statement of work before you ever need them — not improvised in a Thursday-afternoon email. State the normal price, the added fee, the exact delivery date, and what has to happen on the client's end (assets delivered, approvals given) for that date to be realistic. Specific beats vague: "delivery by Monday 9am adds a $400 rush fee, for a total of $1,600" leaves nothing to argue about later.

Common problems and fixes

"The rush fee didn't actually cover what it cost me." Rush work tends to eat more hours than quoted — extra coordination, faster revision cycles, more back-and-forth — and that gap can quietly erase the value of the surcharge if you're not tracking actual time against the estimate. A compressed deadline doesn't shrink the work itself; it just compresses when you feel the pressure of it, which is the practical version of Parkinson's Law working against you instead of for you. Track hours on rush projects the same way you'd track any other, and use what you find to price the next one more accurately.

"This client keeps asking for rush turnarounds." A one-off emergency and a pattern are different problems. If the same client regularly asks for fast turnarounds, they're telling you they need guaranteed availability, not a favor. That's a signal to move them onto a retainer with priority turnaround built into the flat monthly fee, instead of re-negotiating a rush fee every single time.

"Charging extra makes me feel like I'm being difficult." Reframe it: a rush fee is premium pricing for prioritized service, not a penalty for someone being unreasonable. It's also how you keep your existing clients' timelines intact while still saying yes to the client in front of you.

Doing this with Pomlo

The hardest part of pricing a rush job honestly is knowing what it actually displaces — and most freelancers are guessing. Pomlo's time tracking and focus sessions make that concrete: you can see exactly which blocks on your week a rush request would bump, instead of estimating from memory. Projects and clients keep the rush job's hours separate from everything else, so when it's time to bill, the surcharge is easy to justify line by line. And when the work's done, built-in invoicing turns the agreed rush fee into a sendable invoice in one tap — no separate spreadsheet, no re-typing math you already did.

Pomlo is available on iOS, Android, and the web — download it and see where your week actually goes before the next urgent request lands.

Frequently Asked Questions

How much should I charge for a rush fee?

Most freelancers charge 25% to 100% on top of their normal rate, scaling with how compressed the deadline is — 25% for a few days shaved off a timeline, up to 100% (or occasionally more) for same-day or overnight turnarounds. The defensible number is whichever one actually covers what the rush costs you: displaced work, extra coordination, or hours outside your normal schedule.

When should I not charge a rush fee?

Skip it when the extra work is genuinely small, when it's a long-term client you want to keep happy during a quiet week, or as a one-time goodwill gesture for a new client. Even then, it's worth showing a $0 rush-fee line on the invoice so the client sees the value they received for free.

What if a client keeps asking for rush turnarounds?

That's a sign they need guaranteed fast availability as a standing feature, not a one-off favor. Move them onto a retainer that bakes in priority turnaround for a flat monthly fee instead of negotiating a rush fee every time.

Do I lose money if I just reschedule other clients instead of turning down work?

Not automatically. If the displaced work still happens and still gets paid, it's a delay, not a loss. The real cost is the incremental one — extra admin, evening hours, or subcontractor help you wouldn't otherwise need — and that's what a rush fee should cover, not a duplicate charge for hours you were always going to bill.