Draft client updates from approved milestones

Practice relevance

Cross-practice idea · Useful supporting administrative method; no claim of practice-specific legal instructions.

Scope: Clio client portal and prepared milestones; draft updates only, no automatic sending or court-status verification.

The problem

Prepare a factual status draft with a source reference for each sentence.

Why it matters: Clients may seek updates even when a matter is waiting on someone else. A draft based on approved, shareable milestones can explain what is known without inventing progress, dates, or promises.

Sources & evidence

Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.

What’s been verified

Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.

What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.

Pain evidence: What are Client Engagement Portals/Platforms? ↗What are Client Engagement Portals/Platforms?, 2024-01-10 to 2024-01-11, older. OP describes frustration with client communication; a practitioner says weekly updates require substantial cross-firm input. Admin help discussion, 2026-09-06, provides newer corroboration about routine questions and follow-ups consuming the day.
Pain evidence: Admin help discussion ↗Additional self-reported public account; no independent identity or outcome verification.
Method: Clio for Clients setup ↗Clio for Clients setup documents portal messages and document sharing. It does not establish automatic AI status generation.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: Scheduled review or approved milestone

synthesize client-shareable facts
Keep source references and report unknowns instead of filling gaps.
The responsible reviewer checks the report before any separately approved action.

Limits and review

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

Who reviews it: Responsible lawyer approves legal accuracy, privilege boundaries and recipient. Test stale milestones and an internal-only strategy row.

What you need

Adobe Acrobat AI Assistant · prepared inputs

Clio Manage access to the specific matter; AI Launchpad entitlement for the AI retrieval route.
Firm-approved Acrobat AI/PDF Spaces access for the cited drafting step, or prepare the short draft manually from the reviewed ledger. Adobe cloud processing must be approved for any uploaded content.
Responsible lawyer to approve what is client-shareable, exact client recipient, and any dates or next steps.
Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

How to use

Documentation-verified native AI retrieval and portal route; draft adaptation not tested

Before you start

The Clio summary can draw from internal information. It does not decide privilege, confidentiality, client shareability, or completeness.
No native milestones.csv export is documented. That file is an editorial review ledger filled after source checking.

Check access and setup

Firm AI access, matter permissions, Adobe approval and client-portal configuration were not tested.
The exact account UI may vary by region/rollout; no automatic Clio-to-Acrobat transfer is claimed.

Retrieve the matter context
Clio Manage AI · Diamond icon > AI Launchpad > Ask a question > Catch up on a matter
Enter the exact matter name and prompt. If AI is not enabled, open the matter and review its recorded notes, tasks and communications directly; manually capture only the relevant facts.
Clio Manage AI promptSummarize [MATTER NAME] for [START DATE] through [END DATE]. List recorded completed work, recorded next steps, explicit client requests, and any stated timing. Keep these categories separate. If something is not recorded, say unknown. Identify the underlying record for each point where available. Do not send a message or change any matter data.
Expected output
Matter-specific AI summary grounded in accessible communications, activities, events, tasks, notes, bills and documents; completeness is not guaranteed.
Next step
Check each candidate milestone in its actual source record before using it.
Check before continuing
Confirm the correct matter and period; absence from a summary is not proof of no activity.
Step documentation 1 ↗
Build the approved client-shareable ledger
Excel or text editor; original Clio records · Supplied milestones.csv template
The responsible reviewer checks source records, assigns M001-style IDs and a matter alias, copies exact dates/status/next steps/client actions, and sets client_shareable only after review. Put approved timing wording in approved_timing_text. Exclude internal strategy and unnecessary sensitive details. Keep record pointers in an internal mapping note.
Expected output
milestone_id,matter_alias,date_recorded,status_text,next_step,explicit_client_action,client_shareable,approved_timing_text. These are manually reviewed columns, not native Clio fields.
Next step
Use only the approved, deidentified rows in the drafting workspace.
Check before continuing
Do not let AI set client_shareable. Do not invent a next step, action or delivery date. If no current evidence exists, retain an explicit unknown.
Step documentation 1 ↗
Draft from the approved ledger
Adobe Acrobat AI Assistant · Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space; AI Assistant message field
Paste the labeled approved ledger as text, or add an approved TXT/PDF version. Enter the prompt in the space chat. This step does not connect Acrobat to Clio.
Adobe Acrobat AI Assistant promptUse only the supplied milestone rows marked client_shareable=true. Draft a short plain-language update with placeholders for client and matter identity: what happened, what happens next, and any explicitly recorded client action. Use approved_timing_text verbatim when supplied. Do not promise dates or outcomes, invent progress, expose internal rows, or send anything. Return the draft and a separate appendix mapping each sentence to milestone_id. If the approved facts record no change, say that; if they do not establish whether there was a change, say the available update is incomplete.
Expected output
Plain-language draft plus a sentence-to-milestone reviewer appendix.
Next step
Use the response Copy control to place the draft and appendix in an internal review document.
Check before continuing
Click the source numbers and compare every draft claim to the approved rows; remove unsupported wording.
Step documentation 1 ↗Step documentation 2 ↗
Review and send only after approval
Final human review
Clio Manage / Clio for Clients · Selected matter > Communications > Go to client portal > Messages
Lawyer approves content and recipient. A human pastes only the approved client-facing draft, excluding the reviewer appendix, into the existing portal conversation. Inspect recipient and matter before selecting Send.
Expected output
One approved status message in the correct portal, only if the reviewer elects to send.
Next step
Save the approved copy and source ledger internally.
Check before continuing
Check notification privacy: current Clio setup docs say new portal-message emails include the full message by default. Have an authorized administrator review the setting before sensitive content; do not assume portal text stays out of email.
Step documentation 1 ↗Step documentation 2 ↗

What you’ll get

Approved assistant workspace; draft text and reviewer citation appendix. A human copies approved text into the firm’s existing secure client portal.

Inputs and a sample test Synthetic example · not a measured result

Input files

milestones.csv: milestone_id, matter_alias, date_recorded, status_text, next_step, explicit_client_action, client_shareable, approved_timing_text.

Synthetic example

M1 has one shareable milestone “documents received” and one internal-only strategy row → draft mentions receipt only; source appendix cites the receipt row.

Expected output

M1 has one shareable milestone “documents received” and one internal-only strategy row → draft mentions receipt only; source appendix cites the receipt row.

Test a failure

Responsible lawyer approves legal accuracy, privilege boundaries and recipient. Test stale milestones and an internal-only strategy row.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 6 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
Setup and review checklist Required inputs, file use, review steps and limits
Milestones blank CSV Blank input headers for milestones.csv
Milestones synthetic example Synthetic test records for milestones.csv
Synthetic example expected results Compare a pilot result with the planted exceptions

Optional full review prompt for prepared inputs

Prepared-input review prompt with Adobe Acrobat AI Assistant · prepared inputs

Draft a plain-language status update from only the rows marked client-shareable. Use placeholders for client/matter identity. Explain what happened, what happens next and any client action explicitly supplied. Cite each draft sentence to row IDs in a reviewer appendix. Do not promise dates, outcomes or progress not recorded. If there is no change, say so. Do not send.

INPUTS
milestones.csv: milestone_id, matter_alias, date_recorded, status_text, next_step, explicit_client_action, client_shareable, approved_timing_text.

OUTPUT
Approved assistant workspace; draft text and reviewer citation appendix. A human copies approved text into the firm’s existing secure client portal.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read pain evidence