At a glance
The paid inventory’s Excel export carries a document ledger and recorded website-request evidence. Keep the original export as a dated snapshot, then use a working copy to assign owners and actions. Unknown page counts need their status column alongside them so a blank cell never becomes a claimed zero.
Choose the export for the job
Open a finished or partial report and choose Excel for a multi-sheet view. CSV is useful when importing the document ledger into another system. HTML keeps a readable report with coverage context, while the PDF summary supports a compact review.
These outputs describe the saved attempt. They are not a live connection to your CMS or a guarantee that a download URL will serve the same bytes tomorrow. Save the retrieval date and report scope with any exported figures.
- Keep an unchanged copy of the download.
- Create a working copy with your own owner, priority and action columns.
- Filter by result before totaling pages.
- Read the coverage and request information before presenting the scope as complete.
Avoid two spreadsheet mistakes
Do not fill unknown page cells with zero. Keep a status filter or explicit unknown count so a manager sees the unresolved work. If your spreadsheet totals only numeric values, label the total as confirmed pages and show how many documents were excluded.
Do not total both duplicate rows and unique-source rows and call the result unique pages. Choose one source per byte-identical group for work estimates, but retain every URL for the publication checklist. Sorting and filtering should not erase the identity evidence.
| Question | Include | Label |
|---|---|---|
| How much unique source work is confirmed? | One counted source per identical-file group | Confirmed unique pages |
| How many counted pages appear across links? | Every successfully counted URL | Confirmed pages across URLs |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Website requests belong in a separate review
The Website requests sheet records bounded discovery issues for attempts that retained detailed evidence. A blocked web page is not automatically an uncounted PDF. A single failed page might have no PDF links or many; the scanner cannot know what it did not read.
Older reports may contain only aggregate request counts. If the export says detailed addresses were not recorded, keep that limitation visible rather than inventing rows from the current website. Use the crawl-issue template for a separate owner-led investigation and record a new observation date.
Sources and scope
Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.
- DocAccessible PDF inventory
The counting workflow, report options and purchase boundary.
- DocAccessible privacy policy
How service data is handled; read before providing sensitive information.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.
See the evidence in a working example
Explore the public sample inventory report to try its table, full-screen view and missing-count reasons. The downloadable counting fixture check records what the local counter returned for seven self-authored inputs, with hashes and explicit limits.