Add the review table's dates to the chronology
Dated rows of an Insights table turned into timeline events, columns mapped to event fields.
Screenshots are taken from the app on every release. Updated 14 October 2026.
You have run the invoices, notices or delivery notes through Insights, and the table now holds a date for each one. Those dates belong on the chronology: when each notice was served, when each invoice fell due. Instead of retyping them, you transfer the rows to the timeline and decide which column becomes which part of the event.
Two questions shape the transfer. Which rows belong on the chronology? And how many events does each row hold? A contract can give you a signing date and a termination date; an invoice an issue date and a due date.
Choose the rows
Open the insight and filter the table so that only the rows you want are left. Every row the table shows is transferred, so filter out the documents that are not part of the story and the rows with no date.
Transfer the rows to a timeline
Click Export in the bar above the table, and choose Transfer to a timeline.
Under Destination, choose the case chronology to add the events to it, or New timeline to start one. The list holds the timelines in the same matter as the insight, or in the same client group if the insight belongs to a group rather than a matter. A new timeline is created there and takes the insight's name.
Drag columns from Columns on the left onto the event on the right: one onto the title, one onto Add date..., and, if you want them, onto Add description..., Add people..., Add tags... and Add notes.... Besides the table's own columns you can use Document title, Category and Information, the short summary of each document.
If each row holds more than one date, click Add event type and map the second event the same way, for example the due date with a title of its own. Every row gives one event of each type.
Click Make timeline, or Add to timeline if you chose an existing one. Juristic opens the timeline, and the events appear as they are processed; progress shows at the bottom of the timeline.
Check the events
Each event is linked to the document its row came from, so you can open the invoice or the notice from the event. Dates are converted to a single format; a row whose date could not be read becomes an event without a date. Go through the new events before you rely on them: Check and correct the chronology in a table shows them side by side with their dates.
What to map
| The table holds | Title | Date | Worth adding |
|---|---|---|---|
| Notices served on the other side | Document title | The date of service | The sender's column under people, so you can filter by party |
| Invoices in a payment dispute | A column with the invoice number | The due date | A second event type for the issue date |
| Delivery notes | Category or a column with the goods | The delivery date | Notes with the quantity, which stay internal to the team |
Tips from practice
- Keep the insight. It is the record of where each date came from, with the reasoning behind every cell, if the other side disputes a date.
- Tags group the events by issue. A column with the issue each document goes to, dragged onto tags, gives you tagged events from the start (Tag events by issue).
- Transfer once. Transferring the same rows again adds the events a second time, so filter the table to the new rows if you add documents later.
Still building the table? See Review the documents disclosed by the other side.