# Check deposition-vendor confirmations Canonical page: https://agents.paretoid.com/workflows/check-deposition-vendor-confirmations/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Compare approved event details with bookings and change acknowledgments. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Compare approved event details with bookings and change acknowledgments. Why it matters: A calendar entry does not confirm that a reporter or other required vendor is booked for the latest details. Comparing confirmations and acknowledged changes helps the coordinator identify gaps before the event. ## Sources and evidence - pain: [Pain evidence: Practitioner describing a missed reporter booking](https://www.reddit.com/r/paralegal/comments/1x17nzq/comment/pervqzb/) Practitioner describing a missed reporter booking in Paralegals: worst mistake at work, comments 2026-10-09, within the 30-day window: multiple practitioners describe forgetting to book a court reporter, rescheduling and scrambling for availability. I'm exhausted and humiliated, 2025-11-25, older, describes failing to tell a reporter and videographer that a deposition changed to Zoom. - pain: [Pain evidence: Paralegals: worst mistake at work](https://www.reddit.com/r/paralegal/comments/1x17nzq/paralegals_whats_the_worst_mistake_youve_ever/) Additional self-reported public account; no independent identity or outcome verification. - pain: [Pain evidence: I'm exhausted and humiliated](https://www.reddit.com/r/paralegal/comments/1p5ygt9/im_exhausted_and_humiliated/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: Planner task checklists](https://support.microsoft.com/en-us/planner/add-a-checklist-to-a-task?wt.mc_id=otc_planner) Planner task checklists document required subtasks under a task. They do not book vendors or establish who is legally responsible for arranging a reporter. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Attorney-approved deposition enters the schedule, changes format/date, or approaches a firm-defined preparation checkpoint 1. compare event details against required vendor confirmations 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - Attorney-approved event details, arranging-party/service checklist, actual vendor confirmation messages and latest change/acknowledgment evidence. - Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI. - Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path; proposed adaptation, not tested - A calendar entry, sent booking request or automated read receipt is not a vendor booking or acknowledgment. No vendor-confirmation CSV export is assumed. Access and setup: - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. ### 1. Acquire the actual confirmations Tool: Outlook and event/checklist sources Location: New Outlook: selected message > More actions > Save as; classic Outlook: open message > File > Save As Save the relevant booking and change-acknowledgment messages unchanged in the restricted source folder. Open the current approved event and lawyer-supplied service/responsibility checklist. Manually capture aliases, booking reference, stated date/time/timezone/location or platform, service, latest change ID, acknowledgment text and source message reference. Expected output: events/bookings working ledger with explicit confirmed,pending,unknown states and capture time. Next step: Copy only approved metadata and short acknowledgment excerpts into a separate review-input TXT; keep email originals out. Check before continuing: A later format/date change invalidates an earlier confirmation for that field unless evidence acknowledges the change. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://support.microsoft.com/en-gb/outlook/mail/save-an-outlook-message-as-a-eml-file-a-pdf-file-or-as-a-draft https://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events ### 2. Load only the approved AI input Tool: Acrobat PDF Spaces Location: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space Add the minimized event/service ledger, confirmation excerpts, latest-change list and approved responsibility policy. Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing. Expected output: Visible approved source set in the PDF Space; no account integration is implied. Next step: Use the AI Assistant message field in this same space for the next prompt. Check before continuing: Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/supported-formats-limitations.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/pdf-spaces-faq.html ### 3. Run the bounded prompt and inspect citations Tool: Acrobat AI Assistant Location: The PDF Space AI Assistant message field Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance. Prompt: ```text Compare each approved event and required service against the booking and acknowledgment evidence. Return event_id,service,required_vendor_role,booking_ref,confirmed_details,latest_change_id,acknowledgment_ref,exception,approved_owner,source_refs. Flag absent booking evidence, mismatched times/timezones/location/platform and stale acknowledgments. A calendar entry or sent request is insufficient. Use only supplied responsibility and cancellation terms; do not interpret procedural duties, calculate cancellation charges, book, cancel, pay, contact anyone or change calendars. ``` Expected output: Readiness and stale-acknowledgment review list with field-level evidence. Next step: Save the checked draft as vendor-readiness-review.docx; carry source IDs, versions and reviewer corrections into the next review step. Check before continuing: Check each alleged confirmation against the original message and latest approved change, including timezone. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 4. Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Location: Local reviewed report beside the frozen source set Paralegal checks every service and change against the original correspondence; lawyer resolves responsibility and unresolved terms. Record confirmed versus still-unconfirmed fields, owner and separately approved next action. Expected output: Human-reviewed readiness checklist. Next step: Any follow-up to a vendor or change to booking requires separate authorization. Check before continuing: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ## What you will get 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. ## Human review and limits 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. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema 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 Synthetic example input: ```text Synthetic inputs are included in the starter kit. events.example.csv bookings.example.csv scope.example.txt ``` Expected synthetic output: ```text EVT1 reporter exists but confirms in-person and CHG1 while approved event is remote CHG2; flag stale format/change acknowledgment. EVT1 required videographer has no booking row; missing vendor confirmation for Coordinator-A. EVT2 details and CHG1 acknowledgment align; retain Other-party responsibility as supplied, without deciding procedural obligations. No bookings, cancellations, payments, calendar changes, or vendor contacts made. ``` Failure check: Responsible paralegal confirms with original records; attorney resolves responsibility. Test a booked reporter whose confirmation still says in-person after a remote-format change. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/s20-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/s20/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [events.csv](https://agents.paretoid.com/assets/starter-kits/s20/events.csv) — Blank input template with exact recipe headers. - [events.example.csv](https://agents.paretoid.com/assets/starter-kits/s20/events.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [bookings.csv](https://agents.paretoid.com/assets/starter-kits/s20/bookings.csv) — Blank input template with exact recipe headers. - [bookings.example.csv](https://agents.paretoid.com/assets/starter-kits/s20/bookings.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [scope.txt](https://agents.paretoid.com/assets/starter-kits/s20/scope.txt) — Blank text input worksheet. Fill its fields with approved evidence; no default assumptions are supplied. - [scope.example.txt](https://agents.paretoid.com/assets/starter-kits/s20/scope.example.txt) — Separate synthetic text input fixture; use with the example CSV files only. - [Expected fixture findings](https://agents.paretoid.com/assets/starter-kits/s20/expected-fixture-result.txt) — Read-only expected output and failure conditions for the included synthetic input files. - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/s20/README.txt) — Recipe-specific prerequisites, file mapping, prompt, setup steps, checklist and limits. ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text 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. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.