Advanced modality traps at C1 — could vs might, perfect modal misuse, modal calques

At C1, you no longer confuse can with may or forget that must has no past form. The modality you still get wrong is the residual kind — the kind that survives ten years of fluent use because the Russian default underneath is almost compatible with English. Almost.

This lesson collects the modality traps that persist in C1 Russian speakers. Each one passes spell-check, passes most native ears, and quietly tags you as non-native to the careful listener. The fix is not learning a new rule — it’s installing a discrimination habit so the L1 default stops winning.

We will cover: could vs might at the C1 level, perfect modal misuse (should have to vs should have), be supposed to used as a calque, be liable to in wrong contexts, should I vs shall I, modal stacking errors, and the would always habitual that Russians under-use.

Could vs might — the residual confusion

Both could and might express possibility, and most Russian C1 speakers treat them as fully interchangeable. They are not. Could leans toward ability or theoretical possibility; might leans toward epistemic uncertainty about a specific event.

Russian L1 source. Russian uses может and мог бы loosely, with overlap on возможно. The Russian speaker reaches for whichever sounds smoother in English and lands on could by default — it’s shorter and more common in textbooks.

• WEAK: He could be in the office. (sounds like he is capable of being there)

• BETTER: He might be in the office. (specific guess about now)

• WEAK: The deal could fall through. (theoretical possibility, distant)

• BETTER: The deal might fall through. (real, present risk)

• WEAK: She could have forgotten. (she had the capacity to forget — odd)

• BETTER: She might have forgotten. (epistemic guess about a past event)

• WEAK: It could rain tomorrow. (theoretical, weather generality)

• BETTER: It might rain tomorrow. (specific forecast guess)

• OK: Anyone could make that mistake. (general ability — could is right)

• OK: I could ski when I was ten. (past ability — could is right)

Fix strategy. Ask: am I guessing about a specific event (might) or stating general possibility/ability (could)? If specific, default to might. If general, could is fine. In present-time speculation about a person, might almost always wins.

Why it matters. This one rarely blocks comprehension, but it shifts your register. Overusing could makes your speculation sound textbook-academic; might sounds native-conversational. The mismatch flags you as fluent-but-non-native.

Perfect modal misuse — should have to vs should have

The perfect modals (should have, must have, could have, might have, would have) are a graveyard of small errors at C1. The most fossilized one is mixing should have to with should have + past participle.

Russian L1 source. Russian должен был covers both had to (deontic past obligation that happened) and should have (counterfactual regret). When the Russian brain reaches for the English equivalent, it sometimes builds the Frankenstein should have to.

• WRONG: I should have to call her yesterday.

• RIGHT: I should have called her yesterday. (regret — I didn’t, and I wish I had)

• WRONG: He should have to finish the report by Friday.

• RIGHT: He had to finish the report by Friday. (past obligation, fulfilled or not — neutral)

• RIGHT: He should have finished the report by Friday. (criticism — he didn’t)

• WRONG: You should have to tell me earlier.

• RIGHT: You should have told me earlier.

• WRONG: We should have to leave by 5.

• RIGHT: We had to leave by 5. (factual past obligation)

• RIGHT: We should have left by 5. (regret about not leaving)

Fix strategy. Should have to does not exist as a fluent English form. If you want past obligation neutrally, use had to. If you want regret or criticism about a past action, use should have + V3. Drill: every time you almost say should have to, stop and ask am I describing what happened or what should have happened?

Why it matters. Should have to sounds broken — natives notice it immediately and rewind the sentence mentally. This is one of the few C1 errors that does mildly block comprehension.

Should have + V3 vs must have + V3 — wrong direction of inference

Both express past inference, but should have leans expectation and must have leans conclusion from evidence.

Russian L1 source. Russian должно быть covers both should have and must have. The Russian brain picks should have because the lexical match is closer (должно ↔ should).

• WRONG: The package should have arrived — I see it on the porch.

• RIGHT: The package must have arrived — I see it on the porch. (conclusion from evidence)

• WRONG: She should have been tired after that flight. (sounds like criticism)

• RIGHT: She must have been tired after that flight. (logical conclusion)

• OK: The package should have arrived by now. (expectation — but we don’t have evidence it did)

• OK: He should have known better. (criticism / expectation he didn’t meet)

Fix strategy. Ask: am I drawing a conclusion from what I see, or stating what I expected? Evidence in hand → must have. Expectation only → should have.

Why it matters. Using should have when you mean must have sounds like backhanded criticism. She should have been tired implies she had a duty to be tired — strange and slightly judgmental.

Be supposed to — calque from должен/предполагается

Be supposed to is a useful modal-like expression meaning expected to or believed to. Russians calque it from предполагается and use it where natives would use should or be expected to, or they use it in over-formal contexts where it sounds odd.

Russian L1 source. Russian предполагается, что triggers the be supposed to reflex. But Russian должен + infinitive is broader than English be supposed to — it includes plain duty.

• AWKWARD: Every employee is supposed to follow the safety protocol. (sounds like people say employees follow it — undermining)

• BETTER: Every employee is required to / must follow the safety protocol.

• AWKWARD: The new policy is supposed to be implemented next month. (in a press release context — sounds doubtful)

• BETTER: The new policy will be implemented / is scheduled for implementation next month.

• OK (informal): We were supposed to meet at 5. (= the plan was, but we didn’t)

• OK (informal): This restaurant is supposed to be great. (= people say so — secondhand)

Fix strategy. Be supposed to in AmE carries a subtle implication of expected but maybe not happening or secondhand information. In formal writing about rules, requirements, or commitments, prefer must, be required to, will, be expected to. Save be supposed to for casual contexts where the secondhand or unfulfilled meaning is wanted.

Why it matters. Misusing be supposed to in formal text makes the writer sound uncertain about their own claims. It signals non-native register awareness.

Be liable to — wrong context

Be liable to means prone to (negative outcome) or legally responsible for. Russians sometimes use it as a generic likely to equivalent, which collides with the negative connotation.

Russian L1 source. The textbook gloss be liable to = likely to is incomplete. Russian склонен к and способен на mix possibilities, but liable in English is heavily skewed negative or legal.

• WRONG: She is liable to win the gold medal. (sounds like winning a medal is a misfortune)

• RIGHT: She is likely / expected to win the gold medal.

• WRONG: The new product is liable to be popular. (popularity is positive — liable clashes)

• RIGHT: The new product is likely / expected to be popular.

• OK: Old engines are liable to overheat. (negative outcome — fits)

• OK: You are liable for any damages. (legal responsibility — fits)

• OK: He is liable to lose his temper. (negative tendency — fits)

Fix strategy. Reserve be liable to for negative tendencies (overheat, fail, lose temper, break down) or legal liability contexts. For neutral or positive likelihood, use be likely to or be expected to.

Why it matters. Wrong register on liable sounds like you mixed up a translation. Natives don’t usually correct it, but they register the slip.

Should I vs shall I — residual BrE creep

At C1, Russians often retain shall I? from BrE schooling and use it in AmE offers and suggestions. AmE has effectively retired shall except in legal text and a few set phrases (shall we?, shall not be infringed).

Russian L1 source. BrE textbooks teach shall I / shall we for offers; the C1 Russian who switched to AmE keeps the form because no one corrected it.

• BrE / DATED: Shall I open the window?

• AmE: Should I open the window? / Want me to open the window?

• BrE / DATED: Shall I help you with that?

• AmE: Can I / Could I help you with that?

• BrE / DATED: Shall we go?

• AmE: Should we go? / Let’s go. / Wanna go?

• LEGAL / RETAINED: The Lessee shall pay rent on the first of each month. (contracts only)

• SET PHRASE / OK: Shall we? as a stand-alone invitation (formal dinner, toast, dance floor) — preserved in some AmE registers, sometimes used playfully or formally without sounding British.

• BrE-FLAVORED in AmE: Shall I / shall we + full verb (Shall I send the report? Shall we begin?) — replace with should I, should we, let’s, want me to.

Fix strategy. In AmE, drop shall + full verb. The bare invitation Shall we? is still acceptable in formal/playful registers. Keep shall in contract language.

Why it matters. Shall I in AmE sounds either British or theatrical. In a casual workplace, it’s harmless but immediately marks you as not-from-here.

Modal stacking — adding modals you don’t need

C1 Russian writers sometimes stack hedges to a point that sounds non-native: it could possibly maybe be the case that…, I would perhaps suggest that…. The accumulation is a calque from cautious Russian academic style.

Russian L1 source. Russian academic style stacks epistemic markers (вероятно, возможно, по-видимому, как представляется, может быть) without penalty. English tolerates one or two hedges; three or more sound either insincere or non-native.

• WRONG: It could possibly perhaps be argued that the data might suggest a trend.

• RIGHT: The data may suggest a trend. (one hedge is enough)

• RIGHT: Arguably, the data suggest a trend. (one hedge, fronted)

• WRONG: I would maybe perhaps want to recommend that we possibly consider it.

• RIGHT: I’d recommend we consider it. / I’d suggest we look at it.

• WRONG: This could maybe potentially be a problem.

• RIGHT: This could be a problem. / This might become a problem.

Fix strategy. Limit yourself to one hedge per clause. Choose the one that carries the most weight, not the most softeners. Read your sentence aloud — if you hear could possibly maybe, delete two of the three.

Why it matters. Hedge-stacking sounds either insecure or formulaic. Natives associate it with non-native academic writing or with people trying too hard to seem cautious.

Have to vs must — the social register split

In AmE, must and have to both express obligation, but the social register differs sharply. Must sounds formal, written, or strongly imposed. Have to sounds neutral and conversational. Russians under-distinguish these because Russian должен covers both registers without modifying form.

Russian L1 source. Russian должен / надо / нужно don’t carry the register distinction that must / have to do in AmE. The Russian speaker often defaults to must in conversational English because it feels like a more direct translation of должен, but it lands as over-formal.

• AWKWARD (casual): You must come to my party. (sounds demanding, like a command)

• BETTER: You have to come to my party. (warm enthusiasm)

• BETTER: You gotta come to my party. (very casual)

• AWKWARD (casual): I must go now. (sounds dramatic)

• BETTER: I have to go now. / I gotta go.

• OK (formal sign): Visitors must sign in at reception.

• OK (written rule): All employees must complete the training by Friday.

• OK (urgent imperative): We must address this immediately.

Fix strategy. In conversation, default to have to or got to / gotta. Reserve must for written formality, signs, rules, and dramatic emphasis. When you mean I am required to, use have to; when you mean I strongly recommend or I solemnly declare, use must.

Why it matters. Overusing must in casual conversation sounds preachy, theatrical, or non-native. Friends saying I must go sounds like a stage actor; I have to go sounds like a friend.

Would for past habit — under-used by Russians

Russians at C1 reach for used to almost exclusively for past habit and rarely use would. Natives mix both, and would is the more sophisticated choice for repeated past actions in narrative.

Russian L1 source. Russian uses imperfective past for habit (ходил, делал, говорил). There’s no morphological would equivalent, and used to maps cleanly onto раньше + imperfective. Would feels grammatically optional, so it gets skipped.

• BASIC: When I was a kid, I used to play outside every day.

• C1: When I was a kid, I would play outside every day. (narrative would)

• BASIC: My grandmother used to make pierogi on Sundays.

• C1: My grandmother would make pierogi on Sundays — the whole house would smell of dough. (narrative chain)

Caution: would for habit needs a clear past time frame (when I was a kid, back then, every summer) and works only for actions, not states. I used to live in Moscow — never I would live in Moscow.

Fix strategy. In narrative passages about repeated past actions with a clear time anchor, swap used to for would on the second and third mentions. It varies the rhythm and reads more native.

Why it matters. Pure used to sounds slightly textbook in extended narrative. Would unlocks a more literary register.

Can’t have vs couldn’t have — past impossibility

For past impossibility (something definitely did not happen), AmE uses can’t have + V3 (deduction in negative) or couldn’t have + V3 (ability/possibility denial). Russians often confuse these or default to couldn’t have universally.

Russian L1 source. Russian не мог + infinitive covers both meanings — denial of possibility and denial of ability — so Russians don’t internalize the AmE distinction.

• She can’t have known about the meeting — no one told her. (= I conclude she did not know — evidence-based negative deduction)

• She couldn’t have finished the report on time — she only got the data yesterday. (= it was impossible for her to finish — ability/circumstance)

• WRONG: He couldn’t have been there — I just saw him in the office. (sounds odd — you have evidence, so use can’t have)

• RIGHT: He can’t have been there — I just saw him in the office.

• OK: I couldn’t have done it any better. (= I lacked the ability to do better — ability denial)

• OK: They can’t have finished already — they just started. (= deduction from circumstance)

Fix strategy. Can’t have for negative deduction from evidence; couldn’t have for past lack of ability or impossibility. When in doubt, can’t have is slightly more natural for deduction in AmE.

Why it matters. Both forms are accepted by natives, but the wrong choice slightly muddies the inference signal.

Would have vs should have for missed opportunities

C1 Russians sometimes use would have where AmE expects should have for missed opportunities, especially regret about past decisions.

Russian L1 source. Russian я бы сделал covers both hypothetical (I would have done) and regret (I should have done). The Russian speaker often defaults to would have because it feels closer to бы.

• WEAK: I would have called him yesterday. (sounds hypothetical — if X had happened, I would have called)

• STRONG (regret): I should have called him yesterday. (= I didn’t, and I regret it)

• WEAK: We would have taken that deal. (sounds like a hypothetical)

• STRONG: We should have taken that deal. (= we didn’t, and we regret it)

Fix strategy. For pure regret about past inaction or wrong choices, use should have + V3. Save would have for the consequence clause of an unreal past conditional (If I had known, I would have called).

Why it matters. Mixing these slightly fuzzes the emotional tone — should have signals regret, would have signals hypothetical contingency. Listeners hear the difference.

Self-diagnosis checklist

How to spot these in your own English. Run a sample of your last writing through these questions.

• Do you reach for could every time you mean might? Count could vs might in a 500-word sample. If could outnumbers might by more than 2:1 in speculative contexts, you have the C1 default.
• Do you ever write should have to? Search your drafts. Replace with had to or should have + V3.
• Do you use must have for evidence-based conclusion, or do you default to should have?
• Do you use be supposed to in formal text where must or will fits better? Search formal docs for supposed to and challenge each instance.
• Do you ever use be liable to with positive outcomes (winning, succeeding)? If so, fix.
• Do shall I or shall we still appear in your AmE speech?
• In academic writing, do you stack three or more hedges in a single clause?
• In past-tense narrative, do you use would for repeated actions, or only used to?

Drill — transformation exercises

Rewrite each sentence to fix the modality error. Answers in the callout below.

1. He could be very tired — he worked all night.
2. I should have to renew my passport last month.
3. The deal should have closed — I just got the wire confirmation.
4. Employees are supposed to wear safety glasses on the factory floor.
5. Our new product is liable to be a huge hit.
6. Shall I get you some coffee?
7. It could possibly maybe be the case that we need a different approach.
8. When I was little, I used to play in the yard, I used to climb trees, and I used to chase the dog.
9. She could have forgotten — that’s why she didn’t show up.
10. We should have to submit the report by Friday — it’s a hard deadline.

Summary

• Could vs might: might for specific speculation about a particular event; could for general possibility or ability. Russians over-default to could.
• Should have to does not exist. Use had to for neutral past obligation, should have + V3 for counterfactual regret.
• Must have for evidence-based past conclusion; should have for past expectation or criticism. Russians swap these.
• Be supposed to implies secondhand or expected but maybe not happening. In formal rules, use must, will, be required to.
• Be liable to is negative or legal. For neutral or positive likelihood, use be likely to.
• Shall I / shall we is BrE-creep in AmE. Replace with should I, want me to, can I, let’s.
• Stack one hedge per clause, not three. Would for narrative past habit varies rhythm beyond used to.
• Must is formal/written/dramatic; have to is conversational. Russians over-use must in casual speech.
• Can’t have + V3 for negative deduction from evidence; couldn’t have + V3 for past lack of ability.
• The common thread across all of these: the Russian default modal system (должен, может, надо, должно быть, не мог) is broader than any single English modal. Each Russian word maps to 2-4 English forms. Pick by register, direction of inference, and type of obligation — not by lexical similarity.

Next lesson: Britishism creep and AmE purification — whilst, amongst, learnt, in hospital, different to.