Keep the file and its public source together
You may have found a project report through a search result, an AI citation or a social post. Save the actual document URL and the publisher page that links to it before examining its properties. A local filename is useful for organizing your copy but does not establish its publishing history.
Use a public document or a file you are authorized to inspect. Keep unrelated personal fields out of a shared source note. This workflow checks the provenance of a report; it does not turn document metadata into a profile of a private individual.
Open the properties for your operating system
Adobe documents Menu → Document properties → Description on Windows and File → Document properties → Description on macOS. Additional Metadata → Advanced displays the embedded metadata fields. Source
Read the fields without changing the evidence copy. Note the application and view used, particularly if another viewer exposes different information. Missing fields should remain missing in your notes rather than being filled from the report’s filename.
Compare three layers
Adobe describes basic properties such as title, author, subject and keywords, plus creation or modification dates and application-specific metadata. It also notes that editing metadata does not change the document’s content. Source
| Layer | Useful question | Boundary |
|---|---|---|
| Embedded properties | What does this file record? | A field is not independent verification |
| Visible pages | What publisher, version and date are printed? | A cover can describe an older edition |
| Publisher page | Which document does the publisher currently link? | Hosting alone does not validate every claim |
For an illustrative team report, the embedded Author field might name an editing account while the cover credits an organization. Record the mismatch. It is a reason to check the publisher’s explanation, not a basis for accusing either party of false authorship.
Interpret dates narrowly
Keep a PDF creation field separate from its publication date, your download date and the date of an event described inside. A later file revision can still discuss earlier events. If a timeline matters, find the explicit statement in the report or publisher’s notice and preserve its context.
Some metadata is read-only, according to Adobe. Source Whether a particular field can be edited in your viewer does not settle whether its historical value is accurate.
Produce a source note that can be checked
Record the inspected file URL, visible version, relevant metadata fields and unresolved differences. Avoid publishing the entire property set when only a title and revision date matter.
Use the public PDF search guide when you still need the publisher’s copy. Once the right document is located, the AI source checklist helps connect a claim to its supporting passage rather than to metadata alone.