English for developers: deadlines and timelines
How to Negotiate Deadlines in English: Phrases and Strategies for Developers
Deadlines are negotiable. Most developers do not know how to push back without sounding difficult. This guide gives you the exact phrases to use.
Most developers think deadlines are final. So they say yes, work overtime, deliver late, or burn out. But the problem is not the deadline. It is not knowing how to negotiate it in English without sounding unprofessional or difficult.
Negotiating a deadline is a professional skill. Managers do it. Product owners do it. Senior engineers do it all the time. The difference between a junior and a senior is often not the code. It is the communication.
This guide gives you the exact phrases you need to push back on unrealistic timelines, flag risks early, ask for more time, and negotiate scope. All in professional English.
Always explain, never just say no
Siempre explica, nunca digas no sin más
There is a big difference between these two responses:
"I cannot do it by Friday." (sounds like a refusal)
"I can do it by Friday if we remove the API integration, or by next Wednesday with full scope." (sounds like a professional)
The key rule: always explain why and offer an alternative. An alternative can be a new date, reduced scope, or a reprioritization. Never say no without giving a path forward. That is what makes the difference between someone who sounds difficult and someone who sounds like a senior engineer.
How to ask for a deadline when none is given
Cómo pedir un plazo cuando no hay ninguno
Sometimes there is no deadline and you need to set one. This is just as important as pushing back. Here are the phrases to use:
Useful phrases
- "When do you need this by?"
- "What is the target date for this?"
- "Is there a hard deadline, or is this flexible?"
- "What is driving the timeline on this?"
- "Is this blocking anything else I should know about?"
How to flag a risk early (before it becomes a crisis)
Cómo avisar de un riesgo a tiempo
The best time to negotiate a deadline is before you miss it, not after. Flagging early shows professionalism. It gives your manager time to adjust. It builds trust.
Here is the difference between a developer who says nothing and one who flags early:
Useful phrases
- "I wanted to flag a risk on the timeline for X."
- "I am on track for the deadline, but I have a dependency on Y that could delay things."
- "I think we are at risk of missing Friday if we do not resolve the blocker on Z."
- "I wanted to loop you in early so we can adjust if needed."
- "I do not want to come to you at the last minute, so I am flagging this now."
Instead of
"Developer says nothing. On Friday: "I'm not done yet.""
Say
"On Tuesday: "I wanted to flag a risk. I have a dependency on the auth service that could delay things. I think we are at risk of missing Friday. Can we talk?""
Why it works: Flagging on Tuesday gives your manager options. Flagging on Friday gives them a crisis.
How to push back on an unrealistic deadline
Cómo rechazar un plazo poco realista
This is the most important section. Pushing back on a deadline is not insubordination. It is professional communication. Here are the phrases:
Useful phrases
- "I want to make sure I deliver quality work. To do that by Friday, I would need to cut scope. Is that acceptable?"
- "I can commit to X by Friday, but Y would need to move to next sprint."
- "With my current workload, I cannot hit that date without dropping something else. Can we talk about priorities?"
- "That timeline is tight. I can do it, but I want to flag the risk that it may not be fully tested."
- "I want to be realistic with you rather than commit to something I cannot deliver."
- "To hit Friday, I would need to reduce the scope. What is the minimum we need for the release?"
How to ask for more time professionally
Cómo pedir más tiempo de forma profesional
When you know you need more time, say it clearly and early. The pattern is: acknowledge, give a reason, propose a new date, and check in.
Here are the phrases:
Useful phrases
- "I underestimated the complexity of this. I need two more days to do it properly."
- "I hit an unexpected blocker with X. Can we move the deadline to Thursday?"
- "I want to deliver this right. Can I have until end of week?"
- "I made less progress than expected this week. I can have it ready by Monday. Is that okay?"
- "I need a bit more time on this. I can have it done by Wednesday. Does that work?"
The pattern
Acknowledge
"I made less progress than expected this week."
Give a reason
"I hit an unexpected blocker with the database migration."
Propose a new date
"I can have it ready by Monday."
Check in
"Is that okay?" or "Does that work for you?"
How to explain a delay after it happens
Cómo explicar un retraso cuando ya ocurrió
Sometimes you miss a deadline or you are about to miss it. How you communicate this matters a lot. The pattern: acknowledge, explain briefly, give a new date. Do not over-apologize. Do not make excuses. Just be clear and give a path forward.
Here are the phrases:
Useful phrases
- "I owe you an update on X. I am running behind because of Y. I expect to have it done by Z."
- "I should have flagged this sooner. The blocker on Y took longer than expected. I can deliver by Z."
- "This took longer than I estimated. Here is where I am and when I can have it done."
- "I am behind on X. I expect to finish by Thursday. I will keep you updated if anything changes."
Instead of
""Sorry, sorry, I am so sorry, I know this is terrible, I really tried but...""
Say
""I owe you an update. I am behind on the payment feature because of an unexpected issue with the API. I expect to have it done by Thursday. I will keep you posted.""
Why it works: Be clear and factual. Over-apologizing undermines your credibility. A new date and a brief reason is enough.
How to negotiate scope instead of time
Cómo negociar el alcance en lugar del plazo
Sometimes the deadline is truly fixed. In that case, negotiate what you deliver, not when. This is called scope negotiation and it is a critical skill for senior engineers.
Here are the phrases:
Useful phrases
- "We can hit Friday, but it will be the core feature only. The edge cases would come in the next sprint. Is that okay?"
- "I can deliver the MVP by Friday. The full version would need one more week."
- "To hit the deadline, I would need to drop the unit tests. I can add them next sprint. Does that work for you?"
- "We can ship on time if we descope X. That would be a separate story in the next sprint."
- "The critical path for the deadline is A and B. C and D can follow in the next release."
Phrases to avoid
Frases que debes evitar
Some phrases sound neutral but actually hurt your professional image. Here is what to avoid and what to say instead:
Instead of
""I will try.""
Say
""I will have it done by X." or "I cannot commit to that date — here is what I can do instead.""
Why it works: "Try" sounds uncertain. Give a concrete commitment or a concrete alternative.
Instead of
""It is not my fault.""
Say
""The delay was caused by X. Here is the new timeline.""
Why it works: Blame does not help anyone. Explain the cause factually and focus on the solution.
Instead of
""That is impossible.""
Say
""That timeline does not work for me. Here is what does.""
Why it works: "Impossible" sounds dramatic. Stay calm and professional. Offer an alternative.
Instead of
""I am too busy.""
Say
""I have a conflict with X. Can we adjust the priority or the timeline?""
Why it works: Everyone is busy. Name the specific conflict and propose a solution.
Instead of
""Maybe.""
Say
""I need to check my workload. Can I get back to you by end of day?""
Why it works: "Maybe" is not an answer. Give a concrete response or ask for time to give one.
Quick reference: phrases by situation
Referencia rápida: frases por situación
| Situation | Phrase |
|---|---|
| Asking for a deadline | When do you need this by? |
| Flagging a risk early | I wanted to flag a risk on the timeline for X. |
| Pushing back on a deadline | I want to be realistic with you rather than commit to something I cannot deliver. |
| Asking for more time | I hit an unexpected blocker. Can we move the deadline to Thursday? |
| Explaining a delay | I owe you an update. I am running behind because of X. I expect to finish by Y. |
| Negotiating scope | We can hit Friday with the core feature only. Edge cases would come next sprint. |
| When workload is the issue | With my current workload, I cannot hit that date. Can we talk about priorities? |
Related Articles
Ready to practice your English at work?
Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.
Try Lingua-e for free
Written by
Roxana LafuenteLingua-e's founder
Roxana Lafuente is a software engineer with 8+ years of experience. At the beginning of her career, even though she had already passed the First Certificate in English, she still froze every time she had to speak up in the daily standup. That was a gap nobody was fixing. After 2,000+ standups, she figured out what actually builds fluency: practice that looks like your real work. She built Lingua-e so other developers wouldn't have to take the long road to feel confident working in an international development environment.