Estimate disruption, not just production hours
Acceleration can require rearranging other commitments or arranging additional capacity. Price those real effects without claiming a universal market surcharge. If safe delivery is not feasible, decline or reduce scope.
Keep dependencies in the quote
A rush date depends on faster decisions as well as faster production. Make the asset deadline, authorized approver, and response window part of the same approval record.
Copy-and-customize preview
Free editable sample
No purchase or email required.
RUSH ESTIMATE — [Project / request] Standard scope and date: [deliverables / date] Requested accelerated date: [date and timezone] Feasibility confirmed: [yes/no, by whom] Additional capacity or displaced work: [tasks] Scope retained / removed: [items] Acceleration fee: [amount and currency] Revised total: [amount and currency] Client assets and approval due: [deadline] Missed-dependency fallback: [revised schedule process] Approve estimate and conditions by: [deadline] No acceleration begins until written approval.
| Field | Why it matters | Example |
|---|---|---|
| Feasible deadline | Avoids promising an impossible outcome. | Friday delivery requires final assets by Wednesday noon. |
| Disruption | Makes the price basis clear. | Rescheduled production and an additional review slot. |
| Fallback | Defines what happens if inputs slip. | Reconfirm availability rather than preserving the rush date automatically. |
Use it in four steps
- Check feasibility before quoting
- Identify displaced work and extra coordination
- Quote the acceleration and dependency deadlines
- Reserve the exception only after written approval
Customization checklist
- State timezone and client-response cutoff
- Do not promise availability that is not reserved
- Offer a reduced-scope alternative when feasible
Common mistakes to avoid
- Using an arbitrary percentage as an industry rule
- Accelerating without shortening client response windows
- Ignoring quality and testing constraints
Frequently asked questions
- What percentage should a rush fee be?
- There is no universal percentage. Estimate capacity, disruption, coordination, and risk for this request and agree a specific price.
- What if the client misses the rush input deadline?
- Apply the agreed fallback and confirm the next feasible slot. Do not guarantee the accelerated date after its stated dependencies fail.
Continue with the next decision
Rush Fee Message for Freelancers
Explain that accelerated delivery is subject to capacity, an expedited fee, and faster client approvals; then present one feasible option.
Contract clause libraryRush Work Clause and Expedited Fee Wording
A rush-work clause makes accelerated delivery optional, capacity-dependent, and subject to a written expedited fee and compressed review schedule.
Free editable artifactFreelance Change Order Form Template
A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.
Charge for Extra WorkBuild a Rush Quote from Capacity and Disruption, Not a Universal Percentage
Estimate the resources needed to accelerate delivery and the real disruption to existing commitments. There is no universal rush percentage; a feasible quote also needs input deadlines and a fallback.
Change Order TemplatesSend a Conditional Rush Offer When Client Inputs Are Still Missing
A rush offer should remain conditional until required assets and approval arrive. State the input cutoff and the schedule-reconfirmation process if that cutoff is missed.