A PDF can look correct while losing editable annotations, comment relationships or interactive links. Check the complete workflow using an unchanged reference file and explicit success criteria. The aim is to establish what the recipient actually receives, not merely whether the source application reports a successful save.
Build a small reference document
Include representative highlights, underlines, strikethroughs, text comments, freehand ink, shapes and stamps. Add a comment with identifiable replies, a link to another page in the file and a separate web link. Include form fields if form preservation is part of the task, recording them separately from the other categories.
Give the test items distinct identifiers and confirm that each one works before beginning. Otherwise, an existing problem may be mistaken for a transfer failure. Keep this reference unchanged and run each comparison from a copy.
Follow the file through the workflow
- Save the original and record the device, application and version.
- Apply the editing or annotation actions being evaluated.
- Save or export using the exact options intended for normal work.
- Transfer or synchronise the file and identify the received version.
- Open it in the destination viewer and inspect each reference item.
- Repeat the checks after any further export required by the workflow.
Keep intermediate copies when the tools allow it. Finding the first stage at which an item changes is more useful than reporting only that the final copy differs.
| Check | Evidence to record |
|---|---|
| Presence | The expected item exists in the destination |
| Content | Text, address or value matches the reference |
| Position | The item remains associated with the intended location |
| Interactivity | The link, comment or control performs its intended action |
| Editability | The item can be edited when the task requires it |
| Relationships | Replies and related items remain associated correctly |
The PDF specification provides background for inspecting stored annotation structures. Keep a viewer's display and the file's objects distinguishable in the evidence.
For link accessibility, W3C's PDF11 technique covers creating link annotations and associating them with the document's structure. Check that the destination works and that the link has meaningful text for the reader. A clickable region and a usable description are complementary parts of the result.
External references need a separate availability check. Klein and colleagues' 2014 PLOS ONE investigation studied over one million web references from more than 3.5 million articles and found reference rot in about one in five articles. Those are historical scholarly-web findings, not an export failure rate. Record the link's stored address and whether the intended source is still available as two separate outcomes.
Record failures precisely
A missing item, a moved item and a visible but non-interactive item are different outcomes. State the numerator, denominator and success rule for every percentage. Report category totals when a large number of one item type could hide failures in another. Preserve representative examples so the summary can be checked.
Read more about a particular problem
- Notavex B8 reply limits explains per-thread counts and reply relationships.
- Pagelyn T8 offline links covers destinations within the same PDF.
- Docuvex M7 annotation categories separates appearance, presence and editability.
- Folivex C9 URI links distinguishes stored actions from visible addresses.
- VellumPad R6 synchronisation follows saving, transfer and destination display.
The iPad mini A17 Pro guide considers a portable reading and note-taking setup.