Learners interact with fluency and spontaneity. They understand complex and abstract texts, argue a point of view, and write clear, detailed prose across a wide range of subjects.
Printable one-to-one lesson plan
Register & formality
Adapt vocabulary, grammar, directness, and message structure to relationships, channels, purposes, and degrees of formality.
Use after the complete B2 sequence, not as a lesson quiz.
Open diagnostic →15–20 minutes optional: Tutor-read U.S. request reduction, thought-group focus, contrastive deadline, accountable apology, and safety prominence listening check · Next-day register-definition, honest-authority, accountable-agency, professional-contraction, and spoken-focus retrieval
Derived from this lesson’s source
Lesson-specific teaching brief
This is not a second lesson registry. The plan reads the same native content that produces the learner page.
What the learner should do
Adapt vocabulary, grammar, directness, and message structure to relationships, channels, purposes, and degrees of formality.
What must become clear
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.
High-value friction points
- Hello Ms. Lee, I would like to ask whether you could send the signed agreement by Friday.Want to is commonly reduced to wanna in casual speech, but would like to fits this external professional request. The repair also makes the deadline explicit.
- Leave through the east exit now.An emergency instruction should minimize interpretive work. The imperative is proportionate to the risk and does not become impolite simply because it is direct.
- Our scheduling team activated the wrong automation rule at 9:10.The passive hides a known responsible actor. An accountable record can name the team without turning the sentence into a personal attack.
Protect these lesson moments
- Five prerequisite decisions
- Discovery check: infer the situation before labeling the language
- Diagnose seven situation variables
- Complete ten request and direction choices
- Choose eight relationship-sensitive moves
Learner production
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.
Carry this language into the next session
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.
Tutor-only contrastive support
L1 Transfer Lens
Test a pattern. Do not label a learner. Use this only after the learner’s actual production gives you evidence.
Select a first language to reveal only the contrasts relevant to this lesson.
Spanish → English
One pattern to test
Open formal emails directly and plainly
- Possible transfer
By means of the present, I address you to inform you that…
- English rebuild
I’m writing to let you know that…
Why it can happen: Formal Spanish correspondence has established openers such as por medio de la presente or me dirijo a usted. Translated word for word, they sound stiff or confusing in English, where even formal emails usually state their purpose in the first sentence.
Natural English:
- I’m writing to confirm our meeting on Thursday at ten.
- I’m writing about the invoice we received last week.
Turkish → English
One pattern to test
Address a teacher by name, not as teacher
- Possible transfer
Teacher, can I ask a question? / My teacher, I didn’t understand.
- English rebuild
Excuse me, Sarah, can I ask a question? / Sorry, Mr. Lee, I didn’t understand.
Why it can happen: Turkish commonly uses hocam, literally my teacher, as a respectful way to address teachers and many educated people. English rarely uses teacher or my teacher as a form of address with adults; it uses a first name, a title with a last name, or simply excuse me.
Natural English:
- Excuse me, Dr. Brown, could you repeat the last point?
- Thanks, Anna. That was really helpful.
Russian → English
2 patterns to test
Use statement order inside indirect questions
- Possible transfer
Can you tell me where is the station? / I don’t know what does he want.
- English rebuild
Can you tell me where the station is? / I don’t know what he wants.
Why it can happen: Russian embeds a question with the same words and order as a direct question, so the learner may also keep English question order. In English, the polite frame or main clause carries the question, and the embedded part returns to subject plus verb order without do.
Natural English:
- Do you know when the meeting starts?
- I’m not sure how much the tickets cost.
Soften everyday requests with modal questions
- Possible transfer
Give me the menu, please. / Send me the file today.
- English rebuild
Could I see the menu, please? / Could you send me the file today?
Why it can happen: In Russian, an imperative with пожалуйста is a normal, polite way to ask for something in many service and workplace settings. In American English, a bare imperative can sound abrupt even with please, so requests are usually framed as questions with could, can, or would.
Natural English:
- Could you take a look at this before lunch?
- Would you mind moving the meeting to three o’clock?
Ukrainian → English
2 patterns to test
Use statement order inside indirect questions
- Possible transfer
Can you tell me where is the station? / I don’t know what does he want.
- English rebuild
Can you tell me where the station is? / I don’t know what he wants.
Why it can happen: In Ukrainian, a question placed inside a larger sentence keeps the same words and order as the direct question. In English, an embedded question uses statement order, subject before verb, and loses the do-support that the direct question needed.
Natural English:
- Do you know when the next bus leaves?
- Could you tell me how much the ticket costs?
Frame workplace requests as questions
- Possible transfer
Send me the report today, please.
- English rebuild
Could you send me the report today?
Why it can happen: In Ukrainian, an imperative with будь ласка is a normal and polite way to ask for something in many settings. In American workplace English, an imperative can sound like an instruction from a supervisor even with please, so requests to colleagues and clients are usually framed as questions with could, would, or would you mind.
Natural English:
- Would you mind checking these numbers before lunch?
- I was wondering if you could join the call at three.
Czech → English
One pattern to test
Soften workplace requests with could and would
- Possible transfer
Send me the file, please. / I want the bill.
- English rebuild
Could you send me the file, please? / Could we have the check, please?
Why it can happen: In Czech, an imperative with prosím is a normal and polite way to ask, especially in writing: pošlete mi to prosím. In English, please softens an imperative only slightly, so requests to clients, coworkers, and service staff usually use a question with could, would, or would you mind.
Natural English:
- Would you mind sending me the updated version by noon?
- Could you let me know if Thursday works for you?
Italian → English
One pattern to test
Swap formal email calques for plain business English
- Possible transfer
I inform you that the meeting is moved. I remain at your disposal for eventual clarifications.
- English rebuild
Just to let you know, the meeting has moved to Wednesday. Let me know if you have any questions.
Why it can happen: Italian formal correspondence relies on fixed formulas that sound polite in Italian. Translated literally, they can sound stiff or confusing in English, where most business emails prefer short sentences, direct verbs, and friendly fixed closings.
Natural English:
- I’m writing to confirm the details of our call.
- Please let me know if you need anything else.
Use while teaching
Operational teaching notes
Choose a route before class, but change it when the learner’s production gives you better evidence.
Ask before explaining
- Which examples in “Five prerequisite decisions” express the same core meaning?
- How would you explain this decision in your own words: 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.
- What needs to change in this repair, and why: Hello Ms. Lee, I would like to ask whether you could send the signed agreement by Friday.
Correct for the stage
- Controlled work: correct immediately, then require the complete repaired sentence.
- Fluency building: note repeated errors and reformulate after the learner finishes the thought.
- Communication: interrupt only when meaning breaks down or the target decision is the lesson’s main evidence.
Retrieve, do not reteach
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.
Short, core, or extended
Choose the route
All three routes end in learner production. More time means more contrast and transfer, not a longer explanation.
Short route
Retrieve for 3 minutes. Notice and discover for 8. Use the two most diagnostic tasks from Five prerequisite decisions and Discovery check: infer the situation before labeling the language for 12. Protect 9 minutes for Learner production, then reflect for 3.
Core route
Follow the six-stage sequence below. Reduce repeated controlled items when accuracy is already stable, but keep the nearest useful contrast and final production.
Stretch route
Add Tutor-read U.S. request reduction, thought-group focus, contrastive deadline, accountable apology, and safety prominence listening check · Next-day register-definition, honest-authority, accountable-agency, professional-contraction, and spoken-focus retrieval, then repeat the communication task with a new situation or stricter success criteria.
70–80 minutes core working plan
Session sequence
Protect the final communication and reflection time. If the learner needs more support, reduce the number of controlled items instead of removing production.
- 5 min
Retrieve
Activate what the learner already controls and check any prerequisite language.
Teacher move: Open with the first practice route: Five prerequisite decisions · Discovery check: infer the situation before labeling the language · Diagnose seven situation variables.
- 6–8 min
Notice
Let the learner observe meaning and form in a small sample before naming the rule.
Teacher move: Keep the noticing conversation anchored to this decision: 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.
- 8–10 min
Discover
Connect form, meaning, use, word order, and the nearest useful contrast.
Teacher move: Test the learner’s explanation against this repair: Hello Ms. Lee, I would like to ask whether you could send the signed agreement by Friday. Want to is commonly reduced to wanna in casual speech, but would like to fits this external professional request. The repair also makes the deadline explicit.
- 12–15 min
Build + drill
Move from accurate choices to faster retrieval and sentence construction.
Teacher move: Prioritize these lesson tasks: Five prerequisite decisions · Discovery check: infer the situation before labeling the language · Diagnose seven situation variables · Complete ten request and direction choices. Reduce repetitions if needed, but keep the final production time.
- 12–15 min
Communicate
Use the target language for a real adult purpose the learner cannot complete by copying.
Teacher move: Learner production: Audience switch: Keep one fact stable while addressing a familiar coworker, unfamiliar partner, affected customer, and public reviewer. Explain what each person already knows.
- 3–5 min
Reflect
Make progress visible and choose one specific next use.
Teacher move: 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.
Tutor-only source
Listening scripts
Read these lines from the tutor plan while the learner lesson remains on screen. Each clip names the learner item it supports.
Tutor-read U.S. request reduction, thought-group focus, contrastive deadline, accountable apology, and safety prominence listening check
- Clip 1
Read: Could you send the checklist?
Supports: Tutor line 1: Clip 1 Hearing could you as /kʊdʒə/ can be listen .
- Clip 2
Read: Could you CONFIRM it | by THREE?
Supports: Tutor line 2: Clip 2 Main prominence on three presents listen .
- Clip 3
Read: Not THURSday | FRIday.
Supports: Tutor line 3: Clip 3 The two prominences listen .
- Clip 4
Read: We sent duplicate messages to THIRty-eight attendees | and we’re sending a correction NOW.
Supports: Tutor line 4: Clip 4 The thought groups foreground listen .
- Clip 5
Read: LEAVE now | through the EAST exit.
Supports: Tutor line 5: Clip 5 Firm prominence supports listen .
Delivery and evidence notes
- Read each line once carefully and once conversationally. Do not force the reduced forms. Keep dates, numbers, actions, and corrections recoverable, and let the communicative contrast determine the main prominence.
Keep only useful evidence
After-lesson notes
These notes are for deliberate tutor records or printing. Nothing is stored in the learner’s browser.
The learner can now…
Write one observable use of the target language.
Still needs support with…
Record one repeated error, contrast, or point of hesitation.
Next retrieval prompt
Write one short prompt the learner will answer at the next session.
Anonymous live-lesson evidence
Learner pilot worksheet
B2 · Register & formality
Pilot 1 of 30 recorded · 3 remaining
Date
Approximate starting level
Core lesson time
Starting evidence
What did the learner already control? What was the first misconception, hesitation, or contrast that mattered?
Did the principle become clear?
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.
Did the first hint help?
Record the first item that caused difficulty and whether the contextual hint led to self-correction before the full repair appeared.
Could the learner do the outcome?
Adapt vocabulary, grammar, directness, and message structure to relationships, channels, purposes, and degrees of formality.
Listen for: The learner uses the target language independently for a real purpose.
What remained available?
If possible, check before rereading in the next session. Record what returned independently and what still required a cue.
Keep, revise, or investigate?
Note any explanation the tutor still had to supply, the smallest useful revision, and whether another pilot should test the same issue.