Nothing here is legal advice, and no software removes the obligation to check a computed date against the governing statute. Statutory references are current as of August 2026.
What does statute of limitations software actually have to do?
Four things, and only one of them is arithmetic. It has to capture the accrual date at intake as a required field rather than a note. It has to hold the claim type, because the claim type chooses the statute and the statute chooses the number. It has to escalate on a schedule that starts months out rather than days. And it has to survive staff turnover, which is where most of these systems actually fail.
The counting itself is trivial. Two years from March 4, 2026 is March 4, 2028. Any calendar can do that, and our statute of limitations calculator does it for California, Texas, Florida and federal claims with the governing statute printed next to the answer. What software has to add is the part a calendar cannot: making sure the date is entered at all, from the right trigger, on every file, by whoever happens to open it.
The four dates a PI intake has to capture on day one
Most systems ask for one. Firms that do not miss limitations dates ask for four, because in a meaningful share of files the ordinary limitations period is not the deadline that governs.
| Date to capture | Why it is separate | What it drives |
|---|---|---|
| Date of the incident | What the client reports, and what the police report shows | The ordinary limitations period in most negligence cases |
| Date of accrual | Not always the incident. A claim accrues when its last element occurs, which Florida states at section 95.031(1) | The date the clock actually starts |
| Date of discovery | Governs fraud everywhere, and runs alongside an outer limit in California malpractice under CCP 340.5 and 340.6 | The shorter of two clocks, where two run |
| Date of death | Texas runs wrongful death from the death, not the injury, under CPRC 16.003(b) | A survival claim and a wrongful death claim expiring on different days |
A fifth field is worth adding on any file where the defendant might be governmental: whether a notice of claim is required. That question has to be answered in the first week, not the first year, and it is covered below.
Why the government defendant question outranks everything else
Because the real deadline is months rather than years, and it is a condition of suing rather than a limitations period. California requires a written claim for death, personal injury or personal property damage to be presented within six months of accrual under Government Code 911.2(a). Texas requires notice within six months under section 101.101 of the Civil Practice and Remedies Code, and a home rule city charter can shorten that further, sometimes to as little as ninety days. Florida requires a written claim to the agency and to the Department of Financial Services under section 768.28(6)(a) before suit.
A client injured by a city bus in California has a two year personal injury claim under CCP 335.1 and six months to preserve it. A system that stores only the two year date will look completely healthy for eighteen months after the case is already dead. This is the single strongest argument for buying software that treats the limitations calculation as a workflow rather than a date field, and it is the first thing to test in a demo: ask what the system does when the intake form says the defendant is a public entity.
Do the PI specific platforms actually help here?
Yes, and this is the one part of the feature list where the premium is defensible. Filevine and SmartAdvocate both build intake around a limitations date that is a first class object: required at case opening, visible on the case list, and wired to an escalation chain rather than a single reminder. General practice management platforms treat it as one more calendar entry, which means it is only as good as the person who typed it in.
Both are quote only, which is normal for the category. If you are comparing the wider field on published pricing, the platform level comparison is in our guide to deadline management software for litigation teams. The distinction that matters for this article is narrower: docketing software calculates dates inside a filed case, and limitations tracking has to work before a case exists at all, on files that may never be filed. Those are different products even when one vendor sells both.
How should the escalation schedule be set?
Far earlier than most firms set it, and to a named person rather than to a queue. A limitations tickler that first fires thirty days out is a tickler that fires after the useful window has closed, because thirty days is not enough time to locate a missing medical record, identify an unnamed defendant, or discover that the driver was on the clock for a municipality.
A schedule that works in practice: a review at twelve months out, a hard review at six months, a filing decision at ninety days, and a named partner notified at sixty. On any government defendant file, the same chain runs against the notice deadline instead, which compresses all of it into the first ninety days. The escalations should go to a person by name. Anything routed to a shared inbox becomes nobody's job on the first busy week.
The intake call is where this is won or lost
Every limitations failure traces back to a date that was never captured cleanly or was captured from the wrong thing. The caller says "about a year and a half ago." The intake sheet records the call date. Six weeks later somebody works out that the incident was actually twenty-two months earlier and the file has two months left on a two year clock, most of which will be spent ordering records.
The fix is procedural before it is technical: the incident date is a required field, it gets confirmed against a document within the first week, and the file cannot advance until it is. Firms with volume that arrives outside office hours get a second benefit from having the after hours calls answered by something that asks the same questions every time, because a consistent intake script captures the incident date on the first contact instead of the third. The caller who reaches voicemail at seven on a Friday with three weeks left on the statute is the caller you most needed to reach.
What to ask a vendor about limitations tracking
- 1.Can a matter be opened without a limitations date? If the answer is yes, the field is decorative. The whole value of the feature is that it is impossible to skip.
- 2.Does the claim type drive the period, or does a human type the number? Florida cut general negligence from four years to two in HB 837, effective for causes of action accruing after March 24, 2023. A system where someone types "4" is a system that is wrong on every negligence file opened since.
- 3.What happens on a government defendant? The correct answer involves a different, much shorter deadline appearing automatically. Anything else means the notice window is being tracked in somebody's head.
- 4.Can I see every open matter sorted by days remaining? This one report is what a quarterly limitations audit runs on. If it takes an export and a spreadsheet, the audit will not happen.
- 5.Is there an audit trail on the date? Who set it, from what document, and who changed it. If the date is ever disputed, that history is the whole defense.
Referred and transferred files are the highest risk category
A file arriving from another firm carries whatever limitations date that firm computed, and it arrives with a story attached that discourages anybody from recomputing it. That is exactly backwards. The cheapest diligence step in any transfer is to recompute the date from the accrual date in the underlying documents before the file is accepted, and a surprising number of referrals do not survive it.
The same applies to a co-counsel arrangement where the other firm holds the docket. Somebody in your office should still carry the date, because a malpractice carrier will not be interested in whose calendar it was on. Keeping the accrual date and its source document inside the matter, rather than in a spreadsheet somebody maintains, is what makes that recomputation possible at all.
What no software can do for you
Decide the accrual date, and see tolling. Minority, mental incapacity, the defendant's absence from the state, fraudulent concealment, a bankruptcy stay and a written tolling agreement all move the date, and none of them are visible to a date field. Nor is a statute of repose, which runs from a fixed event and cuts the claim off whether or not it accrued: ten years on Texas health care liability claims under CPRC 74.251(b), twelve years on Florida fraud and products claims under section 95.031(2).
What software can do is make sure the question is asked on every file, that the answer is written down where the next person will find it, and that somebody is told while there is still time to act. That is a workflow problem wearing a calendar costume, which is why buying a bigger calendar rarely fixes it.
The short version
Make the limitations date a required field driven by claim type, not a number a human types. Capture accrual, discovery and death as separate dates. Answer the government defendant question in week one, because six months beats two years every time. Escalate at twelve, six and three months to a named person. Recompute the date on every transferred file. And keep a report of open matters sorted by days remaining, because that report is the only thing standing between a busy quarter and a barred claim.
Compute the deadline before you open the file
Pick the jurisdiction and the claim, enter the accrual date, and the calculator returns the last day to file with the governing statute cited beside it, for California, Texas, Florida and federal claims. It carries the six month public entity claim window as well, because that is the deadline that ends more cases than the limitations period does.