A practical workflow for jurisdiction-aware legal calculations (and how to document them)

When you're using a new product, the main question isn't "does it work?" - it's "can I trust what I get out of it?"

For legal calculations, trust usually comes from three things:

1. the right calculator for the question
2. the correct jurisdiction and rule set
3. a clean record of inputs and assumptions

This post gives you a workflow you can use from day one with DocketMath.

The workflow (7 steps)

If you do nothing else, do Step 2 (jurisdiction first) and Step 6 (calculation record). Those two steps prevent most expensive rework.

Step 1) Write the question in one sentence

Be explicit about what you're trying to answer. Examples:

• "What's the total through-date amount given these inputs?"
• "What's the deadline if the trigger event happened on this date in this jurisdiction?"
• "What changes if we move the start date by one day?"

That sentence becomes the header of your calculation record (template below).

Step 2) Choose the calculator, then lock jurisdiction

Start from the tools directory and pick the calculator that matches the question:

Explore calculators

Step 3) Normalize inputs before your first run

Your first run should be as unambiguous as possible.

If you're pulling inputs from a spreadsheet, copy them into your record first. The spreadsheet stays useful as a data container - your calculation record becomes the repeatable "truth".

Step 4) Run once for a baseline

The baseline run isn't about perfection. It's about creating a stable reference point.

After you have a baseline, you can troubleshoot cleanly:

• If the output feels off, is it inputs or assumptions?
• Did the calculator reflect the jurisdiction you intended?
• Are you mixing values from different sources?

Step 5) Sanity-check directionally (fast)

Take 60 seconds:

• Does the result move the way you'd expect if you adjust one obvious input?
• Are the dates and "through" cutoffs what you intended?
• Do any inputs look like they're in the wrong format?

Step 6) Capture a calculation record (copy/paste template)

This is how you turn a one-off calculation into a reusable artifact.

Calculation record
------------------
Question:
- (one sentence)

Tool:
- /tools/<tool-slug>

Jurisdiction:
- (e.g., CA)

Inputs:
- (bullet list; include dates and amounts)

Assumptions / notes:
- (bullet list)

Baseline run:
- Run date/time:
- Result summary:

Changes from baseline (one per run):
1) Changed:
   Expected impact:
   Observed impact:

2) Changed:
   Expected impact:
   Observed impact:

If you have to share the result with a teammate, a client, or a partner, this record is the difference between "trust me" and "here's what we used".

Step 7) Re-run only by changing one variable

When you want to explore scenarios, keep it systematic:

• change exactly one input
• write down what changed
• run again

This keeps you from accidentally mixing assumptions across scenarios.

Common mistakes (and how to avoid them)

Next steps

Browse guides

Explore tools

If you tell us what you're calculating (calculator + jurisdiction + scenario), we'll suggest the best starting point and what inputs to gather first.

Related reading

• Why we started the DocketMath blog
• Introducing Explain++: step-by-step calculation breakdowns

Why this reduces risk

Most calculation errors happen when inputs are incomplete or when the jurisdiction is set late in the process. By locking jurisdiction early and writing down assumptions before you run the tool, you cut the risk of silent drift and make the result explainable to anyone reviewing the matter.

The record you capture in Step 6 is also your change log. When a fact changes, you can rerun the calculation without rebuilding the logic from scratch, which saves time and keeps your team aligned on a single source of truth.

How to scale the workflow

If your team runs the same type of calculation repeatedly, turn the record template into a shared checklist. Use it in onboarding and matter kickoff so everyone collects the same inputs and documents the same assumptions. The more consistent your inputs are, the more reliable the outputs become.

A repeatable workflow

Start by setting the jurisdiction, then gather inputs into a single source of truth. Run the calculator once to get a baseline, and then rerun with sensitivity checks to understand how assumptions move the result.

Save both the inputs and the output in the matter record. This makes it easy to audit the calculation and to update the result when a rule or fact changes.

Finally, link the calculation to the supporting authority so the next reviewer can validate the same inputs without hunting for sources.

A repeatable workflow

Start by setting the jurisdiction, then gather inputs into a single source of truth. Run the calculator once to get a baseline, and then rerun with sensitivity checks to understand how assumptions move the result.

Save both the inputs and the output in the matter record. This makes it easy to audit the calculation and to update the result when a rule or fact changes.

Finally, link the calculation to the supporting authority so the next reviewer can validate the same inputs without hunting for sources.