---
title: "The Evidence pillar: classified, tagged, review-tracked"
url: https://thematteros.com/features/pillar_evidence
updated: 2026-10-17
author: Raghav Handa
---

# The Evidence pillar: classified, tagged, review-tracked

The Evidence pillar is a register of the documents and material on each matter, with classification, tags and review status. In MatterOS it is the Evidence database linked to Matters. Its test is whether you know what you have, its status and what is missing. AI may help read; you decide.

## Key takeaways

- It fixes the problem where finding a document depends on remembering where it was saved.
- Each row records classification, tags, review status and the matter it belongs to.
- The register tracks documents; it does not replace a document management system.
- Missing documents are as important to list as held ones.

## What each row records

| Property | Why it matters |
| --- | --- |
| Matter | Puts the document on the case page |
| Classification | Separates, for example, pleadings, correspondence and privileged material |
| Tags | Issues, parties or witnesses for filtering |
| Review status | Shows what nobody has read yet |
| File or link | Where the document actually is |


## Running the register

1. Log a document as it arrives, not at the end of the matter.
2. Review the Unreviewed view each week.
3. Add placeholder rows for documents you are waiting for.
4. At closure, check privileged and sensitive items before archiving.

- Evidence and document tracking: https://thematteros.com/blog/legal-evidence-and-document-tracking-in-notion


## Related workflows

To file incoming material see document filing, and for litigation sets see discovery tracking.

- Document filing: https://thematteros.com/features/document_drop
- Tracking discovery: https://thematteros.com/features/discovery
- Security: https://thematteros.com/features/two_factor


## Limits

The register does not store files securely beyond what Notion provides, perform OCR, detect duplicates or enforce retention. Decide with your firm where originals live and what information belongs in Notion.


## A worked example

Take an illustrative employment dispute. A client sends a contract, three emails and a payslip. You add four rows to the Evidence database, all linked to the matter. The contract is classified as a contract, the emails as correspondence, the payslip as financial. Tags record the issue (notice period) and the party. All four start as Unreviewed. You also add a placeholder row for the personnel file you have asked the employer for, marked Awaiting.

Next week, the Unreviewed view shows what nobody has read. After review, the status changes and a short note records what the document proves or undermines. The Awaiting row keeps the gap visible on the matter page instead of in your memory.


## Mistakes to avoid

- Logging documents in bulk at the end, when the context is gone.
- Using too many classifications; five or six are enough to filter on.
- Treating the register as the document store when originals live elsewhere.
- Forgetting to mark privileged or sensitive items before sharing a matter with a guest.


## FAQ

### What is the Evidence test?

Do you know what you have, its status, and what is missing?

### Does MatterOS read documents with AI?

Not on its own. You can use an assistant of your choice and decide what to record.

### Can I use it outside litigation?

Yes. Any matter has documents worth classifying.

### Should files be stored in Notion?

That is a choice. You can store links to files kept elsewhere.

### Can the register show what is missing?

Yes, if you add placeholder rows for documents you are waiting for and give them an Awaiting status. Notion does not detect gaps by itself.

### How many classifications should I use?

Few. Five or six that you will apply consistently are more useful than a long list that nobody remembers.