Review the documents disclosed by the other side
Every disclosed document categorised against the issues in one table, with the relevant ones sent to the case timeline.
Screenshots are taken from the app on every release. Updated 13 October 2026.
Disclosure has arrived: hundreds of emails, scanned letters and attachments from the other side, and the team needs to know what is in them before the next hearing. An insight puts every document in one table, with a row per document and a column per question, so you can see which documents go to which issue and build the reading list from there.
Two questions shape the table. Which issues in the case could a document bear on? Each one becomes a column. And what do you need to see without opening the document? Usually the passage that matters, and the date.
Load the disclosure
Open the dispute matter, go to Insight and click Create new.
Click Add documents and choose From computer, or iManage, SharePoint or NetDocuments if your firm has connected one. Emails, PDFs, Office files and images can all go in, and each document becomes a row.
Look for red rows. A red row is a document Juristic could not read, usually a scan with no text. Click Get Insights, choose OCR scan red rows and analyse their cells, pick the language of the documents under Select Language and click Start. For a single document, right-click its row, choose OCR scan and analyse row, pick the language and click OCR.
Ask one question per issue
Click Column Centre in the top bar, then Write a new question. Write the issue as a question about each document: "Does this document concern the delayed deliveries under the supply agreement with Epsilon Trading Ltd?" Click Continue. If Juristic asks which reading of the question you mean, pick the one that fits the issue.
Check that Column type is Yes / No, click Test on 3 documents to see how it answers, and click Add column. Repeat for each issue, so every issue has a column you can filter on.
Add one Verbatim column for the key passage: "Quote the passage that concerns the delayed deliveries." A verbatim answer is the exact wording from the document, so the reading list shows why each document is on it.
If cells stay empty, click Get Insights, choose Analyse missing cells and click Start.
| What you need from each document | Column type |
|---|---|
| Does it bear on an issue? | Yes / No, one column per issue |
| The passage that matters | Verbatim |
| When it was written, or when the event in it happened | Date |
| A short description for the reading list | Short answer |
Search for a name or a term
Click Search in documents in the top bar and type a name, a project or a term: "Anna Lambda", "Project Alpha", a vessel or an invoice number. The results list every document that contains it, with the matching text; click one to open the document beside the table.
Build the reading list
Click Filters and show only the rows where an issue column is Yes. Sort by the date column to read them in order. Each issue gives you its own reading list; change the filter to move to the next.
As you read, right-click a cell to verify or flag it, so the team knows which answers a person has checked. Check and sign off the review covers how.
Send the relevant documents to the chronology
With the filter on, click Export and choose Transfer to a timeline. The transfer uses the table's current filter, so only the relevant documents go across.
Under Destination, choose the case timeline, or New timeline. Drag the columns onto the event fields, such as the date column onto Add date... and the short description onto Add title..., and click Add to timeline (or Make timeline for a new one). Add dates from an Insights table to the chronology goes through the transfer in detail.
Tips from practice
- Keep privilege in its own column. A Yes / No question such as "Does this document appear to contain legal advice to Beta Holding A/S?" lets you filter those documents out before anything goes to the chronology or the client.
- Check a Not found before relying on it. Not found means the analysis found no answer, not that the document is silent on the point. Search for the term with Search in documents, and after an OCR scan run Analyse missing and not found cells.
- One issue per column. A single column that lists the issues is harder to filter than one Yes / No column for each.
- Split the bundles first. If the other side served one long PDF that holds many letters, right-click its row and choose Split document before you add columns. See split a scanned bundle into separate documents.
The mechanics of columns, testing and re-running are in review a set of contracts in a table. For scans that never made it into an insight, see make scanned documents searchable.