# Check that calendar requests became events Canonical page: https://agents.paretoid.com/workflows/check-that-calendar-requests-became-events/ Category: Operations & Reporting Practice relevance: cross-practice. Useful supporting administrative method; no claim of practice-specific legal instructions. Jurisdiction/provider scope: Clio calendar export and Excel comparison; does not derive court deadlines or confirm court attendance. Match approved calendar instructions to actual event IDs and flag gaps. Status: 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. Verification: 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. ## The problem Match approved calendar instructions to actual event IDs and flag gaps. Why it matters: Marking an email complete does not prove its calendar event exists. Matching approved instructions to actual event IDs helps staff find missing or incorrect entries before relying on the calendar. ## Sources and evidence - pain: [Pain evidence: Missed a Calendar Date and Can’t Figure Out How](https://www.reddit.com/r/paralegal/comments/1wyb3dz/missed_a_calendar_date_and_cant_figure_out_how/) Missed a Calendar Date and Can’t Figure Out How, 2026-10-05, recent. OP marked the attorney's email complete but could find no resulting calendar event. The failure is completion verification, not lack of reminders. - method: [Method: Clio calendar exports](https://help.clio.com/hc/en-150/articles/9289958655515-Import-Filter-and-Export-Calendars) Clio calendar exports supports CSV/ICS export; Power Query merge supports joining tables on keys. - method: [Method: Power Query merge](https://learn.microsoft.com/en-us/power-query/merge-queries-overview) 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. ## Suggested approach Start when: End-of-day or completed calendar request 1. match approved instruction IDs and explicit dates to actual event IDs 2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes. 3. The responsible staff member checks the draft against the source records and approves any separate action. ## What you need - 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. - 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 - 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. Access and setup: - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. ### 1. Acquire the actual request and calendar snapshot Tool: Outlook and Clio Manage Location: Outlook selected request > Save as / File > Save As; Clio matter > Calendar > Filters/Upcoming/Past/All > Columns > bottom Export > CSV > Export 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. Next step: Staff checks request wording and event records before constructing a small alias-only comparison ledger. Check before continuing: Include relevant rescheduling/cancellation instructions; missing access or unbounded coverage blocks absence conclusions. 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/9289958655515-Import-Filter-and-Export-Calendars https://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events ### 2. Approve dates and map instructions to events Tool: Local review ledger and originals Location: Request/email text beside actual calendar event details 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. Next step: Paste the approved minimized ledger and scope/matching policy into PDF Spaces as labelled TXT. Check before continuing: Relative dates, duplicate candidates or unknown timezones stay unresolved. Do not infer a new legal date. 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://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 ### 3. 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 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. 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 ### 4. 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 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. Next step: Save the checked draft as calendar-completion-review.docx; carry source IDs, versions and reviewer corrections into the next review step. Check before continuing: Verify any missing finding through a direct calendar search and a second-person check for critical dates. 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 ### 5. Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Location: Local reviewed report beside the frozen source set 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. Next step: Any calendar correction or notification is separately authorized; completion is not inferred from an email flag. 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://help.clio.com/hc/en-150/articles/9289905071387-Calendar-Events ## What you will get calendar-exceptions.csv: instruction_id, matching_event_ids, status, source_row_ids, review_reason. No live changes. ## Human review and limits Two-person review for missing or contradictory critical dates. Completion requires a verified event ID, not an email checkmark. Test missing event, wrong timezone, duplicate title and changed date. 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: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved. ## Original prepared-input schema instructions.csv: instruction_id, matter_alias, event_type, approved_datetime, timezone, completion_status. events.csv: event_id, matter_alias, event_type, start_datetime, timezone, source_instruction_id. Synthetic example input: ```text I1: done, no matching event ID I2: approved time differs from exported timezone I3: exact event and instruction ID match ``` Expected synthetic output: ```text I1: missing event I2: time mismatch for review I3: matched with evidence IDs ``` Failure check: Two-person review for missing or contradictory critical dates. Completion requires a verified event ID, not an email checkmark. Test missing event, wrong timezone, duplicate title and changed date. ## 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/a03-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/a03/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a03/README.txt) — Required inputs, file use, review steps and limits - [Instructions blank CSV](https://agents.paretoid.com/assets/starter-kits/a03/instructions-template.csv) — Blank input headers for instructions.csv - [Instructions synthetic example](https://agents.paretoid.com/assets/starter-kits/a03/instructions-example.csv) — Synthetic test records for instructions.csv - [Events blank CSV](https://agents.paretoid.com/assets/starter-kits/a03/events-template.csv) — Blank input headers for events.csv - [Events synthetic example](https://agents.paretoid.com/assets/starter-kits/a03/events-example.csv) — Synthetic test records for events.csv - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a03/expected-results.txt) — Compare a pilot result with the planted exceptions ## 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 Reconcile these deidentified calendaring instructions with this event export. Match by matter ID, event type and attorney-approved date/time. Output instruction ID, matching event ID, exact match/mismatch/missing/ambiguous, and supporting row references. Do not calculate deadlines from rules, service dates or phrases such as ‘60 days.’ Put those in attorney-review. Do not create, delete or move any event. INPUTS instructions.csv: instruction_id, matter_alias, event_type, approved_datetime, timezone, completion_status. events.csv: event_id, matter_alias, event_type, start_datetime, timezone, source_instruction_id. OUTPUT calendar-exceptions.csv: instruction_id, matching_event_ids, status, source_row_ids, review_reason 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 Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.