Estimates, Deadlines and Saying No (Politely): conditionals without if for negotiating scope

About this lesson

Conditionals without if are the grammar of this C1 English for IT lesson plan on estimates, deadlines and saying no politely.

Grammar
Ten ways to set a condition without if, such as provided, unless and in case, and mixed conditionals: If we had cut scope in Q2, we wouldn't be this late now.
Topic
Negotiating scope for a launch six weeks away when the job needs nine, with words such as buffer, hard deadline and critical path.
Activities
A three-option email to read, a negotiation to hear, self-checking drills, a chat that sets conditions and boxes to negotiate in pairs, then an email with two options and a recording.

What's inside

  1. Chapter 1Warm-up: “It's a two-day job,” they said

    • PictureUnlock
    • Spin the wheel and discussSpin the wheelUnlock
    • Study the words: estimates and scopeVocabularyTry it
    • Match what people say to what they meanMatchUnlock
  2. Chapter 2Reading: three options, one hard deadline

    • Read Priya's emailReal-life documentTry it
    • True or false? Check the emailTrue or falseUnlock
    • Choose the correct answer: Priya's optionsQuizUnlock
  3. Chapter 3Listening: a law with your surname on it

    • Listen to Priya and Daniel negotiateListeningTry it
    • Transcript, for the teacherUnlock
    • Choose the correct answer: who agreed to what?QuizUnlock
  4. Chapter 4Grammar: provided you read this first

    • Study the scheme: conditions without if and mixed conditionalsGrammar schemeTry it
    • Choose the correct option: which connector fits?Choose the optionUnlock
    • Fill in the gaps with the correct verb formsFill in the gapsTry it
    • Fill in the table: mixed conditionalsFill in the tableUnlock
    • Choose the correct answer: what does it mean?QuizUnlock
  5. Chapter 5Speaking: saying no without saying no

    • Choose the replies that set clear conditionsChatTry it
    • Open a box and negotiate with a partnerOpen the boxUnlock
  6. Chapter 6Homework: due Friday, no scope creep

    • Choose the correct option: Daniel's replyChoose the optionUnlock
    • Match the beginnings and endings of the sentencesMatchUnlock
    • Drag the words into the gaps: Priya's Slack messagesDrag and dropUnlock
    • Write an email: two options with conditionsWriting, checked by the teacherUnlock
    • Record your side of the negotiationSpeaking, checked by the teacherUnlock

Vocabulary

10 words and phrases from the lesson, each with a picture and audio in edio.

+7 more with pictures and audio in the lessonMore words

  • buffer
  • reconcile
  • de-scope
  • renegotiate
  • hard deadline
  • critical path
  • squeeze something in

Grammar: conditionals without if and mixed conditionals

A good tech lead rarely says a flat no: the answer is yes, on conditions. Learners set those conditions with ten connectors that replace if, keep the present after them for the future, and tie a past decision to today's problem with mixed conditionals, all in the language of one negotiation over a launch date.

Conditions without “if” and mixed conditionals

Set conditions like a tech lead, and link what happened then to where you are now.

Ten ways to set a condition

Provided, as long as and on condition that name a condition that must be met; only if allows no other; unless means if… not; even if says the result won't change; supposing imagines a situation; assuming states a working assumption; and but for means without.

MeaningConnectorExample
a condition that must be metprovided (that), providing (that), as long asWe'll ship in six weeks provided two engineers join this week.
a formal condition, often in agreementson condition thatFinance will help on condition that the manual checks end after a month.
this condition and no otheronly ifWe'll commit to the date only if the scope is frozen.
if … not, except ifunlessWe'll miss the launch unless we cut scope.
the result stays the sameeven ifEven if we work weekends, the full scope won't fit into six weeks.
as a precautionin caseKeep a feature flag in case the rollout goes wrong.
imagine a situationsupposing, suppose (that)Supposing Maya says no, what's plan B?
a working assumptionassuming (that)Assuming nothing else is added, option A takes nine weeks.
if not, then… (starts a new clause)otherwiseWe need to cut scope; otherwise, we'll miss the date.
without (+ noun)but forBut for Tom's rollback, the bug would have hit every merchant.

Future meaning, present tense

Like if, these connectors take the present for a future condition, so provided we will get is wrong. The will goes in the result: We'll hit the date provided we get two more engineers.

Future meaning? Use the present

After provided, as long as, on condition that, only if, unless, even if and in case, talk about the future with the present tense, not will: provided we get two more engineers (not “provided we will get”), in case the rollout fails (not “in case it will fail”).

In case is not if

If acts only when the thing happens: We'll roll back if the canary fails. In case acts now, as a precaution, whatever happens next: We'll keep the old job running in case the canary fails. No failure, no rollback; the old job runs anyway.

if: only when it happens

  • We'll roll back if the canary fails. (No failure, no rollback.)
  • Page Tom if the error rate spikes.

in case: now, as a precaution

  • We'll keep the old job running in case the canary fails. (We keep it anyway.)
  • Take your laptop home in case you get paged.

Unless, otherwise, but for, even if

Unless already holds the negative, so unless we don't cut scope is wrong. Otherwise starts a new clause after a semicolon or a period, but for takes a noun, and even if is a condition while even though is a fact.

  • unless already means “if … not”: We'll miss the date unless we cut scope. (not “unless we don't cut”)
  • otherwise starts a new clause; in careful writing, put a semicolon or a period before it. It never introduces the condition: not “Otherwise we cut scope, we'll miss the date.”
  • but for takes a noun, not a clause: But for Tom's rollback… (not “But for Tom rolled back”)
  • even if is a condition, even though is a fact: Even if Maya agrees, it's tight. Even though Maya agreed, it's tight.
  • supposing / suppose + present for a real possibility, + past for an unlikely one: Suppose we dropped GBP. Would that help?
  • In an unreal if-clause, were works for every person (If I were less busy…); was is fine in conversation.

Mixed conditionals: then and now

A past condition with a present result: If we had cut scope in Q2, we wouldn't be this late now. A present condition with a past result: If I weren't on call this week, I would have finished the estimate already. Each half keeps its own time.

Mixed conditional 1: past condition, present result

If + past perfectwould / wouldn't + verb

If we had cut scope in Q2, we wouldn't be this late now.

If Daniel had asked Priya first, they wouldn't be renegotiating now.

Mixed conditional 2: present condition, past result

If + past simple (true now)would / wouldn't have + past participle

If I weren't on call this week, I would have finished the estimate already.

If Daniel were more technical, he wouldn't have promised the full scope.

Typical mistakes

  • We'll hit the date provided we will get two more engineers.

    We'll hit the date provided we get two more engineers.

    Present, not will, after provided, unless, in case…

  • We'll miss the launch unless we don't cut scope.

    We'll miss the launch unless we cut scope.

    unless = if … not: no second negative.

  • If we cut scope in Q2, we wouldn't be late now.

    If we had cut scope in Q2, we wouldn't be late now.

    Unreal past condition: past perfect.

  • If I weren't on call, I would finish the estimate already.

    If I weren't on call, I would have finished the estimate already.

    Past result: would have + past participle.

More lessons on this grammar: Third and mixed conditionals lessons and exercises

Try the conditionals without if exercises

Try them yourself: these are the same exercises your students do in edio.

What's in the lesson

  • 12 auto-checked exercises
  • 2 games
  • 2 teacher-checked tasks
  • 1 real-life document
  • 1 grammar scheme
  • 1 set of word cards
  • 1 audio clip
  • 1 picture
  • 1 transcript

The main objectives of this lesson are to:

  • offer options with clear conditions when a date can't be met: EUR and GBP only: six weeks, provided two more backend engineers join us this week.
  • tell a precaution from a condition: Keep a feature flag in case the rollout goes wrong. Page Tom if the error rate spikes.
  • use unless, otherwise and but for correctly, with the present for the future: We'll miss the launch unless we cut scope.
  • link a past decision to the present with a mixed conditional: If Daniel had asked Priya first, they wouldn't be renegotiating now.

Lesson 4 opens the unit Shipping and incidents of English for IT C1 · Across the Company, on estimates, releases and outages. It extends as long as, provided and unless from English for IT B2 lesson 17 to ten connectors and brings back the mixed conditionals of B2 lesson 12; conditional inversion comes later in this course, in lesson 14. When a launch date can't move, the conditions are all that is left to negotiate, so the connectors carry the conversation.

A wheel of questions about bad estimates and padded numbers starts the lesson, then ten words with pictures and audio, from buffer and hard deadline to de-scope and squeeze something in, and phrases to match with what they mean. Students read the tech lead's email with three options for a big merchant's launch, then hear her negotiate with the product manager in an AI-voiced call. The scheme leads into four self-checking drills, among them a table that turns two facts into a mixed conditional. In the speaking chapter, students answer a late feature request in a chat, then open boxes and negotiate in pairs.

Homework has three self-checking exercises: the product manager's reply with connectors to choose, sentence halves to match, and the lesson's words to drag into Slack messages. Then students write a product manager an email with two options and their conditions, and record their side of a negotiation, both for the teacher to review.

Grammar:
conditionals without if · mixed conditionals
Topic:
estimates · deadlines · scope · negotiation

Teaching tips

  • Demand a date in five minutes: one student plays a manager who wants it now, and the other may answer only with a condition, such as provided…, as long as… or assuming…
  • Contrast in case and if with real deploys: ask who keeps the old version running in case a release fails, and who rolls back only if it fails, then have the class explain why both make sense.
  • With an in-company group, negotiate a real deadline: the team lists what a stakeholder has asked for, estimates it, and drafts two options with a condition each, the way the email in the reading does.
  • Turn project regrets into mixed conditionals: each learner names one past decision and its effect today, as in If we had frozen the scope in Q2, we wouldn't be late now.

Liked it?

Teach the whole lesson in edio

22 exercises in 6 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.

  1. Start a free trial

    7 days, no credit card.

  2. 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.

  3. 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 C1 · Across the Company

15 lessons at C1 for people who build software, in American English, with definitions instead of translations. The people of Kestrel Cloud, a fictional payments startup, write updates, reviews, RFCs and postmortems, explain tech to non-tech colleagues and negotiate scope. Real cases include the CrowdStrike outage and the xz backdoor.See the course

  1. Unit 1 Talking to the team

    async updates, code review and plain explanations: the future perfect, hedging, cleft sentences

    1. Lesson 1Async Stand-ups: Status Updates People Can Act OnFuture forms for status updates
    2. Lesson 2Code Review Without the DramaHedging in code review
    3. Lesson 3Explaining Tech to Non-Tech PeopleIt-clefts and wh-clefts
  2. Unit 2 Shipping and incidents

    estimates, releases and outages: conditionals without if, phrasal verbs, modal perfects

    1. Lesson 4 · you're hereEstimates, Deadlines and Saying No (Politely)Conditionals without if and mixed conditionals
    2. Lesson 5Release Day: Rolling Out and Rolling BackPhrasal verbs and their noun forms
    3. Lesson 6Incident! Learning from the CrowdStrike OutageModal perfects and narrative tenses
  3. Unit 3 Security and design

    advisories, trade-offs and RFCs: passive reporting structures, concession and contrast, nominalization

    1. Lesson 7Security Advisory: The xz BackdoorPassive reporting structures
    2. Lesson 8System Design: Every Choice Has a CostConcession, contrast and modified comparatives
    3. Lesson 9Writing an RFC That Gets ApprovedNominalization and formal register
  4. Unit 4 Docs, metrics and meetings

    READMEs, dashboards and follow-ups: participle clauses, describing trends, reporting verbs

    1. Lesson 10Docs People Actually ReadReduced relative clauses and participle clauses
    2. Lesson 11Metrics, Dashboards and SLOsPrepositions with numbers, trends and approximation
    3. Lesson 12Meeting Notes and Follow-upsReporting verbs and their patterns
  5. Unit 5 Retros, interviews and AI

    looking back and ahead: wish and would rather, inversion, formal obligation and permission

    1. Lesson 13The Retro: What Went Wrong This QuarterWish, would rather and it's high time
    2. Lesson 14The Interview: Selling Your AchievementsInversion for emphasis
    3. Lesson 15AI at Work: Writing the Team's RulesObligation and permission in formal rules

Questions about this lesson

How do you use "supposing" in English?
Supposing, or suppose, asks someone to imagine a situation and its result. Supposing Maya says no to the extra engineers, what's our plan B? With the present, the situation is a real possibility; with the past, it's less likely: Suppose we dropped GBP. Would that help? It usually opens a question, so it lets you explore options in a negotiation without committing to any of them.
What are conditionals without if?
Conditionals without if set a condition with another connector, such as provided, as long as, unless, in case, supposing or but for. Each has its own meaning: We'll commit to the date only if the scope is frozen. Finance will help on condition that the manual checks end after a month. The C1 lesson Estimates, Deadlines and Saying No (Politely) on edio.ai sets out ten such ways in one table, with a meaning for each.
What does "but for" mean?
But for + a noun means without this, or if it hadn't been for this. But for Tom's rollback, the bug would have hit every merchant. The result often takes would have, for something that didn't happen. It needs a noun, never a clause: not But for Tom rolled back. The gap-fill in Estimates, Deadlines and Saying No (Politely) on edio.ai includes one: But for Lena's security review last month, we would have shipped a serious bug.
Can a mixed conditional go from the present to the past?
Yes: a present condition can have a past result, with if + past simple and would have + past participle. If Priya weren't on call right now, she wouldn't have missed this morning's planning meeting. She is still on call; the meeting is over. The usual mix runs the other way: If someone had documented the old payout API, we wouldn't be guessing how it works now.
What's the difference between "in case" and "if"?
In case means as a precaution, not on condition: you act now, whether or not the thing happens. Take your laptop home in case you get paged means take it tonight, paged or not. Page Tom if the error rate spikes means page him only when it spikes. Both take the present for the future: I'd keep the new payouts behind a feature flag in case the first real transfers fail.
Is "provided that" more formal than "as long as"?
Slightly: both name a condition that must be met, but provided (that) sounds more formal, and as long as is more common in speech. We'll ship in six weeks provided two engineers join this week. I'm happy to give you a ballpark figure, as long as nobody treats it as a promise. On condition that is more formal still, typical of agreements. All three take the present for the future.
How do you use "assuming" in an estimate?
Assuming (that) states the working assumption an estimate rests on: Assuming nothing else is added, option A takes nine weeks. It tells listeners what would change the number, so a date doesn't turn into a promise by accident. Use the present for the future after it, and name the assumption you're least sure of: Then let's say the end of the month, assuming their finance team signs off on the email format by Friday.
What does scope creep mean?
Scope creep is requirements that keep growing after work has started, usually one small request at a time: Every “tiny” request from Sales is classic scope creep. Teams stop it by agreeing to freeze the scope, which means accepting no new requirements: The scope is frozen from Friday. No more scope creep. After the freeze, a new request means something else has to be de-scoped, or the date moves.
What does it mean to pad an estimate?
To pad an estimate is to quietly add extra time to a forecast, just to be safe: Are you padding that estimate? A buffer is different: spare time planned in openly for surprises. The tech lead's email in Estimates, Deadlines and Saying No (Politely) on edio.ai names hers: That includes a one-week buffer, and no, it isn't padding. Naming the buffer keeps an estimate honest.
How do you say no to your boss politely?
Say yes to part of it, on a clear condition, and offer a choice instead of a refusal: Possibly, provided we keep it simple: one plain-text email per payout, no custom templates. If it will slow other work, say so: It will, unless something else moves out of this sprint. Then suggest what could move. The chat in Estimates, Deadlines and Saying No (Politely) on edio.ai puts an easy yes and a rude no among its wrong replies.
How do I teach conditionals without if to C1 professionals?
Teach the connectors through the pairs learners confuse: in case and if, even if and even though, unless and if… not. Then set a real negotiation around a deadline that can't move, and ask for two options, each with one condition and one precaution. Finish with a mixed conditional about how the team got there: If we had split phase 2 into smaller releases back in Q2, we wouldn't be choosing between options now.
Are there interactive exercises for conditionals without if?
Yes: verb gap-fills and chats show at once whether a condition is built right. Without an account, this page plays four parts of Estimates, Deadlines and Saying No (Politely), a C1 English for IT lesson on edio.ai: the tech lead's email with three options, her negotiation with the product manager, a gap-fill of verb forms after provided, unless, in case and but for, and a chat that meets a late feature request with clear conditions. The rest is locked.

Teach this lesson with your students

No credit card required