Error, evidence or retest?
Choose the most precise status or error class. Do not call one uncertain occurrence a recurring problem.
1. A message says Thursday publication is definite although all four approvals are still pending. What failed first?
2. A close teammate receives “Pursuant to the aforementioned amendment…” but can still understand every fact. What needs review?
3. A learner marks every word prominent in both the familiar and institutional versions, and listeners cannot distinguish the intended relationships. What is the evidence?
4. One otherwise successful message contains a phrase whose audience fit is uncertain, and no similar example appears elsewhere. What status fits?
A fictional repair file
Use this file only where your own log has no recurrent example. These drafts deliberately combine several problems from the Unit 37 scenarios. Diagnose the consequence before replacing the wording.
A · Draft to contributors
Dear Valued Contributors, We regret that our intended meaning was misconstrued. A superior heading has now been devised, and your endorsement is required by Monday. Failure to reply will be understood as consent. We trust that this resolves the matter.
B · Draft to volunteer editors
Hey all, the page is kind of on ice. Tweak whatever needs tweaking, chuck in the new title and we’ll probably be live Thursday. Ping someone when you’re done. The other bits should be fine.
C · Draft to the funding liaison
Subject: contributors who objected — four names copied from the consent log. We’ve hit a bit of a snag because four people didn’t like our title, so we’ve binned it. No worries: we’ll definitely be live Thursday.
D · Rehearsal record. The speaker underlined every word for equal prominence, kept can, to and and full without a contrastive reason, and used the same chunking and pace for the teammate and liaison versions. In two trials, the listener could not identify either relationship from delivery.
Match each observation to A, B, C or D. A source may be used more than once. Some drafts have several problems; select the one named in the observation.
A Contributor draft
B Editor draft
C Liaison draft
D Rehearsal record
1. Treats non-response as approval and therefore changes the consent condition.
2. Blames recipients through misconstrued before announcing a supposedly superior solution.
3. Uses shared-context chat language while leaving the object of editing dangerously vague.
4. Turns a conditional Thursday path into a weak prediction rather than an operational rule.
5. Copies unnecessary personal identification into an external subject line.
6. Combines a casual account of the concern with an unsupported publication promise.
7. Removes information prominence by making every word equally prominent.
8. Shows a repeated failure to create an audible relationship contrast, rather than evidence from one isolated attempt.
Repair in consequence order
When a seam becomes an error-log target
| Status | Evidence threshold | Action |
|---|---|---|
| One occurrence | One choice with uncertain fit or one listener hesitation | Retest in a comparable context; do not generalise |
| Recurring seam | A similar mismatch in at least two stretches, with an observable listener or task consequence | Select one constrained repair and test it |
| Controlled contrast | Meaning remains stable and listeners recover the intended relationships from cited cues | Keep as evidence; increase the audience challenge later |
Four-step repair order
| Step | Repair question |
|---|---|
| 1 · Meaning and ethics | Did certainty, obligation, permission, attribution or privacy change? |
| 2 · Recipient action | Can this audience identify what it should know or do next? |
| 3 · Register bundle | Do lexical, grammatical and discourse choices create one defensible relationship? |
| 4 · Delivery | Do chunking, prominence and weak/full forms serve the information and relationship? |
Match each logged observation to the first repair it requires. Later polish cannot compensate for an earlier content failure.
Choose the intervention that responds to the logged listener consequence. Full forms remain legitimate when contrast earns them.
1. Every word is equally prominent in “The page stays PAUSED unless ALL FOUR approve.” What is the useful repair?
2. A learner keeps full /tuː/ in “from draft TO approved” to mark the endpoint contrast. What should happen?
3. The teammate and liaison versions remain indistinguishable after one retest. What is the next constrained experiment?
4. A planned liaison briefing contains ordinary weak forms but listeners recover the conditions accurately. What is the evidence?
Repair local errors, then rebuild the message
Correct the named content, collocation or register fault. The supplied answer is a compact model; discuss equally precise alternatives after checking.
1. The replacement heading has now been approved. — approval is still pending from four contributors
2. If most contributors approve, the page may be published on Thursday. — restore the threshold
3. Failure to reply will be understood as consent. — only explicit approval counts
4. Editors may update the recordings and captions while they wait. — those media are outside the heading review
5. The excerpt authorisation extends for online publication. — online use is prohibited
6. Please advise us if you’re still up for granting approval. — neutral request to a mixed contributor group
7. Pursuant to the update, can you all give us a shout when the thing is done? — neutral editor instruction
8. We may publish on Thursday, providing all four contributors approves.
Repair each extract for the stated audience and consequence. Preserve the decision record; remove every expression in the avoid list.
Contributors · restore accountability and choice
We regret that you misconstrued our intended meaning. A superior heading has been devised, and your endorsement is required. Failure to reply will be treated as consent.
Editors · replace vagueness with neutral ownership
The page is kind of on ice. Tweak whatever needs tweaking, chuck in the new title and ping someone when you’re done.
Funding liaison · concise, aggregate and conditional
Four named people didn’t like our title, so we’ve binned it. No worries: we’ll definitely be live Thursday.
Spoken liaison briefing · restore information structure
WE HAVE PAUSED THE PAGE WHILE FOUR CONTRIBUTORS REVIEW THE WORKING HEADING AND WE CAN PUBLISH ON THURSDAY IF THEY ALL APPROVE.
Run one evidence-based repair
Repair lab · Your recurring seam or the fictional file
Choose one pattern supported by at least two comparable stretches from Lessons 1, 3, 4 or 5. If your work contains no recurring seam, choose A, B, C or D from the fictional repair file and say so.
Produce a before-and-after repair whose meaning, audience effect and listener result can be compared.
- Use two minutes to record the two evidence points, intended audience, observed cue and consequence. If you have only one point, label the pattern “retest”.
- In four minutes, revise one 90–120-word message or a 45–60-second spoken version. Change only what the repair requires; preserve successful choices.
- In two minutes, annotate the revision: meaning/action repair, lexical and grammatical bundle, then delivery plan.
- Use two minutes for a blind listener test. The listener identifies the audience, reconstructs the key condition or permission and names the cues used.
- In the final minute, record whether the targeted consequence changed. Keep the before, after and evidence for Lesson 7.
Repair record
| Field | Required evidence |
|---|---|
| Pattern status | Recurring from two stretches / retest / fictional practice case |
| Before | Exact local wording or delivery notation plus intended audience |
| Consequence | Changed fact, unclear action, unintended relationship or listener failure |
| After | Minimal meaning-preserving repair |
| Test | What a listener recovered and which cue supported it |
Decide what the repair proves
Choose the conclusion warranted by the before-and-after evidence. Keep claims narrower than the sample.
1. One retest improves after a wording change, but no second example exists. What can be logged?
2. The revised message sounds consistent, but it changes all four approvals to most approvals. What is the verdict?
3. After one delivery variable changes, two listeners identify the audience and condition accurately. What does this support?
Close the error-log entry
Write the final line beneath your before-and-after pair.
State what changed, what stayed stable and what must be tested in Lesson 7.
- Complete: “When I changed ___ for ___, the listener could/could not recover ___.”
- Confirm that certainty, obligation, permission, attribution and privacy remained accurate.
- Carry forward one constraint, not a general instruction to “sound more formal” or “sound more natural”.
Repair the consequence, then stretch the range
Choose the sequence that should govern the Lesson 7 triple piece.
1. Which repair order protects both meaning and register?
Standing informal-input bridge
Use one legally accessible The Allusionist episode concerned with register and one London Review of Books essay. Find one local seam where the language shifts relationship or discourse job. Record the episode time stamp or essay paragraph opening, the two interacting cues and their effect. Do not call the shift inconsistent until the surrounding purpose gives you evidence.