Matter Status Update Cadence

The single most common complaint clients make about lawyers is not fees, competence, or outcome. It is that they could not find out what was happening. A matter can be going perfectly and the client can still be furious, because six weeks of professional silence feels identical to being ignored. In litigation and immigration especially, long stretches where nothing moves are normal and expected by the firm, and completely unexplained to the person whose life is on hold.

So the client calls. The receptionist takes a message. The paralegal has to pull the file, work out what has actually happened since last time, check with the attorney whether any of it can be shared and how, and call back. That cycle burns twenty to forty minutes of chargeable-grade time, produces nothing that advances the matter, and is almost always unbillable. Multiply it across a caseload and a firm is giving away a meaningful share of its capacity to the job of reassuring people. Worse, the clients who call most are rarely the ones whose matters most need attention, so the squeaky wheel sets the firm's priorities.

The firm's usual response is to promise better communication, which depends on individual lawyers remembering to do a thing they are not scheduled to do, in between the things they are. It does not survive a busy month. What works instead is a cadence: every active matter gets an update on a schedule set by its type and phase, including when the honest content of the update is that the matter is where it was and the next expected event is still some way off. A scheduled nothing is enormously more reassuring than an unscheduled silence, and it is far cheaper to produce. This build is that cadence, with the attorney reviewing and approving each substantive update before it leaves the building.

Pipeline and stages

The pipeline here is not the matter's legal lifecycle - the practice management system owns that. This is a Client Communication pipeline tracking the state of the update cycle itself, so you can see at a glance which clients are current and which are overdue a word from the firm.

• Onboarding Expectations Set - matter opened, the client has been told what cadence to expect and has not yet had their first scheduled update.
• Current - last update sent within the cadence interval. The resting state; most matters should be here.
• Update Due - the interval has elapsed and the draft is being prepared.
• Awaiting Attorney Approval - a draft update is sitting with the responsible attorney. The only stage with a human bottleneck by design.
• Overdue - approval has not happened and the client is now past the promised interval. This stage should be loud.
• Client Reached Out First - the client asked before the firm told them. Every matter that lands here is a cadence failure worth reviewing.
• Paused - Client Request - the client has asked for fewer updates, or the matter is dormant by agreement.
• Matter Closed.

Calendars

• Case Check-In Call - 15-minute slots on each attorney's calendar, offered inside the update message, capped at a set number per week so the offer cannot swamp a calendar.
• Quarterly Matter Review - 30-minute slots for long-running matters where a written update stops being enough.
• Attorney Update Review Block - a recurring internal hold, typically 30 minutes twice a week, where the attorney clears the approval queue. Protecting this block is what makes the whole build work.

Custom fields

• Matter Reference, Matter Type, Responsible Attorney, Assigned Paralegal.
• Matter Phase - picklist: Intake, Pre-Filing, Filed and Pending, Discovery, Negotiation, Awaiting Third Party, Awaiting Court or Agency, Resolution, Closing. The phase drives the interval, because a matter in discovery genuinely has more to report than one waiting on an agency queue.
• Update Interval Days - the promised cadence for this matter. Set from a Matter Type and Phase default, overridable per client.
• Last Update Sent Date, Next Update Due Date, Updates Sent Count.
• Current Status Summary - the plain-language sentence the attorney or paralegal approves for client consumption. Deliberately separate from any internal case note.
• Next Expected Event and Next Expected Event Window - e.g. "response from the other side" and "within the next 4–6 weeks". A window, never a promise of a date.
• Client Action Required - yes or no, plus a text field naming it. Updates that ask for something get different copy and their own follow-up.
• Preferred Channel, Update Detail Preference (Brief or Detailed), Language.
• Confidentiality Restriction - free text. Do not contact at work, shared email, do not leave voicemail, use initials only. This field overrides channel choices.
• Client Reached Out Count - how many times this client has called or written asking for a status. The single best diagnostic in the build.
• Portal Link, Satisfaction Score.

Tags

• cadence-active, cadence-paused, cadence-closed - the master switches.
• update-approved, update-overdue, awaiting-approval.
• high-touch-client - shortens the interval; applied manually or automatically once Client Reached Out Count passes a threshold.
• quiet-client - prefers minimal contact; lengthens the interval.
• restricted-contact - a Confidentiality Restriction exists; blocks SMS and voicemail entirely.
• sms-opt-out, review-request-eligible.

Forms and surveys

• Communication Preferences Form - sent at onboarding. Captures Preferred Channel, Update Detail Preference, Language, Confidentiality Restriction and whether voicemail may be left. This form is how the firm earns the right to text somebody about their legal matter.
• Status Update Draft Form - internal. The paralegal writes Current Status Summary, Next Expected Event, Next Expected Event Window and Client Action Required, then submits for approval.
• Attorney Approval Form - internal. Approve as drafted, edit and approve, or hold with a reason. Nothing substantive reaches a client without passing through here.
• Post-Update Pulse - a one-question survey attached to every third update: "Do you feel you know where your matter stands?" with a comment box. Writes Satisfaction Score.
• Cadence Change Request - client-facing link in every update: more often, less often, or a different channel. Self-service, so a preference change does not require a phone call.

BO's role and guardrails

BO assembles and delivers; the attorney decides what is said. That division is the whole design.

• BO may: assemble the draft update from the approved fields, send approved updates on schedule and on the right channel, answer purely administrative questions (who is my attorney, what is my matter reference, when is my next update due, how do I book a call, how do I pay an invoice), book check-in calls, and record a cadence preference change.
• BO may not: generate, infer, embellish or speculate about matter substance; answer "what is happening with my case" from anything other than the approved Current Status Summary; estimate timing beyond the approved Next Expected Event Window; comment on strategy, prospects, or what an event means; or send any substantive update that has not been approved by the responsible attorney.
• When asked anything beyond the approved summary, BO says: "The latest on your matter is what I sent you on [date]. Anything beyond that needs to come from [Attorney Name] - shall I book you a 15-minute call, or ask them to get back to you?" Then it books, or assigns the thread.
• Every message carries the firm's administrative footer: administrative communication, not legal advice, no attorney-client relationship created or altered. Exact wording from the firm's compliance counsel.
• Confidentiality shapes every template. No SMS body or email subject names the matter's subject, the court, the agency, the counterparty, the charge or the condition. Subjects read "Update on your matter with [Firm Name]". Clients tagged restricted-contact get email-only to an address they nominated, with no detail outside the secure link.

Numbers and channels

• A dedicated client-care number for update traffic and inbound status calls, separate from the new-business line.
• Voice AI on that number for status calls: identifies the caller, confirms when the last update was sent and when the next is due, offers to resend it or book a check-in call, and routes anything substantive to the assigned paralegal with a transcript. It states its approved status sentence and nothing further.
• Two-way SMS for brief updates and nudges, with a monitored human inbox.
• Email as the primary channel for detailed updates, from a monitored firm address.
• Secure portal link in every message for clients who want the full picture rather than a summary.
• Printed letter path for clients with no reliable digital channel, generated from the same approved fields.

One client, one long-running matter, from engagement to close.

1. Engagement signed, expectations set in writing. The contact record gets Matter Reference, Matter Type, Matter Phase, Responsible Attorney and Assigned Paralegal. A deal is created in Client Communication at Onboarding Expectations Set and cadence-active is applied. The welcome message states the cadence explicitly: "You will hear from us at least every [Update Interval Days] days, even when there is nothing new to report." Promising the schedule is what makes the schedule valuable.
2. The client sets their preferences. The Communication Preferences Form captures channel, detail level, language, whether voicemail may be left, and any Confidentiality Restriction. A restriction applies restricted-contact, which overrides everything downstream.
3. The interval is set from type and phase. A matter in Discovery might be every 14 days; one in Awaiting Court or Agency every 45. Update Interval Days and Next Update Due Date are written, and the deal moves to Current.
4. The due date arrives. The deal moves to Update Due and a drafting task lands on the Assigned Paralegal with the previous Current Status Summary attached, so the draft is written against what the client was last told rather than from scratch.
5. The paralegal drafts. The Status Update Draft Form takes the new Current Status Summary in plain client language, the Next Expected Event and its window, and whether anything is needed from the client. Submitting moves the deal to Awaiting Attorney Approval and applies awaiting-approval.
6. The attorney approves. In the twice-weekly review block, the attorney approves as drafted, edits and approves, or holds with a reason. Approval applies update-approved and releases the send. Nothing substantive goes out any other way.
7. BO assembles and sends. Channel from Preferred Channel, length from Update Detail Preference, template set from Language, suppressions from restricted-contact and sms-opt-out. Last Update Sent Date is stamped, Updates Sent Count increments, Next Update Due Date is recalculated, and the deal returns to Current.
8. A material event interrupts the cadence. A hearing is set, the other side responds, the agency issues a decision. The scheduled update is not the right vehicle for this. The event triggers a same-day draft-and-approve cycle on a compressed timer, and the scheduled interval resets from the event rather than stacking a routine update on top of a real one two days later.
9. The client asks for something. If Client Action Required is yes, the update names it specifically and a short follow-up sequence runs on it, separate from the cadence, so a request for a signature does not get lost inside a status narrative.
10. The client calls anyway. Voice AI on the client-care line identifies them, confirms the date of the last update and the date of the next, offers to resend it or book a check-in call, and routes anything substantive to the paralegal with a transcript. Client Reached Out Count increments and the deal moves to Client Reached Out First - a flag, not a failure state, but one worth reviewing.
11. The cadence adapts. Three unsolicited contacts inside one interval applies high-touch-client and halves Update Interval Days. A client who uses the Cadence Change Request link to ask for less gets quiet-client and a longer interval. Neither change requires anyone at the firm to make a decision.
12. Satisfaction gets measured. Every third update carries the Post-Update Pulse. A low score creates a task for the Responsible Attorney to make one real phone call - not an automated apology.
13. Approval stalls. If a draft sits unapproved past the promised interval, the deal moves to Overdue, update-overdue is applied, and the escalation ladder runs at the attorney, then the supervising partner. An overdue update is the firm breaking a promise it made in writing at engagement, and the system treats it that way.
14. Matter closes. The deal moves to Matter Closed, cadence-active is removed, all pending steps are canceled, and a closing sequence runs: the outcome summary the attorney approved, the file retention and return position, and - only for clients tagged review-request-eligible after a positive pulse score - a single review request that mentions service and never the outcome.

Eight workflows. Every one checks cadence-active first and exits if it is absent. Every send checks restricted-contact and sms-opt-out before choosing a channel, and respects quiet hours of 8am to 8pm in the client's time zone.

1. Onboarding and Expectation Setting

Trigger: matter opened, deal created at Onboarding Expectations Set.

• Action 1: apply cadence-active, set Update Interval Days from the Matter Type and Phase default table, calculate Next Update Due Date.
• Action 2, within 1 hour: welcome email. "Hi [First Name], your matter is now open with [Firm Name] and your reference is [Matter Reference]. [Attorney Name] is the attorney responsible and [Paralegal Name] will be your day-to-day contact. We will send you an update at least every [Update Interval Days] days. Some of those updates will say that nothing has changed - that is normal in a matter like yours and we would rather tell you so than leave you wondering. Please take two minutes to tell us how you would like us to reach you: [Preferences Form Link]."
• Wait 2 days. If the preferences form is not submitted, SMS: "Hi [First Name], [Firm Name] here - quick 2-minute form so we contact you the way you prefer: [Link]. Reply STOP to opt out of texts."
• Wait 3 days. Still not submitted - task for the Assigned Paralegal to capture preferences by phone. Never default a client into SMS because they ignored a form.

Exit: preferences form submitted or captured by phone; deal moves to Current.

2. Scheduled Update Due

Trigger: daily check at 7am - Next Update Due Date is today or earlier, deal is at Current, not cadence-paused.

• Action 1: move the deal to Update Due.
• Action 2: task for the Assigned Paralegal, due same day: "Draft status update for [Matter Reference]. Last update [Last Update Sent Date] said: [previous Current Status Summary]."
• Wait 1 business day. Not drafted - reminder to the paralegal.
• Wait 1 business day. Not drafted - notify the Responsible Attorney and the firm administrator together. Two silent days on a promised update is the beginning of the failure this build exists to prevent.

Exit: Status Update Draft Form submitted.

3. Attorney Approval Gate

Trigger: Status Update Draft Form submitted.

• Action 1: move to Awaiting Attorney Approval, apply awaiting-approval, create a task for the Responsible Attorney with the draft and the approval form link, due before the next Attorney Update Review Block.
• Branch - approved as drafted or edited and approved: apply update-approved, remove awaiting-approval, release workflow 4.
• Branch - held: the attorney records a reason and a date to revisit. The deal returns to Update Due with Next Update Due Date pushed to the revisit date, and the paralegal is notified. A hold is a deliberate decision, logged.
• Wait 24 hours from task creation with no decision - reminder to the attorney by internal message and SMS.
• Wait a further 24 hours - deal moves to Overdue, apply update-overdue, notify the supervising partner. Escalation is to a person senior to the bottleneck, which is the only kind that works.

Exit: approved or held.

4. Approved Update Send

Trigger: update-approved applied.

• Branch on Update Detail Preference - Detailed, email: subject "Update on your matter with [Firm Name] - [Matter Reference]". Body: "Hi [First Name], here is where your matter stands as of today. [Current Status Summary] The next thing we expect is [Next Expected Event], likely [Next Expected Event Window]. [If Client Action Required: We need one thing from you: [Client Action Detail]. Here is the link: [Portal Link].] [If not: There is nothing you need to do right now.] Your next scheduled update is on or before [Next Update Due Date]. If you would rather talk it through, book 15 minutes with [Attorney Name]: [Check-In Link]. - [Paralegal Name], [Firm Name]"
• Branch on Update Detail Preference - Brief, SMS: "Hi [First Name], update on your matter with [Firm Name]: [short Current Status Summary]. Next: [Next Expected Event], [Window]. Nothing needed from you. Full detail: [Portal Link]. Next update by [Date]."
• Branch - restricted-contact: email only, to the nominated address, no detail in the subject, status content behind the portal link only.
• Action after send: stamp Last Update Sent Date, increment Updates Sent Count, recalculate Next Update Due Date from Update Interval Days, remove update-approved, move the deal to Current.
• Branch - Updates Sent Count divisible by 3: wait 1 day, then send the Post-Update Pulse.

Exit: sent.

5. Material Event Interrupt

Trigger: Matter Phase changes, or a hearing or decision date is written to the record, or the paralegal flags a material event.

• Action 1: cancel any pending routine update step for this matter, so the client does not get a routine note two days after real news.
• Action 2: create a high-priority draft task due within 4 business hours, flagged as event-driven.
• Action 3: hand to workflow 3 with a compressed approval timer - reminder at 4 hours, escalation to the supervising partner at 8 business hours.
• Action 4 after send: reset Next Update Due Date from the send date, so the cadence restarts from the news rather than from the last routine note.
• Guardrail: the event itself never triggers an automatic client message. A court date or an agency decision is exactly the kind of thing a client will read meaning into, and the meaning is the attorney's to supply.

Exit: event update sent.

6. Client-Initiated Contact Handling

Trigger: inbound call, SMS or email from a contact tagged cadence-active.

• Action 1: increment Client Reached Out Count, move the deal to Client Reached Out First, timestamp the contact.
• Condition A - administrative question (who is my attorney, what is my reference, when is my next update, how do I pay, can I reschedule): BO answers directly and closes the thread.
• Condition B - status question: BO replies with the approved summary and nothing more. "As of [Last Update Sent Date]: [Current Status Summary]. The next thing we expect is [Next Expected Event], [Window]. Your next scheduled update is due by [Next Update Due Date]. Want me to book 15 minutes with [Attorney Name]?"
• Condition C - anything substantive (what does this mean, what are my chances, should I accept, what if I do X): BO sends only "That is one for [Attorney Name] rather than me. I have flagged it and someone will come back to you - shall I book you 15 minutes?" Assign to the paralegal, flag urgent.
• Condition D - distress, a complaint, or any mention of a deadline the client believes was missed: notify the Responsible Attorney and the supervising partner immediately, pause all automated messaging on the matter for 3 business days.
• Action last: if Client Reached Out Count has risen by 3 or more within one Update Interval Days window, apply high-touch-client and hand to workflow 7.

Exit: thread closed by a human.

7. Cadence Tuning

Trigger: high-touch-client applied, quiet-client applied, Cadence Change Request submitted, or Matter Phase changed.

• Branch - high touch: halve Update Interval Days, floor at 7, notify the Responsible Attorney: "[Client Name] has asked for a status [n] times this period. Interval shortened to [n] days. Worth a call?"
• Branch - client asked for less: set Update Interval Days to the requested interval, cap at 90, confirm in writing: "Noted - we will update you every [n] days from now, and we will still contact you straight away if anything material happens." Apply quiet-client.
• Branch - client asked to pause: move to Paused - Client Request, apply cadence-paused, set a mandatory 90-day review task for the attorney. A pause is never permanent, because a dormant matter with no contact is a complaint waiting to happen.
• Branch - channel change: update Preferred Channel, confirm on the new channel.
• Branch - phase change: reset Update Interval Days from the type-and-phase table and recalculate the due date.

Exit: fields written and confirmation sent.

8. Overdue Escalation and Close-Out

Trigger A: deal in Overdue.

• Immediately: internal alert to the Responsible Attorney and the firm administrator.
• Wait 1 business day - still overdue, alert the supervising partner and add the matter to the daily partner exception list.
• Wait 2 business days - still overdue: send the client a holding message approved in advance as a standing template. "Hi [First Name], a short note to say your matter is still with us and we owe you an update. [Attorney Name] will be in touch within two business days." Nothing substantive, and nothing about the matter. The firm acknowledging the lapse beats the firm going quiet about going quiet.

Trigger B: matter closed.

• Move to Matter Closed, remove cadence-active, apply cadence-closed, cancel every pending step.
• Day 0: closing email with the attorney-approved outcome summary, the file retention position and the return-of-documents arrangements.
• Day 7: if Satisfaction Score is positive and review-request-eligible is present, one review request referring only to the service experience, never to the outcome or the matter's subject. One request, no follow-up.
• Day 30: a single relationship note with no ask, if the firm wants one: "Hi [First Name], hope things are settled. If anything comes up, you know where we are."

Exit: close-out sequence complete.

Client communication stops being a function of who happens to shout. Every active matter has a promised interval, a visible due date and a pipeline stage that shows whether the firm is keeping its word. Partners can look at one board and see where the firm is behind, which is a very different conversation from hearing about it from an angry client.

The drafting work changes shape. Instead of reconstructing a matter's history at the moment a client calls, a paralegal writes a two-sentence status against the previous one on a schedule, and the attorney reviews a queue of short drafts in a protected block twice a week. The same information reaches the client at a fraction of the cost, and the attorney's judgment is still in the loop on every substantive word.

Inbound status traffic falls because the question has already been answered, and the calls that still come in get handled by the voice assistant stating an approved sentence rather than by a receptionist taking a message that generates a callback. The capacity that frees up is real: it is the time the firm was spending on reassurance it can now spend on the matters themselves.

Metrics to watch

• Share of active matters at Current on any given day. This is the health of the whole system in one number; it should sit high and stay there.
• Cadence adherence: percentage of updates sent on or before Next Update Due Date, by attorney. Published internally, this number changes behavior faster than any reminder.
• Unsolicited client contacts per active matter per month, tracked from Client Reached Out Count. This is the metric the build exists to reduce. Expect it to fall over the first few months rather than immediately.
• Time in Awaiting Attorney Approval. The approval gate is the deliberate bottleneck, so measure it honestly. If it is routinely long, the review block is not protected or the drafts are too long to review.
• Overdue count and overdue duration, by attorney and by matter type.
• Post-Update Pulse scores and the trend, segmented by matter type and by interval length. This is how you learn whether 45 days is actually acceptable for an agency-queue matter or whether it needs to be 30.
• Voice assistant containment: share of inbound status calls resolved without a human callback, and a monthly sample of transcripts reviewed to confirm the assistant stayed inside the approved summary.
• Receptionist message volume for status inquiries. A simple proxy for reclaimed front-office time.
• Complaints and negative reviews mentioning communication. The lagging indicator everything above is trying to move.

Platform and data

• Decide where the matter's substance lives. The practice management system remains the record of the matter; the platform holds the communication state, the approved client-facing summary and the cadence. Do not try to make the platform the case file.
• Build the Matter Type and Phase interval table with the partners before you build anything else. It is a policy decision, not a configuration detail: the firm is committing in writing to a contact frequency per matter type, and it has to be a frequency the firm can actually sustain in a busy month. Set it conservatively and tighten later.
• Decide who drafts and who approves for each practice area, and whether any update type can be pre-approved as a standing template - the holding message and the "no change since last time" note are the usual candidates. Everything else goes through the gate.
• Protect the attorney review block in the calendar before launch. The most common failure mode for this build is a perfectly working draft queue that nobody has time to approve.
• Write the Current Status Summary style guide: plain language, no jargon, no prediction, a window rather than a date, and no characterization of how well or badly the matter is going. Give the paralegals three worked examples per matter type.

Integrations

• Practice management or case management system, for Matter Phase changes and key dates, so the material-event interrupt can fire. If no API exists, use a manual flag - a paralegal ticking a box is better than an interrupt that never runs.
• Calendar sync for every attorney offering check-in slots, plus the review-block hold.
• Two-way email on a monitored firm domain with SPF, DKIM and DMARC configured.
• Client portal or secure document link, since restricted-contact clients get their detail behind a link rather than in the message body.
• Telephony for the client-care number, with call recording configured only if the firm has resolved the consent position for its jurisdiction.

Numbers and messaging compliance

• Provision a dedicated client-care number and complete A2P 10DLC brand and campaign registration before volume sending. Register it as account notifications and customer care for existing clients - not marketing - and keep marketing traffic off it entirely.
• Honor STOP, UNSUBSCRIBE, CANCEL, QUIT and variants immediately and permanently, applying sms-opt-out. Include opt-out language in the first message of each sequence. An opt-out removes a channel, not the firm's obligation to communicate, so make sure it triggers a channel fallback and a notification rather than silence.
• Quiet hours 8am to 8pm in the client's own time zone, holding rather than dropping queued messages, with no automated weekend or holiday sends.
• Capture consent to text at engagement and store the timestamp and source on the contact record. Treat consent as per-channel, not global.
• If the voice assistant records or transcribes calls, confirm the consent requirements in every state the firm's clients are in - some require all-party consent - and configure the disclosure at the start of the call accordingly.

Confidentiality, privilege and professional obligations

Read this section with the firm's compliance counsel before a single template goes live.

• Subject lines and SMS bodies are the exposure. A status message that names the court, the agency, the charge, the condition, the counterparty or the matter's subject can be read by a spouse, an employer, a lockscreen preview or anyone who picks up the phone. Keep all of it out: the subject is "Update on your matter with [Firm Name]" and the substance lives behind the portal link or in a body written as though a stranger will read it.
• The Confidentiality Restriction field is a compliance control, not a preference. Ask at onboarding how the client may be contacted, record the answer, and let the restricted-contact tag hard-block SMS and voicemail. In family, immigration and criminal matters this is the difference between a routine update and a serious problem for the client.
• Privilege. Think carefully about what substantive content is stored in the platform, who at the firm and at any vendor can see it, how long it is retained and what happens on termination. The Current Status Summary is deliberately a client-facing sentence rather than a case note for exactly this reason. Review the vendor's data processing terms, hosting location, retention and subprocessor list with counsel.
• Supervision of automated communication. The attorney approval gate is there because a lawyer remains responsible for communications sent in the firm's name, including ones a system assembles. Do not build a path that lets substantive content reach a client without a lawyer approving it, however convenient that would be.
• No legal advice, no new or altered attorney-client relationship. BO's scope is administrative. Test the guardrails adversarially before launch with the real questions - "do you think we will win", "should I accept this", "what happens if I miss this" - and review a sample of live conversations monthly.
• Timing language. Never let an automated message state or imply a deadline's legal consequence, and never let it give a date where the attorney approved a window. A client who relies on an automated estimate has a legitimate grievance.
• Review requests. Most jurisdictions regulate testimonials and what a firm may say or solicit about outcomes. Keep review requests to the service experience, send them only at close, and have counsel approve the wording and the eligibility rule.
• Record retention. Automated client communications are client communications. Confirm what has to be retained, for how long, and whether it must be preserved in the matter file rather than only in the platform.

None of the above is legal advice. Confirm the specifics - message content, consent, call recording, retention, supervision of automated client communication, solicitation and testimonial rules - with the firm's own compliance counsel and against the applicable rules of professional conduct in every jurisdiction where the firm practises. The attorney who will be responsible for these communications should read and approve every template before launch.

Scoping

Practice areas, the interval table, the practice management integration, voice AI and the number of languages all move the build. To scope it for a specific firm, book a call at bookings.appbo.io.