A fee earner opens a construction file on a Tuesday morning to prepare a witness statement and reads the first attendance note properly for the first time since the matter came in. Four paragraphs down, the client describes standing in the garden looking at the crack above the extension door and telephoning the builder that afternoon, and the date of that call is written into the note. Limitation has been running from that conversation. The diary holds the date of practical completion, entered when the file was opened, and the two sit more than a year apart.
Nothing had gone wrong in a way anyone would recognise at the time. The date existed in the file from the first week, in the client's own words, and it never reached the diary because reaching the diary depends on a person reading a document, recognising that a date inside it carries a legal consequence, working out what that consequence is, and stopping to enter it. That is four separate acts of attention on a morning with eleven other matters waiting.
The diary, on that reading, records what your fee earners noticed rather than what your firm owes. It performs well on the dates that arrive already fixed. An order lands with a date on its face, a hearing gets listed, and somebody types it in. It performs badly on everything else, and everything else is where the claims come from.
The date behind the date
Derived dates are the difficult category, because nobody hands them to you, and limitation running from a date of knowledge is the clearest instance. The operative date is not the accident or the breach but one built out of what the client knew and when, and the material establishing it sits in an attendance note or a medical report rather than in any field of your case management system. A commercial contract carries the same problem, with a notification period running from the moment a party becomes aware of a claim, buried in a clause nobody has reopened since completion.
Then there are the dates that move. An extension agreed by consent in an exchange of emails on a Friday shifts the date for service, and the correspondence records the new date perfectly well, and no one changes the diary. Directions hang off one another, so when a hearing is relisted every date derived from that step moves with it while the diary keeps the originals. The hardest case is the second date sitting behind the first. The hearing goes into the diary because it is an appointment. The order that follows it carries a date for compliance, and that is the date the court will enforce, and it goes in only if someone reads the order and works forward from it.
Reading the file for its dates
There is a discipline any firm can adopt without buying anything. Run a periodic reconciliation between the dates written into the correspondence and the dates held in the diary, matter by matter across a sample, and treat every difference as a finding rather than a slip. A partner owns the exercise and it runs on a fixed cycle, because a reconciliation that happens when somebody remembers has the same defect as the diary it is meant to check.
Treat every incoming document as a possible source of a date. A defence, an expert report, a consent order and a client's account of when they first noticed the damage all carry dates or the raw material for deriving one. Nothing gets filed until someone has asked what date it creates, changes or reveals. The SRA Standards and Regulations expect a firm to run effective systems and controls and to supervise work competently, and a diary populated by memory alone struggles to answer either expectation. What you want is a second diary, independent of the first, that derives its dates from the file rather than depending on anyone typing them in.
Building that second diary by hand across two hundred live matters is where most firms give up, and it is the gap the Bracton AI Assistant is built for. The assistant is built into Bracton, the case and client management platform, which carries its own diary and limitation engine, and it is also sold on its own to run inside the case management or CRM system your firm already has, whether that is LEAP, Clio, Proclaim or another. It reads across every live matter overnight rather than the one file open in front of a fee earner, works through the correspondence and the documents for dates that were never entered, and derives the dates that follow from them, including the compliance date behind the hearing. Each one goes to a qualified fee earner to confirm or reject. Nothing is written into your diary on its own authority, the audit trail records what was done and by whom, hosting is in the UK, and your client data never trains a model.
The only test that means anything is what turns up on something real. The demonstration shows the second diary and the working behind its dates on an invented firm, and the written exercise on your own records starts with the client account: book a client account review.