- Published
- Updated
Saving an electronic record as PDF can produce a readable copy. Yet filters, expandable comments, linked attachments or change history may be omitted, removing context that is necessary to understand the record or reconstruct the decision.
Preserve the meaning of data
Do not accept the format as sufficient before defining its purpose. A review copy, long-term record and decision attachment may require different evidence. Identify dynamic screen elements included in the export and information available through another controlled route. Select representative records that expose truncated text, hidden rows or content extending across page boundaries.
Worked example
For example, a deviation is exported but only its first comment appears; the decision rationale sits in a later comment. The team tests long discussions, attachments and different workflow states. It considers retaining a separate evidence package or changing the export layout rather than declaring success simply because the resulting file opens.
Review checks
- Compare examples containing long text, attachments and multi-stage decisions.
- Make filtering and selection conditions understandable in the output.
- Test controlled access to linked evidence outside the original system.
Acceptance and boundaries
Acceptance means the output retains enough context for its defined use. A PDF need not reproduce every electronic function, but its record role should be explicit. Avoid descriptions implying that omitted dynamic information is present. Preserve traceable relationships between the PDF and remaining controlled evidence so the record can be reconstructed later when needed.
Frequently asked questions
- Is every PDF automatically a faithful copy?
- No. Assess content, context and verification arrangements rather than relying on the file format alone.
- Is an included hyperlink sufficient?
- Its target, access duration and availability after system retirement need separate testing.