Getting the Best from Timelines
A timeline is only as useful as what people put in it. These are the habits that separate a timeline somebody can hand over from one nobody reads.
Where to find it
Architect Panel → Data:
- Activity Stream — the entries themselves
- Datastores — the record type whose timeline you are shaping
Architect Panel → Automation:
- Journeys — where automatic entries can be written as a process runs
Record the decision, not the activity
"Called customer" is nearly worthless. "Called customer; they confirmed access is available Tuesday morning and asked us not to call the landline" is a handover.
The test is whether a colleague reading it tomorrow would need to ask you anything. If they would, the note is not finished.
Do not duplicate what the system records
If a status change writes its own entry, a note saying "changed status to In Progress" adds nothing but length. Every redundant entry makes the genuinely informative ones harder to find, and a timeline people skim is a timeline people miss things in.
Write for the next person
Not for yourself, and not for the file. Avoid abbreviations only your team uses, name people rather than writing "spoke to the manager", and say what was agreed rather than what was discussed.
Log at the time
Notes written at the end of the day lose the detail that made them worth writing, and notes written the following morning are reconstruction. Where the timeline is a record of what was agreed with somebody, contemporaneous matters — an entry written during the call carries weight that one written later does not.
Use the right type
Logging a telephone call as a note works, but it loses the ability to answer "how many times have we called this customer" — a question that comes up in complaints more often than you would expect. Types cost nothing to use correctly and are impossible to reconstruct later.
Attach the evidence
The photograph, the signed form, the supplier's email. An entry describing a document is weaker than an entry carrying it, and the description will outlive somebody's ability to find the file.
Keep an eye on volume
A record accumulating hundreds of entries usually means either the process is genuinely long-running or something automated is writing far more than it needs to. The second is worth investigating: an integration writing an entry on every poll will bury the human record entirely.
Review timelines when you review the process
The entries a process generates are a good diagnostic of the process itself. Steps that always produce the same note are candidates for automation; steps that produce no entry at all are steps nobody can evidence.
Worked example
A team reviewing complaint handling reads twenty timelines. They find that every case carries a manual note duplicating the status change, and that the acknowledgement step leaves no entry at all. They remove the duplicate note from the guidance and add an automatic entry on acknowledgement — and the timelines get shorter and more informative at once.
Recommendations
- Write what was decided, not what was done.
- Never duplicate a system entry.
- Use the specific type — call, email, note.
- Read a sample of timelines whenever you review a process.