Evidence workflow
Defamation evidence workflow: building a publication chronology
How to capture a defamatory statement, prove publication and reach, track repeat publication, and hand a chronology to counsel.
Key takeaways
- Capture the statement and everything around it: the exact wording, the account or publisher, the date, and the surrounding thread, before it is edited or removed.
- Publication and reach are separate facts from the statement itself. Record who could see it, how far it spread, and evidence of actual views or engagement where visible.
- Whether republication restarts limitation periods varies by jurisdiction and is a question for counsel. Capture every instance you find with its own date and source, and track republication and mirroring as an ongoing task, not a one-time step.
- Preserve before you request removal. Once a statement is deleted, the strongest remaining evidence is whatever you captured beforehand.
- Hand counsel a dated chronology with source links and captures attached, not a narrative summary of what you believe was said.
What makes defamation evidence different from other online-harm evidence?
Definition
A defamation evidence file is a chronology that establishes what was stated, where and when it was published, who could see it, and how it spread, kept separate from any legal conclusion about whether the statement was defamatory.
The distinguishing feature is that a single statement is rarely the whole story. Reach, republication, and how the claim spread across accounts or platforms are usually as important as the original post, and they need their own capture and dating.
That means a defamation workflow adds two things a general harassment capture does not always need: proof of publication and reach, and ongoing tracking of repeat or mirrored versions of the same claim. Both are covered below, alongside the core capture and chronology steps common to any online-harm evidence file.
Definition
"Publication" in a defamation context means the statement was communicated to someone other than the person it is about. Online, that typically means it was posted somewhere visible, but establishing who actually saw it, and how many people, is a separate task from capturing the statement itself.
How do you capture the statement and its context?
Capture the exact wording of the statement, not a paraphrase, along with the account or byline that published it, the platform or publication, and the date and time as it appeared. Take a full-page, uncropped screenshot or recording that includes the URL bar and any visible timestamp, and save the source URL separately as text, since a screenshot of a URL is harder to verify than the URL itself.
Context matters as much as the statement. Capture the surrounding thread or article, since replies, quote-posts, or an editor's note can change how a statement reads. If the statement appears in a comment section, capture the parent post or article it responds to, since defamatory comments are sometimes evaluated in light of what they were replying to.
- Exact wording of the statement, captured verbatim, not summarized
- Source URL, publisher or account handle, and platform or publication name
- Visible timestamp and, where available, an edit history or "last updated" marker
- The surrounding thread, article, or comment section for context
- Author or account details as they appeared at capture time, since accounts are sometimes renamed after a statement draws attention
How do you prove publication and reach?
Publication and reach are separate facts from the statement itself, and they need their own record. Reach evidence shows how far a statement traveled and how many people plausibly saw it, which is distinct from whether the statement was published at all.
- Visible engagement signals at capture time: view counts, like counts, share or repost counts, and comment counts, recorded with the date they were observed, since these numbers change constantly
- Screenshots of the statement appearing in a feed, search result, or notification, which help show it was actually surfaced to an audience rather than only existing at a static URL
- Evidence that specific people saw the statement, where available: replies referencing it, screenshots forwarded to the affected party, or direct confirmation from a third party who saw it
- The publication's or account's general audience size or reach at the time, as context for how far the statement plausibly traveled
Caution
Engagement counts and follower numbers are not proof that any specific person saw the statement. Record them as reach indicators, not as a claim that a particular individual read it, and let counsel decide what weight they carry.
How do you build a publication chronology?
A publication chronology lists every instance of the statement, in date order, with its own source, capture, and reach notes. This is the working document that turns a single defamatory post into a complete record of how a claim entered and moved through public view.
Each entry should include:
- Date and time of publication or republication, with the time zone noted
- Source: the exact URL, account, or publication
- A short factual description of what changed, if this is a republication or a variant of the original wording
- A link to the capture file or evidence ID for that instance
- Whether the entry is observed directly (visible in a capture), reported (told to you by someone else), or inferred (a connection you believe exists but have not directly observed)
Mark gaps explicitly. If there is a period where the statement may have spread but you have no captures, note the gap rather than guessing at what happened during it. A chronology that states its own limits plainly is more useful to counsel than one that quietly smooths over uncertainty.
How do you track repeat publication as it happens?
Defamatory statements rarely stay in one place. They get quoted, screenshotted and reposted, summarized by other accounts, or republished after an initial takedown. Each instance is a separate fact for the chronology, and treating repeat publication as an ongoing task, rather than a single capture, is what keeps the file current as the situation develops.
- Search periodically for exact phrases from the original statement, since verbatim reposts are the easiest to find and connect back to the source
- Track accounts that quoted, screenshotted, or summarized the original statement, with their own source URLs and dates
- Note when a statement resurfaces after a period of dormancy, since a gap followed by a new appearance is itself a fact worth recording
- Keep each republication instance separate in the chronology rather than merging it into the original entry, since counsel may need to treat each instance individually depending on the jurisdiction and facts
Whether each republication legally resets any relevant time limit or counts as a fresh instance is a question for counsel, and it can vary by jurisdiction and circumstance. Your task is to capture every instance with its own date and source; the legal significance of repeat publication is not something to resolve at capture time.
Why preserve before requesting removal?
Once a defamatory statement is taken down, whether by the author, a platform, or in response to a legal request, the strongest remaining evidence is whatever was captured beforehand. Preservation should come first, before any removal request goes out, so that the record exists independently of whether the request succeeds. This is true even when removal feels urgent: a hurried takedown request with no prior capture can leave a gap in the record that is impossible to fill later.
How should this be handed to counsel?
Hand counsel a dated chronology, not a narrative account of what you believe happened. Include the captures themselves, organized and referenced by the chronology, and a short summary of the affected party, the general nature of the statements, and the date range covered. Keep your own conclusions about whether something was defamatory in a clearly separate section from the factual record, so counsel can review the facts and reach their own assessment.
For the underlying capture and chronology mechanics that apply across any harm type, see the defamation evidence chronology workflow and the reputation attack evidence monitoring workflow. If your matter involves UK-specific considerations, the United Kingdom jurisdiction hub covers relevant context. Law firms building an intake path for reputational matters can see how evidence packs fit into existing client work at for law firms.
Frequently asked questions
What counts as evidence in a defamation matter?
The statement itself, captured with its exact wording, source URL, and timestamp, along with evidence of publication and reach, such as visible engagement counts, replies, or shares, and any republication or repost of the same claim.
How is defamation evidence different from general harassment evidence?
Defamation evidence needs to establish that a specific false statement was published and reached an audience, so capturing reach, republication, and the statement's spread matters as much as capturing the original statement itself.
What is the "single publication" issue and why does it matter for capture?
Whether each republication or repost counts as a fresh publication varies by jurisdiction and context, and is a legal question for counsel, not something to resolve at capture time. What you can do is capture every instance you find, with its own date and source, so counsel has the full picture to work from.
Should I request a takedown before preserving the statement?
No. Preserve the statement, its context, and evidence of its reach first. Once material is removed, whether by the author or the platform, a prior capture may be the only complete record left.
Will a screenshot of a defamatory post be enough on its own?
Courts and platforms assess evidence case by case, and no format is guaranteed to be sufficient on its own. A screenshot with an intact source URL, timestamp, and a record of how it was captured is consistently more useful to counsel than a cropped image with none of that context.
References