Find calendar differences across tools

Practice relevance

Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.

The problem

Compare mapped appointments for changed times, locations, duplicates, and stale cancellations.

Why it matters: A rescheduled consultation can still show the old time or location in another system. Comparing mapped events helps staff find discrepancies before relying on them or sending another invitation.

Sources & evidence

Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified.

What’s been verified

The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result.

What to measure: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved.

Pain evidence: Public discussion ↗; original post 2026-09-30. The operations manager describes manual appointment entry across Lawmatics, Clio and Outlook and requests reliable synchronization.
Method: Lawmatics calendar-sync scope ↗Two-way sync reflects external changes to Lawmatics-origin appointments, but does not import every external event. Clio documents event operations separately; a universal three-way sync is unproven.
Method: Lawmatics calendar-sync scope · supporting guide 2 ↗Additional official capability reference. It does not validate the complete proposed recipe.

Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. These two scheduling recipes use the same firm discussion; they are different tasks, not independent demand reports. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: Daily upcoming-consult audit

compare existing event IDs and start/end/host/location/cancel status across exports
Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes.
The responsible staff member checks the draft against the source records and approves any separate action.

Limits and review

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.

Who reviews it: Never automatically cancel, move or recreate events; doing so can send client notifications. Keep private events out of the comparison. Different job from G05, which checks whether a proposed slot is feasible.

What you need

Your firm-approved AI assistant · prepared files

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.
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

Before you start

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.

Check access and setup

Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed.

Acquire actual snapshots and record views
Outlook, Clio Manage and Lawmatics · Outlook Calendar > select calendar > File > Save Calendar > More Options; Clio matter > Calendar > Export CSV; Lawmatics left navigation Calendar > selected appointment
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.
Next step
Build the next alias-only ledger from observed fields and keep raw snapshots restricted.
Check before continuing
Do not connect/reconnect calendars or use sync/unsync controls. Missing location in Clio ICS is an export limitation, not a deleted location.
Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗Step documentation 4 ↗
Verify cross-system identity and coverage
Local comparison ledger and actual event records · Owner-reviewed event-map and source-of-truth policy
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.
Next step
Load the ledger, mapping and coverage/source-of-truth policy into PDF Spaces as approved TXT.
Check before continuing
Same title/person/time does not uniquely prove identity. Duplicate map keys or missing recurrence/cancellation coverage block that row.
Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗
Load only the approved AI input
Acrobat PDF Spaces · Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space
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.
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.
Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗
Run the bounded prompt and inspect citations
Acrobat AI Assistant · 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.
Acrobat AI Assistant promptCompare 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.
Next step
Save the checked draft as calendar-drift-review.docx; carry source IDs, versions and reviewer corrections into the next review step.
Check before continuing
Reviewer opens both mapped records, checking timezone display and recurrence exceptions before confirming any mismatch.
Step documentation 1 ↗
Human review and final handoff
Final human review
Responsible staff reviewer and lawyer/process owner · Local reviewed report beside the frozen source set
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.
Next step
Calendar changes are separate actions because they may send attendee notifications.
Check before continuing
All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output.
Step documentation 1 ↗

What you’ll get

calendar-drift.csv: appointment_alias, field, source_system, source_value, other_system, other_value, coverage_status, proposed_review

Inputs and a sample test Synthetic example · not a measured result

Input files

appointments.csv: system, event_id, start_datetime, end_datetime, timezone, host_alias, location_id, cancelled, exported_at
event-map.csv: appointment_alias, system, event_id
calendar-policy.txt: source of truth per field, coverage limits, stale-export threshold; omit private events and client-identifying titles

Synthetic example

AP1: mapped event has a different location in Outlook
AP2: source cancellation remains active in a mapped copy
AP3: unrelated external event absent from Lawmatics

Expected output

AP1: location difference, cite both records
AP2: stale cancellation, staff review
AP3: expected sync limitation unless policy proves otherwise

Test a failure

Supply duplicate mappings and a timezone/DST difference. Leave ambiguous matches unresolved and do not resend invitations.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 10 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
Setup and review checklist Required inputs, file use, review steps and limits
Appointments blank CSV Blank input headers for appointments.csv
Appointments synthetic example Synthetic test records for appointments.csv
Event map blank CSV Blank input headers for event-map.csv
Event map synthetic example Synthetic test records for event-map.csv
Calendar policy template Required policy or native-input preparation aid; synthetic when marked example
Calendar policy example Required policy or native-input preparation aid; synthetic when marked example
Synthetic example expected results Compare a pilot result with the planted exceptions

Optional full review prompt for prepared inputs

Prepared-input review prompt with Your firm-approved AI assistant · prepared files

Compare these anonymized upcoming appointment exports using the supplied event mapping. Flag missing copies, duplicates, stale cancellations and time/location differences. Distinguish an absent sync capability from a failed sync. Recommend which record needs human correction according to our source-of-truth policy, without editing or resending invitations.

INPUTS
appointments.csv: system, event_id, start_datetime, end_datetime, timezone, host_alias, location_id, cancelled, exported_at
event-map.csv: appointment_alias, system, event_id
calendar-policy.txt: source of truth per field, coverage limits, stale-export threshold; omit private events and client-identifying titles

OUTPUT
calendar-drift.csv: appointment_alias, field, source_system, source_value, other_system, other_value, coverage_status, proposed_review

Use only the supplied synthetic or firm-approved inputs. Cite source row or page IDs for each finding. Keep unknowns unresolved. Return a draft for the responsible staff reviewer. Do not send messages, connect accounts, change records, move money, or make legal decisions. Keep source files unchanged. If an input or permission is missing, list what is needed and stop that check.

Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read pain evidence