How to calculate Offer Of Judgment Analyzer in Hawaii
7 min read
Published May 31, 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.
Quick takeaways
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
- Hawaii’s Offer of Judgment framework is governed by HRS § 631-20, which requires each party to make an offer of judgment in certain Hawaii civil actions.
- To calculate outcomes using DocketMath’s Offer Of Judgment Analyzer (US-HI), you’ll typically enter the offer amount, offer date/timing details, and the case result the statute measures against.
- This guide follows the general/default statutory period because no claim-type-specific sub-rule was found in the provided Hawaii materials.
- If the final judgment is more favorable to the offeror than the statute’s comparison, the offer may shift recoverable amounts/cost consequences; if it’s less favorable, the consequences can shift the other way. This analyzer helps you model those “more vs. less favorable” outcomes consistently.
Note: This post explains how the calculator works and which inputs typically drive results under HRS § 631-20. It’s not legal advice.
Inputs you need
Before you open DocketMath’s Offer Of Judgment Analyzer (Hawaii / US-HI) at /tools/offer-of-judgment-analyzer, gather the items that will determine the comparison the statute uses and the time window that controls whether the offer is treated as timely.
Use this checklist:
- Offer amount (the dollar figure you offered)
- Offer date (when the offer was served)
- Judgment outcome date (or the date you’re using as the decision date for modeling)
- Final judgment amount (the court’s ultimate award you’re comparing against the offer)
- Whether your side was the offeror or offeree (this matters for interpreting the analyzer’s “more favorable/less favorable” framing)
- Any relevant offset components (only if your case tracks them—e.g., when the “judgment amount” is not a single clean number)
- Timing window inputs (as required by the tool interface—commonly the analyzer asks for a statutory trigger date and/or the offer’s timing relative to it)
Because the provided statutory excerpt is the general offer-of-judgment rule, the timing period you model should use the general/default period unless your scenario involves a different, statute-driven deadline the tool supports.
Warning: Offer-of-judgment calculations are timing-sensitive. If the tool interface asks for a specific “trigger” date, use the one that corresponds to the procedural posture in your case record.
How the calculation works
DocketMath’s Offer Of Judgment Analyzer (US-HI) is built to turn HRS § 631-20 into a modeling workflow you can run with your case numbers—so you can test what happens if the offer amount changes, or if the offer’s timing changes.
1) What the statute requires (HRS § 631-20)
HRS § 631-20 provides that, in covered Hawaii civil actions, each party shall make an offer of judgment, and the offers and the ultimate judgment determine what consequences may follow.
Use the statute text here as your anchor point:
https://www.capitol.hawaii.gov/hrscurrent/Vol12_Ch0501-0588/HRS_0631/HRS_0631-0020.htm
Also, per the note in the brief: no claim-type-specific sub-rule was found in the provided Hawaii materials. That means:
- The analyzer workflow you’re using should rely on the general/default statutory period, not a special deadline tailored to a particular claim type.
2) The key comparison: offer amount vs. final judgment amount
Most DocketMath “offer of judgment” calculators ultimately ask a simple question:
- Is the outcome more favorable than your offer (for your side)?
- Or is it less favorable?
Once you enter:
- offer amount, and
- final judgment amount,
the analyzer classifies the result (conceptually, “more favorable” vs. “less favorable”) according to its built-in implementation of the HRS § 631-20 comparison logic.
A practical way to think about it:
| Relative outcome | Example pattern | How the analyzer typically treats it |
|---|---|---|
| Outcome favors offeror | Judgment exceeds the offer (or is otherwise more favorable under the tool’s comparison logic) | Labeled as “more favorable” category |
| Outcome favors offeree | Judgment is below the offer (or less favorable under the tool’s comparison logic) | Labeled as “less favorable” category |
| Edge cases | Numbers match, or “judgment amount” is complicated | Analyzer highlights a boundary so you can re-check inputs |
3) Timing: which statutory period controls
In addition to the amount comparison, timing determines whether the offer is treated as meeting the statute’s requirements.
Using the approach consistent with the brief:
- The analyzer should rely on the general/default period because no claim-type-specific timing rule was identified from the provided materials.
If the tool asks for a specific trigger date or other procedural date:
- Use the trigger date that corresponds to the timing framework in your case posture (for example, a date tied to when the statute’s timing clock begins for that stage of litigation).
4) What outputs you should expect
While the exact wording can vary by interface, the analyzer typically gives you:
- a scenario classification (more vs. less favorable relative to the offer),
- a modeled consequence/cost outcome range or result label tied to the statute’s framework, and
- a way to re-run the math by adjusting inputs.
If your litigation produced more than one offer (e.g., superseding or amended offers), run each offer as a separate scenario entry so you can compare modeled results side-by-side.
Pitfall: Don’t feed the analyzer a “final judgment” number that includes items that aren’t part of the judgment figure the tool expects. If your judgment has components (principal/fees/interest) and the form requires a single amount, use the component total that matches the calculator’s “final judgment amount” field.
Common pitfalls
Using the wrong timing window
- This guide’s rule is the general/default statutory period (because no claim-type-specific sub-rule was found in the provided Hawaii materials).
- If you accidentally apply a special deadline from another doctrine, your “timely vs. not timely” result may not reflect HRS § 631-20.
Interpreting the result with the wrong side context
- If the tool has a selector for whether you’re the offeror or offeree, make sure it matches your role.
- The same numerical outcome can be labeled differently depending on which side you select.
Mismatching the “judgment amount” definition
- Judgment totals can differ depending on what’s included (and how the case distinguishes amounts).
- Use the exact figure your judgment structure supports in the calculator’s “final judgment amount” input.
Not checking the “flip point”
- When the offer amount is close to the judgment amount, small input changes can flip the modeled classification.
- Run a quick sensitivity test by adjusting the offer amount in reasonable increments and observe when the classification changes.
Note: If the tool supports multiple scenarios, modeling at least 2–3 offers (for example, slightly below, at, and slightly above the expected judgment) helps you understand how sensitive the outcome is under HRS § 631-20.
Sources and references
- Hawaii Revised Statutes § 631-20 (Offer of judgment; general civil action offer framework)
https://www.capitol.hawaii.gov/hrscurrent/Vol12_Ch0501-0588/HRS_0631/HRS_0631-0020.htm
Start with the primary authority for Hawaii and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
Next steps
To get a reliable result from DocketMath’s Offer Of Judgment Analyzer (US-HI) at /tools/offer-of-judgment-analyzer:
- Enter the offer amount exactly as served (not an estimate).
- Add the correct offer date and the date fields the tool requests for statutory timing analysis.
- Confirm the final judgment amount you’ll compare against the offer.
- Run the base scenario, then run at least one adjustment scenario:
- change the offer amount by a realistic step (e.g., ±$5,000 or ±$10,000),
- keep dates constant to isolate the effect of amount differences.
- Review the outcome classification and any modeled cost/relief consequences shown by the analyzer, then reconcile them back to the case record.
Gentle disclaimer: This workflow models how DocketMath interprets inputs under HRS § 631-20. It doesn’t replace reviewing the full statute text and any record-specific details relevant to your situation.
