Prison Break Conditionals: Discuss Plans That Could Go Wrong
Explaining the plan is easy when everything goes right. The hard part is saying what happens if the train is late, the client says no, the test fails, or one person never confirms.
That is where useful conditionals live. You do not need a grammar lecture first. You need a way to branch a plan without turning it into a fog of maybe, perhaps, probably, somehow.
Base plan → Risk trigger → If-clause → Consequence → Backup
Example: “We’ll leave at six. If traffic is heavy, we might arrive late, so we’ll call the hotel from the car.”
1. Start with the base plan before you branch
If you begin with every possible problem, the listener cannot tell what is actually supposed to happen.
Foggy: “Maybe we’ll go Friday, but if the weather is bad maybe Saturday, unless Anna can’t come, and then maybe next week…”
Clear: “The plan is Friday. If the weather is bad, we’ll move it to Saturday. If Anna can’t make Saturday either, we’ll choose a new date.”
The conditional should modify a visible plan. It should not replace the plan.
2. Use the practical future pattern
For a realistic future possibility, the most useful pattern is:
If + present, will/can/might + base verb
Writer-original: “If the test fails, we’ll fix the bug tonight.”
Writer-original: “If the hotel is full, we can stay near the station.”
Writer-original: “If she joins late, we might need to repeat the first part.”
Notice the difference in certainty. Will presents the planned result. Can gives an available option. Might marks an uncertain result.
3. Do not promise what the condition cannot guarantee
This is where learners often sound accidentally overconfident.
Too certain: “If we send it today, the client will approve it.”
Safer: “If we send it today, the client can review it tomorrow.”
Uncertain outcome: “If we send it today, they might approve it before Friday.”
A condition tells us what depends on what. It does not magically make the result certain.
4. Mark the decision before committing
In the episode, one verified line is about thinking before responding:
Mull it over. Come find me when you're ready to talk.
Mull it over means think carefully before deciding. That is a useful planning habit: if a key choice is still open, build the condition around the choice.
Writer-original: “If the quote is under €2,000, we’ll approve it today. If it’s higher, we’ll review the scope first.”
Now the listener knows exactly where the decision changes the plan.
5. Use negative conditions when failure is the real trigger
Sometimes the useful branch is not “if something happens” but “if something does not happen.”
Writer-original: “If the payment doesn’t arrive by noon, we’ll pause the shipment.”
Writer-original: “If the connection doesn’t work, we’ll switch to mobile data.”
Writer-original: “If nobody replies, I’ll make the booking myself.”
This is often clearer than vague language such as “We’ll see” or “Maybe we’ll need another option.”
6. Use “unless” when one exception blocks the plan
Unless means roughly if not. It is useful when the plan continues normally except for one blocking condition.
| With if | With unless |
|---|---|
| “We’ll meet at ten if nothing changes.” | “We’ll meet at ten unless something changes.” |
| “We won’t cancel if the doctor doesn’t advise it.” | “We won’t cancel unless the doctor advises it.” |
Do not force unless into every negative condition. Use it when the meaning is genuinely “this plan stands except if X happens.”
7. Use “as long as” for a requirement that must stay true
As long as is useful when the plan works only while one requirement is satisfied.
Writer-original: “We can finish today as long as the files arrive by three.”
Writer-original: “You can take the later train as long as you still reach the airport by eight.”
Writer-original: “The study plan works as long as you review yesterday’s cards before adding new ones.”
Think of it as a green-light condition: if this remains true, the plan can continue.
8. When the plan starts wobbling, name the doubt
Are you putting this off? Are you having second thoughts? No.
Having second thoughts means reconsidering a choice. When that happens, a useful conditional turns the doubt into an actionable branch.
Vague: “I’m not sure about the early flight anymore.”
Useful: “I’m having second thoughts about the early flight. If the connection stays under an hour, we’ll book the later one instead.”
You are not merely expressing uncertainty; you are telling the listener what the uncertainty changes.
9. Make the commitment point visible
We have time. We don't, actually. At some point we gotta pull the trigger on this thing.
The idiom pull the trigger means finally commit to action. It is informal and metaphorical, so a professional alternative is often better: make the final decision, confirm the option, or go ahead.
Conditionals are especially useful right before commitment:
Writer-original: “If we don’t find a cheaper supplier by Thursday, we’ll go ahead with the current quote.”
The branch has a deadline and a default action. Nobody has to guess what happens next.
10. Build a backup, not just a warning
“If this fails, we’re in trouble” describes risk. It does not manage risk.
A useful conditional adds recovery:
Trigger: “If the first option fails…”
Consequence: “…we’ll lose one day…”
Backup: “…so we’ll use the local supplier instead.”
That final piece makes the sentence useful in meetings, travel planning, study schedules, and everyday coordination.
11. Waiting can be a deliberate branch
Sit tight. Put direct pressure on that. I'll be back in a sec.
Sit tight is informal language for waiting. In plan language, waiting should have a condition too:
Writer-original: “Sit tight for ten minutes. If I don’t message you by then, call me.”
Now “wait” has an endpoint. That prevents one of the worst plan failures: two people waiting for each other forever.
12. If coordination depends on another person, say so
We're all clear on the Burrows execution, except for one thing. Bishop McMorrow is not in the fold.
In the fold means included in or aligned with a group or plan. The practical lesson is to make outside dependencies visible.
Writer-original: “The team is ready. If finance approves the budget, we’ll start Monday. If they don’t, we’ll postpone the contractor booking.”
That is much stronger than “We should be able to start Monday.”
Repair drill: turn “maybe” into branches
Rewrite this:
“Maybe we’ll finish Thursday. If not, maybe Friday, but it depends on the designer and the test and whether the client replies.”
Show one clear version
Writer-original model: “The target is Thursday. If the designer sends the files by noon, we’ll test them that afternoon. If the test passes, we’ll deliver Thursday. If it fails, we’ll fix it Friday morning. Unless the client changes the scope, Friday is our latest delivery date.”
Practice: branch four real plans
Complete each with a trigger, result, and backup:
- Travel: The flight is scheduled for 18:00. What if it is delayed?
- Work: The client should send feedback today. What if they do not?
- Study: You plan to finish two chapters tonight. What if chapter one takes too long?
- Meeting: Three people must join. What if one person is unavailable?
Show model branches
Travel: “If the flight is delayed more than two hours, we’ll move the dinner booking. If the delay becomes overnight, we’ll ask the airline about accommodation.”
Work: “If the client doesn’t reply today, we’ll continue with the approved version and flag the open questions.”
Study: “If chapter one takes more than an hour, I’ll stop after chapter two’s summary and finish the exercises tomorrow.”
Meeting: “If one person can’t join, we can still review the proposal, but we won’t make the final decision.”
A quick stop-rule for conditionals
When discussing risk, you usually need only three things:
If X happens → Y will/can/might happen → so we’ll do Z.
If you add six more hypothetical disasters after that, the listener may stop hearing the actual plan. Branch only where the decision genuinely changes.
Turn scenes into conditional prediction practice
With FunFluen, pause before a planning or decision line, hide the subtitle, and predict the function of what comes next: condition, consequence, decision, or backup. Then reveal the subtitle and compare your prediction with the scene. In speaking/guess-the-dialogue practice, build your own if-then branch aloud before checking the character’s wording.
The goal is not to force conditionals into the show. It is to use uncertain moments as prompts for producing clear risk language yourself.
The rule to remember
Do not say “maybe” five times when one if-then branch will do.
State the base plan. Name the trigger. Choose the right certainty level. Give the backup. That is how English conditionals become useful planning tools instead of grammar exercises.
Explore more language-learning guides in FunFluen Learn.