G11: native input mapping Check when intake reminders should stop 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 Rules -> native-rules-template.csv Exact columns: workflow_alias,trigger,stop_condition,check_point,version_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Events -> native-events-template.csv Exact columns: lead_alias,workflow_alias,event_type,event_at,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. 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 events.csv Original first line: event_id,form_id,event_type,occurred_at,received_at forms.csv Original first line: form_id,lead_alias,status,updated_at pending-reminders.csv Original first line: reminder_id,form_id,scheduled_at,status race-tests.csv Original first line: test_id,event_order,expected_behavior,verification_needed sequence-policy.txt Original first line: G11: sequence-policy.txt suppression-review.csv Original first line: reminder_id,form_id,observed_state,proposed_action,evidence_refs,unresolved_requirement sequence-policy.txt -> Rules and Scope: obtain actual workflow_alias, trigger, stop_condition, check_point and historical version_ref. Policy prose and current settings alone do not establish the version active at a past event. events.csv plus forms.csv -> Events only through a checked form/lead/workflow map. Map occurred_at to event_at only with its evidenced timezone and event meaning; retain received_at differences in Scope. Add source_ref and workflow_alias from actual records. pending-reminders.csv provides scheduled state only. Acquire actual executed/send-event evidence separately. race-tests.csv contains expected tests, not observed events. suppression-review.csv is an old output. Inventory built-in reminders and every uncovered channel in Scope. 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. No universal automation-history CSV. Present configuration cannot establish historical behavior. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Capture workflow rules without changing them Location: Automations > Workflows > existing workflow > Entry Conditions / Exit Conditions / action nodes; Automations > Reminders for separate reminder rules Copy the existing trigger, target type, delays, actions, exits and AND/OR relationships. Inventory built-in reminders separately. Preserve rule screenshots/version capture time; no edit or activation. Verification: Current navigation differs from older articles using Marketing > Automations. Exit checks occur before the next action after a delay, not immediately upon the event. https://help.lawmatics.com/en/articles/10699800-lawmatics-navigation-experience https://help.lawmatics.com/en/articles/10699927-exit-conditions Capture actual event order Location: Workflow statistics icon > target status; matter > Activities timeline > relevant automation/form/signature events For a bounded reviewed sample, manually capture stop-condition event time, next-action scheduled/executed time, observed workflow state and relevant message evidence. Use historical configuration when available; present rules do not prove past rules. Verification: No bulk event/log export was verified. Delayed is not a defect. Packet completion has its own event; forms/signatures inside E-Signature Packets do not trigger the standalone form/signature events. https://help.lawmatics.com/en/articles/10699922-automation-troubleshooting https://help.lawmatics.com/en/articles/10699938-force-exiting-from-an-automation https://help.lawmatics.com/en/articles/13117687-e-signature-packets Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Normalize timestamps only with evidenced timezone and keep originals. Scope lists every workflow/reminder inspected and all uncovered channels. 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. Verification: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. https://support.microsoft.com/en-us/excel/merge-queries-power-query https://help.lawmatics.com/en/articles/10699927-exit-conditions Do not proceed when - Missing historical rule version, relevant event/send timestamp, timezone or full reminder-channel inventory. 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.