Check document cross references before sharing a report

A final check of document cross references matters even when every section, figure, and appendix appears to be present. A sentence can send a reader to an existing destination that no longer answers the question the sentence raises. Before sharing a workplace report, read each internal pointer alongside the material it promises to show. Check both where it leads and whether that destination supports the claim.

Imagine a fictional report about how meeting rooms were used during a pilot program. Its sections describe observations, interpret them, and recommend a next step. A figure once displayed a comparison, while an appendix originally explained how observations were recorded. During editing, someone renumbers a section, removes the figure, and changes the appendix. None of those edits necessarily makes the report's argument wrong, but each can leave a different kind of misleading pointer.

Choose the exact copy intended for sharing and keep that copy in view for this pass. The point is to check the words recipients will read, including references in captions and notes if those are part of the report. Set aside a brief list of unresolved questions for the author; a reviewer should not fill gaps by assuming what a missing figure or altered appendix used to contain.

Document Heading Hierarchy And Reference Promises

Begin with language that asks the reader to look elsewhere in the report. Some pointers announce themselves with a section number, figure label, or appendix name. Others say “the comparison below,” “as discussed later,” or “the procedure described above.” Read through the report in its normal order and mark each such phrase. A reference need not be formatted as a link to affect how a reader interprets the sentence.

For each marked sentence, write a short description of what the reader is being promised. “The observations are summarized in Figure 1” promises a display of observations. “Section 3 explains why the pattern matters” promises an explanation. “See Appendix A for the recording procedure” promises steps or a description of how the observations were recorded. Those are different obligations, even if the same destination might occasionally satisfy more than one.

Keep the description close to the sentence's actual wording. If it says a figure compares two categories, do not reduce the promise to “something about categories.” If it merely says that a figure illustrates the discussion, do not demand measurements the sentence never promises. This small discipline stops the audit from becoming a general rewrite of the report. You are testing the pointer and its claim, not redesigning the argument.

Now locate the named destination in the sharing copy. Read its heading or label, then read enough of the destination to judge its contents. An exact label match establishes only that the named item exists. A section titled “Pilot observations” might contain a description of room availability but no comparison of usage. In that case, a sentence promising the comparison still needs attention, however accurate the section number looks.

When the pointer is vague, identify all plausible destinations before deciding what to change. “The results below” might refer to a short paragraph, a figure farther down the page, or a table in the next section. If two destinations fit, the author may need to name one. If none contains the promised information, replacing “below” with a more precise label will not fix the substantive gap. A precise pointer to the wrong content is still wrong.

A compact audit note can pair the referring sentence with its promised content, the destination found, and a disposition such as “supported,” “unclear,” or “missing.” Record the actual discrepancy in ordinary words: “Section 3 contains recommendations, not the method named here.” This is a working note for one sharing copy, not a new filing system. Its value is that another editor can understand why a particular sentence was flagged without guessing at your intention.

If section relationships themselves make it impossible to tell which destination is intended, resolve that structural question separately. The guide to document heading hierarchy addresses how headings relate within a long report. Once the destination is identifiable, return to the narrower test here: does the passage under that heading provide what the referring sentence says it provides? A sound structure cannot make an inaccurate claim true.

Document Heading Hierarchy In The Edited Report

Return to the fictional meeting-room report after its edits. Suppose the interpretation section moved from Section 3 to Section 4, but an earlier paragraph still says, “Section 3 explains the likely cause.” Open Section 3 in the sharing copy. If it now contains only observations, the reference has two problems: the number points to the wrong place, and the promised explanation is absent there. Find the explanation in Section 4 before changing the number. If that section does not actually explain a cause, revise the referring sentence rather than making it promise more than the report supports.

Next, consider a sentence that reads, “Figure 1 compares morning and afternoon room use.” The figure was removed in editing. This is a missing destination, not a numbering problem. If the report still contains the comparison in a different form, the author can direct readers to that actual material and adjust the sentence to describe it accurately. If the comparison was removed altogether, delete or qualify the claim according to what remains. Recreating a figure solely to preserve an old reference is an editorial decision, not an automatic repair.

Finally, the appendix was changed from a description of the recording procedure to a discussion of limitations. An earlier sentence still reads, “Appendix A describes how each observation was recorded.” Appendix A exists, so a quick check of labels alone would miss the error. Read the appendix. If it only describes limitations, change the referring sentence to reflect that role where useful, or ask the author where the procedure now appears. Do not treat an appendix title as evidence of content that has been removed.

These cases call for distinct corrections because the underlying failures differ. A moved explanation may need a corrected destination and a more modest claim. A removed figure may leave the sentence without any support. A repurposed appendix can retain its label while changing what that label delivers. Write the proposed correction beside each flagged sentence, and leave an explicit question when you cannot establish the answer from the sharing copy.

Read the revised sentence and its destination together once more. If the sentence says “as shown,” is there something a reader can actually see? If it says “explained,” does the destination give a reason or interpretation rather than simply repeat an observation? If it says “details,” are the promised details present? Small verbs can carry a bigger promise than the destination can meet. Adjust the verb or the pointer to match the information on the page.

Watch for references that appear in passages altered late in the edit. An introduction may still describe a figure that disappeared, and a recommendation may refer back to an interpretation that was shortened. Scan captions and concluding paragraphs as well as the main discussion. The aim is to catch internal invitations to look elsewhere wherever they occur, while leaving ordinary mentions of a topic alone if they do not direct the reader to another location.

Once the author has resolved open questions, repeat the check of document cross references on the copy that will actually be shared. Check the final wording against its final destination, particularly where a correction changed both a sentence and a label. A note marked “fixed” is not evidence that the shared text now reads correctly. It is possible to repair a reference in a working passage and leave an older version of the sentence elsewhere in the report.

Tablet Report Review Before The Copy Goes Out

The audit needs a readable copy and a place to record questions; it does not require a particular device. For someone assembling the report on a laptop, the listed Dell Inspiron can be an optional workspace for checking document cross references against the document. Check that the software you intend to use can open and edit your report before choosing hardware for that purpose. The laptop listing alone does not establish that any particular document application is included.

A separate reading pass can help you encounter pointers in the order a recipient will. The listed refurbished Apple iPad 6th Generation, model A1893, is one optional device to consider for tablet report review. Confirm that suitable software can access and display the intended sharing copy on the device before relying on it. There is no need to assume that the laptop and tablet automatically share a file or present it identically.

On that separate pass, read the report continuously until a sentence tells you to consult another part. Stop and ask what you expect to find before going there. Then find that destination and read it in context. If you have to search several places to understand “see below,” note the ambiguity. If you arrive at a labeled section that discusses a different issue, flag the mismatch even though you reached the named section.

This reading pass complements the earlier audit rather than replacing it. An audit note may accurately identify a moved explanation, yet the corrected sentence may sound awkward when read without the editor's notes. Conversely, a reference can sound plausible in running prose while pointing to an appendix that has changed purpose. Keeping the promise in mind while reading the destination catches both kinds of problem.

If a destination partly supports the sentence, decide which part of the promise to keep. A section may describe that room use differed across periods without identifying why. “Section 4 discusses the observed difference” could be defensible where “Section 4 explains the cause” is not. If the wording needs a decision about what the report intends to claim, ask the author; editorial confidence should follow the material, not replace it.

End with the references that remain unresolved. Tell the author which sentence points where, what the destination contains, and the decision still needed. For example: “The text sends readers to Appendix A for the recording procedure; Appendix A now discusses limitations. Where should the procedure be described, or should this sentence be removed?” That question gives the author a specific choice without inventing missing report content.

Before sharing, read the copy one last time with the corrected references in place. A recipient should be able to follow each pointer to the material that the surrounding sentence promises, whether it names a section, a figure, an appendix, or a nearby passage. If a promise still cannot be supported, leave it out of the sharing copy until the responsible author settles it.