How law firms organise matter files securely

The first decision a small law firm makes when setting up a portal isn't the tool. It's the data model. Should one client get one folder, or should each matter get its own folder?

Boutique firms (1-10 partners) almost always settle on per-matter, not per-client. This article explains why, what the folder structure inside a matter typically looks like, and how to handle the cases that don't fit cleanly.

Why per-matter beats per-client

A retainer client has six matters across two years. Three are commercial contracts, two are employment disputes, one is regulatory advice on a data protection question. If all six matters live in one folder labeled "Acme Industries," the following problems show up:

1. The privilege boundary blurs. The employment dispute file includes negotiations the client's HR director didn't see. The commercial contracts file includes draft language the client's procurement team approved. If those documents commingle in one folder, an inadvertent share to the wrong person at the client can leak privileged work product.

2. Disclosure becomes harder to bound. If the client gets sued by their own former employee, and the firm has to respond to discovery for "all documents related to Acme employment matters," a per-client folder requires you to filter the haystack. A per-matter folder is the haystack.

3. Billing reconciliation drifts. Time entries roll up per matter, not per client. If your file structure doesn't match your billing structure, partners spend Sunday evenings reconciling them.

4. Conflicts checks are noisier. Running a new matter against the per-client folder hits noise from unrelated old matters. Per-matter folders give a clean conflicts query.

5. Closure has no clear end. When the commercial contract dispute is resolved and the file should close, you can't close it without closing the client. So you don't close it. Five years later, the firm is paying storage for matters that closed in 2021.

Per-matter solves all five. Each matter has its own start and end. Each matter has its own access list. Each matter has its own privilege boundary. Each matter rolls up to one client when you need that view, and you can build that view at query time without restructuring the storage.

The folder structure inside a matter

The pattern most boutique firms converge on, after running their own naming experiments for a year or two, looks like this:

Acme Industries · Distribution agreement France 2026/
├── 01-Engagement/
│   ├── engagement-letter-signed-2026-08-12.pdf
│   ├── conflict-check.pdf
│   └── kyc/
│       ├── visura-camerale.pdf
│       ├── poa-andrea-russo.pdf
│       └── beneficial-ownership.pdf
├── 02-Discovery/
│   ├── client-provided/
│   │   └── original-french-draft.pdf
│   ├── third-party/
│   │   └── french-counsel-memo.pdf
│   └── notes/
│       └── intake-call-notes-2026-08-10.md
├── 03-Strategy/
│   ├── strategy-memo-v1-2026-08-15.pdf
│   ├── client-comments-v1.pdf
│   └── strategy-memo-v2-2026-08-22.pdf
├── 04-Work-product/
│   ├── drafts/
│   │   ├── distribution-agreement-v1.docx
│   │   ├── distribution-agreement-v2.docx
│   │   └── distribution-agreement-final.docx
│   └── signed/
│       └── distribution-agreement-signed-2026-09-04.pdf
├── 05-Correspondence/
│   ├── client-correspondence.pdf (consolidated, monthly)
│   └── counterparty-correspondence.pdf
├── 06-Court-filings/        (if applicable, often empty for transactional matters)
├── 07-Billing/
│   ├── time-entries-export.csv
│   ├── invoice-001-2026-09-22.pdf
│   └── invoice-002-final.pdf
└── 08-Closure/
    ├── closing-memo.pdf
    ├── client-deliverable-package.zip
    └── retention-schedule.md

Things to notice:

• Numbered prefixes (01-Engagement, 02-Discovery, etc.) keep the folder order stable in file managers and portals. Without prefixes, the alphabetical order is random ("Billing" sorts before "Engagement").
• Distinct verbs: Engagement (start), Discovery (intake), Strategy (analysis), Work-product (deliverables), Correspondence (audit trail), Court-filings (if applicable), Billing (money), Closure (end). One bucket per phase.
• Sub-folders for sources, not types. The "Discovery" folder splits by who provided the material (client, third party, our notes), not by file type. This makes the privilege chain visible.
• Drafts vs Signed split. Always. The "final" draft and the "signed" copy are different artifacts with different legal weight. They never live in the same folder.

How a portal helps versus a Drive folder

If you're already running this structure inside Google Drive or Dropbox, you don't necessarily need a portal. The structure is the win, not the tool.

A portal adds three things on top of the structure:

1. Per-matter access control. Each portal has its own audience: the client's named contact, the firm's partner, the firm's paralegal. Adding a third party (say, the client's accountant) doesn't require sharing the whole Drive; it requires inviting them to one portal.

2. Audit log per file action. "Who downloaded the signed contract on October 4?" is answerable in a portal. In Drive it's answerable if you're on Workspace Business+ and have the right log retention. In Dropbox it's not answerable at all on the lower tiers.

3. Approval objects. The strategy memo doesn't sit in folder 03 as a passive document; it lives there AND is an approval request with a timestamp and a client signature. Drive can't model that without a separate signing tool.

For Marchetti Avvocati (the boutique law firm walkthrough), the deciding feature wasn't the file structure (they had it). It was that the strategy memos became signable in the same place they lived, with an immutable record of who signed when. That single feature was the difference between a fee dispute they lost in 2025 and a year with zero disputes in 2026.

The cases that don't fit cleanly

Retainers without discrete matters

A regulatory-advice retainer doesn't have a beginning and end. Treat it as one rolling matter, with a folder structure that's date-indexed inside Work-product:

Acme Industries · Regulatory retainer 2026/
├── 01-Engagement/
├── 02-Discovery/
├── 03-Strategy/
├── 04-Work-product/
│   ├── 2026-Q1/
│   ├── 2026-Q2/
│   └── 2026-Q3/
├── 05-Correspondence/
└── 07-Billing/

Roll the retainer year over year. Open a new portal each calendar year (or each renewal cycle). Don't try to make one portal last five years.

Multi-firm representation

Your firm and another firm are co-counsel on a matter. Whose portal is canonical? The pragmatic answer: the firm with the lead role on the matter owns the portal. The other firm gets invited as a team member, not as a client. The client sees one portal with two firms listed in the "represented by" field.

Document-heavy litigation

If a single matter has 8,000+ documents (large commercial litigation), portals start to creak. You need a dedicated litigation-document platform (Relativity, Everlaw, DISCO). The portal still works for the client-facing layer (strategy memos, settlement positions, billing), but the document review database lives elsewhere.

Client confidentiality from team members

Some matters require limiting access within the firm: a partner-only matter that even paralegals shouldn't see (most often partnership disputes, internal investigations, settlements with the firm itself as a party). Per-matter portals handle this naturally; per-client portals don't.

What this means for the tool choice

If your firm is over 10 lawyers, runs hundreds of matters a year, has trust accounting needs, and wants integrated time-and-billing, you need a full practice-management platform. Clio Suite or MyCase. The portal layer is a feature inside that platform.

If your firm is under 10 lawyers, runs 30-150 matters a year, and the practice-management features feel heavy for your size: a per-matter portal at the front, your existing time-tracking spreadsheet at the back, plus Google Workspace for internal collaboration is the lean stack. That's the case ClientNest365 is built for. One slot per matter. €75 buys 25 matters. The structure above maps directly into the portal scaffolder when you select "legal" during setup.

The folder structure is the operating system. The portal is the UI. Get the operating system right first.