Practical guide

Build a timeline that separates facts from uncertainty

Turn scattered records into an ordered account without filling gaps with assumptions.

Choose a scope before arranging dates

A timeline is a navigation tool, not a verdict. Decide what question it should help you answer: what happened over a weekend, how a repair request evolved, or when you received notices. Write that scope at the top. Collect the evidence inventory first, then make one row per event. Start with a narrow period and expand only if earlier or later context helps explain the sequence. A timeline that includes every unrelated detail can obscure the most useful facts.

Give each row an event date or date range, a short neutral description, a source ID, and a confidence note. Separate “the message says it was sent Tuesday” from “I first saw the message Wednesday.” When the source and your memory disagree, keep both observations and mark the conflict. Do not silently choose whichever time supports your preferred interpretation. State the time zone if messages or people crossed regions.

Use source-first language

Write “Email E-02 shows a request sent at 9:14 a.m.” rather than “They deliberately ignored my request.” The first can be checked against a source; the second is an inference about another person's intent. Keep a separate column headed “Questions or interpretations” for ideas to discuss later. If a recollection is your only source, say so: “My recollection, written down three days later.” This is more useful than presenting memory as a timestamped record.

Here is a fully fictional example, not customer data: May 2, 10:00 a.m. — tenant sends a maintenance request (email E-02); May 3 — tenant recalls a phone conversation (note N-01 written May 5; exact time unknown); May 7 — repair receipt shows a visit (receipt R-03). The timeline does not establish what was said in the call or who caused the problem. It gives a reader a route back to each source and tells them exactly where a gap remains.

Review for missing context

Sort your rows by event time, then read the sequence from start to finish. Are there messages with missing replies? Does an attachment belong to a later version of a document? Is an event based on a cropped image when the full image would clarify it? Add a “to locate” list rather than inventing an answer. If you receive new records, add rows with a note about when you obtained them. Keep earlier versions if you have shared a timeline already so you can explain what changed.

It may help to make a one-page overview for a meeting while retaining the full table for reference. The overview should identify major events and open questions, not assert conclusions that the sources cannot support. If another person reviews the table, invite them to flag ambiguities; they may notice a time-zone mismatch you missed.

Practical checklist

Check whether each event has a source ID or is clearly marked as recollection.
Mark approximate dates and conflicting clocks; do not turn “early May” into a precise day.
Include relevant responses and contrary information, not just items favorable to one account.
Keep source files separate from the editable timeline and record later corrections.
Ask a reader unfamiliar with the story which abbreviations or transitions are unclear.

What a timeline cannot do

An ordered account does not establish legal responsibility or determine which records a court will accept. Requirements and procedures differ by jurisdiction and type of matter. If you have a pending court matter, use the court's official website or speak with a licensed local professional about procedures; this page offers no filing instructions or deadlines. Treat the timeline as a draft working aid that makes a consultation more focused.