Practise phrases for renegotiating a deadline: flagging risk early, proposing alternatives, justifying with data, and confirming agreement.
0 / 10 completed
1 / 10
Which opener raises a deadline risk early and professionally?
Flagging risk early and neutrally invites collaboration on a plan instead of delivering a last-minute surprise.
2 / 10
Which sentence proposes a concrete alternative rather than just complaining?
Offering a specific phased alternative keeps the conversation solution-focused and gives the other side something to decide on.
3 / 10
Which phrase justifies the new timeline with evidence?
Grounding the request in data (velocity, measured effort) makes the renegotiation credible rather than subjective.
4 / 10
To confirm a renegotiated date is agreed by both sides, you say:
Explicitly confirming the agreed date prevents later misunderstandings and signals shared commitment.
5 / 10
Which framing keeps the deadline talk collaborative, not adversarial?
A 'how can we' framing treats the deadline as a shared problem, which builds goodwill and surfaces creative options.
6 / 10
Code Review Comment: 'This feature is significantly behind schedule. The original estimate was overly optimistic and doesn't account for the complexity of integrating with the legacy system.' Which response best addresses this concern while maintaining a professional tone?
The correct answer focuses on understanding *why* the original estimate was flawed. Options A suggests a quick fix without addressing the root cause, B directly asks for clarification and potential adjustment, which is crucial in renegotiation. Options C and D are overly negative and don't invite a productive discussion.
7 / 10
Slack Message: 'Seriously? This API endpoint is still taking 20 seconds to respond! We agreed this was a priority for the sprint.' Which of the following Slack messages would be most effective in initiating a conversation about a potential deadline shift?
The best approach is to frame the issue as a problem requiring discussion and potential solutions. Option A is demanding and unhelpful. Option B politely raises the concern and opens the door for collaboration. Options C and D are aggressive and unlikely to lead to a productive outcome.
8 / 10
PR Description: 'Implemented feature X. The initial estimate was 3 days. It took 7 due to unforeseen dependencies and the need for extensive refactoring.' Which statement would best justify a request to extend the release date?
Providing context for the extended timeline is key. This response clearly explains *why* the original estimate was inaccurate and highlights that quality and stability are priorities. Option A ignores the issue, Option C is dismissive, and Option B focuses on personal effort rather than objective reasons.
9 / 10
Standup Update: 'I've been working on the user authentication module. It's proving much more complex than anticipated and I'm currently behind schedule.' Which follow-up would most effectively facilitate a discussion about potentially adjusting the project deadline?
This question tests a proactive approach. The correct answer immediately seeks solutions rather than simply accepting the delay. It prompts a collaborative discussion about resource allocation and timeline adjustments—critical for renegotiation. Options A and D are passive, while Option B offers concrete next steps.
10 / 10
Code Review Comment (to Lead Developer): 'The proposed timeline for this microservice is aggressive. Given the dependencies on multiple teams and the need for thorough testing, I'm concerned we won't meet the original deadline without impacting overall project stability.' Which response best conveys your concern while fostering collaboration?
The correct answer prioritizes stability and suggests an alternative approach (a phased rollout) – a key element of negotiation. This demonstrates understanding while expressing concern about potential negative consequences. Options A is demanding, Option C is alarmist, and Option D avoids addressing the core issue.
What will I practise in "Deadline Renegotiation Language"?
This module focuses on Negotiation English — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Negotiation English exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around negotiation english — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Negotiation English exercises?
See the Negotiation English hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.