Register Control: Adjusting Tone and Formality
How to shift between formal, neutral, and casual English — and why mixing them accidentally is so noticeable.
At C1, the question is no longer "is this correct?" but "is this appropriate?" Register is the dimension most advanced learners control least reliably.
Three levels, one message
Formal: I am writing to enquire whether it would be possible to reschedule our meeting.
Neutral: I wanted to ask if we could move our meeting.
Casual: Any chance we could shift the meeting?
All three are correct. Choosing wrongly is what causes problems.
What actually raises register
1. Latinate vocabulary over phrasal verbs
- casual find out → formal ascertain / determine
- casual set up → formal establish
- casual put off → formal postpone
- casual get in touch → formal contact
Phrasal verbs are the single strongest marker of informality.
2. Full forms over contractions
- I do not believe (formal) vs I don't think (neutral)
3. Modal distance
- Could you possibly...? / I was wondering whether... — more formal
- Can you...? — neutral
4. Impersonal constructions
- It is generally accepted that... rather than Everyone knows...
- It was decided... rather than We decided...
Signals of informality
Contractions, phrasal verbs, get, exclamation marks, sentence-initial So and Well, ellipsis (Sounds good), and vague language (kind of, a bit, stuff).
None of these are wrong — they're wrong in the wrong place.
The channel sets the baseline
Register isn't only about who you're writing to. Each channel has its own default, and violating it is as noticeable as getting the person wrong:
| Channel | Default | Getting it wrong looks like |
|---|---|---|
| work chat | very informal, fragments fine | a formal paragraph reads as passive-aggressive |
| internal email | neutral | over-formality reads as distance or complaint |
| external / client email | neutral to formal | casual reads as unprofessional |
| formal document, contract | formal, impersonal | contractions read as sloppy |
| presentation, spoken | neutral, contractions natural | written-formal read aloud sounds stiff |
The most common real-world error at C1 isn't in an email to a CEO — it's sending a fully formal message into a chat channel where everyone else writes in fragments.
Formal is not one thing
Business formal and academic formal pull in different directions, and mixing them is a genuine C1 tell:
- Business rewards brevity and the active voice: We recommend delaying the launch. Testing isn't complete.
- Academic rewards hedging and impersonal constructions: It would appear that the evidence is insufficient to support the proposed timeline.
A business email written in academic register reads as evasive; an academic paper written in business register reads as overclaiming.
British and American formality
The registers don't line up exactly:
- American business English is more direct and more comfortable with enthusiasm — Great question!, Happy to help! — which can read as excessive to a British ear.
- British business English hedges more and understates more — not bad, a slight concern — which can read as lukewarm or evasive to an American one.
- Dear Sir/Madam and Yours faithfully are still standard in British formal letters and largely archaic in the US.
Neither is more correct. Both are noticeable in the other's context.
The real risk: mixing
The most common C1 failure isn't being too formal or too casual — it's being both in one message.
❌ Dear Dr Hoffmann, I am writing to enquire about the position. Btw, is the salary negotiable? Looking forward to hearing from you!
The opening is formal, the middle is texting, the close is neutral. Pick one level and hold it.
Shifting register on purpose
Within a single document, a deliberate drop into plain English is a strong move — for a conclusion, a warning, or a moment of candour:
The analysis suggests that the projected efficiencies are contingent upon a number of assumptions which have not been independently verified. In short: we don't know if this works.
The contrast only works if the surrounding register was consistent. That's the reason for holding a level — not correctness for its own sake, but so that departing from it still means something.
Matching your correspondent
The safest rule in professional writing: mirror the register you receive. If a client writes in short, contraction-heavy sentences, matching them builds rapport. If they write formally, matching them signals respect.
Start one notch more formal than you think necessary with someone new — it's easy to relax later, harder to recover from being too casual.
Register is a statement about the relationship. Choosing formal English tells the reader you regard this as an official exchange between people who are not close; choosing casual English claims a familiarity you may not have. Neither is safe by default, which is why matching the other person is more reliable than any fixed rule.
The same request, four ways
Chat: any chance we could move thurs? something's come up
Internal email: Hi Marta — could we move Thursday's session? Something's come up at my end. Friday morning would work if that's easier.
Client email: Dear Ms Kaur, I'm afraid I need to ask whether we might move Thursday's meeting. Would Friday morning be convenient?
Formal letter: I am writing to request that our meeting of 12 March be rescheduled. I should be grateful if you would confirm whether an alternative date would be acceptable.
Same message, four relationships. Each would be wrong in the others' place.
Try it yourself
The quiz below asks which version fits a given situation — all options are grammatically correct.