Verify deposition-vendor readiness and change acknowledgments
Get the source data and prepare the review

Documentation-verified component path; proposed adaptation, not tested

WHAT WAS CHECKED
Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- A calendar entry, sent booking request or automated read receipt is not a vendor booking or acknowledgment. No vendor-confirmation CSV export is assumed.

WHEN THIS CAN RUN
Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification.

STEP 1: Acquire the actual confirmations
Tool: Outlook and event/checklist sources
Open: New Outlook: selected message > More actions > Save as; classic Outlook: open message > File > Save As
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Copy only approved metadata and short acknowledgment excerpts into a separate review-input TXT; keep email originals out.
Check: A later format/date change invalidates an earlier confirmation for that field unless evidence acknowledges the change.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source 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

STEP 2: Load only the approved AI input
Tool: Acrobat PDF Spaces
Open: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Use the AI Assistant message field in this same space for the next prompt.
Check: 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.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source 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

STEP 3: Run the bounded prompt and inspect citations
Tool: Acrobat AI Assistant
Open: The PDF Space AI Assistant message field
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.

PASTE THIS PROMPT
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.
Use it next: Save the checked draft as vendor-readiness-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Check each alleged confirmation against the original message and latest approved change, including timezone.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 4: Human review and final handoff
Tool: Responsible staff reviewer and lawyer/process owner
Open: Local reviewed report beside the frozen source set
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

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.
Use it next: Any follow-up to a vendor or change to booking requires separate authorization.
Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not 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.