The Subjunctive

Here's a moment you might recognise. You're writing a careful email — references, a formal complaint, a letter to a landlord — and for a split second you freeze over a tiny word. If I was / were you, I'd ask for that deposit back in writing. Or your fingers want I insist that he is available on Monday, and then something rooted in soft memory mutters that it ought to look like he be available. And then you're halfway down a search rabbit-hole at 10 p.m., feeling slightly foolish that a verb form the size of a postage stamp has eaten half an hour of adult life.

Let's be honest — almost no one was taught this cleanly. I spent years as a copy editor watching good writers second-guess themselves. The good news is the English subjunctive isn't a vast secret grammar underworld. It's a small set of surviving patterns — a few set phrases, the familiar were of unreal advice and wishes, and a formal "mandative" construction after verbs of insisting and recommending. Master those three, and you stop fretting.

Nobody's born knowing this. You're allowed to learn it now, as a practical adult tool — not as a way to police other people's speech.

Before you read on, here's where we're heading. By the end of this article, you'll be able to: - Spot formulaic leftovers (be that as it may, so be it, as it were) and use them when the tone fits. - Deploy were confidently in unreal statements (If I were you…, I wish it were…). - Build and recognise the mandative pattern after insist, demand, recommend, suggest. - Produce UK-natural and US-expected versions of that mandative, without muddling them. - Decide when a rewrite (should, -ing, to-infinitive) is simply better English at work.

Beginner (Foundation): The small toolkit, clearly labelled

Almost all of the time, English verbs behave in their ordinary way — she manages the rota, they were late, I was on annual leave. The subjunctive is a mood — a label for forms that treat a situation as wished, imagined, required, or traditional, rather than as an ordinary report of fact.

English no longer has a full living subjunctive system the way some languages do. What remains is usable residue in three places.

1. Formulaic survivals

These live as whole phrases. You recognise them, you keep them as is:

• Be that as it may
• So be it
• Far be it from me to…
• Come what may
• Suffice it to say…

They're a tiny bit formal — sometimes a bit wry. In a work email they can sound measured; overdone, they sound period-drama. Use with a light hand.

2. The were-subjunctive for unreality

When the situation is not actual, careful English still prefers were over was after I / he / she / it:

• If I were the hiring manager, I'd give feedback in writing.
• If she were free on Thursday, we could move the walkthrough.
• I wish it were that simple.

This is the form locked into If I were you — the classic template for measured advice, from a friend or a mentor.

And versus a real past possibility: - If I was rude on the call, I apologise. (Possible that I actually was rude.)

3. The mandative after "push" verbs

After insist, demand, require, recommend, suggest, move (formal meeting-speak), propose, formal English can use a bare base form following that:

• The board insisted that the report be redrafted.
• I recommend that the applicant provide two references.
• They suggested that the meeting start at nine.

No third-person -s. No tense decoration. Just the base — be, provide, start. That's the mandative subjunctive in one glance: formal, slightly directive, and very common in policy documents and some US workplace writing.

Quick recap: - Subjunctive mood ≈ unreality, requirement, or fixed traditional phrasing — not ordinary past/present fact. - Fixed phrases (so be it, be that as it may) are learned as wholes. - Unreal thoughts lean on were: If I were you, I wish it were… - Mandative: insist/demand/recommend + that + subject + base form.

Intermediate (Development): Working rules, workplace examples, common stumbles

This is the toolkit as you actually need it on a Tuesday afternoon — emails, résumé footnotes, references, short reports.

Where were earns its keep

Unreal present / future thoughts (second-type conditional territory — for full conditional maps, Cluster D owns the terrain; we only claim the were choice here):

• If I were in your position, I'd put the notice period in writing.
• Were the budget larger, we'd keep both freelancers. (inversion — formal)

Wish:

• I wish the deadline were later.
• I wish she were available for a short call this week.

Softener:

• The app is the firm's front door, as it were. (as it were = "so to speak." Fixed idiom.)

When was is not an error — genuine past openness, hedged apologies, reported possibility: If I was unclear in my last email, here's the figure again. That's adult, precise, and correct because the past possibility is real.

Mandative in the wild (and its usual partners)

The clear skeleton:

verb of will / recommendation + that + subject + base form

Workaday examples:

• HR required that every contractor complete the training module.
• I move that the minutes be approved. (very formal meeting language)
• My GP recommended that I see a specialist.

Common partner verbs: advise, ask, demand, insist, order, propose, recommend, request, require, suggest, urge.

Common Mistake: Treating suggest as always subjunctive. She suggested that the contractor was overcharging reports a claim. She suggested that the contractor check the invoice again recommends an action. Meaning picks the form.

Pro-Tip: If you hate how naked the bare form feels, UK English often prefers recommended that he should complete… or recommended **completing… or recommended him to complete** (watch subtle meaning shifts). None of those is cowardice — they're real tools. The bare form isn't the only grown-up option.

Formulaic phrases in professional prose

Use sparingly, and only when the rhythm helps:

• Be that as it may, we still need the signed NDA by Friday.
• Suffice it to say, the pilot did not go to plan.

They can lend a dry, slightly traditional voice — they can also make a Slack message sound like a court filing. Audience first.

Quick recap: - Were = unreality, advice templates, wish; was = real past or hedged past possibility. - Mandative bare form is clean and formal after insist/demand/recommend/require. - Suggest flips between "claim" (indicative) and "recommend" (mandative). - Formulaic pieces work best as occasional colour, not house style for every email. - Rewrites with should, -ing, or to-infinitives are legitimate adult alternatives.

Advanced (Mastery): Register, grey areas, and why the forms still matter

At mastery level, you're not collecting rules — you're choosing effect. The surviving subjunctive is a signal. Were marks counterfactual distance. The mandative bare form marks institutional will. Fixed phrases tip a tone toward tradition or dry formality. Overuse any of them and you sound like a parody of precision; underuse them in the wrong context and your formal writing flattens into the everyday.

Grey zone: as if / as though

• He speaks as if he were the account lead. (counterfactual flavour — he isn't)
• She looked as if she was about to resign. (descriptive of a real-seeming appearance)

Both circulate. In tight formal house style, many editors prefer were when the unreality is sharp. I still pause on a few of these myself after twenty-two years — meaning is the tie-breaker, not a slogan.

Inversion and high register

• Were the landlord prepared to negotiate, we'd stay. (= If the landlord were prepared…)

Useful in long-form opinion, legal-adjacent prose, speeches — odd in a text to a flatmate about whose turn it is to buy bin bags.

Mandative and the adult rewrite repertoire

You're never trapped:

Choose on audience (client? US headquarters? UK local council?), medium (policy vs WhatsApp), and whether you want the sentence to feel prescriptive or collaborative.

Common Mistake: Pasting were into ordinary narrative history. Last year, if I were free of the lease… fights its own timeline. For unreal past counterfactuals, English leans on had been — If I had been free of the lease last year… Again, Cluster D owns full conditional architecture; just don't force were into a slot that wants had been.

Pro-Tip: When editing someone else's work, ask one question only — Is this reality, recommendation, or traditional phrase? Reality → ordinary agreement. Recommendation under formal pressure → bare form or a should/-ing rewrite. Traditional phrase → leave the fossil alone. That one fork covers 95% of subjunctive decisions.

Boundaries (on purpose)

This article doesn't re-teach full conditional systems, modal obligation more widely (B7), the plumbing of that-clauses (Pillar 3), or agreement (Pillar 5). Use the internal links when those systems are the real problem.

Quick recap: - Register, not reverence: were and mandative forms are signals, not medals. - As if / as though reward sense-checks; inversion is optional splash. - Adult mastery includes greyscale rewrites; the bare form is one polished tool among several. - Don't force were into past counterfactuals that want had been.

UK vs US Usage (mandative only)

Shared across varieties: formulaic phrases and the were-subjunctive. If I were you, I wish it were Friday, so be it need no passport.

The only material UK/US difference in this article's scope is how obligatory and expected the mandative bare form feels in formal prose.

Production vs recognition. Learners — and working writers switching variety — should recognise that he be… everywhere. For production: use the bare form freely for US-facing formal work; in UK-facing work, should + base form or a structural rewrite remains thoroughly natural, and the bare form still reads as competent formal English, especially in legal, academic, or board-level prose.

Don't manufacture differences on if I were — that isn't a dialect fork.

Key Takeaways

• Three living pockets: formulaic phrases, were-unreality, and the mandative base form.
• If I were you and I wish it were… are shared, high-value careful English.
• Mandative = power/advise verb + that + subject + base (that the report be…).
• UK English often softens with should or a rewrite; US formal prose leans harder on bare forms.
• Choose for audience and tone — link out for conditionals, obligation, that-clauses, and agreement rather than overloading this page.

Check Your Understanding

1. Choose the better careful form: If I (was / were) you, I'd ask for the deposit back in writing.
2. Label — formulaic / were-subjunctive / mandative: Suffice it to say, the trial went badly.
3. Formal bare-form rewrite: They demanded that the invoice is amended.
4. Why might a UK workplace email prefer …that she should be transferred over …that she be transferred?
5. Is If I was out of line in yesterday's meeting, I apologise "wrong," and why / why not?

Answer key

1. were (unreal advice template).
2. Formulaic.
3. …that the invoice be amended.
4. UK formal habit often favours should + base (or other rewrites) as natural local tone while still fully professional.
5. Not wrong — it reports a real past possibility / hedge, so ordinary was is the right tool.

Internal links (Pillar 4 library)

• B1 — the opening Pillar 4 article this sequence builds on
• B7 — obligation forms (should / must / have to) overlapping the mandative space
• Cluster D — second/third conditionals and wish beyond the were choice
• Pillar 3 — that-clauses supporting mandative structure
• Deferred: Pillar 5 for agreement (not duplicated here)

Roger Fielding — Bristol. For both readers still halfway down that 10 p.m. rabbit-hole: the forms are small; the freedom to choose them deliberately is the adult skill.