How to run Offer Of Judgment Analyzer in DocketMath for United States Federal
6 min read
Published October 29, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Step-by-step
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
This guide explains how to run Offer Of Judgment Analyzer in DocketMath for United States Federal (US-FED) matters using jurisdiction-aware rules. The analyzer is built around Federal Rule of Civil Procedure 68 (Fed. R. Civ. P. 68), which is the federal “offer of judgment” mechanism.
Note: The timing language in your jurisdiction data is the general/default rule because no claim-type-specific sub-rule was provided. The relevant baseline trigger is that the offer must be served “at any time more than 10 days before the trial begins.” (Fed. R. Civ. P. 68; see Cornell: https://www.law.cornell.edu/rules/frcp/rule_68)
1) Open the analyzer
- Go to the primary CTA: /tools/offer-of-judgment-analyzer
- Confirm the jurisdiction selector is set to United States Federal (US-FED).
- If you see a “jurisdiction-aware rules” indicator/label, leave it enabled.
2) Confirm you’re using Rule 68’s federal timing window
Before entering numbers, align your offer date with Rule 68’s baseline.
- Rule 68 default timing (US-FED):
“At any time more than 10 days before the trial begins, a party defending against a claim may serve on the adverse party an offer to allow judgment on specified terms, with the costs then accrued…”
(Fed. R. Civ. P. 68; Cornell source: https://www.law.cornell.edu/rules/frcp/rule_68)
Practical reminder: If the case schedule has changed (for example, the trial was continued), make sure the “trial begins” reference reflects the operative trial schedule, not an older date from a prior order.
3) Enter the offer terms you want the analyzer to evaluate
In the calculator, enter the inputs DocketMath requests to model the Rule 68 scenario. Common inputs typically include:
- Offer amount (the “specified terms” amount)
- Offer date (used to assess whether it is more than 10 days before trial begins under the default Rule 68 timing rule)
- Whether the offer is accepted (if the tool supports this input, it can affect the downstream cost/fee logic)
- Trial begin date (or the operative trial start date you supply)
- Estimated post-offer costs and/or attorney fees (if the tool supports cost/fee components)
If you don’t know costs/fees: run the analysis more than once (e.g., a low estimate and a higher estimate) so you can see how sensitive the results are to those assumptions.
4) Add the case-side numbers the analyzer needs to compare outcomes
Rule 68 analysis often turns on how the ultimate result compares to the offer terms.
To support that comparison, DocketMath’s analyzer generally benefits from:
- Expected or actual judgment amount (the figure you want compared to the offer amount)
- Party position, if the interface asks who made the offer or which side you’re modeling
Pitfall: The Rule 68 text you provided frames it as an offer made by a party “defending against a claim.” If you model the offer as though it were made by the wrong procedural side without reconciling that limitation, the projected consequences can be misleading.
5) Run with US-FED rules enabled
Once all inputs are filled:
- Click Calculate / Run analyzer
- Verify the jurisdiction indicator remains US-FED
- Review any rule-based flags or indicators (for example, an offer timing pass/fail style result, if shown)
If the tool flags that the offer date falls inside the 10-day window, expect the analysis to reflect reduced or different certainty under the default Rule 68 timing language.
6) Interpret the outputs (and re-run with adjustments)
DocketMath’s outputs typically help you evaluate a few dimensions such as:
- Timing compliance with the “more than 10 days before the trial begins” requirement
- Offer vs. judgment comparison (how close the outcome is to the offer terms)
- Projected cost/fee impact, based on the assumptions you entered
Use the outputs for scenario testing, not prediction.
If results look surprising, re-run with one controlled change at a time:
- Move the offer date slightly relative to the threshold (e.g., closer to—yet still more than 10 days before—trial) to test timing sensitivity
- Adjust the offer amount to test whether the “offer vs. judgment” comparison is driving the result
- Update the expected judgment amount if your estimate changes due to new developments
- Update cost/fee assumptions to align with the figure you actually entered
7) Save or export your scenario
If your DocketMath workflow supports it:
- Save the run as a scenario name (e.g., “Rule 68 timing check—Offer 45 days pre-trial”)
- Export results if you need to share them internally
This helps when comparing multiple versions (different offer amounts, revised trial dates, or alternative cost/fee estimates).
Common pitfalls
Avoid these mistakes when using Offer Of Judgment Analyzer in DocketMath for US-FED:
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
Capture the source for each input so another team member can verify the same result quickly.
Timing mistakes around the “more than 10 days” threshold
Rule 68’s baseline timing is explicit:
- “more than 10 days before the trial begins”
(Fed. R. Civ. P. 68; Cornell source: https://www.law.cornell.edu/rules/frcp/rule_68)
Common errors include:
- Pitfall: Using “trial date” from an outdated scheduling order.
- Pitfall: Entering an offer date that is within 10 days before trial begins, which can trigger a timing warning/flag under the default Rule 68 timing rule.
Modeling the wrong procedural posture
Rule 68’s text describes a defending party making an offer:
“a party defending against a claim may serve…”
(Fed. R. Civ. P. 68; Cornell source: https://www.law.cornell.edu/rules/frcp/rule_68)Pitfall: Running the analyzer in a way that treats the offer as if it were made by the wrong side without accounting for that framing.
Comparing mismatched dollar figures
- Pitfall: Comparing an offer amount to a “settlement value” that includes categories not reflected in your expected judgment amount input.
- Pitfall: Updating expected judgment while forgetting to update related cost/fee assumptions, resulting in inconsistent inputs.
Overconfidence in estimates
Even with accurate inputs, outcomes depend on what the court awards.
- Pitfall: Treating the tool’s projections as guarantees rather than scenario analysis.
Gentle reminder: This workflow guide is intended to show how to use DocketMath’s analyzer. It is not legal advice and should not be treated as a prediction of case outcomes. Use results to structure questions and review assumptions with qualified professionals.
Try it
Use this quick “sanity check” workflow to get immediate value from the analyzer:
- Offer amount
- Expected judgment amount
- Any available post-offer cost/fee inputs
- If timing is a concern, adjust the offer date closer to the threshold (while still keeping it more than 10 days before trial) and re-run
- If the “spread” is the concern, adjust the offer amount and re-run
For a fast jump back to the tool, use: /tools/offer-of-judgment-analyzer
