Events are the building blocks of your timeline — time-anchored nodes representing things that happened.
| Field | Required | Description |
|---|---|---|
| Title | Yes | A concise description of what happened (e.g., "Board votes to authorize acquisition") |
| Canonical Time | No | The date and time in ISO 8601 format. If left blank, the event is placed at the end of the sequence. |
| Time Precision | No | Choose the precision level that matches your certainty about the time |
| Description | No | A longer narrative description with context, details, and notes |
| Status | No | The verification state |
The event appears as a card in the timeline sequence.
What you'll see: The event card shows the title, status badge, time precision indicator, and formatted timestamp. It appears in chronological position relative to other events.
Every event records a canonical_time — your best estimate of when it occurred — and a time_precision — how certain you are about that time.
| Precision | Use when | Example input |
|---|---|---|
exact | You know the precise time (to the second) | 2024-01-15T09:30:00Z |
estimated_date_time | You have a specific estimate but aren't 100% sure | 2024-01-15T09:30:00Z (precision flag tells viewers this is approximate) |
exact_time_period_range | You know the event happened within a specific window | Start: 2024-01-15T09:00:00Z, End: 2024-01-15T11:00:00Z |
estimated_time_period_range | You estimate the window but aren't sure about the bounds | Start: 2024-01-15T09:00:00Z, End: 2024-01-15T11:00:00Z |
Be honest about uncertainty. A tool that demands exact times forces you to fabricate precision. This tool forces you to record what you actually know.
Alongside precision, every event has a time_confidence score (0–100). You can have an exact timestamp with low confidence, or an estimated range with high confidence.
You can also edit an event from its detail page at /app/investigations/[investigationId]/timeline/events/[eventId] by clicking the Edit button in the header.
Deleting an event is a soft delete. The data is archived and recoverable through the revision system.
Each event has a dedicated page at /app/investigations/[investigationId]/timeline/events/[eventId]. This page shows the complete picture for a single event, within the investigation context.
To remove a location, clear the selection and save.
Unlink an entity by clicking the X on its badge.
| Status | Use When |
|---|---|
reported | A source mentions this event, but you haven't evaluated it yet |
alleged | Someone claims this event occurred, but confirmation is pending |
confirmed | Multiple reliable sources verify this event |
disputed | At least one credible source contradicts this event's details |
contradicted | Evidence shows this event did not happen or happened differently |
inferred | The event is logically deduced from other confirmed events |
superseded | This event record has been replaced by a more accurate version |
retracted | Previously reported but since withdrawn by the source |
sealed | Restricted access — not publicly visible |
A typical workflow:
reported→alleged→confirmed. Don't leave events atreportedindefinitely.