plan-clio-grow-intake-followup: native input mapping Put intake follow-up into a clear sequence Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs ApprovedSteps -> native-approvedsteps-template.txt Required content: Existing supported step types, exact form/email/appointment IDs, completion events, staff owner roles and approval evidence. Complete each required field from approved source evidence. CurrentWorkflowEvidence -> native-currentworkflowevidence-template.txt Required content: Observed workflow IDs, states, timestamps, errors and source references. Current template rules and historical events remain separate. Complete each required field from approved source evidence. Scope -> native-scope-template.txt Required content: 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. Complete each required field from approved source evidence. Old files and reviewed mapping input-preparation.txt Original first line: 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. intake-plan-inputs-template.txt Original first line: Approved stages: [required] intake-plan-inputs-template.txt and input-preparation.txt -> ApprovedSteps and Scope: transfer only actually approved supported step types, exact asset IDs, completion events, owner roles and approvals. An available template name is not an exact verified asset ID or a completion event. CurrentWorkflowEvidence requires separately inspected workflow IDs, states, timestamps, errors and source references. Keep existing template rules and historical execution evidence separate. The old planning template supplies no execution test result. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. 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. Workflow design is a proposed spec. Current reports cannot replace timestamped workflow evidence. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Read actual Grow workflow states and available assets Location: Settings > Automated workflows; Matters > selected matter > Intake process > Automated workflows > expand workflow 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. Verification: 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. https://help.clio.com/hc/en-us/articles/17770743592219-Clio-Grow-Automated-Workflows Export intake context only if needed Location: Reports > Matter revenue report > filters > View report > Columns > Download CSV 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. Verification: Grow/Manage refresh timing differs; no Grow arbitrary data-query chat is claimed. The support AI cannot access matters or billing. https://help.clio.com/hc/en-us/articles/29739406189339-Clio-Grow-Reports https://help.clio.com/hc/en-us/articles/40283218733467-AI-Support-Agent Do not proceed when - Missing approved communication assets, exact completion events or client-contact policy. Scope template requirements 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. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documentation-checked component path; proposed workflow, not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.