Four-tier register mastery — C1 core

The B2 lesson named the four tiers and gave the basic markers. By C1 you can recognize the tiers in others’ production. The C1 layer is fluency in your own production: switching register cleanly mid-utterance, recovering when you slip, and knowing for each tier what is productive (for non-native speakers) vs recognition-only.

The C2 lesson adds sub-register granularity (humanities vs sciences, consulting vs Big Tech, class markers, generational punctuation). This C1 lesson stays at the four-tier level and works the production-side skill: matching register to context, switching cleanly, recovering from slips.

The four tiers — refresher

Boundaries blur. A Slack channel can be tier-2 with tier-3 leaks. A friendly email between executives can be tier-2 with tier-1 touches. The skill is reading the floor and ceiling of any given context and producing within those bounds.

Trigger lists — what tells you which tier

The C1 skill is recognizing trigger words and structures that mark a register within the first sentence or two of context.

Tier-1 (academic / formal) triggers

• Lexical: moreover, however, nevertheless, notwithstanding, with respect to, vis-à-vis, hitherto, henceforth, in lieu of
• Structural: passive voice (it has been argued), nominalizations (the question of, the matter of), hedged claims (it may be suggested that), long sentences (25-35 words median in humanities)
• Conventions: AmE serial comma in academic prose, em-dash for parenthetical, no contractions, third-person impersonal

Tier-2 (business / professional) triggers

• Lexical: touch base, circle back, deliverable, action item, EOD, EOW, EOQ, follow up, sync, align, deck, kick off, wrap up, table, push back, double-click on
• Structural: medium sentences (15-25 words), some passive (the proposal was tabled), light hedging, occasional first-person plural (we should), bullet points common
• Conventions: contractions OK (we’ll, can’t), em-dash common, list formatting heavy, Slack-style brevity in informal channels

Tier-3 (casual / conversational) triggers

• Lexical: yeah, no way, totally, like, you know, kinda, sorta, gonna, wanna, gotta, lemme, gimme
• Structural: short sentences (6-15 words), heavy contractions, dropped subjects (Going to lunch — want anything?), question intonation tags (right?, you know?, isn’t it?)
• Conventions: relaxed punctuation in text, ellipses common, emoji optional, “lol” and “haha” as tone markers

Tier-4 (slang / in-group) triggers

• Lexical: vibe, the ick, slay, mid, no cap, on God, brain rot, copium, ratio, sus, cope, pilled
• Structural: very short utterances, lower-case style in writing, ironic redeployment of formal phrases, in-group acronyms
• Conventions: age and platform-specific; what’s slang here is dated there

Code-switching mid-utterance — the C1 fluency skill

Native speakers code-switch fluidly within a single conversation or even a single sentence. A C1 speaker should be able to switch register without producing the awkward register-hybrid that marks L2 production.

Clean switch — tier-2 to tier-3

A manager addressing a team:

• Let’s wrap up the action items and align on next steps. — (pause) — Actually, you know what, let’s just grab lunch and figure this out over a slice.

The first sentence is tier-2 (business). The second pivots to tier-3 (casual) cleanly: you know what is the pivot marker, grab lunch and over a slice are tier-3 NYC-flavored casual. A non-native who tries to switch without the pivot marker can produce an awkward hybrid: Let’s wrap up action items and grab lunch over a slice — too fast a switch, the tier-3 elements jar against the tier-2 opener.

Clean switch — tier-1 to tier-3 (op-ed turn)

Long-form journalism routinely switches tiers within a single paragraph for rhetorical effect:

The administration’s foreign-policy framework, as articulated in the State Department’s most recent strategic review, rests on a set of assumptions that have not aged well. Put bluntly: it didn’t work.

The first sentence is tier-1 (formal, with embedded clause and nominalization). The second drops two tiers to tier-3 (put bluntly, didn’t work). The contrast is rhetorically deliberate: the formal setup sets up the casual punchline, which lands harder for the contrast. This is a signature move of The Atlantic and the New York Times op-ed page.

A C1 writer can produce this switch. The trigger is usually a discourse marker — Put bluntly, Frankly, Simply put, Bottom line, To be clear — that signals to the reader “the register is about to shift.”

Failed switch — register hybrid

The L2 failure mode is producing a sentence that mixes registers without a marker, producing a chimera:

• Per my last email, I’d like to touch base re: the deliverable — we shouldn’t really go all in on this if we’re not vibing with the direction.

The phrase per my last email and re: are tier-1 / formal-email; touch base and deliverable are tier-2; go all in is tier-3; vibing with is tier-4. Four registers in one sentence with no pivot markers — this reads as someone who hasn’t picked a register and is producing whatever idiom comes to mind first.

The native-speaker version commits to one register and stays there, with at most one deliberate switch:

• Tier-2 version: Following up on my earlier email about the deliverable — I want to flag a concern with the direction before we commit further.
• Tier-3 version: Just to follow up on what I sent earlier — I’m not really feeling the direction, want to chat before we go further?

Each is internally consistent. The hybrid version is not.

Recovery after a register slip

Register slips happen — even native speakers slip occasionally. The C1 question is how to recover without making the slip worse.

In speech

Slips in speech are usually unrepairable in real time. Native speakers typically don’t acknowledge the slip — they let it pass and continue. The audience usually doesn’t notice or notices and moves on. Russian-trained L2 speakers sometimes try to repair the slip explicitly (“sorry, I mean…”) which actually flags the slip and makes it worse.

The exception is a slip that changed the meaning, where a recovery is required for clarity (“sorry, I said ‘killed’ but I meant ‘cut’” in a business context). Even there, keep the recovery brief and continue.

In writing

Slips in writing should be caught in editing. The recovery is straightforward: identify the off-register word/phrase, replace with the right-register equivalent.

A practical editing pass for register:

1. Identify the target tier for the document (tier-2 corporate email, tier-1 academic paper, tier-3 friendly note).
2. Read each sentence and flag any word/phrase that leaks from a different tier.
3. Replace with a tier-matched expression (use cross-register replacement chains from the idiom-register lesson).
4. Re-read for coherence.

The target tier sets the floor and ceiling. A tier-2 business document has a tier-1 ceiling (don’t go more formal) and a tier-3 floor (don’t go more casual).

Recovering from accidental tone-mismatch

Sometimes the slip is not register but tone — a phrase that landed harsher or softer than intended.

• Sent a message that read as sarcastic when meant earnestly? The recovery move is a follow-up that redoes the original intent without explicit reference to the slip: To be clear, I think the proposal is strong — let me know if I can help refine it.
• Sent a message that read as too informal in a high-stakes context? Send a follow-up in the corrected register: Quick formal note for the record — I support the recommendation.

The recovery should not call attention to the slip; it should add the missing register signal so the corrected version is on the record.

Productive vs recognition table

For each tier, a non-native C1 speaker has a productive vocabulary (what they can use comfortably) and a recognition vocabulary (what they understand when others use it). For most learners, recognition is larger than production at every tier; for tier-4 (slang), the gap should be deliberately large.

The skew is intentional. For tier-1 and tier-2, the recognition-production gap is small because these registers have stable, conventional inventories that you can learn and deploy. For tier-3, the gap is moderate because conversational idiom shifts faster. For tier-4, the gap is large because slang carries in-group history that non-native speakers cannot deploy without context they don’t have.

The C1 production rule:

• Use what you genuinely know. If you don’t know the origin or the typical user, don’t produce it.
• Match the speaker. If your interlocutor uses tier-3 with you, you can use tier-3 back. If they stay tier-2, follow them.
• Default to one tier higher than the casual setting to be safe. Tier-2 in casual contexts reads as competent; tier-3 in formal contexts reads as inappropriate.

Common Russian-L1 register failures at C1

1. Mixing four tiers in one message (the hybrid problem above). Pick one and commit.
2. Importing Russian formality wholesale: producing I would like to kindly inform you that in tier-3 contexts where Just wanted to let you know is the native form.
3. Producing tier-4 slang the speaker doesn’t actually feel: deploying slay, no cap, mid without understanding the in-group history. Recognition is fine; production is risky.
4. Failing to switch when the context shifts: maintaining tier-1 formality in an email that has clearly shifted to friendly chat. Match the speaker’s tier.
5. Over-using tier-2 business idiom in casual contexts: producing touch base, circle back, run it up the flagpole in casual peer conversation, which sounds performative.
6. Failing to recognize tier-mixing as rhetorical: in long-form journalism, the deliberate tier-1-to-tier-3 switch (Put bluntly: it didn’t work) is intentional. Reading it as inconsistent is an L2 misread.
7. Issuing explicit register apologies after slips: “Sorry, I shouldn’t have used that word in this context” — native speakers don’t do this; the apology amplifies what would otherwise pass unnoticed.

Summary

• The four tiers — academic / business / casual / slang — have distinct trigger words and structural conventions. Reading triggers within two sentences is reflex by C1.
• Code-switching mid-utterance is a native skill. Clean switches use a pivot marker (Put bluntly, Frankly, To be clear); switches without markers produce register hybrids that read as L2 production.
• Register slips in speech are usually unrepairable in real time — let them pass. In writing, catch them in editing and swap for tier-matched expressions.
• Productive vs recognition gap is large for tier-4 (slang) and small for tiers 1-2. Use what you genuinely know; match the speaker; default one tier higher than casual to be safe.
• The over-use trap at every tier — too much academic register, too much business idiom, too much slang — signals performance rather than fluency. Native speakers default to plain language and use register-markers strategically.
• The C1 fluency test: in a meeting with a 55-year-old VP, two engineers, and a new hire, can you commit to one tier, run it cleanly, and limit lower-tier leaks to one per utterance? That is the production-side skill the C2 lesson builds on with sub-register granularity.