G21: native input mapping
Keep outbound referrals from disappearing after handoff

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
Referrals -> native-referrals-template.csv
Exact columns: referral_alias,destination_alias,sent_at,acknowledged_at,owner_alias,next_check_at,sharing_scope_verified,evidence_refs
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
followup-policy.txt
Original first line: G21: followup-policy.txt

recipient-verification.csv
Original first line: recipient_alias,verified_channel,verification_ref,verified_at

referral-followup.csv
Original first line: referral_id,acknowledgment_status,followup_due,missing_permission_or_recipient_evidence,owner_alias,proposed_next_step

referrals.csv
Original first line: referral_id,recipient_alias,authorized_at,sent_at,acknowledgment_at,next_check_at,owner_alias,sharing_scope

status-request-drafts.txt
Original first line: EMPTY OUTPUT TEMPLATE: status-request-drafts.txt

referrals.csv -> Referrals: verify referral_id -> referral_alias, recipient_alias -> destination_alias, sent_at, acknowledgment_at -> acknowledged_at, owner_alias and next_check_at against actual outbound evidence. sharing_scope and authorized_at do not automatically establish sharing_scope_verified; record its approved evidence_refs.
recipient-verification.csv and followup-policy.txt -> Scope: retain recipient/channel verification and the exact permitted administrative sharing scope in restricted records, passing only approved aliases/evidence references. referral-followup.csv and status-request-drafts.txt are old outputs; they do not prove delivery or acknowledgment.

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 native end-to-end outbound-referral export is established. The register is a manually evidenced editorial input.
The live account, entitlement, exact headers, records and field coverage have not been observed.

Recipe acquisition / manual mapping instructions
Locate the real outbound-referral evidence
Location: Matter > Details / Activities / Tasks; existing approved outbound-referral register
Read the existing register or maintained custom fields, sent-event evidence, receiving-party acknowledgment, staff owner and follow-up date. Keep recipient identity and client-sharing authorization in restricted records. No inbound-referrer report is substituted.
Verification: Lawmatics Source=Referrals and Campaign/Referrer track inbound referral attribution. They do not prove a referral was sent out or accepted.
https://help.lawmatics.com/en/articles/10699954-tracking-referrals
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
For each staff-nominated outbound referral, verify whether it was sent, what administrative information may be shared, whether an acknowledgment exists, and the already assigned next-check date. 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/10738648-completing-and-editing-tasks


Do not proceed when
- No outbound sent/acknowledgment record, missing recipient verification or missing information-sharing scope.

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.
