Read the PDF as three separate layers: the visible byline and publication context on the page, and the file properties stored in metadata. They can disagree, and metadata can be replaced or inherited from another file or template, so a name in the metadata does not establish who wrote the document. Attribute the document to its visible, published authorship where that exists; log the metadata value as an unverified property and leave any conflict unresolved.
Find public social profile clues with our TraceSeek app.
Start with the page, not the file properties
Open the permitted document and record what a careful reader can see: the stated author or contributor line, the publishing organisation, the date shown, the report title and any edition or issue number. This visible layer is what the document publicly presents itself to be. It is still not independent proof of identity, but it is the layer a career report should normally describe. Save the page number or section where each visible element appears so your notes can be checked.
- Note the visible byline exactly as printed, without correcting spelling or expanding initials
- Record the publisher name, document title and any date printed on the page
- Keep the page reference beside each note
Read metadata as a property, not a claim about a person
Document properties are fields stored in the file, and a PDF editor can view, append, replace and save them. A value can also come from another file or template rather than from the person who wrote the visible text. Metadata is therefore useful as a property of the file you received, not as an author attribution. Record the field name, the value and where you found it; describe it as a metadata value, not as the author. [Adobe: editable PDF metadata]
- Write “metadata value” rather than “author” in your notes
- Keep the exact value including spacing and capitalisation when describing a discrepancy
Place the document in its publishing context
Publication context sits between the page text and the file properties: who issued the document, on what platform or channel it appeared, and what the surrounding listing said about it. A shared document may be posted by an organisation, forwarded by a colleague or re-uploaded somewhere else, so the context you observe is the context of that appearance, not a complete history. If the byline and the issuing organisation differ, describe both rather than choosing one.
- Record the issuing organisation separately from any individual name
- Note whether the document was published directly or shared onward, if that is visible
Hold a discrepancy open instead of resolving it
When the visible byline and the metadata name differ, the honest record is that they differ. There is no reliable way to decide from the file alone which is the person who wrote the text, whether one is a template remnant, or whether both are legitimate contributors. Say so plainly in the career report and stop there; do not assign the whole document to the metadata name, and do not present the disagreement as evidence of anything about either person. This is a limit of the evidence, not a gap you are expected to close.
- Write a one-line note: “Visible byline and metadata name differ; unresolved.”
- Do not merge the two names into one combined attribution
Keep embedded personal details out of the report
Documents can carry contact details, account names or other personal information in text or properties. If a shared document includes such details, keep them out of the career report and out of any forwarded notes; describe the role, organisation or contribution instead. If the artifact is not available, not public, or does not match the document you intended to review, record that specific limit and stop, rather than reaching for other sources to fill the gap.
- Replace any embedded contact detail with a role description such as “listed contact”
- If the source is missing or mismatched, write the limit and end the entry
Separate the three layers in one working note
A short worksheet keeps observation, limit and decision apart. Fill each row only with what you actually saw in the permitted copy.
| observation | limit | next step |
|---|---|---|
| Visible byline printed on page 1 | Shows what the document presents publicly; not independent identity proof | Quote it as the document's stated byline, with page reference |
| Publisher or issuing organisation | Describes this appearance, not a full publication history | Record alongside the byline without merging them |
| Metadata name field value | May have been replaced or inherited from a template | Log as an unverified file property; do not treat as author |
| Disagreement between byline and metadata | Cannot be resolved from the file alone | State the discrepancy and leave it unresolved |
| Embedded contact or account details | Personal information not needed for a career report | Omit; describe the role instead |
What this method does and does not support
This is an editorial worksheet, not a platform test, and it does not verify ownership, identity or current activity. Use it to produce a careful description of one voluntarily shared document. It is not suitable for background checks, hiring, credit, housing or insurance decisions, and a name match between the page and the metadata should not be read as confirmation of a real person behind either.
A couple more questions
The metadata name differs from the byline. Which one should the career report use?
Use the visible byline and the stated publishing context for attribution, and list the metadata value separately as an unverified file property. Do not pick the metadata name to replace the byline, because metadata can be replaced or inherited from a template.
The document is only partly public or differs from what I expected. What then?
Record the specific problem, such as an unavailable source, restricted visibility or a mismatch with the document you meant to review, and stop. Do not seek private records or other sources to force an attribution.
Can I include the contact details printed in the PDF?
No. Keep embedded personal contact details out of the report and describe the role or organisation instead. The report only needs the visible byline, the publication context and a note about the unresolved metadata.
Does a matching name on the page and in the metadata confirm the author?
No. Agreement between two layers shows consistency, not identity or authorship. Note the agreement if useful, but do not describe the person as verified.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.