Find calendar differences across tools
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
- Read access to the actual Lawmatics, Clio Manage and Outlook records; a maintained explicit cross-system event/occurrence map and field-by-field source-of-truth policy.
- 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
- No universal Lawmatics calendar CSV export or universal three-way sync is verified. Use a bounded manual record inspection where necessary.
- Lawmatics external sync does not import every external event; it synchronizes Lawmatics-origin appointments and their external changes when enabled.
- Clio ICS omits locations and limits past events to 30 days. Outlook ICS is a snapshot; complete cancellation/deletion/recurrence history and stable IDs are not guaranteed by either export.
- If stable identity or an owner-verified mapping is absent, this is a candidate-comparison task only and cannot declare a sync failure.

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 actual snapshots and record views
Tool: Outlook, Clio Manage and Lawmatics
Open: Outlook Calendar > select calendar > File > Save Calendar > More Options; Clio matter > Calendar > Export CSV; Lawmatics left navigation Calendar > selected appointment
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

Save the Outlook ICS with explicit date range/detail and the Clio matter CSV with chosen filters/columns, preserving raw headers. In Lawmatics open each bounded appointment and read its fields without saving changes; capture appointment date/time/host/location/state, identity if exposed and source locator. Record current sync settings from Settings > Calendar read-only. Inspect direct event views for fields omitted by exports.

Expected output: Raw snapshots plus manual Lawmatics/direct-field observations and source/capture/scope manifest.
Use it next: Build the next alias-only ledger from observed fields and keep raw snapshots restricted.
Check: Do not connect/reconnect calendars or use sync/unsync controls. Missing location in Clio ICS is an export limitation, not a deleted location.
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-us/outlook/export-an-outlook-calendar-to-google-calendar
https://help.clio.com/hc/en-150/articles/9289958655515-Import-Filter-and-Export-Calendars
https://help.lawmatics.com/en/articles/10699840-editing-or-rescheduling-appointments
https://help.lawmatics.com/en/articles/10699756-calendar-settings-sync-your-calendar-to-lawmatics

STEP 2: Verify cross-system identity and coverage
Tool: Local comparison ledger and actual event records
Open: Owner-reviewed event-map and source-of-truth policy
Access needed: See recipe prerequisites; exact account entitlement and permissions not observed.

For each appointment and recurrence occurrence record a unique alias and verified source event ID/locator in each tool. Preserve original timestamps/timezones, all-day state, cancelled/unknown state and source capture time. Use a human verified match when source IDs are not exposed; do not label a local alias as a native ID. Record whether deleted/cancelled and exceptional occurrences are covered.

Expected output: Verified mapping and minimized appointment ledger, or explicit blocked mappings.
Use it next: Load the ledger, mapping and coverage/source-of-truth policy into PDF Spaces as approved TXT.
Check: Same title/person/time does not uniquely prove identity. Duplicate map keys or missing recurrence/cancellation coverage block that row.
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.lawmatics.com/en/articles/10699756-calendar-settings-sync-your-calendar-to-lawmatics
https://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events
https://support.microsoft.com/en-us/outlook/export-an-outlook-calendar-to-google-calendar

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 cross-tool appointment ledger, unique event/occurrence map and coverage/source-of-truth 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
Compare only records with a unique owner-verified cross-system event and occurrence mapping. Return appointment_alias,occurrence_ref,field,system_a,value_a,system_b,value_b,source_refs,coverage_status,review_action. Flag time,timezone,location,host and cancellation differences, duplicates and stale captures. Missing records are unresolved unless coverage proves the record should be present. Distinguish documented sync limitations from failures; unrelated external events absent from Lawmatics are not automatically errors. Recommend only a human check under the supplied source-of-truth policy. Do not infer mappings, calculate legal dates, edit/cancel/recreate events or resend invitations.

Expected output: Field-level drift queue plus acquisition/mapping blockers.
Use it next: Save the checked draft as calendar-drift-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check: Reviewer opens both mapped records, checking timezone display and recurrence exceptions before confirming any mismatch.
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.

Scheduler verifies each difference in all relevant source views and records the authoritative value and approvals needed for correction.

Expected output: Reviewed drift evidence and correction-request specification.
Use it next: Calendar changes are separate actions because they may send attendee notifications.
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.lawmatics.com/en/articles/10699840-editing-or-rescheduling-appointments

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.
