Learn the concept.
A timeline makes a case easier to review, but only if its times and sources can be trusted. Keep original observations separate from your interpretation.
Normalize carefully
Record original timestamps and offsets alongside a common time zone. Note missing offsets or suspected clock differences.
Link every observation
Use source and event identifiers. Keep evidence within approved storage and access rules.
Avoid causal leaps
An event occurring after another event does not prove the first caused it. Explain what ties them together, such as an account or session.
Field example06 / A
Put it in context
The sign-in is at 09:02 UTC and the export request at 09:07 UTC. Both reference session S17. A later record shows the export failed. Preserve each event and outcome.
Keep the outcome in the timeline
Fictional records associated with session S17.
- 09:02 UTCSign-in accepted
Account jlee; retain the authentication event reference.
- 09:07 UTCExport requested
The request references session S17.
- 09:08 UTCExport failed
The recorded outcome does not show a completed export.
Read the visualDoes the failed export prove no other data was accessed?
No. It limits the claim about this attempt. Review other relevant session activity and collection coverage.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
A useful timeline shows sources, ordering, and uncertainty.
Next lesson: Escalating with a clear handoff