Why Damages Allocation results differ in Hawaii

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you run DocketMath’s Damages Allocation calculator for Hawaii (US-HI) and see different numbers across versions of a case (or across teams), the cause is usually not the math—it’s the inputs and the jurisdiction-aware rules that govern how those inputs are treated.

Here are the most common reasons results differ in Hawaii:

1. Different statute-of-limitations cutoffs are applied to different time windows

   • Hawaii’s general limitations period is 5 years.
   • The applicable general statute is Hawaii Revised Statutes § 701-108(2)(d), which provides the default period.
   • Important: In the jurisdiction data provided for this content, no claim-type-specific sub-rule was found. That means the calculator should treat § 701-108(2)(d) as the baseline default.
   • If one run effectively counts damages back 60 months and another counts back 70 months, the allocation will shift.

2. **Date fields are interpreted differently (service date vs. filing date vs. occurrence date)

   • Small input differences—like using the incident/occurrence date vs. the demand/filing date—can move the start/end of the “recoverable” window under the 5-year rule.
   • Because DocketMath’s recoverability logic is date-sensitive, you’ll see different outputs even with the same headline damages figure.

3. **Allocation basis differs (total claimed damages vs. category caps vs. prefiltered recoverable amounts)

   • Some workflows feed DocketMath using:

     • a single total damages number, or
     • category-level amounts (e.g., economic vs. non-economic), or
     • an already-pruned set of amounts that the user believes fall within the limitations period.
   • Those approaches don’t always align, so allocations can differ even when the “claim” sounds identical.

4. Partial-year accounting and rounding changes the effective month/day count

   • If one dataset treats the damages period using end-of-month logic and another uses exact days, you can end up with a different effective recoverable total.
   • Boundary dates (around “5 years plus a few days”) are where this shows up most.

5. Different assumptions about what is excluded, undisputed, or “already assumed recoverable”

   • Teams sometimes flag certain components as “assumed recoverable” or “excluded,” then rely on DocketMath to allocate only what remains.
   • That creates variance that looks like a rule change, but it’s often an input-state difference.

How to isolate the variable

To pinpoint what changed, run a controlled comparison in DocketMath. The goal is to hold everything constant except one variable at a time.

Use this checklist:

• Since no claim-type-specific sub-rule was found in the jurisdiction data provided here, the default should apply.

A diagnostic sequence that usually works:

1. Baseline run: Use the earliest and latest dates exactly as entered in each version.
2. Cutoff test: Change only the start-of-window date by ±30 days.

   • If results swing noticeably, the limitations window is the driver.
3. Rounding test: If your workflow supports it, switch between monthly and daily prorating.

   • If the outputs tighten or normalize, you likely have a precision/aggregation issue.
4. Input structure test: Convert inputs from category amounts → total damages (or the reverse) while keeping the underlying dollar totals consistent.

   • If allocations shift without a recoverability change, you’re seeing an allocation-basis effect.

Next steps

Once you isolate the variable, you can standardize your workflow so DocketMath runs become comparable.

1. Create a “date standard” for Hawaii runs

   • Pick one date definition as the anchor for the recoverability window and use it consistently.

2. Document the limitations assumption

   • For Hawaii, treat HRS § 701-108(2)(d) as the general default 5-year period, since no claim-type-specific sub-rule was found in the jurisdiction data provided.

3. Lock the input structure

   • Decide whether your team inputs:

     • total damages only, or
     • category breakdowns (and ensure everyone uses the same categories and totals).

4. Rerun with one change at a time

   • Start from your canonical dataset and rerun after each single modification until outputs match.

Primary CTA: /tools/damages-allocation

Gentle note: This is not legal advice—limitations and recoverability can depend on case-specific facts. Use this as a practical checklist for reconciling calculator input differences, not as a substitute for legal review.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules