Check the signed-client handoff
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
- 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.

STOP IF
- No stable checked pair map, no actual field mapping, missing destination access or missing signed-packet evidence.

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: field-map-template.csv
firstLine: source_field,target_field,source_type,target_type,required,overwrite_rule
- file: handoff-template.csv
firstLine: intake_alias,firm_acceptance_approved,conflict_check_status_supplied_by_staff,required_field_values,source_status
- file: sync-results-template.csv
firstLine: intake_alias,sync_run_id,destination_matter_id,destination_status,field_name,observed_value
requiredNativeInputs: - name: PairMap
kind: editorial_table
proposedDistinctTemplate: native-pairmap-template.csv
columns: - matter_alias
- source_ref
- target_ref
- staff_verified
- signed_engagement_verified
- signed_evidence_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: Checks
kind: editorial_table
proposedDistinctTemplate: native-checks-template.csv
columns: - matter_alias
- field_or_file_alias
- expected
- source_present
- target_present
- target_value_matches
- evidence_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.
existingFileMapping: - file: handoff-template.csv
mapping: 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.
- file: field-map-template.csv
mapping: 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.
- file: sync-results-template.csv
mapping: 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.

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.

PairMap: native-pairmap-template.csv
Checks: native-checks-template.csv
Scope: native-scope-template.txt

STEP 1: Inspect the configured handoff
Tool: Lawmatics
Open: Settings > Integrations > Clio > existing integration settings and field mapping
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

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.

Expected output: Read-only integration configuration capture.
Use it next: Use this as the expected-field checklist for a small, staff-nominated set of already synced matters.
Check: 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.
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/10699984-clio-manage-integration

STEP 2: Compare the actual source and destination records
Tool: Lawmatics and Clio Manage
Open: Lawmatics matter > Details / Files / Notes; corresponding Clio Manage matter > details / Documents / Notes
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

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.

Expected output: Paired evidence ledger with source and target links kept internally, mapped-field observations and file presence.
Use it next: Assign matter aliases; pass only presence flags, field aliases and discrepancies downstream.
Check: 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.
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/10699984-clio-manage-integration
https://help.lawmatics.com/en/articles/10699825-matter-profile-overview

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

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.

Expected output: PairMap(matter_alias,source_ref,target_ref,staff_verified,signed_engagement_verified,signed_evidence_ref); Checks(matter_alias,field_or_file_alias,expected,source_present,target_present,target_value_matches,evidence_ref); Scope(integration_settings,capture_time)
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/10699984-clio-manage-integration

STEP 4: 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 PairMap, Checks and Scope only. Stop any pair without staff_verified=true. Report missing or unequal required mapped fields and files. Distinguish signed engagement verified by staff from Hired status and Sync event. Do not infer that a success label proves all files transferred, that identical names mean the same file, or that a missing destination ID proves failure. Return exception,evidence_refs,verification_needed,reviewer_status=pending. Do not sync or resync.

Expected output: Handoff exception list with explicit blocked pairings.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: All passes require paired record evidence; no match by similar names.
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 5: 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 owner and receiving matter team review the source-linked checklist. Save signed-off acceptance or return unresolved items to the operator.

Expected output: Reviewed handoff acceptance/exception record.
Use it next: A separately authorized administrator decides any mapping fix or resync, preserving originals and considering overwrite effects.
Check: No live integration change, matter conversion or file transfer performed.
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/10699984-clio-manage-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.