Use lessons 01–05 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
Make related documents agree with the same source facts.
Check across the update, agenda and action list, not only within each document. Keep pending dates and approvals consistent. Release remains a separate human action.
Cross-document check: Comparing related outputs for conflicting facts or commitments.
See the example and check your understanding
A made-up teaching example
The worked packet uses the same pending date in its update and agenda. Neither claims a room is booked. A reviewer checks the packet before any release.
Ask yourself
Can one document call the room confirmed while another says pending?
Show the explanation
Not without supported new evidence. Preserve the actual commitments and stop for missing confirmation.
Start with these checks
- Compare shared facts across outputs.
- Keep pending items pending.
- Include a stop and escalation path.
Use the different practice case below and check every requirement in its full instructions.
Full learning objectives
- Preserve facts across multiple outputs.
- Test exceptions and commitments.
- Document review, release and improvement limits.
Captions appear here during playback.
Capstone: assemble a checked work packet
Make related documents agree with the same source facts.
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
Make related documents agree with the same source facts.
What appears on screen
Make related documents agree with the same source facts.
0:06 · The idea
Check across the update, agenda and action list, not only within each document. Keep pending dates and approvals consistent. Release remains a separate human action.
What appears on screen
Check across the update, agenda and action list, not only within each document. Keep pending dates and approvals consistent. Release remains a separate human action.
0:20 · One useful term
Cross-document check. Comparing related outputs for conflicting facts or commitments.
What appears on screen
Comparing related outputs for conflicting facts or commitments.
0:29 · A worked example
The worked packet uses the same pending date in its update and agenda. Neither claims a room is booked. A reviewer checks the packet before any release.
What appears on screen
The worked packet uses the same pending date in its update and agenda. Neither claims a room is booked. A reviewer checks the packet before any release.
0:42 · Your turn to think
Can one document call the room confirmed while another says pending? Pause and decide before continuing.
What appears on screen
Can one document call the room confirmed while another says pending? Pause the video if you need more time.
0:59 · Why this answer works
Not without supported new evidence. Preserve the actual commitments and stop for missing confirmation.
What appears on screen
Not without supported new evidence. Preserve the actual commitments and stop for missing confirmation.
1:09 · Check 1
Compare shared facts across outputs.
What appears on screen
Compare shared facts across outputs.
1:14 · Check 2
Keep pending items pending.
What appears on screen
Keep pending items pending.
1:19 · Check 3
Include a stop and escalation path.
What appears on screen
Include a stop and escalation path.
1:24 · 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
A work packet tests whether you can keep several artifacts consistent: update, agenda, action register and procedure. Build them from one factual record, then inspect cross-artifact dates, owners and status. An assistant may improve wording, but you remain responsible for source comparison and release decisions.
Document the workflow so a colleague could repeat it: inputs, model/tool assumptions, acceptance checks, review owner, permitted actions and recovery. Separate proposed improvements from approved instructions. Keep your evidence in a safe workspace; a completion record is self-review, not proof that an employer authorized the workflow.
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
Worked packet outline: source facts → draft update → agenda → action register → contradiction check → reviewer decision. No sending or scheduling is automatic.
A checked result
Review note: “The update and agenda share the same pending date. No artifact claims the room is booked. Release remains a human action.”
Why this works
Consistency across outputs matters as much as polish within a single document.
Your independent capstone
Independent capstone: fictional orientation requested for 7 October, room pending; Dana owns checklist review due 2 October; two accessibility questions unresolved; launch date is a proposal; no sending or booking is authorized. Produce an update, agenda, action register and a release checklist.
Download this task and checklist →Interactive practice / Fictional fixture
Check the work packet before release
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.
Keep dates and unresolved issues consistent; record a correction and manual fallback.
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.
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
- Create a factual register and draft all four artifacts.
- Check dates, owners, commitments and unresolved issues across them.
- Simulate room confirmation remaining absent on 6 October.
- Record one correction, your tool setup or offline route, and a repeatable workflow.
Check your work
- Keep the room and launch pending.
- Preserve Dana’s actual commitment.
- Include a stop/escalation path for missing confirmation.
- Do not invent approvals or perform external actions.
After your attempt: review notes and a common mistake
A strong packet retains uncertainty consistently and provides a useful next action. A beautifully worded invitation announcing a confirmed venue fails the factual and authorization criteria.
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 artifact creates the highest consequence if a fact is wrong?
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.