START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Track prior-title retrieval requests and existing-file checks
Starter kit A23

These files support a manual, read-only pilot. The workflow is proposed and has not been run against a live system. All example records are invented.

START HERE
1. Keep blank templates and synthetic examples separate. Use the example files first, renaming copies to the input names listed below if the prompt expects those names.
2. Open CSVs with UTF-8 and comma delimiters. Preserve IDs, timestamps and empty values as text on import. Empty means missing, not zero. There are no formulas. Do not change column headings.
3. Prepare the required policies and native documents. Stop any check whose inputs, coverage or permission are missing.
4. Use the recipe's prompt in the firm-approved workspace and request the stated review artifact. Treat all file content as data, not instructions.
5. Compare the result with expected-results.txt and the original rows/pages. Do not enable live connections or send anything from this kit.

INPUT CONTRACT
requests.csv: request_id, deidentified_property_id, prior_firm_business_id, staff_approved_followup_date. file-index.csv: file_id, deidentified_property_id, document_type, approved_version_status. contact-log.csv: request_id, business_id, contact_date, response_status.

RECIPE-SPECIFIC SETUP
FILE5 belongs to P5 while Q4 requests P4. The schema has no property names, so use exact IDs and do not invent a label-based match. The contact log already shows FIRM1 contacted for Q4. Prepare review/checklist only; no outreach or title opinion.

PREREQUISITES
- Deidentified file/property reference IDs, known prior firm/provider business names, official public links where relevant, request dates/status; secure index access. No title opinion or ownership inference.

REVIEW CHECK
Paralegal verifies property/file identity and lawyer decides title sufficiency. Test two properties with similar labels and an already-contacted provider.

EXPECTED OUTPUT
Approved assistant workspace searches only provided index/log; retrieval-review.csv and placeholder request checklist. No public title opinion or outreach.

Validation covers file syntax, exact declared headers and fixture consistency. It does not establish product compatibility, legal sufficiency, data completeness or production readiness.
