Statute of Limitations Tracker

$39.00

For the plaintiff-side or small general practice carrying more matters than one person holds in their head, instead of a docket spreadsheet nobody has opened since March.

Local-firstNo telemetry — nothing phones homeNo lock-inNo migration

Every open matter gets its limitations date computed from its accrual date.

The whole list is sorted by how soon it runs, and anything inside 90 days drops into ALERTS.md.

$39/mo per firm. The full matter calendar, the alert file, and the CSV and JSON exports on every run, with no per-matter charge. Cancel any day, and every calendar you generated stays on your disk.

The date that passes silently

Nothing happens when a limitations period runs out. No notice arrives. No filing gets rejected. The date passes on a Tuesday, the file sits in the drawer exactly the way it sat on Monday, and the matter is worth nothing now, and nobody in the office knows yet.

Every other deadline in a practice fails loudly. Miss a discovery response and a motion arrives inside the week. The statute is different. Nobody tells you. The first person to mention it out loud is defense counsel, in a dispositive motion, and by then there is no answer to give.

The spreadsheet where the accrual dates live is not a system. It’s a place the dates are stored. It does no arithmetic and it never speaks. Somebody has to open it, add a number of days to a date, do that for every open matter, and then do it again next month.

How a matter list becomes a calendar

  1. Export the matters. Four columns: matter, client, accrual_date as YYYY-MM-DD, and period_days. Point MATTERS_CSV at the file.
  2. Set the runway. WARN_DAYS is how far ahead you want to be warned, defaulting to 90. AS_OF lets you compute the calendar as of a date other than today, which is how you check what the list should have said six months ago.
  3. Run it. Each limitations date is accrual_date plus period_days, computed in UTC. Each matter is classified against AS_OF, and everything is written sorted by date to SOL_CALENDAR.md, ALERTS.md, sol.csv, and sol.json.

What it does

  • The date is computed in UTC on purpose, so a daylight-saving boundary can never move a limitations date by a day. That off-by-one is a real bug in hand-rolled spreadsheets, and it’s the kind that surfaces exactly once.
  • ALERTS.md holds only what needs attention today, the expired matters and anything inside WARN_DAYS. It’s short by design, because a file nobody opens protects nobody.
  • A row with a missing matter name, or an accrual_date it can’t parse, gets skipped and reported at the bottom of SOL_CALENDAR.md instead of crashing the run. So you find out that four rows in your docket were unusable, which is information you did not have this morning.
  • period_days is set per matter, not per firm, so a two-year personal injury claim and a four-year contract claim sit in the same list and both come out right.
  • Point AS_OF at a past date and it tells you what the alert list should have said then. That is how you audit a docket you inherited from somebody else.
  • sol.csv and sol.json fall out of the same run, so the calendar goes back into a spreadsheet, or into whatever the firm actually uses, without anybody retyping a date.
  • Everything is sorted by limitations date, so the top row of SOL_CALENDAR.md is always the matter closest to running out.

Who this is for, and who it is wrong for

Written for the plaintiff-side or small general practice, roughly two to fifteen attorneys, carrying enough open matters that nobody tracks them all from memory. If you already run a case management system that computes limitations dates and escalates them to a human, this adds nothing and you should ignore it.

It is not a rules engine. It knows nothing about tolling, the discovery rule, revival statutes, or a period shortened by contract. It adds period_days to accrual_date. Every date it produces has to be verified against the governing statute, and the report says exactly that on its face.

What it replaces

A spreadsheet. That’s the honest answer for most firms this size, and the spreadsheet costs nothing and has one failure mode, which is that it doesn’t calculate and nobody opens it.

The real alternative is limitations tracking inside Filevine, Smokeball, or Clio Manage, and those are better at something that matters. They compute the date off the matter itself the moment the matter is created, with no export step in between, and they put the alert in front of a person who has to acknowledge it. If you have one of those, use it. If your matters live in a spreadsheet, this reads the spreadsheet, and it costs $39.

Where the matter list stays

The matter list never moves. MATTERS_CSV is read locally, computed in memory, and never sent anywhere, which is the whole point when the file in question is a list of every client and every claim the firm is holding. Writes land only under OUTPUT_FOLDER, each path checked against that root before anything is written, each output file set to 0600. The calendar isn’t in an account somewhere. It’s four files, where you put them.

What $39 covers

$39 a month for the firm, not per attorney and not per matter. Every run, every export, the alert file, all of it. If your matters already export to CSV, the first SOL_CALENDAR.md is minutes after install, and the first useful thing most firms learn is how many of their rows don’t have a parseable accrual date in them. Cancel any day, and every calendar you generated stays on your disk.

Security and privacy

Handles client matter data (matter names, client names, accrual dates). Security is designed in.

NOT legal advice; verify against governing law. This document covers the software’s security posture only, not the legal correctness of any computed deadline. See the disclaimer in README.md and in every generated report.

Principles
Local-first. MATTERS_CSV is read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
Non-destructive. The source CSV is only read, never modified or deleted.
Least privilege. Reads MATTERS_CSV, writes only under OUTPUT_FOLDER.

Protections implemented (v0.1.0)
Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so the report can’t be written outside OUTPUT_FOLDER.
Fail-fast config validation — clear errors for missing/invalid MATTERS_CSV/OUTPUT_FOLDER/WARN_DAYS/AS_OF before any file is touched.
Restrictive permissions — the generated report (SOL_CALENDAR.md, ALERTS.md, sol.csv, sol.json) is written 0600.
Defensive parsing — the CSV parser never throws on malformed input (missing fields default to empty string); a matter row with a missing name, an unparseable accrual_date, or an unparseable period_days is skipped and listed in the calendar’s “skipped rows” section rather than crashing the whole run.
Deterministic date math — SOL-date arithmetic is done in UTC epoch-days specifically to avoid local-timezone/DST off-by-one errors that could silently shift a deadline.
Secrets discipline.env and generated SOL-Reports/ output are git-ignored; no secrets or client data in the repo.

Distribution / AV trust

Known limitations / roadmap
This tool does mechanical date arithmetic only. It has no model of tolling, discovery-rule accrual, revival statutes, minority/incapacity extensions, or jurisdiction-specific limitations periods. period_days must be supplied correctly by the firm for each matter’s governing statute; the tool does not look this up.
– A bad accrual_date or period_days value causes that row to be skipped (not silently miscalculated) — but a *wrong-but-valid-looking* value (e.g. the wrong statute’s period) will silently produce a wrong deadline. Reviewers should treat every EXPIRED/APPROACHING flag as a prompt to verify, not a final answer.
AS_OF defaults to the machine’s local current date if unset; for audit-consistent output across a firm, set it explicitly.

Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.

Frequently asked questions about Statute of Limitations Tracker

What does the statute of limitations tracker do, and how does it compute an SOL date?

The Statute of Limitations Tracker keeps a running watch on the one date a litigation firm can never miss, the day a claim expires. For each matter, the statute of limitations tracker takes the accrual date, the day the claim arose, and a limitations period you configure, then computes the deadline by which suit must be filed. It holds that date for every matter at once and surfaces the ones coming due, so a firm is never relying on a lawyer to remember a cutoff that might be years out from the day the file first opened.

The workflow is short. You enter each matter with its accrual date and the applicable limitations period. You set a warning window, how far in advance you want to be alerted. The tool returns an SOL calendar plus alerts as dates approach. Because the periods are configurable per matter, a two-year personal injury claim and a longer contract claim each count by their own clock, and the tracker applies the right one to each file without anyone redoing the math for every case by hand.

The SOL calendar the tool maintains is also a record the firm should keep. The Internal Revenue Service reminds every business to preserve the documents behind how it operated, and its guidance on how long to keep records lays out retention periods running for years. A dated record showing that the firm was tracking every matter’s expiration, and acted before it ran, is exactly the kind of documentation worth holding onto long after a case closes.

Setup does not require replacing anything. You enter matters as they open, or import the ones you already have, and the tracker starts watching. There is no migration off your existing case system to survive first. You can read more about how the SOL calendar fits a litigation practice on the Statute of Limitations Tracker page.

The scope stays narrow on purpose. The tool computes and watches dates according to the accrual date and period you give it. It does not decide when a claim actually accrued or which limitations period governs, because those are legal determinations that depend on facts and law a lawyer weighs. What it removes is the risk that a correctly known deadline slips by unwatched, which is the failure that ends careers and forfeits clients’ claims for good.

The firm this is built for is the litigation practice that lives or dies by its deadlines and cannot afford to miss one. For that firm the danger is not the deadline it is thinking about, but the one that fell off everyone’s radar two years ago when the file opened and has been quietly counting down ever since. A calendar entry made at intake is easy to overlook by the time it matters. A tool whose only job is to hold every expiration date and push the approaching ones to the surface changes that, because the watching does not depend on anyone remembering to look. The date announces itself, on schedule, whether or not the lawyer who opened the matter is still thinking about it.

How does the statute of limitations tracker help a firm prove it never let a claim lapse?

The worst malpractice case a litigation firm can face is the one where a client’s claim died because a deadline passed unwatched. There is no defense on the merits, only the question of whether the firm had a system. The statute of limitations tracker is that system, and it produces the evidence that the system was running. Every matter carries a computed expiration date, and the approaching-deadline report shows, on any given day, exactly which claims are nearing their cutoff and getting attention right now.

That running record is what turns a claim of diligence into proof of it. If a client or a bar reviewer ever asks how the firm guarded against a missed deadline, the answer is a dated calendar and a history of alerts rather than an assurance that someone was keeping an eye on things. Keeping that record is also a plain business obligation. The Internal Revenue Service guidance on how long to keep records describes the general duty to retain the documents behind a firm’s operations, and a tracking system’s output belongs in that file alongside the matter records.

The escalating warning windows are what make the record credible rather than decorative. A single reminder on the day a claim expires is worthless. The statute of limitations tracker warns further out and then again as the date nears, so a deadline surfaces while there is still time to file, investigate, or bring in co-counsel. The report shows those warnings firing, which documents not just that a deadline existed but that the firm was acting on it well in advance.

Because the calendar and reports are the firm’s own, they remain available even if the firm later changes case-management tools. Nothing is trapped in a vendor’s system. You can see how the tracker fits with the rest of the practice lineup on the legal and professional page.

None of this substitutes for a lawyer knowing the law. A period entered wrong, or an accrual date misjudged, will still produce a wrong deadline, which is why the inputs stay in the lawyer’s hands and remain reviewable at any time. What the tool guarantees is that a deadline the firm knows about does not slip through for lack of watching, and that the firm can show, with dated records, that the watch was real and running the whole time.

The record also protects the firm in the ordinary course, not just in a crisis. Partners reviewing the pipeline can see at a glance which matters are approaching their limits and staff accordingly, moving investigation or filing work forward before it becomes urgent. That foresight is worth as much as the malpractice protection, because a claim filed comfortably ahead of its deadline is almost always a stronger claim than one rushed out in the final week. The report turns a scattered set of individual cutoffs into a single planning tool the whole firm can work from, which is the difference between managing a caseload and reacting to it. A pile of separate calendar entries never quite becomes that.

Where does our matter data live, and is it safe?

A deadline tracker holds a revealing dataset, the list of the firm’s active claims, when each arose, and when each must be filed. That picture of a firm’s entire litigation pipeline is confidential, and it is worth protecting from anyone outside the firm. The Statute of Limitations Tracker addresses that by keeping the data local. You enter matters, the tool computes and watches the dates on your own machine, and the calendar and reports are written there. The statute of limitations tracker does not push your matter list to a hosted service, so the map of what the firm is litigating stays inside the firm.

The Federal Trade Commission has written plainly about handling information like this. Its guide, Protecting Personal Information: A Guide for Business, lays out five steps: take stock, scale down, lock it, pitch it, and plan ahead. A tracker that reads only the accrual dates and periods it needs, rather than a client’s full file, fits the scale-down principle by holding the minimum required to do its job. There is no third-party copy of your case pipeline to account for, because the data never leaves your systems.

Local operation also keeps access under the firm’s own controls. The matter list, the SOL calendar, and the reports live inside the firm’s file structure, protected by the permissions already guarding those files. No separate cloud login has to be issued or revoked as staff come and go. You can read more about how the tool handles firm data on the Statute of Limitations Tracker page.

The honest caveat is the same one that applies to any local tool. Keeping the data on your machine removes the exposure of an outside vendor, but it does not secure a device left unencrypted or a report shared carelessly. The statute of limitations tracker keeps your matter data on your own equipment and adds no cloud copy of your caseload. The firm still owns the everyday security around that equipment, encryption, strong access controls, and sensible handling of exports. Local-first shrinks the risk of an outside breach. The firm’s own habits inside the office finish the job.

It also helps to know how little the tracker actually needs to do its work. Watching a deadline requires the accrual date and the limitations period, not the client’s medical history, financial records, or privileged strategy notes. That narrow appetite keeps the sensitive footprint small, which is the take-stock and scale-down thinking the Federal Trade Commission urges, put into daily practice. A system that never collects a sensitive document cannot be the thing that leaks it. For a firm weighing a cloud docketing service against a local tool for this one function, keeping the tracking on the firm’s own machines means the safeguards the firm already trusts for its case files cover the deadline data too, with no new outside party introduced into the picture and no fresh contract to read for a data-handling surprise. That control is exactly what a firm holding a full pipeline of pending claims should want over where the data sits.

How is the statute of limitations tracker different from a calendar, a spreadsheet, or a docketing suite?

Most firms track statute deadlines in one of three ways, and each has a weakness. A shared calendar holds a date but does nothing to compute it or escalate as it nears. A spreadsheet can do the math, but only if someone maintains it perfectly, and a dragged formula or a forgotten row fails silently. A full docketing suite handles all of it, but it is priced and built for large firms with staff to run it. The Statute of Limitations Tracker sits between those, a focused tool that computes the date, watches it, and escalates, at a firm-wide price a small practice can absorb without a second thought.

Where the data lives is part of the difference. A full docketing suite is typically cloud-hosted, which means the firm’s entire pipeline of pending claims sits on a vendor’s servers. Running the tracking locally keeps that pipeline on the firm’s own machine. The National Institute of Standards and Technology organizes sound security around identifying and reducing risk, and its Cybersecurity Framework stresses knowing your assets and limiting exposure. Fewer copies of your litigation calendar, held in fewer places, is a smaller surface to defend.

The tool is also deliberately narrower than a docketing suite. It watches statute deadlines and does not try to be case management, billing, and document storage in one login. For a firm that already has systems it likes, that focus is a feature, not a gap. You can see how it fits alongside the other practice tools on the legal and professional page.

The trade-off is honest. A large firm that wants every deadline, filing, and document in a single platform will prefer a full suite, and that is a reasonable choice. The statute of limitations tracker is for the firm that finds a calendar too dumb and a docketing suite too heavy, and that wants the one date it truly cannot miss computed, watched, and escalated, without paying for a platform it will half-use. It does the critical job well and stays out of the way of everything else.

The comparison depends on how a firm actually operates. A large firm juggling thousands of matters across many practice areas genuinely benefits from an integrated docketing platform with dedicated staff to run it, and for that firm the cost and complexity are justified. A small or midsize litigation practice does not need that machinery to solve the one problem that keeps trial lawyers up at night. It needs the statute of limitations tracker to compute the date, watch it, and shout before it is too late, and it needs that at a price that does not require a committee to approve. There is also a portability advantage in staying focused and local. Because this tool keeps its calendar and reports as the firm’s own files, the record of every tracked deadline stays with the firm regardless of what other software it runs. A practice can change case management, billing, or document systems without ever putting its statute-of-limitations record at risk, which is a kind of independence worth having.

How do the escalating warning windows keep a claim from slipping through?

The single most useful feature of the tool is the one that does the least glamorous work, the escalating warning window. A deadline that only announces itself on the day it falls is no protection at all, because by then the options are gone. The Statute of Limitations Tracker warns well ahead of an expiration and then escalates as the date closes in, so a claim surfaces while a lawyer still has room to investigate the facts, draft a complaint, or decide whether to bring in help. The point is to convert a silent, distant date into a series of prompts that grow louder as the risk grows.

Configurable warning windows let a firm match the lead time to its own workflow. A complex claim that needs months of investigation before filing warrants a longer runway than a straightforward one, and the tracker lets you set that per matter. The approaching-deadline report then gives the whole firm a single view of what is coming due and how soon, so nothing depends on one person happening to open the right file on the right day. The team sees the pipeline together, and no single absence leaves a claim unwatched.

That report doubles as a record. Because it captures which deadlines were flagged and when, it documents that the firm was watching and acting rather than merely hoping. The Internal Revenue Service guidance on how long to keep records speaks to the duty to preserve the documents behind a business’s operations, and a dated history of deadline warnings is part of that operational record. You can read more about configuring the warning windows on the Statute of Limitations Tracker page.

The honest limit is that the warnings are only as good as the dates behind them. If the accrual date or the limitations period was entered wrong, the tool will escalate confidently toward the wrong deadline, which is why those inputs stay in a lawyer’s hands and remain open to review. The statute of limitations tracker cannot practice law. What it can do is make sure that once a deadline is correctly known, it never sits unwatched, and that the firm holds a clear, dated record showing every claim was accounted for in time.

The escalation is what separates a real safeguard from a checkbox. A firm can set an early warning that gives the assigned lawyer a gentle heads-up, a second that copies a supervising partner, and a final one that no one can ignore, so a deadline cannot quietly die on a single person’s to-do list. The point is redundancy. By the time a claim is close to expiring, the tool has surfaced it more than once and to more than one person, which is precisely how a firm avoids the failure where everyone assumed someone else was handling it. Letting the firm set the runway per matter means the alerts stay meaningful, loud enough to act on and timed to when action is actually possible, rather than a stream of notices people learn to dismiss without reading.

Attributes Value
Deployment

Cloud

Platform

Web

License Type

Subscription

Billing Period

Monthly

Target Customer

Law Firms

Free Trial

Yes

Reviews

Be the first to review “Statute of Limitations Tracker”

Your email address will not be published. Required fields are marked *