How do I plan updates when one change affects several instruction pages?
Quick answer
Before editing, write down the change and the authoritative source for it. Search for every page, section, example, link, and cross-reference that might depend on the old wording. Track each affected location, its needed action, an owner or status, and the check that will confirm it is consistent. After revising, compare the related pages against the source and mark the change complete only when each listed location has been reviewed.
The question, the details, the next step.
One change affects several instruction pages. How can I work out what needs updating before I start rewriting?
Start with a small change-impact map rather than editing the first page you find. Write the change in one sentence, then identify where readers encounter the affected instruction: the main page, related steps, examples, summaries, links, and any page that repeats the wording.
Use the authoritative source for the change as your reference point. If you do not yet know which source is authoritative, mark that as an unresolved question instead of guessing. A page that merely links to the affected instruction may need a link check, while a page that repeats the instruction may need a content update.
A useful tracker has one row per location, not just one row per page. That makes it easier to catch a changed example or a stale cross-reference buried in an otherwise up-to-date page.
What should I record in the tracker so it helps with both the edits and the final review?
Include enough detail that another writer can understand the task without reconstructing your reasoning. For each affected location, record:
- Page and section, using a title or stable internal identifier.
- What appears there now, described briefly rather than copied at length.
- The action needed: revise, verify, update a link, or leave unchanged after checking.
- The source of truth to compare against, such as a named document or a placeholder for the approved reference.
- Status and reviewer, if your team uses those fields.
- A specific completion check, such as “example matches revised step” or “link points to the current instruction.”
Keep the tracker focused on this change. It is a coordination aid, not a substitute for the actual approved wording.
Could you show a worked example? Say a step changes and several pages repeat it.
Assume, just for illustration, that an approved instruction changes from “include the label” to “include the label and date.” The authoritative reference is represented as [approved instruction source]; those details are placeholders, not claims about a real policy.
A compact tracker could look like this:
Change: Update the instruction to include the label and date. Source of truth: [approved instruction source]
- [Page A], Step 2 | Repeats the old instruction | Revise | Check wording against source | Open
- [Page B], Example 1 | Shows a sample with only the label | Revise example | Check sample demonstrates both items | Open
- [Page C], Summary box | Condenses the instruction | Verify and update if needed | Check summary does not omit the date | Open
- [Page D], Link to [Page A] | Does not repeat the instruction | Verify link and destination | Open
After the edits, read the changed sections together. Check that the example, summary, and main step agree, and that each link still leads to the intended page. If a location was reviewed and does not need a change, record “checked—no edit” rather than leaving it looking forgotten.
How do I avoid inconsistent wording when different people edit different pages, and know when the update is finished?
Give editors the same short change statement and the same approved reference. If exact wording matters, include the approved wording in the tracker or point to its named location; ask editors not to improvise a different version on each page. Where a page needs a reader-friendly variation, record that as an intentional variation and check that it preserves the instruction’s meaning.
For the final review, compare every changed location with the source, then compare related pages with one another. Look for stale examples, summaries that drop part of the change, and references that lead to the wrong place. Mark the tracker complete only after every listed location has a status and a recorded check. If the source or intended wording remains unclear, keep the item open and ask the responsible editor to resolve it rather than treating an assumption as settled.
A practical checklist
Write the change in one sentence and name the authoritative reference.
List every affected page, section, example, summary, and cross-reference.
Give each location a clear action, status, and completion check.
Share the same approved wording or source with all editors.
Review related locations together and record checked items that need no edit.
A few more useful answers
Should I make one tracker row per page or per change location?
Use one row per location that may need a different action, such as a step, example, or summary. Combine locations only when they share the same edit and the same completion check.
What if I find another affected page after editing begins?
Add it to the tracker, identify its source reference and needed check, then review it alongside the other affected locations. Do not assume that an unlisted mention is already consistent.
Can I close a tracker item without changing the page?
Yes, if you reviewed the location against the authoritative reference and recorded why it needs no edit. That distinguishes a deliberate check from an overlooked item.