How to Charge a Rush Fee as a Freelancer

The moment a client emails 'I know this is last minute, but...' you either have a rush policy or you don't. Without one, you absorb the cost of reprioritizing your work and accelerating your schedule to benefit someone who didn't plan ahead. With one, you get paid for it.

What counts as a rush

A rush is any deliverable that compresses your normal turnaround — not an ambitious deadline you agreed to at the outset, but a timeline shorter than what you priced for, or a request that arrives outside your workflow and requires you to shift other commitments to make room. A common working definition: any turnaround under 48 hours, or any project where the delivery date requires evening or weekend work you hadn't planned.

What to charge

The standard range for freelance rush fees is 25% to 50% added to your normal project rate. A practical framework:

• 25% for any deadline under one week that you hadn't scoped for in advance.
• 50% for same-day or next-day delivery, or any work requiring evening or weekend hours you hadn't planned.

On a $1,500 project, a 25% rush fee adds $375, bringing the total to $1,875. On a $600 project requiring same-day delivery, a 50% fee brings it to $900. The percentage needs to reflect the real cost: schedule disruption, reprioritization, and the opportunity cost of other work you moved. If the number feels uncomfortable to say, that is usually a sign it is right.

The contract clause

Rush fee policy belongs in your contract before the project starts — not in an email the first time a client asks for faster delivery. Here is language you can use directly:

• Rush requests — any deliverable with a turnaround shorter than [X] business days, or outside the timeline agreed in this contract — are subject to a rush fee of [25–50]% applied to the affected scope. Rush fees are confirmed in writing before accelerated work begins.

The phrase 'confirmed in writing before work begins' is doing the real work there. It protects you from a client who requests rush delivery, receives it, then disputes the charge after the fact.

How to say it without hedging

Most clients don't realize they're creating a scheduling problem when they ask for faster delivery — they think they're just adjusting a date. You don't need to explain the full impact. State the number and keep moving:

'I can have that to you by [date]. Given the compressed timeline, my rush fee applies — that brings the total to $[amount]. Let me know how you'd like to proceed.' No apology. No softening. You're offering a service at a price; the price is the price.

When a client's delays create the rush

If a project turns into a rush because the client was late sending assets, feedback, or approvals — that is not your scheduling problem to absorb. Treat it as a change order: confirm the revised timeline in writing, calculate the rush fee, and send it before you begin the accelerated work. Waiting until after delivery gives away the one moment of leverage you have.

Consistent rush fees also work as a training mechanism. Clients who learn that last-minute requests carry a real cost tend to plan better — or they book the rush and accept that it costs more. Either outcome works.