Build a timeline without inventing event order
A timeline can create false precision when uncertain timestamps are placed as exact points. Preserve the uncertainty before deciding which event happened first. A small ordering ledger can show what the records establish without turning a plausible sequence into a factual one.
State what each time range means
Fictional practice example: event A happened sometime between 09:00 and 09:05 UTC, event B sometime between 09:03 and 09:04 UTC, and event C exactly at 09:10 UTC. All belong to one stated date. The ranges bound an unknown instant when an event occurred; they are not the durations of activities.
For each record, retain its source description, date, stated clock basis, earliest possible instant, and latest possible instant. If a note describes an activity lasting five minutes instead, classify that separately. Replacing an uncertain event instant with a five-minute activity would change the question being examined.
Keep clock assumptions explicit
Use a common time basis only when the record supplies enough information to establish it. In this example, UTC is already stated. No offset conversion or clock correction is needed. In another record with an unknown zone or unknown date, preserve that gap rather than choosing the most convenient interpretation.
A minute shown on a screen does not by itself establish how precisely the underlying event was recorded. Ask what supports the earliest and latest bounds. Do not narrow them just because an exact point would make the drawing easier. The ledger should expose uncertainty, including a time that cannot yet be compared at all.
Compare bounds for definite precedence
A's latest possible instant, 09:05, is earlier than C at 09:10. A is therefore before C under the stated bounds. B's latest, 09:04, is also earlier than C. Record those two definite relations and the bounds supporting them.
For A and B, the ranges overlap. A could have occurred at 09:01, before B, or at 09:05, after B. The supplied information does not establish their order. Sorting the earliest bounds would put A first in a list, but that presentation choice would not settle which event happened first.
If one range ends exactly where another begins, strict precedence may also remain unestablished because both events could fall at that boundary. State the relation you can support rather than silently treating equality as earlier.
Draw only the order that is known
Place A and B as unresolved relative to one another, with both preceding C. Keep their ranges attached. Do not label them simultaneous: overlapping uncertainty permits several possibilities and does not show that their actual instants were equal.
Nor does A-before-C or B-before-C establish a cause. A time relation can support a chronological account while leaving explanations open. If the working question requires A-versus-B order, identify the missing observation that could narrow one of those ranges rather than collecting more opinions about the most plausible story.
Test the final account against the bounds
Ask another reader to explain which orderings are definite and which remain unknown. Have them give one allowed example in which A precedes B and another in which B precedes A. Both should still put C afterward under the fictional conditions.
Keep the source bounds, justified relations, unresolved comparisons, and next evidence question together. If the summary reads A then B then C as a confirmed sequence, revise it. A useful partial timeline remains honest about an order it cannot establish, even when a single neat sequence would be easier to present.
