Find leads without an owner or next step
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
- The next-action field is firm-maintained, not a guaranteed native field. No bulk task export was verified.

STOP IF
- No complete active-scope list, no owner evidence, or no inspected task coverage.

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: leads-template.csv
firstLine: lead_alias,owner_alias,status,opted_out,next_action_id,next_action_due,last_activity_at
- file: response-rules-template.csv
firstLine: rule_id,stage,allowed_working_hours,response_interval,escalation_owner
- file: tasks-template.csv
firstLine: task_id,lead_alias,owner_alias,status,due_datetime,completed_at
requiredNativeInputs: - name: Leads
kind: editorial_table
proposedDistinctTemplate: native-leads-template.csv
columns: - lead_alias
- status
- stage
- owner_present
- next_action_present
- source_row_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: TasksChecked
kind: editorial_table
proposedDistinctTemplate: native-taskschecked-template.csv
columns: - lead_alias
- open_task_present
- due_at
- coverage
- 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.

Leads: native-leads-template.csv
TasksChecked: native-taskschecked-template.csv
Scope: native-scope-template.txt

STEP 1: Ask the in-app assistant for the source report
Tool: Lawmatics Merlin Copilot, optional
Open: Left navigation > Merlin > Copilot
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: source_application_ai

With an already approved seat and firm-wide reporting access, paste the prompt. Open the returned report/export or inspect its preview; if unavailable or incomplete, use the native report route below. Do not accept mutation previews, routines or feature-request sending.

PASTE THIS PROMPT
For the approved intake scope [SCOPE] as of [AS OF/TIMEZONE], return a read-only matter report with Status, Stage, Owned by, Created At and our exact maintained next-action field [FIELD NAME]. Show blank owners and blank next-action values separately. Include source record references if available. If that field or a complete task list is unavailable, say so; do not infer next steps from narrative. Do not update records, assign work, build automation, schedule a routine or send anything.

Expected output: A report/one-time export or explicit unsupported/missing-field result; exact custom query coverage is not promised.
Use it next: Check actual fields and records, then use the native CSV path where a report is returned. Prose alone does not certify completeness.
Check: Existing firm-approved AI entitlement and data handling approval are prerequisites. Lawmatics Merlin reporting can operate at firm scope; do not use it across ethical walls or assume matter-level permissions protect aggregate/search output. The detailed Copilot article and September 2026 release notes describe availability; the suite overview still contains a stale Coming Soon heading. Verify actual account access, with no purchase or permission changes.
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/16139872-merlin-copilot
https://help.lawmatics.com/en/articles/15890617-merlin-ai-suite-overview
https://help.lawmatics.com/en/articles/15788585-recent-updates-q3-2026

STEP 2: Get the actual Lawmatics rows
Tool: Lawmatics
Open: Reports > Custom Reports > existing matter report > eye/view icon > Export
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

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.

Expected output: Native matter/contact-field rows; no promise of task history, audit history, destination IDs or custom fields that the firm never recorded.
Use it next: Open in restricted Excel; compare rows to matter records before preparing aliases.
Check: 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.
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/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

STEP 3: Check tasks without inventing a task export
Tool: Lawmatics
Open: Matters > selected matter > Tasks; or main Tasks dashboard
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 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.

Expected output: A bounded staff-checked task capture with coverage per matter.
Use it next: Pass only task existence, assigned-role alias and due date to the analysis workbook.
Check: A blank next-action field does not prove there is no task; incomplete access or omitted tasks means unknown.
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/10699825-matter-profile-overview
https://help.lawmatics.com/en/articles/10738648-completing-and-editing-tasks

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

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.

Expected output: Leads(lead_alias,status,stage,owner_present,next_action_present,source_row_ref); TasksChecked(lead_alias,open_task_present,due_at,coverage,source_ref)
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/10699825-matter-profile-overview

STEP 5: 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 Leads, TasksChecked and Scope only. List active lead_alias values with owner_present=false, then those lacking both an evidenced next action and an open task. Distinguish blank field, no task after complete inspection, and unknown coverage. Return lead_alias,exception,evidence_rows,coverage,proposed_internal_check,reviewer_status=pending. Never infer urgency from case facts, legal merit, owner identity or silence; do not create tasks or messages.

Expected output: Source-linked owner/next-step exceptions.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: Inspect each flagged matter; report excluded/unknown rows and the denominator.
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 6: 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

Intake manager verifies each exception in the matter and decides owner/next action. Save the reviewed queue; any task creation is a separately authorized human action.

Expected output: Approved internal follow-up queue or unresolved coverage list.
Use it next: Human returns to the cited matter/Tasks record if corrections are approved.
Check: No autonomous lead ranking, client communication or legal judgment.
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/10738648-completing-and-editing-tasks

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.