Check original brand and marketing source
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 brand field or export of full old/new field history was verified. CallRail first-touch data depends on tracking actually installed.

STOP IF
- Missing original capture, historical mapping, timestamps or unambiguous cross-tool identity.

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: first-touch-policy.txt
firstLine: G08: first-touch-policy.txt
- file: leads.csv
firstLine: lead_alias,brand_id,original_source,later_source,tracking_number_token,utm_source,utm_campaign
- file: source-history.csv
firstLine: lead_alias,field,old_value,new_value,changed_at,source_ref
- file: source-review.csv
firstLine: lead_alias,rule_ids,brand_conflict,original_source_evidence,later_touch_evidence,proposed_rule_test
- file: tracking-rules.csv
firstLine: rule_id,brand_id,number_token,utm_match,priority
requiredNativeInputs: - name: Attribution
kind: editorial_table
proposedDistinctTemplate: native-attribution-template.csv
columns: - lead_alias
- current_brand
- current_source
- current_campaign
- current_capture_at
- original_brand
- original_source
- original_capture_at
- change_evidence_ref
- coverage
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: SourceHistory
kind: editorial_table
proposedDistinctTemplate: native-sourcehistory-template.csv
columns: - lead_alias
- field
- old_value
- new_value
- changed_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.

Attribution: native-attribution-template.csv
SourceHistory: native-sourcehistory-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 [SCOPE], return existing current Source, Campaign and Created At values and our recorded original-brand/original-source fields [EXACT FIELDS] if present. Identify unavailable fields. Do not claim these current values are immutable first-touch history. Return record references or a report; do not change attribution.

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 Source, Campaign, Created At and exact existing original-brand/original-source fields. 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: Capture the source evidence and present mapping
Tool: CallRail and Lawmatics
Open: CallRail Analytics > Activity > Call log > Timeline; Lawmatics phone icon > Assigned / Unassigned / All Callers; Settings > Marketing Sources
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

Manually capture the relevant first-touch/call source evidence and the existing mapping values. Inspect source and campaign settings without saving. Separately collect retained historical form/call captures or logged field-change evidence showing original value, later value and timestamp.

Expected output: Current mapping plus an evidence ledger; a current snapshot is not history.
Use it next: Assign evidence IDs; copy only brand/source labels and timestamps into the analysis workbook.
Check: Lawmatics CallRail matching uses phone numbers; later calls do not overwrite existing source/campaign. Settings changes affect subsequent calls. Current rules cannot prove past configuration.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking
https://help.lawmatics.com/en/articles/10699987-callrail-integration

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

Keep current_field, original_capture and change_evidence separate. Do not reconstruct first brand from the latest landing page. 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: Attribution(lead_alias,current_brand,current_source,current_campaign,current_capture_at,original_brand,original_source,original_capture_at,change_evidence_ref,coverage); SourceHistory(lead_alias,field,old_value,new_value,changed_at,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 Attribution, SourceHistory and Scope. Compare current source/brand against recorded original captures only. For each mismatch cite the original and later evidence and timestamp. Without old/new/timestamp evidence, say original attribution not verifiable. Separate wrong-current-value, legitimate later-touch difference and unknown history. Do not overwrite fields, infer causal marketing credit or invent a brand.

Expected output: Evidence-bounded discrepancy list.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: No current field or present mapping alone establishes original source.
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

Marketing and intake reviewers validate each discrepancy against preserved original evidence. Save a factual correction proposal.

Expected output: Reviewed attribution proposal and unknown-history list.
Use it next: Any correction goes to the exact original CRM record after separate approval.
Check: Never reattribute historical leads merely to improve campaign results.
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/10699987-callrail-integration

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.