Worked example: Damages Allocation in Hawaii

Example inputs

This worked example shows how DocketMath’s damages-allocation calculator can allocate amounts across claim components while using Hawaii jurisdiction-aware defaults. It’s designed for planning and estimation—not legal advice.

Scenario (fictional, for demonstration)

A claimant sues for damages arising from the same underlying event. For simplicity, we allocate the total demand into three buckets:

• A. Economic damages (e.g., repair costs, medical bills)
• B. Non-economic damages (e.g., pain and suffering)
• C. Statutory/penalty damages (where applicable)

Hawaii jurisdiction rule used for the time window

For this example, we apply Hawaii’s general statute of limitations (SOL) timeframe:

• General SOL Period: 5 years
• General Statute: Hawaii Revised Statutes § 701-108(2)(d)
  Source: https://codes.findlaw.com/hi/division-5-crimes-and-criminal-proceedings/hi-rev-st-sect-701-108/?utm_source=openai

Important scope note: Based on the information available for this worked example, no claim-type-specific sub-rule was found, so the default/general 5-year period is used across the board in this example.

Inputs you’d enter in DocketMath

Assume the following facts:

• Date of injury / accrual start: 2019-05-10
• Filing date: 2024-06-01
• Economic damages total demanded: $120,000
• Non-economic damages total demanded: $80,000
• Statutory/penalty damages total demanded: $20,000

To make allocation concrete, we also define what “damages within the limitations window” means for this planner run:

• Window filter method (estimation): allocate by proportional time coverage
• Coverage basis: damages assumed to accrue steadily over time (linear approximation)

How the tool uses the SOL window

DocketMath uses the Hawaii general 5-year SOL (HRS § 701-108(2)(d)) as the maximum lookback for damages you may be able to recover in this simplified planning model. The calculator then estimates what portion of each bucket falls within the limitations period based on your accrual start date and filing date.

Example run

Here’s the step-by-step run using DocketMath for US-HI (Hawaii).

1) Determine the limitations lookback window

Using the general SOL period:

• Filing date: 2024-06-01
• General SOL period: 5 years
• Lookback start (estimated): 2019-06-01

Because the provided accrual start date is 2019-05-10, the period from 2019-05-10 to 2019-06-01 is treated as potentially outside the limitations lookback in this estimation model.

2) Compute coverage ratio (time-based allocation)

Assume accrual runs from 2019-05-10 through 2024-06-01.

• Total accrual span (estimated): ~5 years and 22 days
• In-window span: 2019-06-01 through 2024-06-01

  • That’s essentially 5 years (minus the early partial period outside the lookback)

A practical way to express this is a ratio:

• Coverage ratio ≈ (in-window span) / (total accrual span)
• Approximate ratio: ~0.94

(DocketMath performs the exact day-count math based on the dates you input.)

3) Allocate each damages bucket using the coverage ratio

Using the demanded totals:

4) Show “potentially time-barred” portion (planning estimate)

Subtract the estimated within-SOL amount from the total demanded:

• Potentially outside SOL (estimate): $220,000 − $206,800 = $13,200

This estimate is for planning and allocation only. It does not determine actual recoverability in court; it helps quantify how the 5-year general SOL in HRS § 701-108(2)(d) could affect damages exposure.

5) Where the calculator result typically appears

After you run the calculation, DocketMath will generally provide:

• A within-SOL allocation per bucket
• A time-barred/filtered-out amount per bucket
• A jurisdiction indicator tied to US-HI and the selected SOL logic (general 5-year default)

If you’re also auditing timelines across issues, you can pair this with other tooling on DocketMath—for example, timeline-style calculations via /tools (see: /tools/damages-allocation).

Sensitivity check

Small changes in dates can move the allocation materially. Use this section to stress-test your numbers.

Change 1: Filing date pushed 30 days later

• Keep accrual start: 2019-05-10
• Move filing date: 2024-07-01 (instead of 2024-06-01)

What happens:

• The lookback window shifts forward.
• More of the early accrual period falls inside the 5-year window.
• The coverage ratio increases, raising within-SOL allocation.

Practical effect (directionally):

• Within-SOL total increases
• Potentially outside-SOL decreases

Change 2: Accrual start moved later by 60 days

• Keep filing date: 2024-06-01
• Move accrual start: 2019-07-09 (instead of 2019-05-10)

What happens:

• If accrual starts after the lookback boundary, nearly all damages fall within SOL.
• The time-filter becomes far less restrictive.

Practical effect:

• Coverage ratio rises toward ~1.00
• Time-filtered-out amount shrinks dramatically

Change 3: Different accrual pattern assumption

In this worked example, allocation uses a time-based proportional method. If you switch to a more event-driven workflow (where inputs represent discrete damages dates), the allocation can diverge.

Common scenarios where allocation changes substantially:

• One-time invoice/medical event near the end of the accrual period
• Ongoing harm that isn’t “steady” over time
• Discrete statutory triggers

Quick checklist for sensitivity testing

Run the calculator with toggled inputs and compare totals:

• Filing date ± 30 days
• Accrual start date ± 60 days
• Coverage method (if your workflow supports it)
• Re-run allocation totals per bucket and check percent shifts

A useful metric is % of total demand allocated within SOL:

• If that percentage swings by 5–10% with modest date movement, the allocation is timeline-sensitive, so you should refine factual accrual dates and damage event dates before relying on the estimate.

Related reading

• Browse the blog