Client deadlines
What to do when a client wants work delivered earlier
Do not promise the new date right away. Check the unfinished work, approvals, people, cost, and quality first. Then give clear choices: keep the full job on the original date, deliver a smaller part sooner, or agree to rush work with new terms.
What to do now
- Ask why the earlier date matters.
- List every unfinished task.
- Check what you still need from the client.
- Decide whether scope, price, help, or review time must change.
- Offer two realistic choices.
- Confirm the chosen plan in writing.
Choose the closest situation
A quick decision table
| Situation | Best answer | Main risk |
|---|---|---|
| Small change and enough buffer | Accept and confirm the hour | Missing final checks |
| Same budget and less time | Reduce the first delivery | Unclear missing items |
| Extra hours or moved work | Add a rush fee | Unpaid overtime |
| Missing files or approval | Set a client cut-off | Waiting and rework |
| Testing would be skipped | Keep the safe date | A broken result |
What to do when the earlier date may be possible
Start with the real workload, not the pressure in the message.
1. What to do when a client asks only a few hours earlier
Check the remaining tasks and leave time for one final review. If the change will not hurt quality or another client, confirm the exact new hour. Do not say “no problem” until you have checked export and upload time.
Example: “I can deliver by 2 p.m. instead of 5 p.m. after one final check.”
2. What to do when a client asks one day earlier
Write down what is finished, what is open, and which approval you still need. Accept the new date only when every part has enough time. Make the client’s response deadline part of the deal.
Example: “The new date works if final notes arrive by noon today.”
3. What to do when the project is almost finished
Count the last jobs, including testing, naming, export, and delivery. These small tasks often take longer than expected. Give a firm delivery hour instead of saying the file will arrive “soon.”
Example: “The main work is done. I can send the checked files by 4 p.m.”
4. What to do when only a draft is needed sooner
Separate the draft date from the final delivery date. Mark the early file clearly as a draft so it is not published, printed, or sent to customers by mistake.
Example: “I can send a review draft tomorrow. The final date stays Friday.”
5. What to do when the client accepts a smaller first version
Define the smallest useful version and list what moves to phase two. Get approval before removing anything. A smaller delivery works only when both sides understand what is not included yet.
Example: “I can deliver the landing page Tuesday and the FAQ Friday.”
What to do when speed changes the price or scope
Less time usually means a smaller delivery, a higher price, or more people.
6. What to do when rush work needs an extra fee
Work out the real cost of overtime, moved work, or extra help. State the rush fee before doing the work. Do not hide it in the final invoice or use it as a punishment.
Example: “Tomorrow is possible with a $150 rush fee.”
7. What to do when the client will not pay a rush fee
Keep the original date or reduce the first delivery. Do not turn the client’s planning problem into unpaid overtime. Give two useful choices and let the client decide.
Example: “At the current price, delivery stays Friday. A smaller version can be ready Thursday.”
8. What to do when the budget cannot change
If the money cannot change, the time or scope must change. Ask which items matter most and move the rest to a later phase. Record the revised list.
Example: “Choose the three items you need first, and I will schedule the rest next week.”
9. What to do when another client would need to move
Do not break one promise to solve another request. Check whether the other project has a true buffer. If it does not, decline the rush or offer only a partial delivery.
Example: “I cannot move another confirmed delivery, but I can send a partial version Thursday.”
10. What to do when extra staff could help
Split only work that can be handed over cleanly. Use trusted help, protect private files, and keep one person responsible for the final check. Tell the client when a new person will see the project.
Example: “I can add a second designer and still review every file before delivery.”
What to do when client input is missing
Fast delivery needs fast decisions and complete material.
11. What to do when important files are missing
Send one checklist and one cut-off time. Explain that the early deadline starts only after all required files arrive. This prevents a slow stream of separate files.
Example: “I need the logo, final text, and photos by 10 a.m. Monday.”
12. What to do when approval is late
Name the exact decision that blocks progress. Give a simple approve-or-change choice. State that a late reply moves the delivery by the same amount of time.
Example: “Please approve option B by 3 p.m. A later reply will move delivery.”
13. What to do when several people give feedback
Ask for one decision maker and one combined feedback list. Separate messages create rework and make a rush date unsafe. Do not guess which manager has the final word.
Example: “Please send one final feedback list from Anna by noon.”
14. What to do when the brief is still unclear
Ask the few questions that change the result. Do not fill gaps with guesses just to look fast. A short call can help, but write down the final decisions afterward.
Example: “I need the final size, audience, and call to action before confirming Thursday.”
15. What to do when the client keeps adding material
Set a content freeze. Anything received after that time belongs in the next version. Without a freeze, the target keeps moving while you work.
Example: “I will use material received by 4 p.m. today. New items go into version two.”
What to do when quality or safety may suffer
Do not trade a usable, safe result for a date that only looks good.
16. What to do when there is no time for testing
Explain which tests would be skipped and what could go wrong. Offer a test build now and a checked release later. Never call an untested file final.
Example: “I can send a test build Friday. The checked release needs until Monday.”
17. What to do when legal or compliance review is required
Keep required legal, privacy, safety, or compliance review in the schedule. Ask the reviewer for priority or move the public launch. Do not remove a required check.
Example: “The design can be ready Thursday, but it cannot go live before approval.”
18. What to do when rushing would reduce quality
Name the exact loss. Say if there will be no proofread, no print test, or fewer checks. Clear facts help the client make a real choice.
Example: “Friday allows one proofread. Monday also allows a print test.”
19. What to do when the work includes a physical product
Include making, drying, packing, and shipping time. Check the carrier cut-off before offering express delivery. Some physical steps cannot be made faster.
Example: “The item can leave Thursday. Next-day shipping costs $40.”
20. What to do when a technical limit cannot be shortened
State the fixed limit without drama. Rendering, data transfer, manufacturing, platform review, or drying may need a set amount of time. Offer a preview while it finishes.
Example: “The export takes six hours. I can send still previews first.”
What to do when urgency appears suddenly
Find out what changed before rebuilding the whole schedule.
21. What to do when a client says it is urgent but gives no reason
Ask what happens if the date is missed. You do not need private details, but you need to know whether there is a fixed event, handoff, or only an internal wish.
Example: “What event or handoff depends on the new date?”
22. What to do when the client made a planning mistake
Stay neutral. Do not blame the client, but do not absorb every cost. Focus on the choices: later delivery, smaller scope, rush fee, or added help.
Example: “We can deliver a smaller version Friday or the full project Monday.”
23. What to do when the request arrives during a weekend
State your real availability and boundaries. If weekend work was not included, offer a paid rush slot or the next business-day plan.
Example: “I can start Monday, or offer a paid weekend slot if confirmed today.”
24. What to do when the request arrives near the end of the day
Do not promise while tired or before checking the files. Tell the client when you will return with a reliable answer. A careful answer is better than a fast failure.
Example: “I am checking the workload and will confirm by 5:30.”
25. What to do when the client contacts the whole team
Choose one person to answer. Team members should not make separate promises about price, scope, or time. Agree internally before sending a plan.
Example: “Sam will coordinate this and send one confirmed plan.”
What to do when the earlier deadline is not possible
A clear no works best when it includes the nearest safe option.
26. What to do when you must say no
Say no early, briefly, and without a long defense. Then give the earliest safe date. Do not leave the client waiting while hoping the schedule will improve.
Example: “I cannot complete it Thursday. The earliest safe delivery is Monday noon.”
27. What to do when only part can be delivered
Choose the part that helps the client’s next step. Label it clearly and list what remains. A partial delivery should solve a real need.
Example: “I can send homepage assets Friday so development can start.”
28. What to do when the client threatens to cancel
Stay calm and return to the agreement. Offer realistic choices, but do not promise an impossible date out of fear. Explain the cancellation steps if needed.
Example: “I can offer the two options above, or follow the cancellation terms.”
29. What to do when the contract has a fixed deadline
Read the deadline, change process, and client duties. Save the new request and your reply. Get professional advice in the correct location if a serious dispute may start.
Example: “Our agreement lists Monday. A formal change needs updated scope and approval.”
30. What to do after agreeing to early delivery
Send one change note with the new date, scope, price, client duties, and review rounds. Update the calendar and team. After delivery, note why the rush happened.
Example: “Confirmed: draft Thursday, feedback by 5 p.m., final Friday, rush fee $150.”
What not to do
- Do not say yes before checking the workload.
- Do not hide a rush fee until the invoice.
- Do not skip required safety, legal, or quality checks.
- Do not break another client’s confirmed deadline.
- Do not accept endless new material without changing the plan.
When to pause or get help
Pause when the new date could break a contract, expose private data, remove a required review, or create a safety problem. Ask a manager, qualified specialist, or lawyer in the correct location when the risk is more than a normal schedule change. Keep the request, options, and decision in writing.
Frequently asked questions
Should rush work always cost more?
No. A tiny change inside the current schedule may not need a fee. Charge more when the request creates extra hours, moves confirmed work, or needs extra people.
How much should a rush fee be?
Base it on the real cost and disruption. Use a clear rule in future proposals, such as a fixed fee or percentage for very fast delivery.
Can the original deadline stay?
Yes. A request is not a new agreement. The original date stays unless both sides accept a written change.
Should unfinished work be sent early?
Only when it has a clear purpose and is marked as a draft, preview, or test. State what the client may and may not do with it.