Calendar Sync for Law Firms, Done Right

Every firm that has lost a date can tell you exactly where it went. It was in someone's head on Tuesday, in a personal calendar on Wednesday, and nowhere at all by Friday, because that person was in a hearing and their phone had quietly stopped syncing eleven days earlier. Nobody caught it, because a calendar that has dropped an event looks precisely the same as a calendar with nothing scheduled. There is no red banner for absence.

Most firms respond to that story by buying more calendar. They connect another account, turn on another sync, and put a second screen in the corridor showing the week ahead. What they have not done is decide what the calendar is for, who it belongs to, and what happens when the connection between two systems breaks in the middle of a busy month. Those three decisions are the whole of calendar hygiene, and software only helps once they are made.

This piece is about the boring mechanics that separate a diary a firm can rely on from a collection of personal calendars that happen to overlap. It covers the difference between the two, the visibility question nobody answers until it goes wrong, the specific ways sync fails without announcing itself, and the reason a court deadline has to sit on the matter rather than on a person.

The firm diary and the personal calendar do different jobs

A personal calendar exists to protect one person's time. It holds the school run, the dentist, the block of focus time before a mediation, and the recurring internal check-in that only matters to the two people in it. It is edited constantly, it is full of provisional entries, and it is meaningful mainly to its owner. Nobody else should be reading it closely, and nobody else should be depending on it.

The firm diary exists to protect the client's position. It holds hearings, filing dates, limitation cut-offs, service deadlines, undertakings with a date attached, and the internal working dates that precede them. Every entry in it has a matter, a responsible fee earner, and a consequence if it passes unattended. Treating these two objects as one thing is the root of nearly every calendar failure I have watched a firm walk into, because the moment a court date lives in a personal calendar it inherits the fragility of a personal calendar. It can be declined, deleted, moved without notice, or lost entirely when the person holding it leaves.

A court date is not an appointment

An appointment has a start time and an end time and that is roughly all it needs. A court date carries a cluster of derived obligations, and the hearing itself is usually the least urgent of them. Working backwards from a trial you find exchange of witness statements, expert reports, a bundle deadline, a costs schedule, and internal dates for getting instructions in time to draft any of it. The hearing entry alone tells a supervising partner almost nothing about whether the matter is in trouble.

This is why a diary that only records the visible external date is a diary that reports good news right up until the week it collapses. The derived dates are the early warning. When Casely's deadline diary attaches a deadline to the matter and auto-tracks the next date, the point is not that a date appears on a screen, it is that the matter itself now carries a forward obligation that somebody can see without opening the file. A calendar entry describes an event. A deadline describes a duty, and duties belong to files.

Why the deadline belongs to the matter and not to the lawyer

Ask a firm who owns a filing date and the honest answer is usually a name. That works until the name is on annual leave, in hospital, on secondment, or gone. When ownership is personal, coverage is improvised. Someone remembers there was something happening on that file, opens it, and starts reconstructing the schedule from correspondence. That reconstruction is where dates get missed, because email is a terrible index of obligations.

When the deadline sits on the matter, coverage becomes a routine question rather than an emergency. Anyone with legitimate access to the file sees what is due next and why, and the responsible person is an attribute of the deadline rather than the container holding it. Casely's matter stage tracker helps here for the same structural reason, because a clickable stepper configured per practice area makes the file's position legible to a colleague in seconds. Connected matters extend it further by linking related files with the reason stated, so a date on one matter is visible from the file it actually affects. None of this depends on anybody remembering to forward an invitation.

Deciding who sees what, before someone sees the wrong thing

Calendar visibility is a confidentiality question wearing a scheduling costume. A hearing entry can leak a client name, an opposing party, a court, and the subject matter of a dispute, all in a title bar that a dozen people scroll past every morning. Firms doing conflicts work, family matters, employment disputes involving current staff, or anything where a screened team exists need to answer this before a shared calendar goes live rather than after.

The workable pattern is layered. Free and busy time is visible broadly, because scheduling requires it. Full entry detail is visible to the matter team and to supervisors, because supervision requires it. Restricted matters are invisible to walled users completely, which is where a lot of software quietly disappoints, because hiding a calendar entry in the interface is not the same as making it unreachable. Casely enforces ethical walls at the server and data access layer, so a walled user genuinely cannot reach a restricted matter by any route, including search, calendar, or a forwarded link. If your current setup relies on people not clicking the wrong thing, it is a convention, not a control.

The failure modes that drop events without telling anyone

Sync does not usually fail loudly. It fails at the edges, in ways that leave the calendar looking healthy. An OAuth token expires after a password change and the connection stops pulling, but the events already synced stay on screen, so the calendar looks populated and current. A mobile device caches a limited forward window and simply never receives entries beyond it. An invitation is declined by someone tidying their inbox, and depending on the client, the entry vanishes from their view without any signal reaching the person who created it.

Then there are the quieter ones. Recurring events sync as a rule plus a set of exceptions, and exceptions are the first thing to break when two systems disagree about how to represent them, which is how a single moved hearing reverts to its original slot on one device only. Two-way sync between calendars that both claim authority produces update loops, and one system eventually wins by overwriting the other. Rate limits during a bulk import drop the tail of a batch silently. A device restored from backup replays stale deletions. None of these produce an error a fee earner will ever see, and every one of them ends with a date that exists in one place and not another.

One-way, two-way, and the direction most firms get backwards

Two-way sync feels generous. Anyone can add anything anywhere and it all shows up everywhere. In practice it means two systems both believe they are authoritative about the same entry, and reconciliation happens by whichever write landed last. For personal scheduling that is fine. For a limitation date it is unacceptable, because the losing write disappears without trace and nobody can later tell you which version was correct or who changed it.

The arrangement that survives contact with a real week is asymmetric. The firm diary is authoritative for anything with a legal consequence, and it pushes out to personal calendars in one direction so that everyone's phone shows the day correctly. Personal calendars stay authoritative for personal time, and they push back only availability rather than content. If a hearing needs to move, it moves in the diary, on the matter, where the change is recorded and visible. The same instinct runs through Casely's approach to corrections in trust accounting, where an entry is voided and stays visible rather than being deleted, because a record you can quietly erase is not a record.

Time zones, all-day events, and the midnight problem

Most calendar systems store an all-day event as a date without a time, then render it against whichever zone the viewing device is currently in. Put a filing deadline in as an all-day entry, travel two zones east, and it can display on the wrong day. Firms with a remote paralegal in a different region, counsel abroad, or a partner who spends part of the year elsewhere hit this constantly, and the symptom is always the same argument about whose screen is right.

The fix is unglamorous. Anchor anything with a legal consequence to the jurisdiction and the court's local time rather than to a floating date, and give it a real time rather than making it all-day. Filing windows close at a specific hour in a specific place, and electronic filing systems in different jurisdictions apply different cut-offs and different treatment of after-hours submissions, so the local rule is the only rule that counts. Daylight saving transitions deserve the same suspicion, since the northern and southern hemispheres shift on different dates and a recurring entry that spans a transition can drift by an hour in exactly the week you are least able to check.

Recurring events and the exception that never syncs

Recurring entries are the most common source of phantom scheduling in a firm diary. A weekly matter review, a monthly billing block, a fortnightly client update call, all defined once and then modified endlessly. Every modification creates an exception to the rule, and exceptions are represented differently by different calendar platforms. When a series is edited on one system and the change fails to propagate, you get a meeting that exists for half the team and not the other half, and both halves are certain they are looking at the truth.

For anything that carries a deadline, avoid recurrence entirely. Generate discrete dated obligations from the matter rather than repeating a pattern, because a series edited three times over eight months is no longer describing what anyone believes it describes. Recurrence is a convenience for internal rhythm, not a mechanism for tracking duties. The tell that a firm has this wrong is when someone says the recurring entry is roughly right, which is a sentence nobody should be comfortable saying about a court obligation.

What actually belongs on a lawyer's personal calendar

Personal calendars should carry the individual's real commitments and a read-only reflection of what the firm diary says they are doing. That reflection matters, because a lawyer standing in a corridor needs the day on their phone without opening anything else. What personal calendars should not carry is the only copy of anything, the authoritative version of a matter date, or entries that only make sense to the person who wrote them.

The practical test is simple. If that person were unreachable for a fortnight starting tomorrow, could the firm run their matters from the diary alone? If the answer involves phoning them, the diary is decoration and the real schedule is still in someone's pocket. The purpose of the split is not tidiness. It is to make the firm's obligations independent of any individual's device, memory, phone battery, or continued employment.

Testing your sync instead of trusting it

Nobody tests calendar sync, which is why so many firms are running on a connection that broke months ago. The test takes an afternoon and it is the same discipline you would apply to backups. List every calendar feeding the diary, including the ones set up by someone who has since left. Create a test entry on each source and confirm it lands on the matter where it should. Then change it, then delete it, and confirm both operations propagate in both directions you expect and in neither direction you do not.

The part firms skip is the deliberate break. Revoke a token, sign out a device, change a password, and see whether anything or anyone tells you the connection has stopped. If nothing does, you have learned the most important fact about your setup, which is that its failure mode is silence. Write down what reconnection actually requires and who owns doing it, because that knowledge currently lives with one person and is the reason sync stays broken for weeks once it breaks.

Making the diary the thing people actually trust

A firm diary earns trust the way any record does, by being complete, by being visible to the right people, and by never quietly losing anything. That means deadlines attached to matters rather than to individuals, visibility governed by role and enforced below the interface rather than inside it, one authoritative direction for anything with legal consequence, and a test that proves entries are still arriving. None of it is exotic. It is just the set of decisions most firms defer until an empty Friday afternoon makes them.

The upside is not only avoidance of the bad week. A diary built this way gives supervisors a genuine view of exposure across the practice, lets colleagues cover a file without a handover meeting, and gives clients a straight answer about what happens next. Casely's client portal contributes there, since it is privilege-filtered automatically per document, works on mobile, and lets a client see and sign inside the same login with no separate account, which removes an entire class of chasing from the week. If you want to see how the matter-anchored version of this works in practice, our legal calendaring software page walks through how deadlines, matters and responsibility fit together, and there is a free plan you can start on at no cost.

One last thing, and it is the one that varies most. Everything above is about the mechanics of a diary, not about how to compute a period. Limitation, service, and filing calculations differ sharply between jurisdictions and often between courts within one jurisdiction, and the treatment of weekends, public holidays, and after-hours electronic filing is genuinely local. Build the diary so it cannot lose a date, then calculate every date against the rules that actually govern that matter, and confirm them locally rather than from habit.