Written Expression: Register, Tone and Audience Awareness
What the question is really asking
These items test whether a text suits its reader and situation: a formal report, a letter of complaint, an email to a colleague, a public notice. The right answer matches the audience's expectations for formality, politeness, and directness.
Concepts to master
- Register levels: formal, neutral, informal. Formal writing avoids contractions, slang, exclamation marks, and vague intensifiers (really, a lot).
- Audience and purpose: a complaint letter to a company is firm but courteous; an internal memo is concise and neutral; a notice is brief and imperative.
- Politeness strategies: hedges and modals soften requests ("Could you possibly...", "We would appreciate..."). Direct imperatives can sound rude to superiors or customers.
- Consistency: mixing registers within one text ("Dear Sir, gonna...") is an error even if each part is acceptable alone.
- Objectivity: formal reports favour passive or impersonal constructions and evidence over emotion.
- Inclusive, respectful language: avoid slang, jargon unexplained to outsiders, and dismissive wording.
Traps to expect
- A grammatically perfect sentence that is too casual for its context.
- Over-formality that becomes archaic or pompous ("I beg to remain your humble servant").
- An emotional outburst presented as "stronger" writing.
- A shift of register inside one text.
- A direct command where a polite request is expected.
Rule of thumb
Name the reader and the relationship before choosing: Who is this for, and what do they need to feel and know? Then check that every sentence could appear in the same document without a jolt.
Worked example
To a supplier: "We'd really love it if you could, like, sort out the delay ASAP!" becomes "We would be grateful if you could resolve the delay as soon as possible." The meaning is unchanged; the register now suits a business relationship.