Put intake follow-up into a clear sequence Get the source data and prepare the review Documentation-checked component path; proposed workflow, not tested WHAT WAS CHECKED Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution. BEFORE YOU START - Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. - Responsible lawyer/operations reviewer approves scope, definitions and any later action. - AI optional; use only approved minimized data and retain originals separately. DATA ACQUISITION LIMITS - Workflow design is a proposed spec. Current reports cannot replace timestamped workflow evidence. STOP IF - Missing approved communication assets, exact completion events or client-contact policy. KEEP THE ANALYSIS COPY SEPARATE Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. INPUT FORMAT LIMIT All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data. NATIVE REVIEW INPUTS version: 1 status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible compatibleWithoutMapping: False existingKitFilesInspected: - file: input-preparation.txt firstLine: Collect the approved intake-stage list, exact names of available forms/email/appointment templates, role list and communication policy. Identify which actions are documented in the account and region. Missing capabilities must say VERIFY. The result is a review plan; no Clio configuration is included. - file: intake-plan-inputs-template.txt firstLine: Approved stages: [required] requiredNativeInputs: - name: ApprovedSteps kind: approved_text_section proposedDistinctTemplate: native-approvedsteps-template.txt requiredContent: Existing supported step types, exact form/email/appointment IDs, completion events, staff owner roles and approval evidence. - name: CurrentWorkflowEvidence kind: approved_text_section proposedDistinctTemplate: native-currentworkflowevidence-template.txt requiredContent: Observed workflow IDs, states, timestamps, errors and source references. Current template rules and historical events remain separate. - name: Scope kind: approved_text_section proposedDistinctTemplate: native-scope-template.txt requiredContent: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. templateFilesCreatedByThisTask: False requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence. OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. ApprovedSteps: native-approvedsteps-template.txt CurrentWorkflowEvidence: native-currentworkflowevidence-template.txt Scope: native-scope-template.txt STEP 1: Read actual Grow workflow states and available assets Tool: Clio Grow Open: Settings > Automated workflows; Matters > selected matter > Intake process > Automated workflows > expand workflow Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Capture existing template steps and approved form/email/appointment/task choices. In a bounded sample, manually record in-progress/completed timestamps and errors from the expanded workflow. Do not apply a workflow or alter its state. Expected output: Native workflow-state capture plus approved step inventory. Use it next: Prepare an ApprovedSteps text inventory of existing supported step types and actual form/template/appointment IDs, a CurrentWorkflowEvidence ledger of observed state/timestamps/source refs, and a full Scope note. Include all three labeled sections in the minimized packet passed to Acrobat; missing assets or history remain blocked. Check: Applying a published workflow starts its first step. Assign task waits for completion; form and appointment steps advance on their documented event. No bulk workflow log export is claimed. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.clio.com/hc/en-us/articles/17770743592219-Clio-Grow-Automated-Workflows STEP 2: Export intake context only if needed Tool: Clio Grow Open: Reports > Matter revenue report > filters > View report > Columns > Download CSV Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step For current intake/source context, use the actual report and preserve its selected columns/date scope. Do not enable shared contacts just to run it; if not already configured, the export route is blocked and manual matter inspection remains available. Expected output: Native current intake rows; not the workflow event log. Use it next: Only administrative columns needed for the sequence enter the analysis packet. Check: Grow/Manage refresh timing differs; no Grow arbitrary data-query chat is claimed. The support AI cannot access matters or billing. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.clio.com/hc/en-us/articles/29739406189339-Clio-Grow-Reports https://help.clio.com/hc/en-us/articles/40283218733467-AI-Support-Agent STEP 3: Draft from the approved source packet Tool: Acrobat PDF Spaces / AI Assistant, optional Open: Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: downstream_application_ai Paste only the approved nonconfidential packet, source IDs and full Scope note. Paste the exact prompt into the Space chat. Do not upload raw client records; this is a downstream drafting assistant, not an AI in the source application. PASTE THIS PROMPT Using only ApprovedSteps, CurrentWorkflowEvidence and Scope, draft a Clio Grow intake sequence. For each step specify its actual supported type, input template/form/appointment ID, completion event, owner and human gate. Use Assign task for checks requiring staff completion. Give a cancellation/exception-review plan and mark unsupported delay/stop logic as unresolved; do not invent an always-on AI query or automatic legal/conflict decision. Return a build specification and synthetic acceptance cases, not a live automation. Expected output: A supported-step sequence with human gates and exception tests. Use it next: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs. Check: No form/email/appointment template or policy can be invented to complete the chain. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source 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 STEP 4: Human review and final action Tool: Responsible firm reviewer Open: Internal Review worksheet / review document Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included. AI role: not_an_ai_step Administrator reviews the spec and client-contact permissions. A later authorized build goes to Settings > Automated workflows > New template > Create my own, choosing supported items, then Save draft & exit. Publishing and applying require separate approval. Expected output: Approved draft build brief; no Grow account change. Use it next: Human builder gets the exact step/input map and validation checklist. Check: Published workflows cannot simply be edited in place; cancel/recreate behavior must be considered before changes. Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations. Source documentation: https://help.clio.com/hc/en-us/articles/17770743592219-Clio-Grow-Automated-Workflows ACCOUNT AND SOURCE CHECKS STILL NEEDED - The live account, entitlement, exact headers, records and field coverage have not been observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.