Check cross-references before a shared document is released
A shared handout can contain clear sentences and still send readers to the wrong place. A numbered step may no longer exist, two diagrams may share a label, or a link may work while landing on unrelated guidance. Review those relationships explicitly. Colleagues can discuss the findings in a virtual office while keeping the reference register beside the document in their established tools.
Inventory pointers and targets separately
For this fictional practice exercise, imagine a workshop handout with four steps and two diagrams. Its opening says, “Use Figure 3 to choose a route.” A later paragraph says, “Follow Step 7 if your request is returned.” The revision contains only Steps 1–4, and both diagrams are labeled Figure 3.
Give each target a temporary identity independent of its displayed number: the route diagram, the category diagram, and the returned-request instruction. Record where each appears. Separately collect every sentence that points to a step, figure, heading, or anchor. A register entry includes the referring location, displayed pointer, intended target, and current finding. Listing only headings misses stale references embedded in prose.
Establish uniqueness before following a pointer
The first Figure 3 pointer is ambiguous even if both diagrams remain visible. Ask the author which diagram the sentence intends, then assign distinct labels to the targets. Suppose the route diagram keeps Figure 3 and the category diagram becomes Figure 4. Inspect every reference to Figure 3 before changing it; some may correctly describe routes while others describe categories.
A pointer that names Step 7 has no matching target. Do not redirect it to the last step merely to make the number exist. Locate the intended returned-request instruction, which may now be part of Step 4. If that instruction was removed entirely, the author needs to restore it or change the promise in the referring sentence.
Check the meaning at the destination
Read the referring sentence and its proposed target together. A link to Step 4 passes only if Step 4 explains what to do with a returned request. A destination that discusses final publication is not a substitute just because it concerns the same project.
Also inspect scope. A section can contain separate instructions for ordinary and exceptional cases. A pointer that promises an exception route should identify that part clearly. Record the actual mismatch: missing target, duplicate label, wrong subject, or unclear scope. Those findings require different repairs and should not disappear into a general comment that the links need work.
Repair both ends and repeat the inventory
After the author confirms intent, change the target label or content and each affected pointer. Keep a short note connecting the repair to the finding. Moving a section may affect references that were previously correct, so rerun the full register rather than checking only the edited paragraph.
In the exercise, verify that route references use Figure 3, category references use Figure 4, and every former Step 7 reference now identifies the actual returned-request guidance. Check captions and introductory summaries as well as body paragraphs. A successful repair should preserve the information the pointer promised.
Leave unresolved intent visible
Ask another reader to follow a few important pointers using the revised document alone. They should find one intended target and the relevant instruction without author hints. If the author cannot establish what a stale reference meant, mark it unresolved rather than inventing a convenient destination. The final register explains which relationships were checked and which still need a decision; a working link alone is not evidence that the reference is correct.
