Skip to main content
Out of Scope

Is a rush deadline out of scope?

Yes — a mid-project deadline acceleration is out of scope unless your contract explicitly accommodated shifting timelines. The work itself may still be the original work; what's changed is its cost to deliver.

Why this answer

Timeline is one of the three dimensions of scope, alongside deliverables and fee. When any of those three shifts mid-project, the other two have to shift with it. If a client moves the deadline in by two weeks, they're asking you to compress delivery, which usually means working evenings and weekends, dropping other client work, or bringing in help. Each of those carries a real cost that wasn't in the original fee. The clean framing: 'The deliverable is the same; the timeline is different; the fee reflects the timeline.' Clients sometimes frame it as 'just moving the date,' but timing is an asset — an early delivery costs more than an on-time one because you're paying to compress your own schedule.

When the answer flips

If your contract includes a timeline-compression clause or a rush-rate schedule, the acceleration is covered but the fee scales automatically. If the client is moving the deadline out — later rather than sooner — that's usually In Scope, though it may trigger other issues (payment timing, your own availability, dependencies on other work). If the acceleration is small (a few days on a multi-month project), it's often absorbable without a rush fee and the goodwill of flexibility is worth more than the marginal rate. The sharp flip toward Out of Scope is anything that compresses the timeline by 25% or more, or anything that forces weekend/evening work you wouldn't otherwise do.

What to do next

Confirm the new deadline is real, not aspirational. 'Can we deliver by the 15th?' and 'We need to deliver by the 15th' are different conversations. Once confirmed, quote the rush rate. A simple schedule: 25–50% fee premium for a 25–50% compression, scaling up for tighter windows. Be explicit that the premium pays for your rescheduling and the risk of concurrent-work conflicts. Offer a minimum of two options — the rush rate, or a renegotiated deliverable (drop a feature, ship a simpler version) that fits the original timeline. Clients often prefer the second when they see the first priced fairly.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

What's a reasonable rush rate to quote?+

25–75% over your standard rate, depending on compression. 25% for modest acceleration (10–25% less time), 50% for significant compression (25–50% less time), 75%+ for extreme (50%+ less time). Above 75% compression, consider declining unless the fee is truly compelling — the quality risk is real.

The client says they've always had this deadline — I just didn't hear it. What now?+

Check your original project brief, SOW, or contract. If the earlier deadline is documented, the client is mistaken and the rush fee is warranted. If it's not documented, you're in an 'ambiguous original scope' situation — fairness suggests splitting the difference: partial rush rate, or free acceleration in exchange for an upfront deadline clause on the next engagement.

Should I charge the rush rate if the compression was caused by the client's own delays?+

Yes — especially in this case. A client who took three weeks to approve a phase and now wants final delivery on the original date has consumed your buffer time, and the rush fee reflects the cost of getting it back. Name the dynamic directly: 'The timeline shifted because feedback took longer than planned; compressing the back half to hit the original date is rush work.'

What if I can actually deliver on time without extra effort?+

Then there's no rush fee to charge — the scope hasn't actually changed from your side. Be careful though: 'delivering on time without extra effort' often means dropping quality passes, review cycles, or buffer time you were planning to use. If the client is moving the deadline in, make them choose between rush rate and explicitly reduced quality.

How do I write a clause that prevents these disputes?+

Specify (1) the delivery date in the contract, (2) a buffer window on either side, (3) a rush-rate schedule keyed to percentage of timeline compression, and (4) your right to renegotiate the timeline if the client causes material delay in their own feedback. Four sentences again.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide