How to Preserve an Original PDF Before Analysis

The most valuable PDF in a review is often the least convenient one: the attachment exactly as it arrived. It may be large, sideways, awkwardly named, or accompanied by an unhelpful message. Keep it anyway. If you replace that copy with a cleaner export, later reviewers may be examining your processing choices instead of the material received.

Preservation does not require an elaborate evidence platform for every routine task. A small folder structure and a brief record can prevent most avoidable confusion. This guide describes that working practice; it does not claim to create a formal forensic chain of custody.

Separate three roles for files

Create a received folder for attachments as downloaded, a working folder for inspection copies, and an outputs folder for reports or prepared submissions. These can be ordinary folders within storage your organization already approves. Limit access to the people who need the material.

Keep the received filename somewhere in the record even if your filing system adds an internal reference. Filenames such as final, final-new, and final-approved are descriptions chosen by people, not reliable version histories. A local reference should distinguish files without making an unsupported claim about their status.

Avoid placing a person's full identifying details in every filename. A short case reference plus a document role is often enough. Store the connection to the person only where your existing process requires it.

Record receipt before changing anything

Write down the received filename, file size, date and time of receipt, channel, and relevant sender context. Include the time zone where timing matters. Record the page count after opening the file, and note whether the attachment arrived alone or as part of a package.

Do not replace the attachment with a screenshot of the message or a printout of the visible pages. A screenshot can document context, but it serves a different role from the file. If you need both, label them as separate items.

For repeatable file identification, consider a SHA-256 file hash. A matching hash helps establish that two copies contain the same bytes. It does not establish that the document's assertions are true or that the sender is authorized to make them.

Work on a deliberate copy

Make the working copy before rotating pages, adding comments, applying OCR, or reducing size. Use a name such as working-review followed by the local reference. Keep your observations in a separate note if the viewer might save annotations into the PDF itself.

Opening and reading is different from explicitly saving an altered document. Be alert when a viewer asks to save changes on exit, especially after form interaction. If you are unsure what changed, discard the working copy and create a fresh one from the received file.

Acrobat's comparison feature is designed to compare two document versions. It can be useful when checking a transformed copy against the source, although a comparison report still requires interpretation. See Adobe's comparison documentation for the supported workflow.

Keep a transformation note

A useful note has five parts: input file, operation, software used, output file, and reason. For example, in a fictional submission task: “Created upload copy from received attachment; reduced size to meet portal limit; checked all eight pages afterward.” Record the date and reviewer as well.

If the operation fails or makes small text unreadable, retain the original and mark the output unsuitable. Do not silently replace the file again until nobody knows which copy was checked. The compression review guide covers this situation in more detail.

Cropping also deserves a note. The visible page boundary is not a sufficient description of everything a PDF contains. If margins are relevant to a discrepancy, follow the cropped-page review checklist before preparing a presentation copy.

Handle replacements without erasing history

When the sender supplies another file, save it as a new received item. Record whether the sender calls it a correction, direct export, clearer scan, or replacement version. Those explanations may matter more than a small change in file size.

In a fictional case, a two-page letter is replaced by a three-page package containing an appendix. Your record should show that the new appendix arrived later. It should not imply that the first reviewer overlooked a page that was never supplied.

For technical inspection, use CleanPDF's edit check with the appropriate received copy and retain its findings separately. The service can surface some modification and hidden-information traces, but cannot certify the document's authenticity. Preservation gives those observations a stable object to refer to.

Before handing the case onward, confirm that the next reviewer can identify the received copy, the working copy, and the latest intended version. That simple distinction keeps useful review work from being undone by an accidental overwrite.