Tag events by issue
Colour-coded tags on the events and a legend a reader can follow, with working tags kept out of exports.
Screenshots are taken from the app on every release. Updated 13 October 2026.
The facts of a dispute rarely go to one issue. A letter in March may go to liability, a meeting in June to causation, and the invoices to quantum. Tagging each event with the issues it goes to lets you see the case issue by issue, and gives the reader a coloured legend to follow.
Before you start, decide which issues the case turns on, and which tags are for the team only, such as "to check" or "ask the client".
Tag the events
Open an event. Under Tags, click Add tags.
Start typing. Pick an existing tag from the list, or choose Add followed by the new name to create one.
For a new tag, click its colour in the palette. If you click away without choosing one, the tag is added in white. The colour is how the reader tells the issues apart, so give each issue a colour that stands out from the others.
To tag events while you go through the chronology line by line, switch to the table view and use the Tags column. To add a tag to many events at once, see change many events at once: adding tags there keeps the tags the events already have.
To take a tag off one event, open the event and click Remove (the cross) on the tag.
Keep the list of tags in order
Click the tag icon in the toolbar. The Tags list shows every tag on the timeline, with its colour and the number of events that have it. Click a tag to see its events.
To rename a tag or change its colour, click Edit. In Edit tag, change the Name or the Colour and click Save. The change applies to every event with the tag.
To delete a tag, click the bin and confirm in Delete tag. The tag comes off every event that has it; the events themselves stay.
Editing and deleting tags is for people who can edit the timeline.
Review one issue at a time
Click Filters in the toolbar to open Filter events.
Under Tags, choose the issue you want to review. The panel shows how many of the events are left.
With two or more tags chosen, choose Any to see events that go to at least one of the issues, or All to see only events that go to every one of them. All is how you find the events where liability and causation meet.
Click DONE. The filter stays on when you switch between the linear, relative and table views. To keep the selection for later, save it as a story; see save the events for each issue as a story.
You can also click a tag on any event card to see every event with that tag in a list.
Set up the legend
The legend tells the reader which colour means which issue. It is built from the tags, people and colours on the events.
In the linear or relative view, click Show legend in the controls at the bottom of the timeline.
Switch off the entries the reader should not see. The switch's tooltip reads Hide from legend and exports: the entry is left out of the legend on screen and of the legend in exports. Do this for working tags such as "to check".
Click an entry's name to change what the legend says, and drag entries into the order the reader should take them in, for example liability before quantum.
When you export, include the legend. In a PDF export, set Tags legend to Include legend. In a PowerPoint export of the linear timeline, set Include tags legend in export to Include legend. See present the case chronology.
Only people who can edit the timeline see Show legend and can change the legend.
Tips from practice
- Agree the tags with the team early. Three people tagging the same issue as "Causation", "causation" and "Cause" make three tags and three colours. Settle the list when the chronology is started and fix stray tags with Edit.
- Tag by issue, not by document type. Correspondence, pleadings and witness statements are better kept apart with swimlanes; see show each party's side in swimlanes.
- Hide the working tags before anything goes out. "To check" and "privileged?" are useful to the team and confusing to everyone else.
- One colour per issue. If two issues share a colour, the reader cannot tell them apart on a printed page.