Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Analyst ordering events, dated sources, contradictions and unknown intervals

OSINT method guide · 12 min

Build an OSINT timeline that separates events, publications and unknowns.

A folder of screenshots is not a timeline. Separate when something happened, when a source reported it and when the analyst observed it.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Keep multiple dates per item.
  • Normalise time zones.
  • Link every row to its source.
  • Display gaps and contradictions.

Step-by-step method

A reproducible path from question to conclusion.

  1. Two organisers preparing event registrations — AI-generated photograph
    1

    Define the time question

    Set the period, event to explain and useful granularity. A crisis lasting hours and a company history need different precision.

  2. A team preparing an object photograph and reviewing a notebook — AI-generated photograph
    2

    Create core fields

    Separate event, publication, update and consultation dates, time zone, source and confidence for every item.

  3. 3

    Preserve original meaning

    Summarise without removing source caveats. Keep a short excerpt or contextual copy that supports review.

  4. Photographic memories being sorted into an archive box — AI-generated photograph
    4

    Normalise without inventing

    Convert times to a chosen zone, mark approximate dates and never turn a vague period into a precise instant.

  5. 5

    Test competing sequences

    Place contradictions side by side, identify source dependence and look for events that should exist if a hypothesis were true.

  6. Reading materials gathered for regular monitoring — AI-generated photograph
    6

    Write the decision reading

    Identify what precedes what, uncertainty windows, turning points and checks that could change the order or conclusion.

One source often contains several dates

A displayed date may describe publication, last modification or the reported event. Metadata, archives and syndication may reveal a different sequence.

Record what each date means. Apparent precision without definition creates a misleading timeline.

Expose time zones and uncertainty

Use a stable format, retain the original zone and state conversion. Do not force a date-only item before or after an event with an exact time.

Intervals, “before”, “no later than” and “between” should remain visible. Unknowns are methodological information, not defects to hide.

Compare hypotheses against sequence

A timeline tests causality without assuming it. One event preceding another does not prove that it caused it.

Mark sources copying each other. Five successive articles may all derive from one report and are not five confirmations.

Preserve a partial order when times are missing

Keep the precision of dates and time intervals rather than assigning midnight. Overlapping intervals may not establish order. Separate event, publication, modification and consultation; an article’s current date does not reconstruct its history.

Connect each quotation to a version

Retain version and quoted passage. Connect corrections with the initial finding so readers can follow the assessment’s evolution. UTC comparison orders values without proving accuracy: clocks, transcription and publication delay remain possible explanations for differences.

Reading technical evidence

Compare times without inventing precision

Keep the original value before converting it. The UTC offset is part of the information needed for comparison.

Field or situation and its interpretation
Observed itemWhat it means
2026-10-27T10:00:00+01:00The same instant as 2026-10-27T09:00:00Z.
10:00 without a timezoneDo not assume UTC or the reader’s timezone.
Date onlyDo not arbitrarily assign a midnight time.

Separate event, publication and consultation times in the timeline. Mark unknown precision before ordering events.

RFC 3339, § 5.6

Local chronology tool

Do these timestamps describe the same instant?

Compare two dates with explicit UTC offsets. The calculation stays in this tab. It orders supplied timestamps; it does not establish when an event actually happened.

Three distinct times: the event, the publication and the collection. Each needs its own evidence.
The three times can differ. If one is unknown, keep it unknown rather than deriving it from another.
Event
When did the event allegedly happen?
Publication
When was the content published?
Collection
When did you view or preserve it?

Format: YYYY-MM-DDTHH:MM:SSZ or ±HH:MM offset, optionally 1–3 fractional digits. Dates without a timezone, unknown local offsets (−00:00) and leap seconds are not supported. No timezone is guessed.

RFC 3339, § 5.6 · Retain the original values and their stated precision alongside the calculation.

Worked example

Two posts appear to reverse the order of events

Fictional teaching case, not a client investigation.

Do their timestamps establish the sequence of actual events?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
Two pages display different times without timezones.Two publication times are visible.They cannot be directly compared while timezone is unknown.
One page was updated after its initial publication.That source reports a revision.Revision time must not silently replace initial publication time.
An original document places the event within an interval without a precise time.The event is bounded by a declared period.The interval does not justify inventing a minute or strict sequence.
Two displayed times do not specify their time zones.The capture order is known; the event order still needs checking.Keep original values, record an established time zone and make every conversion explicit; do not infer the sequence from a simple alphabetical sort.

Conclusion to record

Keep raw times, known timezones and uncertain intervals in separate fields. Do not infer event order from publication times alone.

What would change the conclusion?

Review after obtaining metadata or a document with a compatible marker; retain the conversion used.

Check your reasoning

What wording remains valid if the intervals overlap? Prefer uncertain ordering over an invented sequence.

· Open the verification log

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. Timestamp

Original time, zone, normalised time and available precision.

Limit: Capture date may differ from event date.

2. Order

Events linked to their sources with unknown intervals retained.

Limit: Temporal succession does not prove causation.

3. Version

Correction log and reason for each change.

Limit: Do not erase a contradiction to make a smoother story.

4. Observed and claimed dates

Separate your observation time, the date displayed by the page and the date of the described event. Keep the time zone and any uncertainty.

Limit: An updated article can describe an earlier event; its timestamp alone does not date the underlying facts.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
TimestampOriginal time, zone, normalised time and available precision.Capture date may differ from event date.
OrderEvents linked to their sources with unknown intervals retained.Temporal succession does not prove causation.
VersionCorrection log and reason for each change.Do not erase a contradiction to make a smoother story.
Observed and claimed datesSeparate your observation time, the date displayed by the page and the date of the described event. Keep the time zone and any uncertainty.An updated article can describe an earlier event; its timestamp alone does not date the underlying facts.

Common pitfalls

Four shortcuts that weaken the result.

A person preparing the structure of a publication — AI-generated photograph

Using publication date only

It may be days later than the event described.

Mixing time zones

Offsets can reverse close events.

Filling gaps by intuition

An unknown interval should remain explicit.

Confusing order with causation

Sequence guides analysis but does not alone prove cause.

Practical questions

Frequently asked questions.

Which date format should be used?

An unambiguous format such as ISO 8601, including time zone where time matters.

How can a screenshot without metadata be dated?

Keep at least the observation date and seek an independent source or archive for first visibility.

Should everything enter the timeline?

No. Keep what answers the question and move secondary detail to appendices.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

HRC Berkeley / OHCHR — Berkeley Protocol. Framework for collecting, preserving and verifying digital open-source material. It was developed for human-rights and international investigations; using its documentation principles does not establish admissibility in a particular proceeding.

Editorial scope

Published by Internet Intelligence Service on 15 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections