How to ask for a deadline change
Discuss a deadline early: keep the date and reduce scope, or move delivery. Examples with a manager and a client, plus a 30-second rehearsal.
Say what is ready, what will not fit the deadline and why. Offer two specific options: less work by the original date, or all the work by a new date. Ask which matters more, then confirm the agreed scope and date in writing.
The Persuasion demo lets you practise a proposal and a reply to an objection using a general task about shortening a meeting. It is not a dedicated deadline scenario.
Open the persuasion demo Open this trainer on the home pageYou start the timer; the website does not record your voice.

- Ready
The main pages are laid out
- Remaining
Two new sections and testing
- Two options
Core pages on 28 October or all on the 30th
- Agreement
Confirm scope and date in writing
There is still time before delivery, but you can see that the full scope will not fit. It feels awkward to raise it, and you want to “do a bit more first”. The useful moment to talk is while the other person still has options. Prepare facts and alternatives, even if you are still refining the estimate.
What to check before the conversation
Check the original agreement: what you are delivering, by which date, and what counts as done. List completed work, remaining work and dependencies on other people separately. The reason should help reach a decision, not become a long defence. If your estimate was wrong, say so; do not invent an external blocker.
Do not guess a new date. If the estimate depends on a colleague’s answer, say: “I will confirm the date today after checking the designs.” Distinguish a commitment from a preliminary estimate, or the new deadline may become the next problem.
Dialogue 1: keep the date, reduce the scope
All examples below are fictional. Their dates and circumstances are for practice; use only real information in your own conversation.
Employee: “The main pages are ready. The two sections added yesterday still need layout and testing. I can deliver the main pages on 28 October and the new sections on the 30th, or deliver everything together on 30 October. Which do we choose?” Manager: “We have a partner demo on the 28th.” Employee: “Then I suggest showing the main pages without the new sections. I will list what that version includes in an email. Would that scope work?”
The demo date stays, but “ready” now has clear boundaries. Reducing scope means agreeing on exactly what is left out, not quietly dropping work. If the demo is pointless without the new sections, this option does not work; find another together.
Dialogue 2: keep the scope, move client delivery
Consultant: “The first-quarter analysis is ready. The second-quarter data arrived today, and checking it needs two more working days. I propose the full report on 30 October instead of the 28th, or the completed part on the 28th and the rest on the 30th.” Client: “I need one document for a meeting on the 29th.” Consultant: “Understood; you need the full scope before my estimate. I can send the completed section and a list of unchecked data today, but cannot call that data verified. Let us clarify which conclusions the meeting needs and whether the rest can follow later.”
The client does not have to accept a delay. There is no agreement yet in this dialogue: the consultant is finding out what the meeting actually needs. Do not close with “agreed, then” until both sides confirm the same option.
Make the agreement unambiguous
After the conversation, send a brief confirmation: “I will deliver main pages A and B by 28 October; sections C and D follow on 30 October and are excluded from the first version.” Add a time and time zone if they matter. Ask the other person to confirm the scope. Discussing how to phrase a request does not itself change contractual terms.
If the deadline has already passed, do not call this advance notice. Say what is unfinished now, what you can deliver and when you will update the remaining estimate. “Just a little longer” gives the other person nothing to plan around.
A 30-second request and a reply to refusal
Choose a real task or invent a clearly labelled practice scenario. Write the completed part, remaining work and two options with dates. Say the request in 30 seconds. Then answer “The date cannot change” by asking which work must be included by that date. Repeat the request with that answer in mind, without promising the impossible.
- Are the dates and contents of each version specific?
- Is the reason true, and does the new estimate have a basis?
- Can the other person choose between clear options?
- Have you distinguished a proposal from an agreed decision?
For a brief team update, see the meeting article below. If the issue is the manager’s decision itself, use the disagreement article. Here the aim is to agree what will be ready and when.
Continue in the Persuasion demo: it offers a general conversation about shortening a meeting, without audio recording or AI feedback. Then use the link to open Ritora in Telegram and choose persuasion training, the situations section, in Practice. Choose a suitable situation from the available list. Check access and remaining feedback attempts before recording. The app interface is in Russian.
Try it aloud
Try a relevant 30-second exercise. Start the timer with the button; this website does not record your voice.
Open a 30-second exerciseSuggest shortening a team meeting to 20 minutes. Explain why that would be enough.
An original teaching example. Speak aloud: there is no recording or automated assessment here.
Did you include a benefit for the team and a specific suggestion?
Start with a benefit for the listener. Give a reason and finish with a specific suggestion.
Read the task first. The timer starts when you press the button.
Open Ritora in Telegram (RU)One small attempt
