Practical guide

Map a procedure change to every lesson element it affects

Last materially reviewed 2026-10-02

Quick answerTrace the changed rule into examples, answers, feedback and shared references before publishing a revision.
What to know

Describe the change, not just the new version

“Updated to version four” does not tell a reviewer what to inspect. Name the source step and the actual difference: a new waiting-list state, changed owner or revised confirmation condition. Separate wording improvements from changes in expected action. The former may need a reading check; the latter can affect practice answers and the way previous completions should be interpreted.

What to know

Walk the dependency chain

Use the source map to identify explanations, examples, questions and feedback that depend on the rule. Then list shared locations such as a course link, embedded page or exported package. Our local worksheet turns a non-sensitive list of affected lesson elements into a review checklist. It does not discover dependencies automatically, edit a course or send a notification.

What to know

Review old results honestly

A completion recorded before a material change does not prove that the learner has seen the new instruction. Decide what follow-up is appropriate within your real training process, and avoid rewriting historical results to make them appear current. This publication does not determine compliance or employment consequences. Keep the content-change record separate from the observed learner activity.

What to know

Publish only the checked version

After the revision is reviewed, inspect the actual shared learner view and any exported destination within your authorized workflow. Preserve enough history to explain which source supported the old and new answers. If a dependency remains unknown, do not claim the update is complete. Use the maintenance-cost worksheet to decide whether a large collection is becoming too costly to keep trustworthy.

What to know

Example dependency checklist

For the fictional waiting-list change, inspect the status explanation, booking-sheet example, scenario answer and feedback. Also inspect any embedded copy and link description that promises the previous behavior. The checklist is complete only for the dependencies you actually identified; it is not an automatic inventory of every shared copy.

Continue when useful

Next: Revision check

Test the changed dependency and a nearby unchanged path; preserve the scope of the review.

Open Revision check →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. CDC Quality Training Standards — Standards and certification reference · cdc.gov · Publisher independence not verified · checked 2026-10-02
LOCAL WORKING DRAFT

Make the changed dependency visible.

Use fictional or non-sensitive descriptions only. No names, private procedures, learner records or confidential operating details. Nothing is uploaded or stored by this tool.

No draft prepared.