G09: native input mapping Check the signed-client 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 PairMap -> native-pairmap-template.csv Exact columns: matter_alias,source_ref,target_ref,staff_verified,signed_engagement_verified,signed_evidence_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Checks -> native-checks-template.csv Exact columns: matter_alias,field_or_file_alias,expected,source_present,target_present,target_value_matches,evidence_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 field-map-template.csv Original first line: source_field,target_field,source_type,target_type,required,overwrite_rule handoff-template.csv Original first line: intake_alias,firm_acceptance_approved,conflict_check_status_supplied_by_staff,required_field_values,source_status sync-results-template.csv Original first line: intake_alias,sync_run_id,destination_matter_id,destination_status,field_name,observed_value handoff-template.csv: intake_alias can seed matter_alias only after a staff-checked PairMap; firm_acceptance_approved/source_status do not prove a signed engagement. source_ref,target_ref,staff_verified must be independently captured. field-map-template.csv: source_field,target_field,required,types and overwrite_rule inform expected Checks and Scope integration settings. The file does not contain observed source/target presence or equality. sync-results-template.csv: destination_matter_id/field_name/observed_value may contribute destination evidence after source validation. A logged sync_run_id or status is not proof of source pairing, file integrity or complete sync. Checks still needs source_present,target_present,target_value_matches and evidence_ref. PairMap additionally requires signed_engagement_verified and signed_evidence_ref from actual approved signed-engagement completion evidence. firm_acceptance_approved and source_status never substitute for signed evidence. Keep client documents and identifying source maps in restricted storage. 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. This verifies configured mapping and observed presence, not legal engagement validity or a tested sync. Supported file types/size limits and exported destination IDs remain unverified. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Inspect the configured handoff Location: Settings > Integrations > Clio > existing integration settings and field mapping Read the existing conversion-sync, document-sync, note-sync and relationship-sync settings; capture mapping pairs and field types. Do not connect, toggle, convert or resync. Verification: Convert changes Hired status and Converted Date; Sync to Clio can occur without hiring. Folders do not sync. Compatible field types are required; open text is an exception. https://help.lawmatics.com/en/articles/10699984-clio-manage-integration Compare the actual source and destination records Location: Lawmatics matter > Details / Files / Notes; corresponding Clio Manage matter > details / Documents / Notes Staff verifies the exact source/destination record pair using an existing cross-reference or a checked record-link map. Capture required values and document presence/version metadata on both sides, plus approved signed-engagement completion evidence. No client documents are uploaded to AI. Verification: Hired status is not proof of a signed engagement. Documentation does not establish a universal export of destination IDs, sync event logs, file-type/size support or file integrity; missing proof blocks those checks. https://help.lawmatics.com/en/articles/10699984-clio-manage-integration https://help.lawmatics.com/en/articles/10699825-matter-profile-overview Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Make a one-to-one PairMap checked by staff, retaining source_ref, target_ref, staff_verified, signed_engagement_verified and signed_evidence_ref. Map the actual integration requirements and observations from the paired records into Checks: expected is the approved mapped-field or file requirement; source_present and target_present come from inspected source and destination records; target_value_matches is the staff-verified comparison, not a sync-status inference; evidence_ref points to the supporting capture. Keep matter_alias and field_or_file_alias on each Checks row. Unknown or uninspected facts stay unknown. Include the signed-engagement evidence in PairMap; Hired status alone does not establish it. 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/10699984-clio-manage-integration Do not proceed when - No stable checked pair map, no actual field mapping, missing destination access or missing signed-packet evidence. 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.