Setting Conditions in English: Practice Negotiation With The Blacklist
You know the grammar of if. Then a real negotiation starts, and suddenly your sentence sounds either vague—“maybe if you can…”—or much harsher than you intended.
The useful skill is not memorizing first, second, and third conditionals in isolation. It is learning to make the condition, your controllable action, and the result easy to hear.
The Condition Map
Good condition = clear trigger + controlled action + honest result.
1. Deal conditions: make the exchange visible
deal conditionB1
It's yours if you let me go.
The grammar is compact: benefit + if + requested action. The scene context is high-stakes, so don’t copy the bargain itself. Copy the structure into a safe negotiation.
Writer-original vendor version: “We can approve the full amount if you can deliver by Friday.”
verify first
How do I know you still have it?
A condition is only useful if the promised value is real. Before accepting, ask what confirms the other side can deliver.
Writer-original: “Can you confirm the stock is reserved before we sign?”
Fine. I'll take it.
Acceptance can be short once the terms are genuinely clear. In professional settings, add the condition back if there is any chance of ambiguity: “That works for me, provided the support hours are included.”
- No, no deal!
You also need a clean exit. A safer professional version is: “I can’t agree to that condition.” Then say what would make the deal workable.
2. IF versus WHEN: possibility versus expectation
Now, if he doesn't show up,
If presents the trigger as a condition: it may happen, or it may not. That makes it the natural choice for uncertain delivery, approval, timing, or performance.
and when she does,
When presents the future event as expected. You are not asking whether it happens; you are organizing what follows once it happens.
| Meaning | Writer-original negotiation English |
|---|---|
| Uncertain condition | “If legal approves the clause, we can sign Friday.” |
| Expected milestone | “When legal sends the final wording, I’ll forward it to you.” |
| Don’t pretend certainty | If approval is genuinely uncertain, don’t say “when legal approves.” |
3. Sequence conditions: this first, then that
after
After I surrender you to the court
After sets order. One action must happen before the next one. In ordinary work, this is perfect for approvals, payments, deliveries, and handoffs.
Writer-original freelance version: “After you approve the final draft, I’ll issue the remaining invoice.”
optional condition
That said, if time permits,
This is softer: the extra action is optional and depends on available time. It is useful when you want to distinguish the core commitment from the nice-to-have.
Writer-original: “The bug fix is the priority. If time permits, we’ll also clean up the old settings screen.”
4. Boundaries: NOT UNTIL and UNLESS
boundaryB2
not until you tell me what's going on.
Not until means the action is withheld before a requirement is satisfied. For professional use, make the boundary about your action—not control over the other person.
Writer-original: “We won’t deploy until the rollback procedure has been tested.”
unless
So unless you go home
Unless is roughly if not. It identifies the exception that changes the result.
Writer-original: “Unless the scope changes, the current estimate still stands.”
Easy repair:
Confusing: “Unless you don’t approve it, we can start.”
Clearer: “If you approve it, we can start.”
Use unless when it genuinely makes the exception easier to understand—not because it sounds fancy.
5. Planning conditions: condition + expected result
so if we push on, we should
The important word here is should. It signals an expected result rather than a guaranteed one.
Writer-original project version: “If QA finishes by noon, we should be ready for the 4 p.m. review.”
or fight extradition. In either case...
In either case is a useful compression tool: two different paths, same result. In negotiation, it stops you repeating the consequence twice.
Writer-original: “You can pay annually or quarterly. In either case, onboarding support is included.”
Commitment, capability, or forecast?
This is where otherwise-good negotiators accidentally overpromise.
| Pattern | What it means | Use it when… |
|---|---|---|
| If X, I can Y | Capability / offer | You have the ability or authority to do Y. |
| If X, I will Y | Commitment | You control Y and genuinely intend to commit. |
| If X, Y should happen | Expectation | The result depends on factors beyond your full control. |
What not to promise: don’t use will for an outcome controlled by a courier, another department, a regulator, the weather, or the universe’s general sense of humor.
Condition Card: build the sentence before you say it
| IF / WHEN trigger | What I control | What I expect | What I need confirmed |
|---|---|---|---|
| Vendor delivers by Friday | I can approve payment Monday | Launch should stay on schedule | Written delivery date |
| Client locks scope today | I can hold the current price | Work should finish this month | Final feature list |
Now speak only what you can defend: “If you lock the scope today, I can hold the current price. We should still finish this month, but I’d like the final feature list in writing.”
High-pressure recovery language
If your condition came out too strong, vague, or absolute, repair it immediately.
- Clarify: “Can I check the condition we’re agreeing to?”
- Rephrase: “Let me rephrase that. I can commit to the review date, not the final approval date.”
- Separate expectation from promise: “I expect it Friday, but I can’t promise that until the carrier confirms pickup.”
- Ask for reciprocity: “If we extend the deadline, what can you confirm on scope?”
Repair the Deal
“If you help us, everything will be done Monday.”
Problem: “everything” is vague and “will” may overpromise.
Writer-original repair: “If you send the final assets by Thursday, I can complete the build Monday. QA should finish Tuesday.”
“We can refund you if the issue is bad enough.”
Problem: the trigger is subjective.
Writer-original repair: “If the replacement fails the same test within 14 days, we can issue a refund.”
“I’ll lower the price if you give me more work later.”
Problem: future work is undefined.
Writer-original repair: “I can reduce this project by 10% if we sign the three-month support package at the same time.”
Five original negotiation drills
Vendor scope
“If the API work is included in the quoted scope, we can approve the proposal today.”
Project deadline
“If design signs off Wednesday, engineering should have enough time for Friday’s build.”
Freelance contract
“I’d be willing to add one revision round if the feedback comes back in a single document.”
Team scheduling
“Unless the incident call runs late, I’ll join the planning session at 3.”
Service negotiation
“If you can’t restore the service today, could we agree on a credit for the downtime?”
Condition or threat?
A professional condition describes exchange, sequence, limits, requirements, or consequences you legitimately control. A threat tries to create compliance through fear.
“If you send the files by noon, I can include them in today’s review.”
Condition. Clear trigger, controllable action, no intimidation.
“Do what I want or you’ll regret it.”
Threat. It is intimidation, not negotiation. Don’t borrow this shape from crime drama.
“We won’t sign until the liability clause is clarified.”
Boundary. It states what your side will withhold and what needs clarification.
Three useful negotiation moves from the episode
A proposal.
Sometimes the cleanest move is simply to label what comes next. In normal business English: “I have a proposal.”
if you might have a case.
The combination of if and might avoids assuming the answer. That is useful when you are exploring an option rather than demanding one.
Wouldn't say even if we did.
Even if means the condition does not change the result. Writer-original workplace version: “Even if we finish early, we still need security approval before release.”
With FunFluen, you can replay a negotiation scene and mark the trigger and result separately: if/when/unless on one side, consequence on the other. Save the safe transferable structure, then replace the scene content with your own vendor, deadline, contract, or scheduling scenario.
The takeaway
Strong condition-setting English is not about sounding tough. It is about making the logic visible.
Trigger → what I control → what follows. Use if for uncertain conditions, when for expected milestones, unless for exceptions, and not until for boundaries. Then make sure your promise is no bigger than what you actually control.
Explore more language-learning guides in Learn English.