# Draft reminders for missing client documents Canonical page: https://agents.paretoid.com/workflows/draft-reminders-for-missing-client-documents/ Category: Client Service Practice relevance: cross-practice. Useful supporting administrative method; no claim of practice-specific legal instructions. Jurisdiction/provider scope: Clio Manage records and an Excel/Copilot draft queue. Staff check the missing-document list and approve any separate send. Compare a document checklist with receipt records before drafting one reminder. Status: Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified. Verification: The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result. ## The problem Compare a document checklist with receipt records before drafting one reminder. Why it matters: Missing documents can leave staff preparing a matter with an incomplete file. Checking receipt records before drafting a reminder also avoids asking clients for items they already supplied under another name. ## Sources and evidence - pain: [Pain evidence: Slack clients](https://www.reddit.com/r/paralegal/comments/1ka1ny8) Slack clients, 2025-04-28, older. A family-law paralegal describes unresponsive clients and missing documents before final hearings. This is established-client collection, separate from intake. - method: [Method: Clio for Clients actions](https://help.clio.com/hc/en-au/articles/9156698397467-Clio-for-Clients-Law-Firm-Actions) Clio for Clients actions documents messages, document uploads and notifications. Important: adding documents to a previously shared folder automatically shares them with that client. Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. ## Suggested approach Start when: Staff-set document request review date 1. compare approved checklist with received-file metadata 2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes. 3. The responsible staff member checks the draft against the source records and approves any separate action. ## What you need - Actual lawyer-approved client document checklist and actual receipt records for a bounded matter. - Current approved secure-upload instructions and explicit requested due dates; no inferred deadline. - Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent. - Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab. - 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-checked proposed route; source collection and human approval required - A document filename is not evidence that the requested item was supplied or sufficient. Receipt_status is a staff judgment after opening the actual receipt. - No universal client-checklist export or AI query is verified. This route explicitly reads maintained requests and receipts. Access and setup: - Actual account access, plan and source-data completeness have not been tested. ### 1. Inspect the real requests and receipts Tool: Clio Manage and local document viewer Location: Matters > selected matter > Tasks / Communications / Documents Read the actual approved checklist or request in Tasks/Communications. In Documents, inspect the actual received item and receipt history under firm procedures. If the source records are outside Clio, open those actual records locally; this route does not claim an export from that unidentified system. Expected output: An explicit requested-item list and a separately verified receipt log. Next step: Keep source references and identities restricted; prepare aliases and shareable descriptions. Check before continuing: A portal upload, message acknowledgment or similar filename does not itself prove fulfillment. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://help.clio.com/hc/en-us/articles/9285920226075-Get-Started-With-Matters ### 2. Map the observed records to the starter input Tool: Excel and authorized staff Location: Separate analysis workbook > Home > Format as Table Create requested-items.csv with a stable request_item_id,matter_alias,approved_plain_description,supplied_due_date and secure_upload_instruction copied from the approved request. Create received-items.csv with receipt_id, an explicitly matched request_item_id_if_known,matter_alias,deidentified_filename and staff-verified receipt_status. Keep ambiguous matches unresolved. Put the approved reminder policy/cutoff in Scope. Create named tables for RequestedItems and ReceivedItems. Put the policy and review scope in visible worksheets or paste them into the next prompt. Expected output: RequestedItems and ReceivedItems, with actual manually reviewed source evidence. Next step: Check the mapping against each original source before using AI. Check before continuing: Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ### 3. Review the bounded evidence with Copilot Tool: Excel Copilot, optional Location: Approved analysis workbook > Copilot icon at lower right > Chat only Use Chat only and submit the prompt. Without Copilot: compare explicit item IDs and draft from approved descriptions after checking receipts. Prompt: ```text Compare RequestedItems and ReceivedItems by explicit request_item_id only, within Scope. List missing, partial, unclear and unmatched receipts with cited row IDs. Draft a brief client reminder using only approved_plain_description, supplied_due_date and secure_upload_instruction. Include only staff-confirmed outstanding items. Use a placeholder when the due date or upload instruction is absent. Do not infer legal requirements, sufficiency, deadlines, identity or attachment contents, and do not send. ``` Expected output: Missing-item review list and a lawyer-reviewable reminder draft. Next step: Copy the draft exception list to the reviewer; retain row references. Check before continuing: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel ### 4. Approve the review result Tool: Responsible staff reviewer Location: Reviewed local worksheet Staff reopen the actual receipts, clear ambiguous matches and check the upload destination. The lawyer approves the exact outstanding items and wording before any client communication. Expected output: Approved reminder draft or a hold for missing facts. Next step: Any external message, source change, payment or deletion requires its own authorized process. Check before continuing: Do not transmit a reminder based solely on filename comparison; no attachment or client identity goes to AI without specific firm approval. Execution status: Official documentation checked 2026-10-15; account and workflow not personally tested Step documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ## What you will get missing-items.csv: request_item_id, receipt_ids, status, evidence_rows, approved_description, supplied_due_date; separate placeholder reminder. No live changes. ## Human review and limits Staff confirm material was not received under a different name; lawyer approves scope and urgency. Never place internal files in a client-shared folder. Test alias filenames and already-received items. 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: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved. ## Original prepared-input schema requested-items.csv: request_item_id, matter_alias, approved_plain_description, supplied_due_date, secure_upload_instruction. received-items.csv: receipt_id, request_item_id_if_known, matter_alias, deidentified_filename, receipt_status. Synthetic example input: ```text DOC1: matching request ID under a different file name DOC2: no receipt DOC3: possible receipt with no matching ID ``` Expected synthetic output: ```text DOC1: received, no reminder DOC2: draft uses approved description and date DOC3: uncertain, ask staff before chasing ``` Failure check: Staff confirm material was not received under a different name; lawyer approves scope and urgency. Never place internal files in a client-shared folder. Test alias filenames and already-received items. ## 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/a10-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/a10/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/a10/README.txt) — Required inputs, file use, review steps and limits - [Requested items blank CSV](https://agents.paretoid.com/assets/starter-kits/a10/requested-items-template.csv) — Blank input headers for requested-items.csv - [Requested items synthetic example](https://agents.paretoid.com/assets/starter-kits/a10/requested-items-example.csv) — Synthetic test records for requested-items.csv - [Received items blank CSV](https://agents.paretoid.com/assets/starter-kits/a10/received-items-template.csv) — Blank input headers for received-items.csv - [Received items synthetic example](https://agents.paretoid.com/assets/starter-kits/a10/received-items-example.csv) — Synthetic test records for received-items.csv - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a10/expected-results.txt) — Compare a pilot result with the planted exceptions ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Reconcile this approved document checklist against receipt metadata. List missing or ambiguous items without judging the content's legal adequacy. Draft a short reminder using placeholders and the supplied secure-upload instructions. Explain each requested item only from the approved descriptions. Do not request extra records, threaten withdrawal, change dates or send. INPUTS requested-items.csv: request_item_id, matter_alias, approved_plain_description, supplied_due_date, secure_upload_instruction. received-items.csv: receipt_id, request_item_id_if_known, matter_alias, deidentified_filename, receipt_status. OUTPUT missing-items.csv: request_item_id, receipt_ids, status, evidence_rows, approved_description, supplied_due_date; separate placeholder reminder Use only the supplied synthetic or firm-approved inputs. Cite source row or page IDs for each finding. Keep unknowns unresolved. Return a draft for the responsible staff reviewer. Do not send messages, connect accounts, change records, move money, or make legal decisions. Keep source files unchanged. If an input or permission is missing, list what is needed and stop that check. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.