FIG. 8 — How the calendar mirror works
Your attorneys dock deadlines in AppColl. From a docket report AppColl already exports — no API needed — DocketBridge mirrors them into Clio Calendar or Google Calendar, whichever your firm runs, so they reach every phone on the next sync. The mirror only ever runs one way. First the everyday routine, then watch it land on the phone.
FIG. 8a — A day in the life
The only thing a person does each day is dock the deadline in AppColl, the way they always have. From a scheduled docket report — keyed by TaskID, never a login — DocketBridge writes it to the responsible attorney's calendar, one way, so it reaches their phone without anyone re-keying a thing. Set up once, each attorney is mapped to their own Clio or Google calendar.
Matter — Nimbus Therapeutics · Office Action
Matched by TaskID and routed to the responsible attorney's calendar: a new TaskID creates the event, a changed due date updates it in place, and a closed deadline cancels it — so re-running the same report never doubles up. One-way only: editing the calendar never changes AppColl.
The moment the event lands in Clio or Google Calendar, it syncs to every attorney's phone — no app to install, nothing to re-key. Watch the deadline surface on the phone below.
FIG. 8b — On the attorney's phone
Matter — Nimbus Therapeutics · Office Action
FIG. 8c — What we need from AppColl
The whole mirror runs off a single report from AppColl's Tasks module — a snapshot of open deadlines, delivered as CSV by email, SFTP, or a manual drop. These are the columns DocketBridge maps; every one already exists in AppColl.
One requirement that matters: the report is a full open-horizon snapshot (e.g. the next 90 days) — not "new since last run" — so a deadline removed in AppColl is cancelled on the calendar too.