G06: native input mapping
Find leads without an owner or next step

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
Leads -> native-leads-template.csv
Exact columns: lead_alias,status,stage,owner_present,next_action_present,source_row_ref
Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.

TasksChecked -> native-taskschecked-template.csv
Exact columns: lead_alias,open_task_present,due_at,coverage,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
leads-template.csv
Original first line: lead_alias,owner_alias,status,opted_out,next_action_id,next_action_due,last_activity_at

response-rules-template.csv
Original first line: rule_id,stage,allowed_working_hours,response_interval,escalation_owner

tasks-template.csv
Original first line: task_id,lead_alias,owner_alias,status,due_datetime,completed_at

leads-template.csv -> Leads: retain lead_alias and status only after source verification. owner_alias and next_action_id may support owner_present and next_action_present only after checking the actual record; a blank does not establish absence. Acquire stage and source_row_ref separately. Keep opted_out and any response-policy restrictions in Scope where relevant.
tasks-template.csv -> TasksChecked: retain the checked lead_alias; inspect task status, due_datetime and completed_at to establish open_task_present and due_at. Record inspection coverage and source_ref. An old task list is not a verified complete native task export.
response-rules-template.csv -> Scope: carry the approved stage, working-hours, response-interval and escalation rules with their version. It supplies policy, not observed lead/task facts.

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.
The next-action field is firm-maintained, not a guaranteed native field. No bulk task export was verified.
The live account, entitlement, exact headers, records and field coverage have not been observed.

Recipe acquisition / manual mapping instructions
Get the actual Lawmatics rows
Location: Reports > Custom Reports > existing matter report > eye/view icon > Export
Use an existing authorized report, or have its owner prepare a targeted report with Status, Stage, Owned by, Created At and the exact firm-maintained next-action field if it exists. Record the agreed review period and matter scope, including which date field sets the range. Export the viewed report to CSV; large exports may arrive by email. Preserve headers and file unchanged. A report creation/save is a separate account write, not performed here. If no suitable report exists, use the documented Settings > Export > Export Matters route only in restricted storage, then minimize locally.
Verification: A matter report may contain contact and matter fields. A contacts-only export omits matter fields. Date-created and date-converted scopes differ; exported grouping is not preserved.
https://help.lawmatics.com/en/articles/10699961-exporting-custom-reports
https://help.lawmatics.com/en/articles/10699766-exporting-data
https://help.lawmatics.com/en/articles/10699953-custom-reporting-using-filters
https://help.lawmatics.com/en/articles/10699957-custom-reporting-columns-grouping

Check tasks without inventing a task export
Location: Matters > selected matter > Tasks; or main Tasks dashboard
For each nominated row, inspect actual tasks and status/due-date/assignee filters. Open a task for its activity history if needed. Manually record the next open task and due date with a record pointer; no native bulk task CSV is claimed.
Verification: A blank next-action field does not prove there is no task; incomplete access or omitted tasks means unknown.
https://help.lawmatics.com/en/articles/10699825-matter-profile-overview
https://help.lawmatics.com/en/articles/10738648-completing-and-editing-tasks

Make the checked, minimized handoff
Location: Restricted original workbook > separate analysis workbook > Scope worksheet
Create Leads from the export and TasksChecked from explicit per-matter task inspection. Staff assign lead_alias and source_row_ref. Define active statuses and overdue rules in Scope. 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/10699825-matter-profile-overview


Do not proceed when
- No complete active-scope list, no owner evidence, or no inspected task coverage.

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.
