Yes, if… Polite negotiating language for scope and deadlines
About this lesson
Students learn polite language for negotiating scope and deadlines, from What if we…? to Would that work for you?, in this B2 English for IT lesson plan.
- Grammar
- Proposals, offers with a condition and checks, with the form after each: How about scaling back? We could… if you… I was wondering if we could…
- Topic
- Cutting scope on a mobile release a week behind, at a fictional payments startup, with words such as a must-have, a deal breaker and scale back.
- Activities
- A story, a priority list and a team chat, a negotiation call, self-checking drills, a chat and role cards, then a message and a recording proposing a scope change.
What's inside
Chapter 1Warm-up: Must, Should, Could
Chapter 2The Story: Won't Have This Time
Chapter 3At Work: A Week Behind
Chapter 4Listen: Finding the Yes
Chapter 5Grammar: What If We…?
- Study the scheme: negotiating phrasesGrammar schemeTry it
- Sort the phrases into the correct columns: which move is it?Sort into columnsUnlock
- Fill in the gaps: rewrite each sentence with the words in bracketsFill in the gapsTry it
- Choose the best replyQuizUnlock
- Drag the words into the gaps: Jordan and Beatriz plan the testingDrag and dropUnlock
Chapter 6Speak Up: Yes, If…
Chapter 7Homework: Your Offer in Writing
- Read your phrase bankReal-life documentUnlock
- Do you remember? Choose the correct answerQuizUnlock
- Is the sentence correct? True or falseTrue or falseUnlock
- Match the beginnings and endingsMatchUnlock
- Write a message proposing a scope or deadline changeWriting, checked by the teacherUnlock
- Record your negotiation openingSpeaking, checked by the teacherUnlock
Vocabulary
12 words and phrases from the lesson, each with a picture and audio in edio.
+9 more with pictures and audio in the lessonMore words
- a win-win
- a concession
- a counteroffer
- a deal breaker
- a deadline extension
- negotiate
- push out
- scale back
- meet halfway
Grammar: negotiating language for scope and deadlines
A negotiation at work moves in four steps: propose, offer, check, then accept or refuse, and each step has its own fixed phrases. The phrases are short, but the form after them matters: How about takes -ing, and will never comes after if. Past forms such as I was wondering if we could… make a request softer without moving it into the past.
Negotiating: from “no” to “yes, if…”
Propose, make an offer with a condition, check, then accept or refuse: politely, but clearly.
Four moves and their phrases
To propose, use What if we…?, How about…? or Why don't we…?; to offer, We could… if you… or on one condition; to check, Would you be willing to…? or Would that work for you? Answer with That works for us or I'm afraid we can't go that far.
Phrases for every move
| What it does | Phrase | Example |
|---|---|---|
| Propose | What if we + present / past…? | What if we pushed the release out by a week? |
| Propose | How about + -ing…? | How about scaling back instead? |
| Propose | Why don't we + base form…? | Why don't we start with Android? |
| Offer with a condition | We could + base form … if you + present / past | We could keep the date if you moved partial refunds. |
| Offer with a condition | I / We can agree to that on one condition: … | I can agree to that on one condition: it goes first. |
| Check | Would you be willing to + base form…? | Would you be willing to ship a simple version? |
| Check | Would that work for you? | Two weeks later, behind a flag. Would that work for you? |
| Propose softly (past form, present meaning) | I was wondering if we could + base form… | I was wondering if we could do a follow-up release. |
| Say what you want, softly (past form) | We were hoping to + base form… | We were hoping to give Jordan a full testing week. |
| Accept | That works for us. / Deal. | Two weeks later? That works for us. |
| Refuse politely | I'm afraid we can't go that far. | Drop them completely? I'm afraid we can't go that far. |
A negotiation in four moves
proposeoffer with a conditioncheckaccept or refuse
What if we pushed it out a week? We could keep the date if you moved partial refunds. Would that work for you? That works for us.
The form after each phrase
How about takes -ing (How about cutting the calendar?), Why don't we the base form, and Would you be willing takes to. After if, use the present or the past, never will: What if we move the date? We could keep it if you dropped the calendar.
| After… | use | Example |
|---|---|---|
| How about | -ing | How about cutting the calendar? |
| Why don't we | base form | Why don't we ship it later? |
| What if we | present or past, never will | What if we move / moved the date? |
| We could … if you | present or past, never will | We could keep it if you drop / dropped the calendar. |
| Would you be willing | to + base form | Would you be willing to test it? |
| I was wondering if we | could + base form, not can | I was wondering if we could talk. |
Past forms with a present meaning
I was wondering if we could… and We were hoping to… are about now: the past form only adds distance, so the request sounds softer. Keep could after I was wondering if we. What if we pushed…? sounds more careful than What if we push…?, and both are correct.
Past forms, present meaning
I was wondering if we could… and We were hoping to… are about now, not the past: the past form only adds distance, so the request sounds softer. What if we pushed…? sounds a little more careful than What if we push…?, and both are correct. After if, don't use will for the future.
One call, from no to yes
The examples follow one call from proposal to deal: What if we pushed the release out by a week?, a counterproposal, an offer with a condition, a check, I can agree to that on one condition and, at the end, That works for us.
- What if we pushed the release out by a week?Kenji: a proposal
- How about scaling back instead?Beatriz: a counterproposal
- We could keep the date if you moved partial refunds to Won't have this time.Kenji: an offer with a condition
- Would you be willing to ship a simple version?Beatriz: checking
- I can agree to that on one condition: partial refunds go at the top of the next sprint.Beatriz: a yes with a condition
- That works for us.Beatriz: accepting
Typical mistakes
How about to cut the calendar?
How about cutting the calendar?
How about + -ing
What if we will move the date?
What if we move / moved the date?
no will after if
I was wondering if we can talk.
I was wondering if we could talk.
keep the past form: could
Would you be willing cutting the calendar?
Would you be willing to cut the calendar?
willing + to + base form
Try the negotiating language exercises
Try them yourself: these are the same exercises your students do in edio.
What's in the lesson
- 13 auto-checked exercises
- 2 games
- 2 teacher-checked tasks
- 3 real-life documents
- 1 article
- 1 grammar scheme
- 1 set of word cards
- 1 audio clip
- 1 picture
- 1 transcript
The main objectives of this lesson are to:
- propose a change politely: What if we pushed the release out by a week? How about scaling back instead?
- make an offer with a condition: We could keep the date if you moved partial refunds. I can agree to that on one condition.
- soften a request and check: I was wondering if we could do a follow-up release. Would that work for you?
- negotiate a scope or deadline change with a product owner, then accept or refuse: That works for us. I'm afraid we can't go that far.
Lesson 18 closes Stakeholders and scope, unit 6 of English for IT B2 · Beyond the Code, where learners practice saying no and finding a yes with people outside the team. It brings back lesson 16's diplomatic language and lesson 17's offers with as long as and unless, and it carries the unit's work task: negotiating a scope or deadline change with a product owner.
A wheel about cuts and deadlines opens the lesson, and twelve word cards with pictures and audio add a deal breaker, a deadline extension, push out and scale back. The story chapter explains MoSCoW and why “Won't have this time” is easier to accept than a flat no. Students read the MoSCoW list and a team chat about a week's delay, sort requests into the four groups and hear Kenji and Beatriz turn a no into a deal in an AI-voiced call. After the scheme, four self-checking drills run from sorting phrases by the move they make to a testing plan with words to drag in. Students then find a yes with Fatima in a chat and negotiate a release from role cards that give each player a goal and a limit.
Homework starts with a phrase bank and three exercises that check themselves, among them a quiz that also brings back lessons 16 and 17. Students then write a message proposing a scope or deadline change and record the opening of a negotiation, two tasks the teacher reviews.
- Grammar:
- negotiating language · What if / How about + -ing / I was wondering if we could
- Topic:
- prioritization · negotiation · scope and deadlines
Teaching tips
- Before the reading, sort a real backlog: give pairs eight requests from their own work, or a packing list, and four columns: Must, Should, Could and Won't this time. Arguing about what counts as a Must is the warm-up.
- Let pairs swap role cards after each deal, so that everyone has to ask for something and to refuse something politely. Give the product owner's card, with a date that can't move, to a confident student first.
- Play the call twice and listen for the moves: the second time, students raise a card for each proposal, offer with a condition, check and answer they hear.
- One-to-one, rehearse a negotiation from the learner's week: they bring a real deadline or request, you play the stakeholder, and you swap roles once they have reached a deal.
Liked it?
Teach the whole lesson in edio
26 exercises in 7 chapters, ready to teach. edio is an online platform for language schools and teachers: ready-made interactive lessons, live classes, homework and student progress in one place.
Start a free trial
7 days, no credit card.
Open the lesson
Find it in the library of 621 ready lessons. Teach it as it is, or copy any chapter into your own lessons.
Teach it live or as homework
Students work in their own accounts, in sync with you during the lesson, and the practice exercises check themselves.
The whole course: English for IT B2 · Beyond the Code
24 lessons at B2 for software teams, in American English. A year on at Kestrel Cloud, a fictional payments startup, Iryna and her team estimate work, write docs and postmortems, argue trade-offs, give demos and negotiate scope. Each lesson starts from a real case, from the Apollo 11 alarms to Conway's law.See the course
Unit 1 Planning and estimates
estimates and deadlines: approximating numbers, the future continuous and perfect, likelihood
Unit 2 Docs people read
specs and design docs: modals for requirements, participle clauses, plain English
Unit 3 Incidents and postmortems
telling an incident without blame: narrative tenses, the passive, the third conditional
Unit 4 Architecture and trade-offs
comparing options and recording decisions: contrast linkers, modals of deduction, mixed conditionals
Unit 5 Demos and tech talks
a clear structure on stage: signposting, cleft sentences, describing trends
Unit 6 Stakeholders and scope
saying no and finding yes: diplomatic language, as long as and unless, negotiating
Lesson 16Pay down the debtDiplomatic language for hard messages
Lesson 17Why meetings argue about the bike shedAs long as, provided, unless and otherwise
Lesson 18 · you're hereYes, if…Negotiating language for scope and deadlines
Unit 7 AI, security and ethics
AI tools, passwords and team rules: be used to and get used to, past modals of deduction, purpose linkers
Unit 8 Growing your career
feedback, retros and goals: phrasal verbs, reporting verbs, wish and if only




















