PDF export prompts: verify the delivered file again

Last updated: 5 Oct 202611 min read

tutorial

A PDF export is a new artifact with its own failure modes. A release prompt should name the source file, export method, expected page count or range, required text, and manual checks. Verify selectable text, document structure or tags where supported, reading order, descriptive alternatives for meaningful figures, and visible layout on every page. Do not assume the source application's accessibility checks automatically carry through conversion. Compare the exported report's counts and decision statement with the approved claim ledger and editable source. If the PDF is flattened or loses structure, repair the export path or clearly withhold that artifact rather than describing it as accessible.

Operational case

North Quay's editable report passes its own review. The first PDF export preserves 47, 38, 6, and 3 as text, but moves a footnote to the next page and leaves the chart out of the reading order. The PDF is not released. The team adjusts the source layout and export settings, exports again, inspects each page, and checks structure in the actual PDF. The final delivery packet retains the editable report, six-slide deck, PDF, claim ledger, and a short note of tested limitations. A request for equipment replacement approval would require a new brief; no formatting check can authorize it.

Source: approved editable North Quay report.
Export checks: text selectable; 47/38/6/3 present; pages inspect clean.
Structure: heading order, figure alternative, logical reading order.
Cross-file: report, six slides, and PDF use the same claims.
Release: owner reviews actual files; failed PDF is withheld.

Performance and operating cost

With P PDF pages, visual and text checks take O(P) page passes, plus a small set of cross-file claim comparisons. Structural inspection takes longer when a chart or multi-column layout has a complex reading order. Re-export after source edits and rerun checks on the new file; a previous PDF pass does not transfer to changed bytes. Hashing the approved artifact is O(B) for B bytes and gives a stable receipt for which exact file was reviewed, though it does not prove the file is correct.

Common Mistakes

Do not infer PDF accessibility from a clean source document alone.
Do not release a flattened PDF that only appears readable in a screenshot.
Do not reuse an earlier approval after the exported bytes change.

Connected lessons

prompt engineering

document delivery