# Draft client updates from approved milestones Canonical page: https://agents.paretoid.com/workflows/draft-client-updates-from-approved-milestones/ Category: Client Service Practice relevance: cross-practice. Useful supporting administrative method; no claim of practice-specific legal instructions. Jurisdiction/provider scope: Clio client portal and prepared milestones; draft updates only, no automatic sending or court-status verification. Prepare a factual status draft with a source reference for each sentence. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: 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. ## 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 and evidence - pain: [Pain evidence: What are Client Engagement Portals/Platforms?](https://www.reddit.com/r/LawFirm/comments/193g9ag/what_are_client_engagement_portalsplatforms/) 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: [Pain evidence: Admin help discussion](https://www.reddit.com/r/LawFirm/comments/1w8tcez/when_did_you_know_it_was_time_to_get_help_with/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: Clio for Clients setup](https://help.clio.com/hc/en-us/articles/9043484357147-Clio-for-Clients-Law-Firm-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. ## Suggested approach Start when: Scheduled review or approved milestone 1. synthesize client-shareable facts 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - 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 - 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. 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. ### 1. Retrieve the matter context Tool: Clio Manage AI Location: 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. Prompt: ```text Summarize [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. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/29658072890523-Clio-Duo-Ask-About-Matters-and-Contacts ### 2. Build the approved client-shareable ledger Tool: Excel or text editor; original Clio records Location: 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. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/29658072890523-Clio-Duo-Ask-About-Matters-and-Contacts ### 3. Draft from the approved ledger Tool: Adobe Acrobat AI Assistant Location: 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. Prompt: ```text Use 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. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 4. Review and send only after approval Tool: Clio Manage / Clio for Clients Location: 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. Execution status: Official documentation checked 2026-10-15; product account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/9156698397467-Clio-for-Clients-Law-Firm-Actions https://help.clio.com/hc/en-us/articles/9043484357147-Set-Up-Clio-for-Clients ## What you will get Approved assistant workspace; draft text and reviewer citation appendix. A human copies approved text into the firm’s existing secure client portal. ## Human review and limits Responsible lawyer approves legal accuracy, privilege boundaries and recipient. Test stale milestones and an internal-only strategy row. 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. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema milestones.csv: milestone_id, matter_alias, date_recorded, status_text, next_step, explicit_client_action, client_shareable, approved_timing_text. Synthetic example input: ```text M1 has one shareable milestone “documents received” and one internal-only strategy row → draft mentions receipt only; source appendix cites the receipt row. ``` Expected synthetic output: ```text M1 has one shareable milestone “documents received” and one internal-only strategy row → draft mentions receipt only; source appendix cites the receipt row. ``` Failure check: Responsible lawyer approves legal accuracy, privilege boundaries and recipient. Test stale milestones and an internal-only strategy row. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/a09-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/a09/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a09/README.txt) — Required inputs, file use, review steps and limits - [Milestones blank CSV](https://agents.paretoid.com/assets/starter-kits/a09/milestones-template.csv) — Blank input headers for milestones.csv - [Milestones synthetic example](https://agents.paretoid.com/assets/starter-kits/a09/milestones-example.csv) — Synthetic test records for milestones.csv - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a09/expected-results.txt) — Compare a pilot result with the planted exceptions ## Optional original prepared-input prompt Destination: Adobe Acrobat AI Assistant · prepared inputs This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text 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 Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.