Check that calendar requests became events
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
- Actual calendaring-request messages, attorney-approved explicit dates/timezones and access to the selected Clio Manage matter calendar; no deadline calculation.
- Clio Manage calendar/export permission; exact subscription and available columns must be checked in the account.
- 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
- source_instruction_id and matter_alias are staff mappings, not promised native export columns. Matching by title alone is unsafe.
- Clio calendar ICS includes future events and only the prior 30 days, and omits event locations. Use the per-matter table export for the intended audit and inspect omitted fields directly.
- Recurrence exceptions, cancelled/deleted events, all-day dates and inaccessible calendars can make an export incomplete; absence is not automatically a missing event.

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 request and calendar snapshot
Tool: Outlook and Clio Manage
Open: Outlook selected request > Save as / File > Save As; Clio matter > Calendar > Filters/Upcoming/Past/All > Columns > bottom Export > CSV > Export
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Preserve the request emails and raw native CSV separately. Select the actual matter, period and visible/all columns; record account/calendar, capture time, filters and headers as returned. Read any required event details that the CSV omits from the actual event; do not rename sample columns onto the export.

Expected output: Actual request sources and native calendar CSV with scope manifest.
Use it next: Staff checks request wording and event records before constructing a small alias-only comparison ledger.
Check: Include relevant rescheduling/cancellation instructions; missing access or unbounded coverage blocks absence conclusions.
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/9289958655515-Import-Filter-and-Export-Calendars
https://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events

STEP 2: Approve dates and map instructions to events
Tool: Local review ledger and originals
Open: Request/email text beside actual calendar event details
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Assign request IDs and aliases; copy only attorney-approved explicit date/time/timezone and stated event type. Record actual event source IDs where exposed and an observed source locator. Set source_instruction_id only after a human confirms the relationship. If no stable event ID is exposed, keep a unique local capture ref and actual source locator and label it manual evidence, not a native ID. Review occurrences and exceptions individually.

Expected output: instructions/events comparison input plus mapping confidence and coverage flags.
Use it next: Paste the approved minimized ledger and scope/matching policy into PDF Spaces as labelled TXT.
Check: Relative dates, duplicate candidates or unknown timezones stay unresolved. Do not infer a new legal date.
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://help.clio.com/hc/en-150/articles/9289958655515-Import-Filter-and-Export-Calendars
https://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events
https://support.microsoft.com/en-gb/outlook/mail/save-an-outlook-message-as-a-eml-file-a-pdf-file-or-as-a-draft

STEP 3: 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 approved instruction/event ledger, explicit mapping and coverage/matching 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 4: 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
Reconcile only these approved calendaring instructions and observed event records. Use the supplied verified mapping first. Return instruction_id,event_source_id or null,source_capture_ref,exact_match|mismatch|missing_within_verified_scope|ambiguous|coverage_unknown and evidence refs. Match event type and attorney-approved date/time/timezone; keep recurrence occurrence IDs separate. A checkmarked email is not event evidence. If scope, timezone, cancellation history or mapping is incomplete, return unresolved rather than missing. Do not calculate deadlines from rules, service dates or relative phrases; put those in attorney review. Do not create, delete, move or notify anyone about events.

Expected output: Source-linked calendaring exception queue and coverage gaps.
Use it next: Save the checked draft as calendar-completion-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Verify any missing finding through a direct calendar search and a second-person check for critical dates.
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 5: 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.

Responsible staff verifies each event and correction need; a second person checks critical dates. Record the actual event ID/locator and review timestamp before marking the request verified.

Expected output: Reviewed instruction-to-event evidence log.
Use it next: Any calendar correction or notification is separately authorized; completion is not inferred from an email flag.
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://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events

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.
