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. S20: Verify deposition-vendor readiness and change acknowledgments Starter kit Status: Proposed / not tested PURPOSE Attorney-approved deposition enters the schedule, changes format/date, or approaches a firm-defined preparation checkpoint → compare event details against required vendor confirmations → readiness checklist and missing/stale acknowledgment queue. PREREQUISITES 1. Deidentified event ID, approved date/time/timezone/location or remote platform, attorney-specified arranging party, required services, chosen vendor, booking reference, last confirmation, latest change ID, acknowledgment reference and approved cancellation terms. Existing Planner/Lists or spreadsheet; vendor links remain in authorized internal storage. 2. Synthetic files first. Real use requires firm-approved access, privacy, processing terms, retention controls, export coverage and a named reviewer. 3. Prepare any required original files or rendered evidence separately. This kit does not configure accounts, connectors or live actions. FILES AND FORMATS events.csv: event_id, approved_datetime, timezone, format, location_alias, arranging_party, required_services, latest_change_id, owner_alias, cancellation_terms_ref bookings.csv: event_id, service_code, vendor_alias, booking_ref, confirmed_datetime, timezone, confirmed_format, confirmation_ref, acknowledged_change_id, acknowledgment_ref scope.txt: approved preparation checkpoint and export cutoff Files without .example are blank input worksheets; CSV templates contain headers only. .example files contain invented records for the dry run. Text input .txt files contain blank labeled fields. Use the original base filename when supplying an example to the prompt, or explicitly map the example filename to that input. CSV files are UTF-8 with comma delimiters, quoted fields where needed, and CRLF row endings. Preserve identifiers as text when importing into Excel. Blank means missing or unresolved, never a zero or a pass. Multi-value fields use a pipe only where the fixture scope says so. SETUP AND DRY RUN 1. Copy this kit to an approved working folder. Keep examples separate from any real exports. Do not upload client, privileged, personal, credential or financial-account data to an unapproved service. 2. Read the .example text policy/scope files and all .example.csv inputs together. They define this fixture only. For a real pilot, fill the blank templates from approved exports without changing headers and obtain approved policy values. 3. Use native read-only exports, exact joins and arithmetic for deterministic checks. This kit includes no executable automation, OAuth setup, live-action instructions or importable Make blueprint. 4. Give only the approved prepared inputs to a firm-approved text assistant and use the recipe prompt below. Keep source IDs, source row numbers and unresolved evidence visible. 5. Compare the proposed result with expected-fixture-result.txt. Verify every listed issue and that the prompt invents no missing evidence. The expected file describes assertions, not a performed workflow run. 6. Have the named reviewer check source evidence and record remaining questions before any separately authorized action. RECIPE PROMPT For each approved event, compare the required service checklist with booking and acknowledgment records. Flag missing reporters or other specified vendors, unacknowledged date/location/format changes and mismatched times or timezones. Treat a calendar entry as insufficient proof of a booking. Use only the attorney-supplied responsibility allocation and cancellation terms. Produce owner-assigned questions; do not book, cancel, pay, contact anyone, change an event or decide procedural responsibilities. INPUTS events.csv: event_id, approved_datetime, timezone, format, location_alias, arranging_party, required_services, latest_change_id, owner_alias, cancellation_terms_ref bookings.csv: event_id, service_code, vendor_alias, booking_ref, confirmed_datetime, timezone, confirmed_format, confirmation_ref, acknowledged_change_id, acknowledgment_ref; scope.txt: approved preparation checkpoint and export cutoff OUTPUT vendor-readiness.csv: event_id, service_code, arranging_party, booking_ref, confirmed_details, current_approved_details, acknowledged_change_id, evidence_ref, gap, owner_alias. No bookings or vendor contacts. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. REVIEW CHECKLIST [ ] Headers match the exact input schema and the export covers the stated scope [ ] Synthetic example files were used alone for the first dry run [ ] Every output finding retains its original source ID/row/page reference [ ] Missing keys, contradictions, unavailable originals and ambiguous dates remain unresolved [ ] Every expected fixture finding is present; no live action or unsupported result is claimed [ ] Responsible reviewer checks the original records before a real deployment RECIPE-SPECIFIC REVIEW Responsible paralegal confirms with original records; attorney resolves responsibility. Test a booked reporter whose confirmation still says in-person after a remote-format change. Distinct from A03 calendar creation checks and G05 consultation room availability. VALIDATION Exact CSV header order, field counts, serialized round-trip values and fixture semantics were checked during kit preparation. This does not test OCR, a vendor integration, a model response or end-to-end reliability. All data and identifiers are synthetic. Dates are fixed fixture dates, not current monitoring results.