How to calculate Offer Of Judgment Analyzer in Hawaii

Quick takeaways

• Hawaii’s Offer of Judgment procedure is governed by Haw. R. Civ. P. 68.
• The key gatekeeper is timing: an offer must be served “at any time more than 10 days before the trial begins.” (Rule 68 general/default timing—no claim-type-specific sub-rule was identified from the rule text you provided.)
• In DocketMath (US-HI), the analyzer typically focuses on two practical questions:

  1. Was the offer eligible under Rule 68 timing?
  2. Did the final outcome “beat” the offer for the relevant side?
• To run the calculator reliably, you’ll need at least: offer amount, trial start date, offer serving date, final judgment amount, and which side/role you’re analyzing (because the “better outcome” comparison can flip).
• If the offer is not served using the more-than-10-days-before-trial rule, treat any “beat” math as informational only until you confirm Rule 68’s qualifying requirements apply.

Disclaimer: This is an educational workflow for using the DocketMath calculator. It’s not legal advice, and you should confirm the full application of Haw. R. Civ. P. 68 in your case record.

Inputs you need

To calculate the Offer Of Judgment Analyzer in DocketMath for Hawaii (US-HI), collect the following facts from your case timeline and judgment paperwork.

Case + timing inputs (Rule 68 eligibility)

• Offer serving date (the calendar date the offer was served)
• Trial start date (the date the trial begins, as stated in your scheduling notice/order)
• Confirm it’s a Rule 68 offer (i.e., an offer “of settlement” / “to allow judgment to be taken,” consistent with Haw. R. Civ. P. 68)

Monetary outcome inputs (comparison / “beat” condition)

• Offer amount (the “money or property” or “effect specified” in the offer)
• Final judgment amount (the money amount actually awarded, or an equivalent figure if the relief is structured differently)
• Which party the analyzer should treat as the comparison beneficiary
  (This matters because “more favorable” depends on whose posture you’re evaluating—offeror vs. recipient, or the role selection in your DocketMath setup.)

Optional cost-related inputs (if your workflow tracks them)

Haw. R. Civ. P. 68 references “costs then accrued.” If your DocketMath workflow incorporates cost timing, consider adding:

• Costs accrued as of the offer date (if available)
• Costs after the offer date (only if your tool asks for it separately)

If you don’t track “costs then accrued,” you can still run the analyzer for the timing eligibility and beat-the-offer logic, but cost-shift conclusions may be limited.

How the calculation works

Below is the intended US-HI logic for the Offer Of Judgment Analyzer using Haw. R. Civ. P. 68 as the jurisdiction rule.

1) Confirm Rule 68 timing (eligibility gate)

Rule text (timing rule):
Haw. R. Civ. P. 68 allows an offer to be served “at any time more than 10 days before the trial begins.”
Source rule excerpt (Hawaii HRCP, Rule 68): https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.pdf

So the analyzer’s first check is whether the offer was served early enough:

• The offer serving date must be more than 10 days before the trial begins.
• Practically, that means the offer must be served no later than 11 days (or earlier) before trial, depending on calendar counting.

Illustrative example (calendar-based):

• Trial begins: June 20
• “More than 10 days before” means an offer served on June 10 is not early enough (that’s exactly 10 days before).
• An offer served on June 9 is early enough (more than 10 days before).

Important: Don’t assume business-day vs. calendar-day counting without matching how your case record reflects “service” and “trial begins.” Use the dates as recorded in the filings/orders.

No claim-type-specific override found:
Based on the rule text you provided, no claim-type-specific timing sub-rule was identified. Treat the more-than-10-days-before-trial timing as the general/default baseline for the calculator.

2) Determine whether the judgment “beats” the offer

Once timing eligibility is satisfied, the analyzer evaluates the beat condition: whether the final judgment outcome is more favorable than the offer for the relevant side.

Because DocketMath uses role selection, the comparison direction depends on your chosen posture:

• If you’re analyzing as the offeror, the key question is often whether the opponent’s outcome ended up worse than your offer.
• If you’re analyzing as the recipient, the key question is often whether the judgment ended up better than the offer.

Workflow implication:
If you select the wrong role (plaintiff vs. defendant posture, offeror vs. recipient, etc.), the “beat” result can flip.

3) Account for “costs then accrued” (but don’t overstate without the full text)

The rule text you supplied includes the phrase “with costs then accrued.” That signals that the cost consequences are tied to costs accumulated at (or as of) the offer timing.

However, your excerpt is truncated after:
“If within 10 days after …”
Because the remainder of the procedural consequence language wasn’t included in your materials, the safest approach is:

• Let the analyzer compute what it can: timing eligibility and the beat-the-offer comparison.
• For any final procedural consequence (cost-shifting outcomes), confirm the remainder of Rule 68 in your case record before relying on a specific triggered outcome.

4) What outputs to expect in DocketMath (US-HI)

In practical terms, the US-HI analyzer output should include items like:

• Qualifying Rule 68 timing? (Yes/No based on the more-than-10-days rule)
• Judgment beats the offer? (Yes/No based on amounts and role direction)
• Cost-shift indicator / estimate (if your tool is configured for “costs then accrued” inputs)

Common pitfalls

• Using the wrong “trial begins” date

  • If trial was continued or rescheduled, ensure trial start date reflects the actual scheduled start used in your case timeline.

• Serving exactly 10 days before trial

  • The rule requires “more than 10 days before”. A date exactly 10 days prior typically fails the eligibility gate.

• Inverting the role / benefit direction

  • If DocketMath’s role selection doesn’t match whether you’re treating the offeror vs. recipient comparison, the “beat” result can reverse.

• Mixing non-monetary “effect” with monetary comparisons

  • Rule 68 permits offers for “the money or property or to the effect specified in the offer.” If your case relief isn’t purely money, you may need to map the relief into a comparable figure for the calculator (or use whatever non-monetary structure your tool supports).

• Over-relying on partial rule text

  • Since the provided excerpt truncates the post-offer mechanics (“If within 10 days after …”), don’t treat the calculator’s cost-shift conclusion as definitive without confirming the full Rule 68 language as applied to your procedural posture.

Sources and references

• Haw. R. Civ. P. 68 (Offer of settlement / offer of judgment)
  Source (rule text): https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.pdf
  Provided key excerpt: “At any time more than 10 days before the trial begins, any party may serve upon any adverse party an offer of settlement or an offer to allow judgment to be taken against either party for the money or property or to the effect specified in the offer, with costs then accrued. If within 10 days after …”

Next steps

1. Start the calculation in DocketMath: /tools/offer-of-judgment-analyzer
2. Enter your dates first

   • Offer serving date
   • Trial start date
3. Confirm the offer type

   • Make sure your offer is styled/treated as a Rule 68 offer consistent with Haw. R. Civ. P. 68.
4. Enter amounts

   • Offer amount
   • Final judgment amount
5. Set the correct role/direction

   • Choose the posture that matches who should benefit from the “beat” condition.
6. Review the gating checks

   • If timing isn’t qualifying, treat cost-shift implications as contingent and verify with the full Rule 68 rule in your case file.
7. If your relief is non-monetary (“effect”)

   • Translate it into a comparable metric only if DocketMath supports that mapping in your workflow, and document your assumption.

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• Inputs you need for Offer Of Judgment Analyzer in Philippines — Input checklist with sourcing guidance