The court emailed. Your calendar already knows.
Calendaring connects to the Microsoft 365 account you already use (the same connection as CaseFile's OneDrive sync) and reads your inbox for court notices — e-service, opinions issued, judgments signed, settings. A rules engine turns each notice into the deadlines it starts running: the appellate court hands down its opinion, and the motion for rehearing (TRAP 49.1), en banc reconsideration (TRAP 49.5), and petition for review (TRAP 53.7) dates appear in your review queue, each with its rule citation. You confirm; Calendaring puts them on your Outlook calendar and the native one.
What it does
Inbox scanning, on your account
Connects with Mail.Read on your own Microsoft 365 mailbox — the same per-attorney OAuth connection CaseFile uses, extended with mail and calendar scopes. Scans run automatically every 30 minutes, or on demand.
A rules engine, not a guess
The AI only identifies what happened and when — opinion issued, judgment signed, petition denied. The deadline math is deterministic code: TRAP 49.1 rehearing at 30 days, TRAP 53.7 petition for review at 45, TRCP 329b motion for new trial at 30, FRAP 4(a) notice of appeal — with weekend and legal-holiday rollover per TRAP 4.1.
Citations on every date
Every proposed deadline carries the rule that generated it and the caveats that matter (extension availability, the 90-day notice-of-appeal window when a timely MNT is filed). Verify the math before you rely on it — the authority is right there.
Confirm before it calendars
Nothing touches your calendar silently. Extracted notices land in a review queue with their proposed deadlines; you confirm, adjust, or dismiss each one. Confirmed events sync to Outlook as all-day events and stay on the Calendaring module's native calendar.
Matched to your matters
Cause numbers and case styles in the notice are matched against your Lawdiem matters automatically, so the deadline lands on the right case — and the whole history is one click from CaseFile.
Settings and stated deadlines too
Not everything is rule math. Hearing settings, trial dates, and deadlines stated in the notice itself ('response due July 21') are extracted and proposed as-is.
One scan, two modules
The same inbox scan feeds ProposedReply, which drafts suggested replies to the correspondence that warrants one — deadlines here, replies there, one Microsoft connection.