A project is due Friday. The client promised feedback Tuesday but sends it Thursday. Now you’re rushing to finish in two days instead of five. Who pays for that compressed timeline? Many freelancers just work late and absorb the stress. Don’t. Delays caused by the client should either extend the deadline or come with a rush fee. Here’s how to set that up and manage it professionally.
Build Delay Protection Into Your Original Proposal
The best time to address delay billing is before the project starts. Make your timeline clear and note what happens if they delay.
In your proposal, write something like: “Project timeline begins once we receive your approval on the initial strategy. If feedback or approvals are delayed, the project timeline extends accordingly. Rush delivery to meet an accelerated timeline will incur a 25% rush fee.”
This isn’t threatening. It’s clear. The client knows upfront that delays have consequences.
You can also build in decision-making time. “I need approval on the initial direction by [date] so I can stay on schedule. If approval is delayed, the completion date will shift accordingly.”
Identify Delay vs. Extended Timeline
A delay is when the client causes the timeline to slip. They take three weeks to send feedback instead of two. They keep changing their mind. They’re slow to approve. Don’t confuse this with an extended timeline that was always part of the plan. If you said “I’ll have initial concepts in two weeks, you review them, and we deliver in six weeks total,” their two-week review isn’t a delay. That’s what you agreed to. But if you said “We’ll deliver in six weeks, starting now” and the client takes a month to send feedback, that’s a delay.
Offer Two Options for Client-Caused Delays
When a delay happens, you have two choices. Offer both.
Option one: Extend the deadline. “You sent feedback on Friday instead of Wednesday. No problem. I’ll adjust the completion date to [new date] so I can do quality work without rushing.”
Option two: Rush fee. “If you need it by the original date, I can prioritize it. That would require a 25% rush fee to account for the expedited work.”
Most clients will extend the deadline. Some will pay the rush fee if they need it urgently. Either way, you’re protected.
Don’t just absorb the delay and work late. That’s teaching the client that delays are free.
Calculate the Rush Fee Fairly
A 25% rush fee is standard. Some freelancers use 20%, others up to 50%. Pick what makes sense for your work. The fee covers the extra stress of rushing and the opportunity cost. Canceling other work to finish this faster costs you. Working overtime impacts your week. 25% is reasonable and not so high that clients will never pay it. Document it: “Rush fee for expedited delivery: [Original cost] × 25% = $X.”
Put Delays in Writing Before You Work Extra
Don’t just agree verbally to absorb a delay. When the client says “We’ll be late getting feedback,” write it down.
“I understand feedback won’t arrive until [date]. I’ll adjust the delivery date to [date] accordingly. Does that work for you?”
Get confirmation. Then when the delay happens, you have documentation that you addressed it proactively.
This also prevents arguments later. The client can’t claim they gave you feedback on time if you have an email saying they expected to give it late.
Handle Scope Creep Delays Differently
If the client keeps adding features or asking for revisions beyond what you quoted, that’s not a delay. That’s scope creep. Use a change order, not a delay fee.
“The project originally included two rounds of revisions. You’ve requested four. The additional revisions would require $X and would push delivery to [date]. Should I proceed with a change order?”
Scope creep is different from a client being slow to respond. Don’t conflate them.
Prevent Delays With Clear Checkpoints
Build decision points and approval deadlines into your project timeline.
“Week 1: Initial strategy due for your approval. Feedback deadline: Friday at 5pm. Week 2: I’ll implement feedback and deliver first draft. Week 3: Revision feedback due by Friday at 5pm. Week 4: Final delivery.”
When the client sees that their feedback deadline is critical to the timeline, they’re more likely to meet it. They understand the project can’t move forward without their input. Some clients will still miss these, and that’s when you use the delay process.
Invoice for Delays Clearly
When you invoice for a rush fee, be specific. Don’t just add 25% to the bill without explaining.
“Original project cost: $2,000 Rush fee (25% for expedited delivery due to client-delayed feedback): $500 Total: $2,500”
Or if they paid upfront and you’re sending a change order, note the rush fee there.
Track Clients With Chronic Delays
If a client has delayed multiple projects, build delay assumptions into your next proposal.
“Based on previous projects, I’m quoting a timeline with built-in buffer for feedback delays. The total project timeline is eight weeks, with a target completion of six weeks if feedback moves smoothly.”
Or just raise your rates and don’t work with them again.
Client-caused delays shouldn’t cost you time or money. Either they extend the deadline or they pay the rush fee.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
