How to verify dates, locations, and timelines

A timeline is not a list of timestamps copied from pages. It is a set of events whose times, places, identities, and relationships have each been tested. The same item can have a capture time, upload time, public-release time, update time, and archive time—and none of them may be the time of the depicted event.

The reliable method is to normalize every timestamp without erasing its original form, keep source events separate from publication events, and test whether the resulting sequence is physically and chronologically possible.

Define the event you are trying to place

Write one row for each factual event, not one row for each web page:

| Event ID | Actor or object | Action | Claimed place | Claimed time | | --- | --- | --- | --- | --- | | E1 | Named account | Published an image | Platform | Visible post time | | E2 | Depicted people | Attended an event | Venue or city | Event window | | E3 | Camera or device | Captured the file | Possible scene location | Metadata time |

This prevents a post date from silently becoming the date a photograph was taken. It also separates “the organization announced a change” from “the change took effect.”

For each event, state the precision you actually need: year, day, hour, or minute. Do not chase minute-level certainty when the public claim is only about which month something happened.

Preserve every timestamp in two forms

Record the timestamp exactly as the source displays it, then add a normalized value for comparison. Keep:

• original text and language
• source timezone or UTC offset, if shown
• normalized UTC time
• named timezone and location used for conversion
• precision and uncertainty
• the source URL, identifier, and retrieval time

For example, retain both 14 August 2026, 9:30 PM GST and its calculated UTC instant. Do not replace the original with the conversion.

RFC 3339 defines an Internet timestamp with a numeric UTC offset or Z for UTC. That format is useful in an evidence table because 2026-08-14T21:30:00+04:00 states more than “9:30 tonight.” If a source gives no timezone, mark it unknown; do not assign the researcher's local zone by default.

Name what each date measures

Use a timestamp type beside every value:

• event time: when the real-world action occurred
• capture time: what a camera, recorder, or file claims about creation
• upload time: when a platform received a file
• publish time: when it became publicly available
• update time: when the page or record changed
• archive time: when an archive captured a representation
• retrieval time: when you observed the source

Platform definitions matter. YouTube says upload and publish dates can differ when a video was private or unlisted before becoming public, and its public watch-page date uses Pacific Standard Time. Therefore, a visible YouTube date is evidence about public availability under the platform's rule—not proof of recording time.

Likewise, an archive capture proves a version was captured by that time, not that it was first published then. A file's metadata can be missing, copied, edited, or reset by an export. Keep these limitations in the row.

Convert timezones with historical rules

Timezone offsets change with daylight-saving law and political decisions. Do not apply today's offset to an old local time. Use the named location and the rules in effect on the event date.

The IANA Time Zone Database records offset histories and daylight-saving rules for representative locations and is periodically updated when rules change. Record the named zone, such as America/New_York, and the database or tool version used for important conversions. A three-letter abbreviation such as CST can be ambiguous across countries and seasons.

If the location is uncertain, show each plausible conversion instead of choosing the one that makes the narrative work. Around daylight-saving transitions, a local time may occur twice or not occur at all; seek an explicit offset or another synchronized event.

Verify the place at the right level

Separate location claims by precision:

• country or broad region
• city or municipality
• venue, street, or identifiable public site
• exact coordinates

Evidence supporting a city does not automatically support a specific venue. Use independent location anchors such as visible signs, language, road design, transit, terrain, skyline, storefronts, event programs, official venue material, and other contemporaneous views.

Compare several clues. A single business name can have branches. A landmark can appear in a screen, poster, reflection, or composite. GPS or location metadata can be useful, but it may be absent or editable and should agree with the visible scene and external records.

Stop at the least precise location needed to resolve the claim. Do not publish an exact home, hotel room, school route, or current private location merely because visual clues make it inferable.

Turn evidence into intervals and constraints

Most public evidence supports a window rather than an instant. Express it honestly:

• no earlier than: a prerequisite event occurred at this time
• no later than: a dated publication or archive already contains the item
• between: the last confirmed state without a change and the first state with it
• approximately: the source itself gives only a coarse or uncertain value

Then add sequence constraints:

• E1 must occur before E2
• E2 and E3 claim the same person in incompatible locations
• travel between E3 and E4 requires at least a plausible interval
• a building or product shown in E5 did not exist before a documented date
• daylight, weather, or scheduled activity conflicts with the claimed hour

Do not infer exact travel from public location traces about a private person. The purpose is to test a public event claim, not reconstruct someone's movements.

Require identity continuity across the timeline

A clean sequence can still connect the wrong people or objects. Give each actor, account, vehicle, document, and media item a stable identifier where possible. Record when an identity link is direct and when it is inferred.

For people, use public, time-appropriate anchors rather than name alone. For accounts, preserve stable handles or platform IDs and consider compromise or renaming. For images and video, compare the same file, crop, keyframe sequence, or attributable source—not merely similar scenes.

If an identity changes between rows, split the candidate timeline. Do not make the timeline appear consistent by silently merging namesakes or reposts.

Build a contradiction table

Test the strongest alternative explanation, not just your preferred story:

| Evidence | Supports | Conflicts with | Reliability and limit | | --- | --- | --- | --- | | Source URL or record | Event or interval | Competing event or claim | Direct, inferred, editable, incomplete, or copied |

Resolve contradictions by returning to the underlying source. Check whether a timezone, date format, scheduled post, archive replay, delayed publication, misidentified person, or mislabeled location explains the difference. If it does not, preserve the conflict.

Silence is not resolution. One missing event may leave both timelines possible.

State what the timeline establishes

Use conclusions tied to the tested proposition:

• Verified sequence: the relevant event identities, locations, and intervals agree across direct and independent evidence.
• Consistent but not independently verified: no contradiction was found, but the chain depends on one source or inferred links.
• Claimed timing or location contradicted: reliable evidence makes a material part of the proposed sequence impossible or wrong.
• Bounded window only: the evidence supports earliest/latest limits, not an exact moment.
• Unresolved: missing timezone, identity, coverage, or source evidence leaves more than one plausible sequence.

Publish the timeline table and conversion assumptions so another person can reproduce it. For disputed web publication dates, continue with how to find the earliest version of a web page. For source files and capture logs, use how to preserve and document a web source.