Docket & Deadline Calculator

$29.00

For the one-to-five-attorney litigation shop counting off a printed rules chapter and a wall calendar, instead of buying a whole practice platform to get one docketing screen.

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

Hand it one trigger date and the whole downstream docket comes back counted the way each rule actually counts.

21 calendar days for the answer, 30 court days for the discovery cutoff, weekends and holidays already handled.

$29/mo per seat. That covers the rule engine, the sorted docket, the CSV and JSON exports, and the docket.ics calendar file. Cancel any day, and every docket you already generated stays on your disk.

The day you counted wrong

You counted 21 days from service. It landed on a Saturday. The rule rolls forward to the next business day, so the date is Monday, unless Monday is a court holiday, and then it’s Tuesday.

Now do the same arithmetic for the discovery cutoff, which counts 30 court days and skips weekends outright rather than rolling off them. Different basis, different answer, same trigger date.

That distinction is where the mistakes live. A miscounted deadline doesn’t announce itself. It sits on the calendar looking correct right up until the day it isn’t, and the first two people who find out are opposing counsel and your carrier.

What it does with a trigger date

  1. Set the trigger. TRIGGER_DATE is the ISO date the clock starts from, service or filing or the order. TRIGGER_LABEL is the human name for it, and it’s what shows up in the calendar entries.
  2. Point it at your rules. RULES_FILE is a JSON array of {name, days, basis}, where basis is court or calendar. Leave it blank and it falls back to a built-in default set. Court holidays go in HOLIDAYS as comma-separated ISO dates.
  3. Run it. It computes each deadline, sorts the docket ascending by date, and writes DOCKET.md, deadlines.csv, deadlines.json, and docket.ics into OUTPUT_FOLDER.

What you get in the docket

  • A calendar rule gets counted the way the rule reads. Add the days, and if the result lands on a weekend or a listed holiday, roll forward to the next business day. You stop doing that step in your head at 5:40 on a Friday.
  • A court rule gets counted in business days only, skipping weekends and every date in HOLIDAYS entirely. The 30-day discovery cutoff stops being a 30-day guess.
  • Your rules live in a JSON file you own, not inside the software. When a division changes a response window, you edit one number and the entire docket recomputes.
  • docket.ics is a VCALENDAR file. It imports into Outlook, Google Calendar, or Apple Calendar, so the deadline reaches your assistant without anybody retyping a date.
  • DOCKET.md prints as a sorted table with the rule, the basis, the day count, the deadline, and the weekday. That last column is there because the weekday is where you catch the error.
  • deadlines.csv and deadlines.json fall out of the same run, so the same dates go into a spreadsheet and into whatever else the firm keeps without a second pass.
  • Config validation fails fast. A missing trigger date stops the run instead of quietly producing a docket that’s wrong.

Who should run this, and who shouldn’t

Built for the one-to-five-attorney litigation practice where the person counting the deadline is the same person arguing the motion. If you employ a full-time docketing clerk who already maintains a jurisdiction rules database, you don’t need this and you’d be moving backwards.

It also isn’t a rules service. It doesn’t know your local rules, doesn’t track a court’s quirks, and says so on every report it writes. It counts the rules you hand it. If you want a vendor to be responsible for knowing the rule itself, buy a rules service instead.

What it replaces

Two things, mostly. A printed rules chapter next to a wall calendar, which is free and is exactly as reliable as the Friday afternoon you use it on. And the docketing module inside Clio Manage or MyCase, which beat this in one way that genuinely matters: they carry maintained court-rules libraries by jurisdiction, and they tie the deadline to the matter, the file, and the bill.

You buy the whole platform to get that. If you already run one, keep it. If you don’t, this counts the days correctly for $29 a seat and writes you a calendar file.

Where the dates and the rules live

On your disk. RULES_FILE is read from the path you give it and never leaves the machine, and the only thing written is the docket, only under OUTPUT_FOLDER. Every write is checked against that root before it happens, and output lands at 0600 permissions, readable by your account and nothing else. No trigger date, no matter label, and no rule you wrote ever crosses a network.

Pricing, and how fast you get a docket

$29 a month per seat. No setup fee, no contract, no tier above it. After install, the first docket takes about as long as it takes to type one date and one folder path into a .env file, because that is the entire configuration. Cancel whenever you want, and every DOCKET.md you wrote stays exactly where you wrote it.

Security and privacy

Handles matter/case metadata (a trigger date, a label, an optional custom rule file). Security is designed in.

Principles
Local-first. RULES_FILE (if provided) 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 optional rule file is only read, never modified or deleted.
Least privilege. Reads RULES_FILE (if set), 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 docket can’t be written outside OUTPUT_FOLDER.
Fail-fast config validation — clear errors for missing/invalid TRIGGER_DATE/OUTPUT_FOLDER before any file is touched.
Restrictive permissions — the generated docket (DOCKET.md, deadlines.csv, deadlines.json, docket.ics) is written 0600.
Defensive parsing — malformed HOLIDAYS entries are silently dropped rather than crashing the run; a malformed RULES_FILE (bad JSON, missing fields, invalid basis) fails fast with a clear error rather than silently computing wrong deadlines.
Secrets discipline.env and generated Docket/ output are git-ignored; no secrets or client data in the repo.

Distribution / AV trust

Known limitations / roadmap
NOT legal advice. This tool performs pure date arithmetic against rules you supply (or the small illustrative default set). It has no knowledge of jurisdiction-specific local rules, standing orders, or court-specific computation methods (e.g. some courts exclude the trigger day, some don’t; some define “day” differently near a deadline that falls on a court holiday unique to that courthouse). Every computed deadline must be verified against your jurisdiction’s rules before you rely on it.
Holiday calendar is whatever you supply. HOLIDAYS is a flat, manually maintained list — it does not automatically track federal, state, or county court holiday calendars, and does not update itself year to year.
UTC-normalized dates. All date math is done against UTC-midnight “calendar day” values to avoid daylight-saving arithmetic errors; this is a computation convention only and has no bearing on legal timekeeping in any jurisdiction.
RULES_FILE is trusted input. It’s expected to be a file you (the operator) created or reviewed; it’s read and its structure validated (JSON array of {name, days, basis}), but its *content* (the actual day counts and bases) is not checked against any legal standard.

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

Frequently asked questions about Docket & Deadline Calculator

What does the Docket & Deadline Calculator do, and how does it compute a docket?

The Docket & Deadline Calculator turns a single triggering event into every deadline that flows from it. You tell the tool what happened and when, a complaint was served, a motion was filed, an order came down, and you pick the rule set that governs that kind of matter. From there it computes the full chain of downstream dates and hands you a docket you can drop straight onto a calendar. The point is to take the deadline math off a lawyer’s desk, where a miscounted day can cost a client their case, and give it to a defined engine that counts the same way every time.

The workflow is three steps. Enter the trigger event and its date. Choose the applicable rule set, which can be configured per matter type so a civil case and a probate matter each count by their own clock. Get the full computed docket back. Because the output exports as an ICS-ready deadline list, those dates go into Outlook, Google Calendar, or whatever the firm already runs, rather than living in a separate silo nobody checks. The Docket & Deadline Calculator does the arithmetic and leaves the calendaring to the tools your staff already open every day.

That computed docket is also a record, and records have to be kept. The Internal Revenue Service reminds every business, law firms included, to hold onto its supporting records, and its guidance on how long to keep records sets out retention periods running from three years to indefinitely depending on the document. A dated docket showing how each deadline was derived is exactly the kind of business record worth preserving, both for the matter file and for the firm’s own protection later on.

Setup does not require a consultant or a migration. You install the tool, configure the rule sets your practice actually uses, and start entering triggers. There is no rip-and-replace of your calendar or your case management system. You can read more about how the docket fits into a matter workflow on the Docket & Deadline Calculator page.

The honest scope is narrow on purpose. The tool does not practice law and it does not know your local rules better than you do. It counts days according to the rule set you give it, applies the court-day and holiday logic you configure, and shows its work. A lawyer still owns the rule sets and still reviews the output. What changes is that the counting itself, the part most prone to a tired-Friday error, becomes repeatable, auditable, and fast, so a missed date stops being one distraction away from happening.

For the solo or small firm this is aimed at, the alternative has usually been a wall calendar and a lot of hope. A dedicated docketing clerk is a luxury most two- and three-lawyer shops cannot justify, so the counting falls to whoever opened the file, often between a deposition and a client call. That is precisely when a court-day period gets counted as calendar days or a holiday gets missed. Moving the arithmetic into a tool that never gets tired or interrupted takes the single most error-prone task in a small practice and makes it boring, which is exactly what you want a deadline to be. Boring deadlines are the ones that get met without drama.

How does the Docket & Deadline Calculator help a firm keep a defensible record of its deadlines?

Missing a deadline is one of the most common ways a firm ends up facing a malpractice claim, and the defense against that is not just hitting the date, it is being able to show how the date was calculated. The Docket & Deadline Calculator builds that proof as it works. Every docket it produces records the trigger event, the rule set applied, and the resulting dates, so the firm has a written derivation for each deadline rather than a number someone remembers typing into a calendar late one afternoon.

That written derivation matters when a deadline is ever questioned. If opposing counsel disputes a filing date or a client later asks why a step happened when it did, the firm can point to the computed docket instead of reconstructing the reasoning from memory. The record is contemporaneous, created at the moment the deadline was set, which carries far more weight than an after-the-fact explanation. Keeping that record is also a plain business obligation. The IRS guidance on how long to keep records makes clear that businesses are expected to retain the documents that support how they operated, and a firm’s docketing history sits squarely in that category.

Because the docket exports to a standard ICS file, the record does not depend on the tool staying installed forever. The dates live in the firm’s own calendar system, and the source docket can be filed with the matter. That separation means the proof survives even if the firm later changes software. You can see how the tool fits next to the rest of the practice lineup on the legal and professional page.

The Docket & Deadline Calculator does not promise a firm will never miss a date. No tool can, because a deadline entered against the wrong rule set will still compute the wrong answer confidently. What it does is remove the arithmetic errors, apply the same holiday and court-day logic every time, and leave a dated trail showing the work. For a solo or small firm without a dedicated docketing clerk, that combination, consistent math plus a retained record, is the practical core of deadline discipline. The lawyer supplies the judgment about which rules apply. The tool supplies the counting and the paper trail that backs it up when someone asks how a date was reached.

The retained docket also changes the tone of a hard conversation. When a client is anxious about whether a step was handled on time, showing them the dated computation, the trigger, the rule, and the resulting date, replaces reassurance with evidence. It is the difference between saying the work was done and showing it was. There is a practical filing habit worth adopting alongside the tool. Save the exported docket into the matter folder the day it is created, so the record travels with the case rather than living only inside the calendar. Combined with the ICS export that feeds the working calendar, that gives the firm two copies serving two purposes, one that drives the reminders and one that documents the reasoning, without any extra data entry.

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

A docketing tool touches real client information, the parties to a matter, the nature of the case, and the dates that reveal a firm’s litigation strategy. That makes the question of where the data lives a fair one. The Docket & Deadline Calculator answers it by keeping the work close. You enter matter details, it computes the docket, and the result exports to your own calendar and case file. The tool is not a hosted service harvesting your matter list into someone else’s database, so the sensitive picture of who you represent and what you are litigating stays inside the firm.

Handling that data responsibly is something the Federal Trade Commission has written plainly about. Its guide, Protecting Personal Information: A Guide for Business, sets out five steps any firm can follow: take stock of what you hold, scale down to what you need, lock it, pitch what you no longer require, and plan ahead for trouble. A docket calculator that reads only the trigger and the rule set, and does not demand a client’s full personal file to do its job, fits the scale-down principle by design. It asks for the minimum it needs to count days and nothing more.

The calculator also leaves access control where it belongs, in the firm’s hands. Because the computed docket and any exported file live in the firm’s own systems, they inherit the permissions already protecting those systems. There is no separate web login for a departing employee to retain and no third-party portal to worry about. You can read more about how the tool handles firm data on the Docket & Deadline Calculator page.

The limit is worth naming. Keeping the data local shrinks the exposure to an outside vendor, but it does not secure a machine the firm neglects. An unencrypted laptop or a shared login undoes the benefit. The Docket & Deadline Calculator keeps your matter data on your own equipment and does not add a cloud copy of your case list. The everyday security around that equipment, encryption, strong passwords, and controlled access, remains the firm’s job, and it is what turns local operation into protection you can actually count on rather than a slogan.

It is also worth being clear about what a docketing tool cannot see. Because the calculator works from the trigger event and the rule set rather than the full client file, it never ingests the medical records, financial statements, or privileged correspondence that make a matter file sensitive. The data it does touch, party names and dates, is the least of what a firm holds, which keeps its exposure low from the start. That aligns with the take-stock step in the Federal Trade Commission guidance, which asks a business to know exactly what personal information it keeps and where. For a firm comparing a local tool against a cloud docketing service, keeping the computation on the firm’s machines means the firm’s existing safeguards cover the docketing data too, with no new outside party added to the chain of custody.

How is the Docket & Deadline Calculator different from LawToolBox or CompuLaw?

The established names in deadline calculation, LawToolBox and CompuLaw among them, are capable tools, but they are priced and built for firms larger than the solo or two-lawyer shop. LawToolBox runs on a per-user subscription that adds up quickly across a small team, and the free workaround, an AI chat tool plus Google Calendar, is exactly the kind of improvisation that produces a confidently wrong date. The Docket & Deadline Calculator sits in the gap between them, a defined rules engine at a small-firm price of a few dollars a seat rather than the enterprise tier.

Price is only part of the difference. The bigger platforms are cloud-hosted, which means your matter data and docketing activity flow through a vendor’s servers. For a firm that would rather keep its case information close, running the calculation locally is a real distinction. The National Institute of Standards and Technology organizes sound security thinking around identifying and reducing risk, and its Cybersecurity Framework covers identifying assets, protecting them, and detecting problems. A tool that keeps matter data on the firm’s own machine gives the firm fewer external dependencies to reason about under that framework.

The tool is also deliberately narrower than a full docketing suite. It does not try to be case management, billing, and document storage rolled together. It computes deadlines, exports them, and stops. For a firm that already has case management it likes, bolting on a full competing platform just to get deadline math is overkill. You can see how the calculator fits alongside the other practice tools on the legal and professional page.

The trade is honest. The bigger platforms ship with vast libraries of pre-built jurisdiction rules maintained by their vendors, and a firm that needs fifty jurisdictions out of the box may still want one of them. The Docket & Deadline Calculator expects you to configure the rule sets your practice actually uses, which is less work than it sounds for a firm that lives in a handful of courts. In exchange you get local operation, a small per-seat price, and a tool that does one job well instead of a suite you pay for in full and half-use in practice.

The comparison also depends on how a firm works. A large litigation shop juggling dozens of jurisdictions and hundreds of active deadlines genuinely benefits from a vendor-maintained rules library and a dedicated support line, and for that firm the enterprise price can be worth paying. A small firm that practices in two or three courts is paying for a fleet of features it will never touch. The Docket & Deadline Calculator is built for the second firm, the one that needs the counting to be right and the price to be sane. Because this tool exports to a standard ICS file and files its dockets locally, the firm’s deadline record is portable from the first day, so you are never locked in by the format your own history is stored in. That portability is a quiet form of protection every small firm should insist on before it commits.

How does the tool handle court-day versus calendar-day math and holidays?

Deadline math goes wrong most often on two details, whether a period counts in court days or calendar days, and how holidays and weekends shift a due date. The Docket & Deadline Calculator is built around exactly those details. Its rule sets let you specify, per matter type, whether a given period runs on court days that skip weekends and holidays or on straight calendar days, and it applies that choice consistently across every deadline in the chain. A period that should have skipped a three-day holiday weekend does, every time, without a person remembering to check the court’s calendar.

Configurable rule sets are what make this hold up across different kinds of work. A civil litigation matter, a probate filing, and an appellate deadline each count time differently, and hard-coding one firm’s assumptions would break the moment the practice took a different case. Instead you define the rule set once for each matter type, and the tool applies it again. When a rule changes, you update it in one place rather than re-teaching every lawyer the new count. The computed docket then shows which rule set produced which dates, so the logic is visible rather than buried in someone’s head.

That visibility ties back to recordkeeping. Because each docket documents the trigger, the rule set, and the holiday logic applied, it doubles as a retained record of how the firm calculated its obligations. The IRS guidance on how long to keep records speaks to the general duty to preserve the documents behind how a business operated, and a firm’s dated deadline computations belong in that file. You can read more about configuring rule sets on the Docket & Deadline Calculator page.

None of this removes the need for a lawyer to get the rule set right in the first place. The tool counts faithfully according to what it is told, which means a wrong rule produces a wrong date with the same confidence as a right one. That is why the rule sets are configurable and reviewable rather than hidden away. The lawyer owns the rules. The Docket & Deadline Calculator owns the counting, the holiday shifts, and the court-day versus calendar-day distinction, and it applies them the same way on every matter so the mechanical part of the work stops being the risky part.

Holidays are where a lot of do-it-yourself counting quietly fails, because court holidays are not always the same as bank or federal holidays, and a single overlooked closure can push a deadline to the wrong day. The tool applies the holiday list you configure against every period, so once a court’s calendar is set up correctly, no one has to remember it again for that jurisdiction. When a new closure is added, you enter it once and every future computation respects it. The same discipline helps when a firm expands into a new court. A lawyer configures the rule set and holiday calendar once, reviews a few known deadlines to confirm the setup, and then trusts the tool, so the learning happens in a calm moment rather than under a filing deadline.

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 “Docket & Deadline Calculator”

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