How to run Offer Of Judgment Analyzer in DocketMath for Hawaii
6 min read
Published December 25, 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 DocketMath’s Offer Of Judgment Analyzer for Hawaii (US-HI) using jurisdiction-aware rules and the general/default offer timing framework under Hawaii Revised Statutes (HRS) § 631-20.
DocketMath is designed to help you model and compare outcomes—not to provide legal advice. Treat results as decision support, and verify any deadlines and assumptions using the case docket and any local scheduling orders.
Note (important): In Hawaii, the analyzer uses the general/default offer period from HRS § 631-20 because no claim-type-specific sub-rule was identified for customizing that timing.
1) Open the tool
- Start at the primary CTA: /tools/offer-of-judgment-analyzer
- On the tool page, make sure the jurisdiction setting is set to Hawaii (US-HI).
2) Choose what the analyzer needs (inputs)
DocketMath typically maps your situation into a few key fields. Depending on your screen, you’ll usually provide:
- Offer amount: the judgment/offered amount you want the tool to evaluate.
- Offer date (or similar wording): the date the offer was served or filed, as the tool requires.
- Case context fields: additional selections that determine how the tool models the consequence structure for the Hawaii framework.
If the interface shows labels such as “Offer date”, “Judgment date,” or timeline dates, enter the dates from the docket rather than estimating.
3) Enter the statutory timing inputs that drive the analysis
Hawaii’s HRS § 631-20 provides the baseline rule for offers of judgment in civil actions. The statute’s general structure is:
- “In any civil action, each party shall make an offer of judgment…” (general framework)
In practical terms for the analyzer workflow, this means:
- You should rely on the tool’s Hawaii logic tied to HRS § 631-20 for its timing-based computations.
- You must be careful with which date you enter, since the modeled outcome can shift if the offer timing changes.
Date entry guidance (to reduce errors):
- Use the offer filing/served date as the offer date (not the date you drafted the offer).
- If DocketMath includes a timeline panel, ensure any “deadline” or “comparison” dates align with your selected offer date and the judgment-related dates you input.
4) Configure the “outcome comparison” fields
Offer-of-judgment analyzers generally compare:
- What the offer proposed, vs.
- What the final judgment awarded (or what you’re modeling as the final outcome).
Enter:
- Final judgment amount (or your expected award amount, if your use case is forecasting)
- If the tool supports it, provide damage category breakdowns that match your case.
- If it only accepts one total amount, enter the total that best matches the judgment you’re modeling.
Tip: If the judgment in your case is entered as a combined number, input the combined number rather than trying to substitute separate components unless the tool explicitly asks for category detail.
5) Review the results and how they change with your inputs
After you run DocketMath, review two things:
- Outcome comparison: how the modeled result relates to the offer amount (e.g., whether the judgment outcome “beats” the offer in the tool’s logic).
- Timing-based notes: how the analyzer applies the offer period framework under HRS § 631-20.
To make sure you understand the sensitivity, test the model:
- Adjust one variable at a time.
- For example:
- Increase the offer amount and re-run.
- Change the offer date (only if the tool permits it) and confirm the timing-based notes update consistently.
Warning: Even small date differences (like an offer served near the end of a month) can materially change timing-based modeled outcomes. Always cross-check the analyzer’s computed timeline with the docket.
6) Validate the “Hawaii rule set” shown by the tool
Before relying on the output, confirm the tool is using the correct Hawaii framework. For this workflow, it should align with:
- Hawaii Revised Statutes § 631-20 (general offer framework)
Source: https://www.capitol.hawaii.gov/hrscurrent/Vol12_Ch0501-0588/HRS0631/HRS_0631-0020.htm
If the interface includes options like “rule assumptions” or timing frameworks, keep it aligned with the general/default offer period unless you have a clearly documented workflow that changes the logic.
Statute reference (as used in this guide):
HRS § 631-20 includes the general offer framework:
- Statute text (excerpt): “In any civil action, each party shall make an offer of judgment...”
Common pitfalls
Use this checklist each time you rerun the analyzer—these are the most frequent reasons the model’s results don’t reflect what happened in a Hawaii case.
- missing a required input
- using a stale rate or rule
- ignoring calendar or holiday adjustments
- skipping documentation of assumptions
Input accuracy pitfalls
- In this guide/workflow, the analyzer uses the general/default period from HRS § 631-20, because no claim-type-specific sub-rule was identified for customizing timing.
Timing-model pitfalls in Hawaii
Interpretation pitfalls
Pitfall: If court orders altered deadlines (extensions, scheduling changes, procedural amendments), the analyzer will only match reality if you update the relevant dates you enter.
Try it
Use this short “dry run” to confirm your workflow produces stable, sensible results.
- Open /tools/offer-of-judgment-analyzer
- Set jurisdiction to **Hawaii (US-HI)
- Enter:
- Offer date (served/filing date from the docket)
- Offer amount
- Final judgment amount (or the modeled award you’re comparing against)
- Run the analysis.
- Change only one variable:
- Increase the offer amount by 5–10%, then rerun
When you compare results, look for a logical pattern:
- If the final judgment amount is on the same side of the offer threshold, the “advantage” direction in the output should behave consistently.
- If the offer date changes, the analyzer’s timing-based notes should update in a coherent way under the HRS § 631-20 general/default framework.
If anything seems off—especially around timing—return to the docket dates, correct the relevant field(s), and re-run. This is usually the fastest way to align the model to reality.
