B2 Vocabulary · Relationship, channel, purpose, and linguistic distance

Register & formality

The best message is not the most formal one. It gives this reader the right facts, the right amount of distance, and a clear next action in language that fits the situation.

Can-do: By the end, you can distinguish register, formality, tone, and politeness; identify how audience, relationship, role, purpose, channel, stakes, and shared context shape a message; choose direct or mitigated requests without confusing length with respect; use accurate request, disagreement, refusal, apology, and update patterns; shift phrasal verbs, lexical verbs, contractions, pronouns, active and passive voice, and nominalization according to their actual effect; preserve responsibility and evidence in plain professional language; recognize that professional U.S. English can be warm and contracted; hear reductions, thought groups, and contrastive prominence in polite speech; and rebuild one set of facts for an internal chat, external email, public update, and formal incident record.

Retrieve the language this lesson depends on

Five prerequisite decisions

1Priya wanted an action, not information about ability. Report “Please send me the file” as Priya .

2The proposal addresses the immediate delay. , it does not fund the required review.

3A public safety instruction should normally prefer over a culture-specific metaphor.

4If the source establishes who made an operational error, a responsible update should .

5A short internal chat can omit details that coworkers already know because they share .

Notice: one practical need, four appropriate messages

Fictional Cedar Loop workshop

Message 1, familiar coworker in chat: Can you send me the accessibility checklist by three? I need it for the venue call.

Message 2, project partner by email: Could you send me the completed accessibility checklist by 3:00 p.m.? I need it before today’s venue call. Thanks.

Message 3, external venue coordinator: Could you please confirm by 3:00 p.m. whether the north entrance will be step-free during the October 14 workshop? We need this information for the attendee notice.

Message 4, safety instruction after confirmation: Keep the north entrance clear. Do not move the temporary ramp.

The messages are not four decorative versions of one sentence. The writer changes what is explicit because each reader has different knowledge and responsibilities. The safety instruction is the most direct, but it is not the least respectful. Its purpose and consequences make directness appropriate.

Discovery check: infer the situation before labeling the language

1Message 1 can say the checklist without naming the event because the coworkers have .

2In Message 2, Could you...? performs .

3Because the external coordinator does not share the full project history, Message 3 states .

4Message 4 uses imperatives because .

5Across all four messages, the practical purpose is to .

6The strongest message is the one that .

Get to the root: register is a bundle, not a ladder

Register is the recurring bundle of vocabulary, grammar, organization, reference, and spoken delivery associated with a situation or activity. Formality is one dimension of that bundle, often involving convention and social distance. Tone is the attitude or interpersonal effect a reader or listener perceives, such as warm, cautious, firm, impatient, or collaborative. Politeness manages relationships and expectations. These ideas interact, but they are not synonyms.

Question	Why it matters	Possible consequence
Who is the audience?	knowledge, language needs, and expectations	define unfamiliar terms or omit shared detail
What is our relationship?	closeness, trust, history, and social distance	choose a familiar, neutral, or more ceremonious opening
What roles and power apply?	authority, obligation, choice, and vulnerability	avoid disguising an order as if refusal were equally available
What action is the purpose?	request, inform, refuse, apologize, record, warn, or persuade	state the needed action and response clearly
What is the channel or genre?	chat, call, email, notice, report, form, or legal record	adjust structure, permanence, and recoverable context
What are the stakes?	consequences of delay, refusal, or misunderstanding	increase explicitness and reduce interpretive burden
What context is shared?	what the reader can identify without explanation	use concise reference only when it remains unambiguous

Do not assign one permanent register to a person

A manager may use relaxed language in a familiar team chat and exact formal language in a compliance record. A friend may need direct literal language during an emergency. Culture, workplace practice, age, identity, and personal preference can affect expectations, but they do not let us predict every individual. Observe the actual community, explain your purpose, and repair when your first choice does not land as intended.

Diagnose seven situation variables

1A public notice explains north entrance instead of saying the usual door because of the readers’ limited .

2Two coworkers who have collaborated daily for five years may open with Hi, Sam because their established .

3A supervisor who requires attendance should say that attendance is required rather than pretending the employee has a free choice. This is a question of .

4An apology needs to acknowledge impact and repair, while a record needs to preserve events and times. The difference begins with communicative .

5An internal chat may use one short paragraph, while an incident report uses labeled fields. The relevant variable is .

6A medication warning and a lunch invitation require different degrees of explicitness because their differ.

7The revised version is clear only if both participants can identify which version. That depends on .

Choose request grammar by action, choice, and consequence

Request forms do more than move from casual to formal. They can present the action as routine, optional, burdensome, negotiable, or required. A longer indirect form is not automatically kinder. If the listener has no real choice, state the requirement and explain it instead of performing false optionality.

Pattern	Typical use	Example
imperative + reason	clear routine, procedure, or urgent action	Please submit the signed form by noon so payroll can process it today.
can / could you + base verb	ordinary action request	Could you confirm the room number?
would you mind + -ing	acknowledges some imposition	Would you mind joining ten minutes early?
would it be possible to + base verb	asks whether an arrangement can change	Would it be possible to move the call to Friday?
I would appreciate it if + could	more formal request with a named action	I would appreciate it if you could confirm by May 8.
requirement + reason + support	action is obligatory, not optional	All visitors must sign in so we can account for everyone during an evacuation.

Contractions do not automatically make professional English casual

I’m writing to confirm..., we’ve attached..., and I’d appreciate... are common in many professional U.S. messages. An organization, legal genre, or highly ceremonial context may prefer uncontracted forms. Follow the real genre and relationship instead of applying a blanket rule.

Complete ten request and direction choices

1You are messaging a familiar teammate about a nonurgent shared task:

2You need a colleague to check specific attached data by a real deadline:

3You are asking an interviewer whether an agreed appointment can change:

4You recognize that an external presenter would need to give extra time for an access check:

5A manager is announcing a mandatory session and should not imply free choice:

6Smoke is entering the west hallway, so a safety officer gives the immediate action:

7An external reviewer needs to confirm receipt of a formal submission:

8Payroll genuinely needs a form today, so the writer gives an action, deadline, and reason:

9A public interface must tell every user exactly what to do next:

10A normal professional U.S. email may naturally begin:

Manage disagreement, refusal, and repair without hiding the message

Diplomacy protects the working relationship while preserving the real claim. It does not require vague agreement. A useful disagreement often moves through common ground + precise concern + evidence + workable alternative. A useful refusal often includes recognition + clear limit + brief relevant reason + possible alternative. An apology needs the problem + impact + responsibility + repair + next update when those facts are known.

Respect the listener’s agency

If you hold authority, do not make a requirement sound freely optional. If the other person can refuse, leave room for refusal. If you disagree, criticize the proposal or evidence rather than the person. If a problem affected someone, do not bury the impact beneath ceremonial language.

Choose eight relationship-sensitive moves

1Disagree with a budget proposal by acknowledging the concern and identifying one specific missing requirement:

2Decline a workshop invitation clearly while offering a realistic alternative:

3Apologize for a confirmed communication failure without hiding the organization’s action or inventing lost registrations:

4A possible gas leak requires proportionate urgency:

5A meeting change is genuinely negotiable, so leave room for refusal:

6The training is mandatory for the role, so state the requirement honestly:

7Challenge an overgeneralized research claim by identifying the evidence limit:

8Redirect an impractical proposal toward a testable next step:

Use plain language at every level of formality

Formal English does not require inflated synonyms. Use is usually clearer than utilize. We reviewed the data is often stronger than we conducted a review of the data. A phrasal verb and a single-word verb may differ in syntax, collocation, or meaning, so replace them only when the new sentence preserves the claim.

Choice	Useful effect	Risk to check
active subject + verb	makes responsibility and action clear	can overstate agency if the actor is uncertain
passive voice	focuses the event, result, or unknown actor	can hide a known responsible actor
nominalization	packages a known process as a concept	can hide who did what and increase density
phrasal verb	may sound natural and familiar	may be ambiguous or less expected in a formal genre
single-word lexical verb	may fit technical or formal collocation	may sound inflated or change the meaning
explicit I / we / you	clarifies participants and responsibility	the institution may require another perspective

Passive is a tool, not a formality switch

At 9:10, 38 duplicate emails were sent appropriately foregrounds the event if the actor is not yet known. Once the record establishes that the Cedar Loop scheduling team activated the wrong automation rule, our scheduling team activated the wrong rule preserves relevant responsibility. Choose focus from evidence and purpose, not from a rule that active is always informal or passive is always formal.

Complete seven clarity and responsibility decisions

1The formal report remains clear when it says the team , not that it utilized the checklist.

2The investigation confirms the responsible group and action, so write that .

3The equipment stopped, but no source yet establishes why. The cautious incident update says .

4In a formal case assignment, look into can be replaced without changing the purpose: .

5Replace the hidden verb in conducted a review of the data with .

6The public correction should report the bounded scope: the duplicate email problem .

7An external follow-up is easier to identify when it refers to , not merely the aforementioned matter.

Pronunciation focus: hear respect, focus, and urgency in U.S. speech

Politeness does not have one melody. A routine request may have a gentle fall, a rise, or a rise-fall depending on region, relationship, expectation, and conversational meaning. Speakers often group a request into a frame, action, and deadline: Could you send the checklist | by THREE? The most informative word in a thought group usually receives the main prominence.

In fluent U.S. speech, could you may sound like /kʊdʒə/ and would you like /wʊdʒə/. I would often contracts to I’d. These reductions are options, not requirements. Preserve clearer forms when the listener, audio quality, or stakes make them useful. Contrastive prominence repairs a detail: by THURSday, not FRIday.

Five spoken-form decisions

1Tutor line 1: Clip 1 Hearing could you as /kʊdʒə/ can be .

2Tutor line 2: Clip 2 Main prominence on three presents .

3Tutor line 3: Clip 3 The two prominences .

4Tutor line 4: Clip 4 The thought groups foreground .

5Tutor line 5: Clip 5 Firm prominence supports .

Read the Cedar Loop record across four channels

Internal incident notes, October 6: At 9:10 a.m., the Cedar Loop scheduling team activated the wrong automation rule. Thirty-eight of 240 registered attendees received two cancellation emails. Registration records were not deleted, and payments were not affected. Devin disabled the rule at 9:18. At 9:42, the team tested 60 fictional accounts with the corrected rule; no duplicate messages appeared. This staging test did not establish how the system would perform during the next live mailing.

Internal chat at 9:21: Devin wrote, “I turned off the rule. Registrations and payments are still intact. I’m checking the corrected version now. Can someone draft the attendee message?”

Attendee correction sent at 10:05: “This morning, we sent duplicate cancellation emails to 38 attendees. If you received two messages, please disregard the second one. Your workshop registration remains active, and no additional payment was taken. We apologize for the confusion. We corrected the mailing rule and will confirm the next workshop update by 11:00 a.m.”

Incident record completed at 11:20: “The scheduling team activated Rule C-17 instead of Rule C-12 at 9:10. The rule sent duplicate cancellation notices to 38 of 240 registered attendees. Devin Ortiz disabled C-17 at 9:18. A 60-account staging test at 9:42 produced no duplicate messages. The communications lead sent a correction at 10:05. Live-mailing reliability remains to be verified.”

Eight channel-and-evidence decisions

1. Which agency claim is established by the record?

2. Which sentence reports the bounded scope accurately?

3. What reassurance is directly supported?

4. Which immediate repair appears in every durable account?

5. Which conclusion matches the 9:42 test?

6. Why does the attendee message contain information absent from Devin’s short chat?

7. What does the formal incident genre require here?

8. Which principle connects all four channels?

Build three messages from shuffled chunks

1. External access request

Ask the venue coordinator to confirm one condition for the workshop.

2. Professional disagreement

Challenge the plan without attacking the person who proposed it.

3. Accountable public correction

Name the organization’s action, bounded scope, and supported reassurance.

Repair four register failures

Repair 1: mixed register

Tap the phrase that conflicts with the external email.

Repair 2: excessive mitigation in an emergency

Tap the phrase that delays the required action.

Repair 3: hidden responsibility

Tap the phrase that erases the established actor.

Repair 4: inflated formality

Tap the phrase that contains the clearest unnecessary inflation.

Rehearse fast shifts aloud

Respond before revealing. State the audience, relationship, channel, purpose, and stakes that justify your choice.

1 Ask a familiar teammate for the updated link without inventing urgency.

Can you send me the updated link when you have a minute?

2 Ask an external coordinator to confirm the step-free entrance by 3:00 p.m.

Could you please confirm by 3:00 p.m. whether the north entrance will be step-free?

3 Disagree with a claim based on twelve users without attacking the researcher.

The result is promising; however, a sample of twelve users does not yet support a general conclusion.

4 Report Cedar Loop’s error with responsibility, scope, and one unaffected system.

Our scheduling team activated the wrong rule, which sent duplicate cancellation emails to 38 of 240 attendees; registration records remained active.

5 Give the Cedar Loop staging result without turning it into a live guarantee.

The corrected rule produced no duplicates in 60 fictional staging accounts, but live reliability remains unverified.

6 Deliver a literal emergency direction with action and safe route prominent.

LEAVE now | through the EAST exit.

Play and practice

Games and a short reading that recycle this lesson. Use them as a warm-up, a fast finisher, or homework. Each one checks itself.

Read

One burst pipe, two messages

Read once for meaning. Then read again and do the tasks below.

Workplace case195 wordsAbout 2 min

Early on Tuesday morning, a pipe burst under the ground floor of the Maple Court office building. Facilities manager Jordan Lee had to tell two very different groups of readers about the problem before 9:00 a.m.

First, he wrote to his own team in their group chat: “Heads up: a pipe burst downstairs, and the ground floor is closed today. Don’t come in unless you need the archive. I’ll post an update at two.”

Then he emailed the 40 guests who had booked meeting rooms for that day: “Dear guests, we’re sorry to tell you that a water leak has closed our ground-floor meeting rooms today, Tuesday, May 6. Your booking has been canceled, and you won’t be charged. We’ve reserved rooms at our partner center on Elm Street, two blocks away, if you’d like to move your meeting there. Please reply by 11:00 a.m. so we can confirm your space.”

The chat is short because Jordan’s team already knows the building, the archive, and his role. The email gives the date, the cost, an alternative, and a deadline, because the guests know none of that. Both messages use contractions, and both fit their readers.

Find it

Tap the 6 contractions inside Jordan’s two messages (such as it’s). Do not tap names that end in ’s.

Check your understanding

1. Why is Jordan’s chat message so short?

2. What does the email offer the guests?

3. Why does the email include a reply deadline?

Memory

Inflated and plain wording

Flip two cards. If they belong together, they stay. Find every pair in as few turns as you can.

Unscramble

Build the request

Tap the words in order to build the sentence. Tap a placed word to send it back.

1. A familiar teammate, nothing urgent.
2. An ordinary action request.
3. Acknowledge some imposition.
4. Ask whether an arrangement can change.

Sort it

Who did it?

Does the sentence name who acted, or leave the actor unstated? Tap a sentence, then its box. Press Check when the tray is empty.

Practice register without private disclosure

You never need to reveal a real workplace conflict, disciplinary event, medical matter, immigration process, legal dispute, financial problem, family relationship, discrimination experience, confidential message, or power imbalance. Use Cedar Loop, a public notice, or a tutor-created situation. The skill is making language fit an explicit communicative situation, not proving that you know a hidden social code.

Audience switch: Keep one fact stable while addressing a familiar coworker, unfamiliar partner, affected customer, and public reviewer. Explain what each person already knows.

Power audit: Decide whether the listener can genuinely refuse. Rebuild false optionality as an honest requirement, or make real choice visible.

Plain-language edit: Replace three inflated nouns or verbs, restore any relevant actor, and preserve the original evidence strength.

Spoken shift: Deliver one request warmly, one correction contrastively, and one safety direction firmly. Change prominence, not every word.

Repair move: If a listener hears you as blunt, distant, vague, or overly familiar, name your purpose and reformulate instead of defending one expression as universally correct.

Final production and check

Final production: one event, four accountable messages

Use Cedar Loop or a new fictional event. Establish the event, date, people or teams, action, affected group, unaffected systems, immediate repair, current evidence, uncertainty, and next update. Produce four versions: a familiar internal chat, a neutral-professional partner email, a public correction, and a formal incident record. Keep supported facts stable while changing reference, organization, explicitness, vocabulary, grammar, and spoken delivery.

Include one ordinary request, one honest requirement or urgent direction, one professional disagreement, and one apology or refusal. Use a contraction naturally in one professional version. Use one phrasal verb only where its meaning and channel fit, then give a plain lexical alternative. Choose active or passive voice from evidence and focus. Deliver one spoken version with thought groups, optional reduction, and contrastive prominence. Your listener changes one variable, such as power, urgency, shared context, or channel; revise immediately.

Listener check: Can the listener identify the audience, relationship, role, purpose, channel, stakes, required action, deadline, agency, scope, and certainty? Does every mitigation serve a real interpersonal purpose? Does every formal choice remain clear?

Seven final decisions

1. Which definition is accurate?

2. A manager requires attendance. Which message represents the power relationship honestly?

3. Which sentence is a defensible professional disagreement?

4. Which incident sentence preserves established agency and scope?

5. Which sentence challenges the false rule that every professional message must avoid contractions?

6. Which Cedar Loop conclusion is appropriately calibrated for a formal report?

7. Which spoken delivery makes a routine request’s action and deadline easy to recover?

Reflect: could this reader act correctly?

Explain the choice, not only the label

Complete these lines aloud: My audience knows... Our relationship is... My role gives me... The message must... This channel expects... The consequence of ambiguity is... The listener can / cannot freely refuse... I named / omitted the actor because... The main spoken prominence belongs on... A plainer version would be...

Then change one variable. Rebuild the message instead of merely exchanging one “informal” word for one “formal” word.

Return tomorrow for the five-item retrieval check before rereading the lesson.

Next use: Before sending one real nonprivate message, write audience, relationship, role, purpose, channel, stakes, shared context, action, and deadline. Revise only the choices that do not serve that situation.

Next-day retrieval

Return without rereading. Reconstruct the decision system in five new fictional situations.

Five delayed decisions

1. Which principle should guide a new message first?

2. Which sentence communicates a real entry requirement appropriately?

3. Which public correction preserves responsibility and scope?

4. Which sentence is a natural neutral-professional follow-up?

5. The listener has the old file and knows a file is needed. Which delivery makes the changed version and deadline prominent?