Use lessons 01–01 or equivalent skills before this exercise. You can revisit them from the lesson list.
A browser and text editor. Supplied notes and drafts work offline. Optional live tools must be approved for the data.
Start with the idea
Improve a message’s tone without adding a commitment.
Keep promises, conditions and unknowns intact when rewriting. A friendlier sentence can still change the obligation. Compare the new wording with the original note.
Conditional commitment: A possible action that depends on a stated condition.
See the example and check your understanding
A made-up teaching example
The note says a prototype may be delivered by 4 September if the test environment is ready. Readiness is unknown. “We guarantee delivery” removes the condition and adds a promise.
Ask yourself
Can you remove the readiness condition just to make the email sound confident?
Show the explanation
No. Keep the possible date conditional and request confirmation without inventing a new promised action.
Start with these checks
- Preserve conditions and requested dates.
- Do not invent owners or confirmations.
- Check obligations after editing tone.
Use the different practice case below and check every requirement in its full instructions.
Full learning objectives
- Distinguish proposals from commitments.
- Check names, dates and conditions.
- Handle missing information transparently.
Captions appear here during playback.
Draft correspondence without changing commitments
Improve a message’s tone without adding a commitment.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · What you will learn
Improve a message’s tone without adding a commitment.
What appears on screen
Improve a message’s tone without adding a commitment.
0:05 · The idea
Keep promises, conditions and unknowns intact when rewriting. A friendlier sentence can still change the obligation. Compare the new wording with the original note.
What appears on screen
Keep promises, conditions and unknowns intact when rewriting. A friendlier sentence can still change the obligation. Compare the new wording with the original note.
0:19 · One useful term
Conditional commitment. A possible action that depends on a stated condition.
What appears on screen
A possible action that depends on a stated condition.
0:27 · A worked example
The note says a prototype may be delivered by 4 September if the test environment is ready. Readiness is unknown. “We guarantee delivery” removes the condition and adds a promise.
What appears on screen
The note says a prototype may be delivered by 4 September if the test environment is ready. Readiness is unknown. “We guarantee delivery” removes the condition and adds a promise.
0:42 · Your turn to think
Can you remove the readiness condition just to make the email sound confident? Pause and decide before continuing.
What appears on screen
Can you remove the readiness condition just to make the email sound confident? Pause the video if you need more time.
1:00 · Why this answer works
No. Keep the possible date conditional and request confirmation without inventing a new promised action.
What appears on screen
No. Keep the possible date conditional and request confirmation without inventing a new promised action.
1:09 · Check 1
Preserve conditions and requested dates.
What appears on screen
Preserve conditions and requested dates.
1:15 · Check 2
Do not invent owners or confirmations.
What appears on screen
Do not invent owners or confirmations.
1:20 · Check 3
Check obligations after editing tone.
What appears on screen
Check obligations after editing tone.
1:26 · Now try a different case
Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →
The method
Use a source-first correspondence workflow: facts, purpose, draft, comparison, final review. Ask for a specific audience and tone, plus an instruction to preserve conditions and identify gaps. Avoid asking the model to “make it persuasive” before deciding what you can truthfully promise.
Review dates, names, amounts, dependencies and commitment verbs separately. “Could,” “will,” “approved,” and “subject to review” are not interchangeable. Keep a change log for meaningful edits. If an assistant cannot inspect an attachment, provide the relevant permitted text or stop; it should not imply it read the file. A second generated draft is another candidate, not proof of correctness.
Choose your model, harness and offline route
Text-only assistant
Use supplied text. Ask for a plan or draft; do not claim browsing, code execution or file access that was unavailable.
Tool-enabled application or harness
Record which tools actually run, allowed files and actions, approval boundaries and observable results. Tools are optional unless the task needs them.
Local or cloud deployment
Inspect inference, retrieval, connectors, logs and storage separately. Use only authorized environments for real data; training fixtures are fictional.
Higher-capability or frontier model
Evaluate the exact task and configuration. Capability does not supply missing evidence or grant permission. No provider ranking or guarantee is implied.
Offline alternative
Use the supplied inputs and inspect the worked example manually. Builder exercises use local deterministic Python. No paid account or live model call is required.
Record the exact product/model label when available, tools actually used, inputs, permitted actions, observed output and checks. Live accounts or APIs may have external costs; they are optional and are not used by this page.
Read the general workflow guide →Worked example
Supplied input
Fictional note: a team may deliver a prototype by 4 September if the test environment is ready. Environment readiness is unknown. Draft: “We guarantee delivery on 4 September.”
A checked result
“A prototype by 4 September remains conditional on test-environment readiness. Readiness still needs confirmation before any delivery commitment.”
Why this works
The rewrite preserves a conditional possibility and unresolved readiness without adding a new promised action.
Try a different case
Independent note: room booking requested for 9 June; no confirmation; accessibility arrangement pending. Repair: “Your room and accessibility arrangements are confirmed for 9 June.”
Download this task and checklist →Interactive practice / Fictional fixture
Repair an unsupported commitment
Use the supplied independent case above. Check the bounded decisions, then review your written artifact against the full acceptance criteria.
Everything runs in this browser. No AI model is called and no work is uploaded. Bounded checks cover specific facts and rules. Your writing is not graded: you review it yourself. Practice never marks a lesson complete automatically.
Preserve 9 June as the requested date and identify confirmations needed. Do not invent a venue or owner.
Try the task, run the checks, then revise. Checks are teaching feedback, not an instructor grade.
Observed browser simulation
This trace comes from the bounded local checker. It is not a Python run, model result or production tool execution.
Self-review
Locked. Write every written part, then run the checks. A few words is not an attempt.
This is self-review, not grading. Read our answers, then tick what your own work does. Ticks are optional. They stay on this page and are not saved or sent anywhere. A different answer can be just as good if it meets the lesson criteria.
Your repaired message
A strong answer
We have requested a room for 9 June. We have not received a confirmation yet. The accessibility arrangement is also still pending. Two things need confirming before you can rely on this: the room booking and the accessibility arrangement. I will tell you when either one changes. (Proposed, not agreed: I can check on both again this week.)
A flawed answer
Your room is likely confirmed for 9 June in Room 4, and the accessibility arrangements should be fine. Sam will follow up on Friday.
What is wrong with it: “Likely confirmed” and “should be fine” add confidence the note does not have. Room 4, Sam and Friday are invented: the note names no room, no owner and no follow-up date.
Keep or restore your work
Drafts are not saved automatically. Save only fictional practice data. A browser draft may be lost if storage is cleared; download a copy to keep it.
Your steps
- Mark each unsupported commitment.
- Write an audience-appropriate correction under 80 words.
- List the confirmations needed before release.
Check your work
- Booking and arrangement remain pending.
- 9 June remains the requested date.
- Do not invent an owner, venue or confirmation.
After your attempt: review notes and a common mistake
A supported draft says the requests are pending and identifies the confirmations still needed. Label any proposed follow-up as a proposal rather than a new promise. “Likely confirmed” still supplies confidence absent from the note.
Different wording or a different justified decision can pass. Check your work against every requirement; these notes are not an automated grade.
Explain your approach
Which words in your draft create a new promise?
Keep your artifact, one correction or decision, its evidence and one remaining limitation. Nothing on this page sends or uploads your work.
Check your understanding
Choose an answer to see feedback. This is a knowledge check, not instructor assessment.
Review your independent practice
Complete the supplied task before recording progress. Use the acceptance criteria and reveal the review notes after your attempt. Keep your artifact yourself; nothing is uploaded.
Not yet self-reviewed. Completion stays in this browser and does not issue a badge.
Optional deeper study
Explore the related general-course lesson → This opens the existing canonical lesson; it is optional depth, not another copy of this focused task.
Revision 2026-10-03. Fictional examples, not observed provider results. Knowledge checks and completion records are self-study aids.