One Docket, Everyone's Local Time

A hearing occupies a single instant. That instant does not move because the people who must attend are scattered. A partner in transit, an associate at the seat of the court, a paralegal preparing the bundle from another office: each reads the same entry, and each is tempted to read it in the clock nearest to hand.

The danger is quiet. Nobody misreads the date. They misread the hour, by the exact offset between where they stand and where the court sits. The docket says ten. Ten arrives in the wrong city first, and by the time it reaches the courthouse the appearance is already lost.

Timezone arithmetic is deceptively hard. Offsets are not whole numbers everywhere. Daylight saving shifts on different dates in different places, and a few regions do not observe it at all. A traveling advocate can cross two boundaries before lunch and carry one stale assumption across both.

Shared spreadsheets and group messages make this worse, not better. A time typed once, in one author's clock, is read by everyone as though it were their own. The document never says which clock it meant. That silence is the defect, and it survives every careful re-reading.

The remedy is structural, not a matter of vigilance. Store each event as one true instant, tied to the place the court actually sits. Render that instant to each member in the clock they actually stand in. The lawyer then reads a local time and trusts it, because the conversion happened once, correctly, beneath the interface rather than inside a tired head at an airport gate.

Mersal renders hearings, filing deadlines and limitation dates in each member's local time, and its reminders fire before the event and escalate as it approaches, never after. A reminder that arrives after the hour it was guarding is not a reminder.