Guide

Client status reports in Notion: what to send, how often, and what to leave out

Client status reports for law firms: the six things clients want, a cadence by matter type, a Notion template and what to keep out of the client view.

By Raghav R Handa, practising lawyer3 October 202616 min read

TL;DR

Clients want six things: where we are, what happened, what is next, what we need from them, what it has cost so far, and anything that changed.
Build a Client updates database and a Client view of each matter so the report is a view of data you already keep, not a rewrite.
Send on a fixed cadence matched to the matter, not only when something goes wrong, and put bad news first.
Keep internal notes, privileged analysis and candid assessments out of the client view, and preview before sharing.

Free downloadLawyerOS — Matters, Clients, Billing & AIGet it

A good client status report answers six questions: where are we, what happened, what is next, what do you need from us, what has it cost so far, and has anything changed. If your matter data already holds those answers, the report should be a view of the matter, not something you write from scratch each month. Poor communication is among the commonest sources of client complaints, and a regular, accurate report is the cheapest protection. This guide gives the structure, four ready templates, a cadence, the data model, the writing rules and the controls that stop an update from leaking what it should not.

The six questions, with examples

Question	Where it lives in Notion	A good answer
Where are we?	Matter phase and RAG status	"We are in negotiation; on track."
What happened?	Client update text, dated	"The other side replied on 3 October accepting two of our four points."
What is next?	Next milestone and next deadline (filtered view)	"We will respond by 10 October; completion targeted for the end of the month."
What do you need from us?	Client actions (tasks marked client-visible)	"Please send the signed authority and the January invoices by Friday."
What has it cost?	Rollup of fees and costs against estimate	"Fees to date $6,200 against an estimate of $9,000."
Has anything changed?	Scope changes and risk notes marked client-visible	"The counterparty has asked to add a warranty; this is outside scope and would add about $800."

The data model

Client updates (a database)

Property	Type	Why
Update	Title	Matter and date
Matter	Relation to Matters	Where it belongs
Date sent	Date	Evidence and cadence
Summary	Text	What happened, in plain words
Next steps	Text	What is next and when
Client actions	Text	What you need from them
Fees to date, Estimate	Number	Money transparency
Changes	Text	Scope, risk, timing
Status	Select: Draft, Approved, Sent	Review workflow
Channel	Select: Email, Shared page, PDF, Call	How it was delivered
Approved by	Person	Who checked it

Fields on Matters and Tasks

A Cadence select on Matters (Milestone, Monthly, Fortnightly, Weekly).
A Client visible checkbox on tasks, scope changes and notes.
A Last client update rollup (the latest Date sent from Client updates).

Cadence by matter type

Matter type	Suggested cadence	Also send
Routine transactional	At each milestone	On any delay or issue
Ongoing advisory	Monthly	After significant advice
Active litigation	Fortnightly, and after each event	After every order or hearing
Urgent or high-risk	Weekly	Immediately on material change
Dormant (waiting on others)	Every six to eight weeks	When something moves

Agree the cadence in the engagement letter so it is a promise you can keep, and record it on the matter so the system can check you keep it.

Four ready-to-adapt templates

1. Monthly update (advisory or ongoing)

Subject: [Matter]: update for [month]
Where we are: [one sentence].
What happened this month: [two or three bullet points].
Next steps: [what and when].
What we need from you: [action and date, or "nothing at present"].
Fees and costs to date: [amount] against [estimate or budget].
Anything to flag: [change, risk or decision needed, or "nothing"].

2. Milestone update (transaction)

Subject: [Matter]: [milestone] reached
[Milestone] is complete. The next stage is [stage], which we expect to take [duration] and which depends on [dependency]. Attached is [document]. Please [action] by [date]. Fees to date: [amount]; we remain within the estimate of [amount].

3. Litigation event update

Subject: [Matter]: [event] on [date]
What happened: [plain account of the hearing, order or filing]. What it means: [effect on the case]. What happens next: [steps and dates; any deadline the client must help meet]. Our view: [candid but careful assessment, only if appropriate to put in writing]. Fees to date: [amount].

4. Bad-news update

Subject: [Matter]: important development
I need to tell you about [development]. [Plain statement.] This means [effect]. We are [steps being taken]. The options now are [options]; I recommend [recommendation] because [reason]. I would like to discuss this by phone: are you free [times]? We will not take further steps on [point] until we have spoken.

Writing rules for a good update

Lead with what the client cares about, usually the outcome and the next step, not the process.
Plain words. Define any term you must use.
Bad news first, in the first paragraph, with what you are doing about it.
One screen. If it needs more, attach it.
Dates and owners. "We will do X by Friday" beats "soon".
No surprises on money. Flag costs approaching an estimate before they pass it.
Consistent format, so clients learn where to look.

Build a Client view

Add a Client visible checkbox on tasks, scope changes and notes.
On a template client page, add linked views filtered to the client's matter and to Client visible items: milestones, client actions, latest updates.
Share it through controlled, named access, or export it as a page or document.
Preview it as the client would see it (a test guest account) before sharing for real.

The approval workflow

A junior or the responsible lawyer drafts the update (status Draft).
The matter lead reviews for accuracy, tone and confidentiality (status Approved).
It is sent through the agreed channel and logged (status Sent, with date and channel).
The Last client update rollup refreshes automatically.

Views that keep you honest

View	Filter	Purpose
Updates overdue	Open matters where Last client update is older than the cadence	Should be empty at the weekly review
Drafts awaiting approval	Status Draft	Clears the queue
Matters over 80 percent of estimate	Fees to date over 80 percent of estimate	Prompts a cost conversation
Client actions outstanding	Client visible tasks assigned to the client, not done	What you are waiting on

// Days since last client update
if(empty(prop("Last client update")), 999,
  dateBetween(now(), prop("Last client update"), "days"))

// Overdue flag by cadence
if(prop("Cadence") == "Weekly" and prop("Days since last client update") > 7, "OVERDUE",
  if(prop("Cadence") == "Fortnightly" and prop("Days since last client update") > 14, "OVERDUE",
    if(prop("Cadence") == "Monthly" and prop("Days since last client update") > 31, "OVERDUE", "")))

What to leave out

Internal discussion, strategy debate and candid assessments of weakness unless you have decided to share them.
Other clients' information, including in rollups and linked views.
Anything that would be unwise to put in writing to the client.
Speculation presented as fact.

Check the client view in preview before sharing, and see client portals in Notion for the sharing mechanics and privilege and Notion.

Delivering it: shared page, email or call?

Channel	Good for	Watch for
Shared Notion page	Clients who like a live view; ongoing matters	Access control; client forwards link; keep it clean
Email with PDF	Most clients; creates a clear record	Confidential detail in email; use secure delivery where needed
Call, then a written note	Sensitive or complex news	Always follow with writing
Secure portal or sharing tool	Document-heavy matters	Another system to maintain

Measure it

Update compliance: the share of open matters within cadence.
Complaints about communication, before and after.
Client questions after an update: fewer means clearer updates.
Time to send: a good system makes an update a five-minute job.

Common mistakes

Sending updates only when asked, or only when something goes wrong.
Burying bad news in the fourth paragraph.
Rewriting from scratch each time instead of using the matter data.
Showing a client a page that includes internal notes.
Promising a cadence in the engagement letter and not tracking it.

Frequently asked questions

What should a client status report include?

The current stage, what has happened since the last report, the next steps and dates, anything you need from the client, fees and costs to date against any estimate, and any change in scope, risk or timing.

How often should a lawyer send status reports?

As often as the matter warrants and the client expects: monthly for ordinary matters, fortnightly or at each milestone for active or urgent ones, and immediately when something material changes. Agree the cadence in the engagement letter.

Can I produce client reports directly from Notion?

Yes. Create a view of the matter showing only client-appropriate fields, then share it through controlled access or export it. Keep privileged commentary and internal notes in fields that the client view does not show.

How do I deliver bad news in a status report?

Put it first, state it plainly, say what it means, what you are doing about it and what, if anything, you need from the client. Do not bury it, and do not wait for the next scheduled update.

Should status reports include fee information?

Usually yes: fees and costs to date against any estimate, and a heads-up when you approach it. Transparency about money reduces complaints and surprises.

How do I make sure updates actually get sent?

Build a view of matters with no client update in the last period for their cadence, and review it at the weekly meeting. A view that should always be empty is the cheapest compliance control you can have.

Is it safe to share a Notion page with a client?

It can be, with named access, a page that shows only client-appropriate content, no public link, and a preview before sharing. Consider whether a PDF or email suits the client better.

What if the client does not read the updates?

Keep sending, ask what format they prefer, and record in the file that you sent them. A concise, predictable update in the client's preferred channel gets read more often than a long one.

Related guides