Guide
The best Notion template by firm type: solo, boutique, in-house and virtual
The best Notion template for law firms by type: solo, boutique, in-house and virtual. What each needs first, what to watch for and where to start free.
By Raghav R Handa, practising lawyer16 min read
TL;DR
- A solo needs matters, deadlines and time. A boutique adds contacts, permissions and a knowledge base. An in-house team needs a request queue, a contract tracker and reporting. A virtual firm needs written procedures and disciplined sharing.
- The same six tests apply to every template (relations, matter-centric design, deadline provenance, rolled-up time, confidentiality guidance, maintenance), but what you check first differs by firm type.
- Start small: the minimum useful system in month one, then add a database only when you have felt its absence.
The best Notion template depends on the shape of your practice. A solo needs matters, deadlines and time. A boutique firm adds contacts, permissions and shared knowledge. An in-house team needs a request queue and reporting. A virtual firm needs written procedures and disciplined sharing. The same six tests apply to all (see the best Notion templates for lawyers), but what you check for first differs, and so does what you build in month one.
| Needs first | Watch for | Start here | |
|---|---|---|---|
| Solo | Matters, deadlines, time, Today dashboard | Over-building before you have used it | Notion for solo lawyers (see link below) |
| Boutique (2 to 10) | Matters, contacts, permissions, wiki, SOPs | Sharing and guest mistakes | Notion for small law firms |
| In-house | Request queue, contract tracker, reporting | Privilege mixed with business data | Notion for in-house counsel |
| Virtual firm | Procedures, secure sharing, async handoffs | No one to catch a mis-shared page | Notion for virtual law firms |
Start pages: solo lawyers, small law firms, in-house counsel, virtual law firms.
Six tests to apply to any template, first
- Relational: separate databases joined by relations, not one wide table.
- Matter-centric: opening a matter shows everything about it.
- Deadline provenance: each date records trigger and rule.
- Time rolls up: hours total per matter and per client.
- Confidentiality guidance: it tells you what not to store and how to restrict access.
- Maintained: there is an update policy and a creator who answers questions.
Solo
A solo is the fee earner, office manager and IT department at once, with nobody to cover. The system should make one person feel supported, not add admin.
Build first (month one)
| Database | Properties to start with |
|---|---|
| Matters | Name, client, status, next action, waiting on, opened, closed |
| Deadlines | Date, trigger, rule, matter, status, confirmed (a second check by a colleague or next-day self-review) |
| Time entries | Description, matter, date, hours, billable, billed |
Build next (months two and three)
- Contacts, for conflicts and referrals.
- Documents, linked to matters.
- Intake form and enquiries pipeline.
- Practice admin: certificate renewal, insurance, CPD hours, software renewals.
A solo's week
Monday: open Today, check deadlines and next actions. Daily: log time as you finish tasks. Friday: 45-minute review (deadlines, waiting-on, unbilled time, enquiries).
Pitfalls
- Building a client portal in week one.
- No second check on dates because "I am alone". Use a paid colleague or a next-day structured self-check.
- Trying to do trust accounting in Notion.
Boutique (two to ten people)
The problem changes from "I cannot keep it all in my head" to "nobody else can find what I did". The system must carry knowledge and manage access.
Build first
| Area | What to set up |
|---|---|
| Core databases | Matters, Contacts (with aliases), Time entries, Deadlines, Documents |
| Permissions | Practice area visible to the team; sensitive matters restricted; guests by named page only; MFA for all |
| Wiki and SOPs | Procedures for opening a matter, conflict checks, billing, closing; owners and review dates |
| Rhythm | Weekly team review of deadlines, waiting-on and workload |
Build next
- Onboarding checklist and training record (see onboarding and hiring and training).
- Referral and business-development tracking.
- Client status views.
Pitfalls
- Sharing and guest mistakes; review access monthly.
- Different people using different properties; agree a definition of each.
- Nobody owning the workspace; name an owner and a backup.
See the firm wiki, procedures and team collaboration in a small firm.
In-house legal team
Work arrives from the business, in many forms, from many people. The system must turn requests into a queue and show the business what the team does.
Build first
| Database | Properties to start with |
|---|---|
| Requests | Requester, business unit, type, priority, due date, owner, status, matter |
| Matters | Name, type, risk rating, owner, status, key dates |
| Contracts | Counterparty, type, status, value, term, renewal and notice dates, owner, document link |
| Reporting | Views for volume, turnaround and open items by business unit |
Pitfalls
- Privileged advice mixed with business content, with broad access. Keep legal in a restricted area.
- Ignoring your company's IT, security and records rules. Check them first.
- A request form so long nobody uses it. Keep it to five fields.
See contract lifecycle management in Notion and privilege and Notion.
Virtual law firm
With no office, structure replaces presence. Every handoff, status and procedure has to be visible and written.
Build first
- Next action, owner and waiting-on on every matter.
- A handoff note whenever work changes hands, written on the matter page.
- Views that surface quiet matters, approaching deadlines and stale waiting items.
- Procedures in the wiki for everything done more than twice.
- A monthly access review and a device rule.
Pitfalls
- Handoffs in chat that never reach the file.
- Lots of accounts and guests with no review.
- Assuming people see what an office would show them.
See the virtual law practice guide and Notion for virtual law firms.
Choosing between buying and building
| Question | Lean toward building | Lean toward a template |
|---|---|---|
| Do you enjoy building? | Yes | No |
| Is your practice unusual? | Yes | No |
| Is your time billable at a high rate? | No | Yes |
| Do you have an owner for the system? | Yes | Either |
| Do you want to see how Notion fits first? | Try a free starter | Try a free starter |
How to test a template safely
- Duplicate it into a separate test workspace.
- Fill it with fake clients and matters.
- Try the relations, views and buttons; open a matter and see if everything appears.
- Check default permissions and sharing settings.
- Read its guidance on confidentiality, and your own plan's limits.
- Only then move to a real workspace, starting with open matters.
Not sure? Try the free template library first, or read LawyerOS (free Starter Kit; Pro with AI is a one-time $99), and the best way to use Notion for lawyers.
Frequently asked questions
What is the best Notion template for a solo lawyer?
One built around matters, with deadlines and time entries related to them and a Today dashboard. Start with a free matters-and-clients template if you are unsure, and keep trust accounting in a separate tool.
What is the best Notion template for an in-house legal team?
One with a legal request queue, a contract tracker, a matter list and reporting the business can read. Sensitive privileged material needs a deliberate decision about what lives where, and your company's IT and records rules come first.
Do virtual law firms need a different Notion setup?
They need the same core databases plus clearer written procedures, asynchronous handoffs, secure client sharing and stricter permission discipline, because there is no office to catch mistakes.
What is the best Notion template for a small law firm?
A matter-centric system with Matters, Contacts, Time entries, Deadlines and Documents, plus a firm wiki and procedures, and a permissions design that keeps sensitive matters restricted. Judge any template against the six tests.
Should I buy a template or build my own?
Build if you enjoy it and your practice is unusual; start from a free or low-cost template if your time is worth more than the build. A free starter will tell you whether Notion suits you before you spend anything.
How many databases should my first system have?
Three to five. A solo can start with Matters, Deadlines and Time entries; a boutique adds Contacts and Documents. More databases mean more maintenance, so add them as you need them.
How do I check a template before I use it with client data?
Duplicate it into a test workspace, fill it with fake data, try the views and relations, review its permissions and sharing defaults, and read its guidance on confidentiality. Do not put real client data into an untested template.