plan-clio-grow-intake-followup: ApprovedSteps

Blank approved text input. Replace each placeholder only with approved source information.

Required content (contract wording):
Existing supported step types, exact form/email/appointment IDs, completion events, staff owner roles and approval evidence.

Required fields:
Existing supported step types: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
exact form/email/appointment IDs: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
completion events: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
staff owner roles: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
approval evidence: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]

Scope and evidence rules:
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.
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.

Do not proceed when:
- Missing approved communication assets, exact completion events or client-contact policy.

Execution status:
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.

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.