Check when intake reminders should stop
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
- No universal automation-history CSV. Present configuration cannot establish historical behavior.

STOP IF
- Missing historical rule version, relevant event/send timestamp, timezone or full reminder-channel inventory.

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: events.csv
firstLine: event_id,form_id,event_type,occurred_at,received_at
- file: forms.csv
firstLine: form_id,lead_alias,status,updated_at
- file: pending-reminders.csv
firstLine: reminder_id,form_id,scheduled_at,status
- file: race-tests.csv
firstLine: test_id,event_order,expected_behavior,verification_needed
- file: sequence-policy.txt
firstLine: G11: sequence-policy.txt
- file: suppression-review.csv
firstLine: reminder_id,form_id,observed_state,proposed_action,evidence_refs,unresolved_requirement
requiredNativeInputs: - name: Rules
kind: editorial_table
proposedDistinctTemplate: native-rules-template.csv
columns: - workflow_alias
- trigger
- stop_condition
- check_point
- version_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: Events
kind: editorial_table
proposedDistinctTemplate: native-events-template.csv
columns: - lead_alias
- workflow_alias
- event_type
- event_at
- source_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- 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.

Rules: native-rules-template.csv
Events: native-events-template.csv
Scope: native-scope-template.txt

STEP 1: Capture workflow rules without changing them
Tool: Lawmatics
Open: Automations > Workflows > existing workflow > Entry Conditions / Exit Conditions / action nodes; Automations > Reminders for separate reminder rules
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

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.

Expected output: Rule specification with workflow IDs/aliases and reminder coverage.
Use it next: Compare the rules against actual event histories in the next step.
Check: Current navigation differs from older articles using Marketing > Automations. Exit checks occur before the next action after a delay, not immediately upon the event.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://help.lawmatics.com/en/articles/10699800-lawmatics-navigation-experience
https://help.lawmatics.com/en/articles/10699927-exit-conditions

STEP 2: Capture actual event order
Tool: Lawmatics
Open: Workflow statistics icon > target status; matter > Activities timeline > relevant automation/form/signature events
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 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.

Expected output: Event ledger with visible states/timestamps and explicit missing entries.
Use it next: Pass only aliases, event labels/times and source refs, not message bodies.
Check: 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.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
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

STEP 3: Make the checked, minimized handoff
Tool: Excel / source-record reviewer
Open: Restricted original workbook > separate analysis workbook > Scope worksheet
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

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.

Expected output: Rules(workflow_alias,trigger,stop_condition,check_point,version_ref); Events(lead_alias,workflow_alias,event_type,event_at,source_ref); Scope(timezone,history_coverage)
Use it next: Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook.
Check: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/merge-queries-power-query
https://help.lawmatics.com/en/articles/10699927-exit-conditions

STEP 4: Ask AI to inspect the checked inputs
Tool: Excel Copilot, optional
Open: Analysis workbook > Copilot icon at lower right > Chat only
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

Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually.

PASTE THIS PROMPT
Use Rules, Events and Scope. For each lead/workflow, order evidenced events, identify whether the stop condition was still true before the next action, and flag possible send-after-stop exceptions with source refs. Treat Delayed as pending until the next action checkpoint. Distinguish standalone form/signature events from packet completion. Missing timestamps, version history or send records means inconclusive, not failed or passed. Do not stop, rerun, skip delays, edit or send.

Expected output: Proven exceptions, pending checkpoints and untestable cases.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: Check each alleged violation in timeline and actual send record; current status is not complete event history.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel

STEP 5: 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

Workflow owner reviews exceptions and approves any later sandbox test or configuration change. Save the audit and unresolved coverage.

Expected output: Reviewed stop-rule audit.
Use it next: Any urgent manual intervention or rule change requires authorized operator action in the source workflow.
Check: Never restart an automation as a diagnostic step; it may send communications.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://help.lawmatics.com/en/articles/10699922-automation-troubleshooting
https://help.lawmatics.com/en/articles/10699927-exit-conditions

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.