A scanner's page count tells you how many images reached a file. It does not tell you whether they represent the complete document. An office can capture ten images from a ten-sheet batch and still miss every reverse side.
Use this check when preparing routine paper documents for filing or delivery. It is the capture stage of the business PDF handoff plan, not permission to discard paper or alter an original record.
Establish the expected set before scanning
Give the batch a working reference and record its owner. Count sheets separately from expected page sides. Identify attachments, inserts, different paper sizes and pages with content on the reverse. If some sides are intentionally blank, establish whether the receiving workflow expects them to remain visible.
Do not remove a page because it looks unimportant. A divider, blank signed form or reverse-side note can matter to the owner. Ask about uncertain items and keep them with the batch until resolved.
Inspect every page in the final file
Open the saved PDF rather than relying on the scanner's preview. Check sequence at thumbnail scale, then inspect each page at a readable zoom. These are different tasks: thumbnails reveal ordering patterns, while enlarged inspection reveals clipped characters and faint marks.
Look at all four edges. Confirm orientation, page boundaries, small print and the area near staples or folds. If a sheet has a handwritten note or stamp, make sure the captured output preserves what the source actually shows. Do not infer the meaning of an unreadable mark.
Reconcile page labels with physical order
A document may contain a cover, numbered body and separately numbered attachment. The PDF viewer's page number will not necessarily match the printed number. Record the expected sequence in ordinary language, such as “cover, body pages 1–4, attachment A pages 1–2.” This is an example, not a required numbering scheme.
Check transitions: the last page of each section and first page of the next. For a merged batch, confirm that each source appears once and that a rescan has replaced the defective page rather than creating an unnoticed duplicate.
Use a small exception log
For each issue, record the file page, source reference, defect and requested action. Useful defect descriptions include “bottom line clipped” or “reverse side absent.” “Bad scan” is too vague for someone else to repair reliably.
Retain the original capture while working on a corrected copy. Rescan when the capture missed information. If the paper itself is damaged or incomplete, refer the issue to its owner instead of attempting a cosmetic repair that changes meaning.
Keep capture and OCR acceptance separate
Adobe's scan settings guidance distinguishes image-quality choices from text recognition. A legible image is not proof that the searchable text is accurate. Once the page set is accepted, run the separate searchable-text review if the recipient needs search or copying.
Likewise, run the file-size quality test again after compression. A later transformation can change the output you already reviewed. Keep the release decision attached to the actual file delivered.
Close the capture check
Make repeat problems diagnosable
If missing sides recur, check the selected capture workflow and test it with a known double-sided sample. If clipping recurs, compare the source size and capture area. Ask support to investigate the specific pattern rather than repeatedly changing unrelated settings.
Retain a non-sensitive sample and the device or app details for the support conversation. That evidence helps distinguish preparation, feed, capture and export problems without claiming the equipment is defective before it has been examined.
Editorial review: October 22, 2026. These proposed office checklists do not certify document accuracy, accessibility or legal compliance. Use current guidance for your approved software.