Resources
How to Build a Timeline from WhatsApp Conversations
A useful timeline shows what changed, when it changed, and which message supports each event. It also separates the time a message was sent from a date mentioned inside it, so a future deadline does not become a past event.
This matters when a project change or order amendment unfolds across several days. Reading the chat in message order gives you the sequence of communication. It does not always give you the sequence of the events being discussed.
Decide what the timeline needs to explain
Choose a question before adding rows. “What happened in this project?” can produce a long list with little focus. “When was the wall change requested, approved and reflected in the proposed schedule?” gives each event a purpose.
Keep enough surrounding conversation to understand references such as “that change,” “the earlier date” or “as discussed.” If the reference cannot be resolved from the available messages, mark it as unclear.
Separate three kinds of time
- Message time: when someone sent the message.
- Event time: when the message says something happened.
- Target time: when something is proposed or expected to happen.
A message sent on Wednesday saying “we approved this on Monday” is evidence that the sender reported a Monday approval. If the original approval is missing, do not present the Wednesday message as though it were that original approval.
Keep the timezone if the record supplies one. If it is absent and could affect the sequence, state that limitation rather than choosing one silently.
Work through a fictional project change
| Message time | Sender | Message |
|---|---|---|
| Day 1, 09:00 | Client | Can we move the partition wall by 40cm? |
| Day 1, 09:10 | Contractor | That adds three working days if approved today. |
| Day 1, 09:20 | Project manager | Approved. Please send the revised completion date. |
| Day 2, 10:00 | Contractor | I propose Friday as the new completion date. |
| Day 2, 10:15 | Client | Is Friday now confirmed? |
The wall change has an explicit approval. Friday is a proposed completion date followed by a question. The excerpt contains no answer confirming it.
A timeline can therefore record:
| Event | Source | Status |
|---|---|---|
| Wall change requested | Day 1, 09:00 | Request recorded |
| Three-working-day impact stated, conditional on approval that day | Day 1, 09:10 | Stated estimate/condition |
| Wall change approved; revised completion date requested | Day 1, 09:20 | Approval recorded |
| Friday completion proposed | Day 2, 10:00 | Proposed; confirmation not shown |
| Client asks for confirmation | Day 2, 10:15 | Unanswered in the excerpt |
Do not turn “three working days” into a calendar date unless the starting point and working calendar are known. Do not turn a proposed date into an agreed deadline simply because it appears last.
Keep every row reviewable
For each important event, keep a short description, the message timestamp, any separate event or target date, a source reference, and its confirmation status. Keep the wording close to what the source supports.
If two messages conflict, preserve both and explain the difference. A timeline that displays an unresolved disagreement is more useful than one that silently selects a version.
Before sharing it, check:
- Can each row be traced to a message?
- Have message times and referenced dates been kept distinct?
- Are proposed, approved and completed actions labelled differently?
- Have later corrections or cancellations been considered?
- Are unresolved references and missing confirmations visible?
Use analysis to organize, then review
DialogSignal's chat-analysis views help organize conversation history, and its reports and export page explains the available output types and limits. Review the source messages before using a timeline to plan the next action.
Join the early-access list to be contacted about trial availability. The same review checklist applies whether you organize the timeline manually or use analysis to help.