A client sits on feedback for five weeks. When they finally come back, they want the original deadline honored anyway — which now means compressing what was supposed to be a comfortable final stretch into a scramble. The freelancer absorbs the schedule pressure the client actually created.
Why this delay cost usually goes unbilled
"You asked for 3 extra changes" is concrete. "Your five-week delay meant I had to rearrange my other client work and rush the final stretch" is real, but fuzzier — and fuzzier costs are much easier to let slide without a clean way to quantify them.
When it's fair to bill for a delay
- Rush fees for compressed timelines the client caused. If hitting the original deadline now requires working evenings or reprioritizing other clients, that's a legitimate rush cost.
- A delay clause tied to the calendar, not to blame. Frame it structurally: feedback received after X days pushes the final date by the same number of days, unless a rush fee applies to hold the original date.
- Retainer or day-rate work where idle time still has a cost. If you've blocked calendar time and it's unused due to client delay, a holding fee can be reasonable.
What's usually not fair to bill for
Charging retroactively for a delay that wasn't discussed beforehand tends to feel punitive — the client had no chance to make an informed choice (compress timeline and pay more, or accept later date for free).
A real tiered structure, not a guess
- Shortened by 1–2 weeks: ~25% above standard rate
- Shortened by 3–5 days: ~50% above standard rate
- Under 48 hours / same-day: Up to 100% (double rate)
Podcast editors often use similar tiers (24hr ~30%, same-day 50–75%). Design/brand work often prices rush fees as 25–50% of the whole project fee since compression affects the entire creative process.
Checking whether a rush fee is actually worth it
A rush fee should cover more than extra effort — it should cover displaced revenue. Example: 6 hours at $75/hr = $450 displaced. A $600 rush fee leaves $150 incremental gain after subtracting displaced revenue. If the other work is lost entirely, the true cost is higher.
A real risk worth knowing before charging a premium
Accepting a rush fee can be read as an implicit promise the compressed deadline is achievable. Missing a rush-priced deadline is generally viewed more seriously than missing an ordinary one, potentially exposing you to claims of material breach. Only quote a rush fee if you're genuinely confident you can hit it — and be honest if you can't. This is general information, not legal advice.
A worked example
A video editor's client sat on footage approval for 9 days, then asked to still hit the original launch date (3-week timeline compressed significantly). Other booked work worth ~$300 would need to shift. A 25% premium on a $2400 project = $600 rush fee; $600-$300 = $300 real incremental value — reasonable if the other work can be rescheduled. If unmovable or deadline couldn't be met reliably, better to accept the delay-adjusted date instead.
Scripts for introducing this without it feeling like a penalty
Just so it's clear upfront — if feedback comes in later than expected, I'll typically shift the final date rather than compress my other work. If holding the original date matters, a rush fee can keep us on track instead.
Since feedback came in [X] days later than planned, I can either move final delivery to [new date], or hold the original date for a rush fee of [$X] given the compressed timeline. Which works better?
Making the delay itself undeniable
A timestamped record is key. A rolling timeline engine that logs overdue days and shifts downstream dates automatically makes "X days late" an objective fact rather than a negotiation point.
FAQ
Is a delay clause something to add to every contract, or only some?
Worth including any time a hard deadline matters — for ongoing or deadline-flexible work, it's less critical, but for anything tied to a launch date, event, or external commitment, it's worth having in writing from the start.
How is a rush fee typically calculated?
Common approaches use a tiered structure based on how compressed the timeline is: roughly 25% for a schedule shortened by 1-2 weeks, 50% for 3-5 days, and up to 100% (doubling the rate) for under 48 hours — adjusted based on what other work would actually need to be displaced to accommodate it.
What if the client argues the delay wasn't really their fault?
This is exactly why a neutral, timestamped record helps — it turns a subjective disagreement about blame into an objective conversation about dates, which is usually much faster to resolve.
Does charging for delays damage long-term client relationships?
Handled proactively and framed as a structural policy rather than a personal accusation, most clients respond reasonably — the relationships that suffer are usually ones where the charge appears as a surprise after the fact.
Does accepting a rush fee create any risk for the freelancer?
Yes, and it's worth knowing before agreeing to one — charging a premium for a compressed timeline can be read as an implicit promise that the tighter deadline is achievable, which may create a heightened obligation to actually hit it. Missing a rush-priced deadline is generally viewed more seriously than missing an ordinary one, potentially exposing the freelancer to claims of material breach. This is general information, not legal advice.