The checklist
| Area | Check |
|---|---|
| Scope | Written list of what Notion will and will not hold |
| Security | Read Notion's security and privacy documentation |
| Regulation | Read your bar or regulator's guidance on cloud and AI |
| Permissions | Workspace private by default; share per page, deliberately |
| Accounts | Strong unique passwords and any two-step verification Notion offers |
| Members | Remove people who leave; review guests |
| Structure | Matters and Deadlines databases with consistent properties |
| Backups | Know how you export data and do it regularly |
| AI | Decide whether AI features are on and write a short policy |
| Pilot | Run a month on a few matters before committing |
Notes on the hard parts
Check what Notion's current plans offer on admin controls, export and security reporting before relying on them, since details change. Do not assume that a template or Notion makes you compliant with anything.
After the pilot
- Review what the team actually used.
- Delete unused properties and views.
- Write a one-page procedure for updating matters.
- Set a date to re-run this checklist.
Questions to put to yourself
- If Notion were unavailable for a day, what would I need and where is it?
- Who besides me can see this workspace, and should they?
- Would I be comfortable explaining my set-up to my regulator or a client?
- Have I told clients what I use if my rules or engagement terms suggest I should?
A one-page version to print
- 1
Before
Written scope, vendor review, regulator guidance read, decision recorded with a date.
- 2
Setup
Private workspace, named members, no public pages, guests reviewed, Matters and Deadlines built.
- 3
Pilot
A few real matters for a month, one weekly review, notes on what was missing.
- 4
Go-live
Written update procedure, backup routine, AI policy if AI is on, review date set.
Print it, tick it, and file it with your risk records. A dated tick-sheet is more useful in a later conversation with a client or regulator than a memory of having thought about it.
Common mistakes
- Starting the pilot with every client and learning about problems later.
- Sharing a page by link for convenience and forgetting it.
- Leaving former staff as members or guests.
- Turning on AI features without deciding what may be sent to them.
- Treating the checklist as a one-time task.
If an item does not apply, write why. The note is part of the record.
Frequently asked questions
- Is this checklist legal advice?
- No.
- Does it guarantee compliance?
- No. Your obligations depend on your jurisdiction.
- How often should I redo it?
- At least yearly.
- Do solos need all of it?
- Most items apply even for a solo.
- Who should own the checklist?
- One named person, usually a partner or the practice manager, who signs off each review and records the date.
About the author
Raghav Handa trained as a lawyer, then spent years building legal technology, from enterprise legal products to custom systems for law firms.
Keep reading
- About this siteGetting Started with Notion for Your Law PracticeA first-week plan for starting Notion in a law practice: decide the scope, set security, build Matters and Deadlines, and review before adding more.3 min read · 17 October 2026
- Security and ethicsIs Notion secure enough for lawyers? Confidentiality, ethics and setupIs Notion safe for client data? Its certifications and encryption, the ABA's reasonable-efforts standard, the real risks and how to configure it.3 min read · 17 October 2026
- Security and ethicsCan lawyers use Notion for client data?Can a law firm keep client data in Notion? What counts as client data, who decides, what to check first, and a short list of data you may prefer to keep elsewhere.3 min read · 17 October 2026
- About this siteThe Free Starter Kit: A Structure You Can Build TodayA free-to-build starter structure for lawyers in Notion: two databases, four views and a home page, with a path to LawyerOS Starter if you prefer it ready made.3 min read · 17 October 2026