Tracking Deadlines Without Relying on Memory

A missed deadline is one of the few mistakes in practice that no amount of skill later can undo. Limitation runs out, an appeal window closes, a filing is rejected, and the merits of the case never get heard. The reflex is to add more reminders — but a calendar full of alerts nobody can verify is not a system. It is a pile of dates you are being asked to trust on faith. A dependable deadline is one whose origin you can check in seconds.

Record the trigger, not just the date

The date is the least useful thing to store, because it is the thing you cannot check. Record what created the deadline: the event it runs from, the source that governs the period, who owns the resulting task, and whether the calculation has been confirmed. "Appeal due 12 May" tells you nothing you can verify. "Appeal period runs from the order dated 12 March; limitation under [source]; owner [name]; calculation confirmed by [name]" tells you everything you would need to defend the date or catch an error in it.

Separate the triggering event from the calculation

Two things can go wrong independently: the date the clock started, and the sum you did on it. Capture both. Note the triggering event and its source document, then note the period and how you counted it — including how you handled the start day, court holidays, and any provision that extends or condenses the period. When a deadline is questioned, you want to see immediately whether the error is in the event or the arithmetic, rather than recomputing from scratch under pressure.

Mark calculated dates as provisional until confirmed

A deadline computed by one person and never checked is a single point of failure. Treat a freshly calculated date as provisional and mark it as such until a second person, or the responsible lawyer, has confirmed the trigger and the count. This is especially true for dates a tool or an AI assistant proposes: a computed limitation date is a prompt to verify, not an answer to file against. The confirmation step is cheap; the missed date is not.

Build in lead time, not just the deadline

Diarise the work, not only the due date. A filing deadline needs backstops before it — a date to have the draft ready, a date to brief counsel, a date to collect the client's documents. If the only entry is the final deadline, you discover on the last day that a dependency you needed a week for is now impossible. Working deadlines backward from the drop-dead date is what turns a date into a plan.

Keep the dates where the matter lives

A deadline stored away from the file it belongs to is a deadline waiting to be forgotten. The triggering document, the calculation, and the reminder should sit with the matter, so that anyone opening the file sees what is due and can trace why. When deadlines live in one person's private calendar, they vanish the day that person is on leave — which is exactly when they tend to fall due.

Review the whole list on a fixed rhythm

Individual reminders catch individual dates; they do not catch the deadline nobody entered. A short, regular sweep across every live matter — asking "what is coming up, and is anything missing?" — is what catches the gap before it becomes a miss. The system is not the alerts. The system is the routine of checking that the alerts are complete.

None of this depends on remembering anything, which is the point. Memory is the weakest link in deadline management and the one under the most pressure on a busy day. A structure that records the trigger, shows the calculation, marks what is unconfirmed, and keeps it all beside the matter — as a workspace like Juniorlawyer is designed to — turns deadline-keeping from an act of vigilance into something the file itself carries.