When Page Numbers Disagree: A Source-Page Map for Report Drafts

When page numbers disagree, identify the document copy first and record both its viewer position and its printed page label. Keep the position in a combined review packet in a separate field. A reference such as “page 3” is not sufficient if a cover sheet, an unnumbered insert or a later packet arrangement makes several different pages fit that description.

This guide provides an original manual source-page map for report writers and reviewers. It supports document organization only. It does not establish the truth of a source, certify that a packet is complete, or make coverage, liability, payment or other claim decisions. The map is a working document; it is not a claim that StateClaimAI automatically numbers, combines or validates source files.

Separate the three locations

A printed page label is the text visible on the page itself. It might be a number, a section label, or absent. A viewer position is the page's place in a particular file as opened in the viewer being used. A packet position is its place within a particular assembled review packet. These locations can coincide, but they should not be assumed to do so.

Always pair a viewer position with the exact file identity or copy version. Position four in an original scan may differ from position four in a later copy with a cover sheet. Likewise, two different documents can each contain a printed page labeled “2.” Neither label identifies a unique source without its document context.

The existing source-labeling worksheet tracks the source of each proposition. The page map solves a narrower retrieval problem: helping the reviewer open the exact page that the source reference intends. Finding that page is a necessary documentation check, not a finding about the underlying statement.

Create a map without renumbering the originals

Use your team's authorized source locations. Give each document copy a stable working identifier and record the name or version needed to distinguish it from other copies. Preserve the original label as seen, including an absent or unclear label; do not invent a printed page number to make the sequence tidy.

For each page being cited or included in the current packet, record:

• Document ID and copy version: the exact source copy being mapped.
• Source locator: its existing authorized file location or reference.
• Viewer position: the page position in that particular copy, with the viewer convention stated.
• Printed label: the visible label, or an explicit “no visible label” or “unclear” note.
• Recognition cue: a brief heading or other non-sensitive detail that helps confirm the intended page.
• Packet position: the page's place in the identified packet version, if applicable.
• Open issue: a missing, repeated, unclear or replacement-copy question and its review owner.

The recognition cue is a check, not a replacement for file identity. Two pages may share a heading. Avoid copying unnecessary personal information into the map merely to make a cue distinctive. Keep the map and source material within the handling process authorized for the work.

The original need not be edited to create this crosswalk. If your process uses an assembled working copy, identify it as such and keep the route back to each source. A neat packet sequence should not conceal that a source had an unnumbered page or a gap.

A fictional two-document example

All names, pages and identifiers below are invented for this exercise. Suppose document D-A, copy v1, has four viewer positions: an unnumbered cover, then pages visibly labeled 1, 2 and 4. Document D-B, copy v1, has two viewer positions visibly labeled 1 and 2. Packet P1 starts with a separate packet cover, followed by all four pages of D-A, then both pages of D-B. The example does not establish why D-A lacks a visible page 3.

One map row reads: “D-A v1; viewer position 3; printed label 2; heading Room notes; packet P1 position 4.” A second reads: “D-B v1; viewer position 2; printed label 2; heading Visit summary; packet P1 position 7.” Both source pages display 2, but they are different pages in different documents.

A draft reference can therefore identify “D-A v1, printed page 2, viewer position 3,” using the team's agreed format. A reviewer starting from packet P1 position 4 can follow the same row back to D-A. This is more precise than changing the reference to a bare “page 4,” which could be mistaken for D-A's printed page 4.

The map also records an open question: “D-A shows printed labels 1, 2 and 4; confirm whether another page or an explanation is available.” The preparer does not create a replacement page, infer what the missing page said, or silently relabel 4 as 3. Until the issue is resolved, the packet handoff describes the gap.

Treat gaps and repeats as questions

A skipped printed number is a reason to inspect the source and ask for clarification. It does not by itself prove that a page was lost: the copy might contain an insert, a section-specific numbering scheme or another explanation. Record the observation separately from any proposed explanation.

Repeated pages also require care. Two pages with the same printed number may be duplicates, different versions or pages from separate sections. Compare their actual content and source identities before deciding how the working packet should represent them. Do not delete an original merely because its label matches another page.

Record blank or unnumbered pages according to the packet's purpose and the team's process. The map should distinguish “a page is present but unnumbered” from “a page has not been located.” Those descriptions support different follow-up questions and should not be reduced to one empty field.

If a page cannot be read clearly enough to support the intended wording, keep that issue visible. A page locator tells the reviewer where to look; it does not make an unreadable passage usable or justify guessing its content.

Handle a replacement scan as a new copy

When a clearer scan arrives, identify the new copy and compare the pages relevant to the draft. Do not assume that only image quality changed. A cover may have been added, a page may have been inserted, or the order may differ. Keep the old map associated with the old copy and make the new relationship explicit.

Suppose fictional D-A v2 includes an additional front sheet. The page previously at viewer position 3 may now be elsewhere. Update the map for v2 after checking the actual file, then find every draft reference that depended on the old viewer position. Retain enough version information for a reviewer to understand which copy was used at each stage.

If a working packet is rearranged while the source files stay the same, only the packet-position relationship may need to change. Recheck it rather than overwriting the source locators. The photo index guide provides a related approach for image identity, but a multipage document still needs its own file-and-page relationship.

Test retrieval in both directions

Before handing over the draft, ask a reviewer to start from a cited passage, use the reference to open the named source copy, and confirm the intended page by its visible content. Then start from a packet page and use the map to locate the original. Record which document and packet versions this check covered.

Check all changed mappings and the references affected by them. A small sample may help reveal a problem, but it should not be described as verification of every page. Distinguish a located page from a reviewed proposition, and leave unresolved completeness or wording questions with the designated reviewer.

StateClaimAI's drafting standards emphasize traceable sources and visible review questions. Once the relevant inputs are organized, use the report drafting workspace within your authorized workflow and keep this manual map available alongside the draft. Have a qualified professional review the resulting text. For an interface question, use official support without sending passwords or unnecessary source records.