How to run Damages Allocation in DocketMath for Hawaii

Step-by-step

This guide shows you how to run Damages Allocation in DocketMath for Hawaii (US-HI) using jurisdiction-aware setup. It’s written to help you produce consistent, auditable outputs—not to provide legal advice.

• Select Hawaii in the Damages Allocation tool.
• Enter the trigger dates and any caps or rates.
• Run the calculation and save the output.

1) Start the calculator in the right place

1. Open DocketMath and go to the Damages Allocation tool.
2. Use this primary CTA: Damages Allocation in DocketMath.
3. Confirm the jurisdiction context is set to Hawaii (US-HI) in the calculator UI (or select it if prompted).

2) Enter case fundamentals that affect allocation inputs

DocketMath’s Damages Allocation flow typically asks for several case details that influence how damages are allocated and organized. Gather the following before you start:

• Date(s) relevant to accrual (often the event date and/or other key timeline dates)
• Claim category / damages categories you’re allocating (e.g., different buckets you want split)
• Amounts per bucket (or inputs that let the tool allocate by weight/ratios, depending on your workflow)
• Any inputs tied to time limits (if the tool includes a “time window” or “include/exclude” based on an end date)

If you already have your damages broken into separate components, entering them as discrete amounts usually yields the most transparent results.

3) Set the Hawaii time limit rule (SOL) using the general default

When the tool asks for the statute of limitations (SOL) period or a “time window” rule, use Hawaii’s general default SOL.

For Hawaii, the general SOL period is 5 years, and the general statute citation is:

• Hawaii Revised Statutes (HRS) § 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 clarity about sub-rules:
No claim-type-specific sub-rule was found for this workflow, so you should apply the general/default 5-year period rather than trying to select a special sub-period. In other words: use the 5-year default SOL tied to the statute above.

4) Choose the calculation window (how the SOL affects results)

Once you set the SOL period to 5 years, you’ll usually need to define the start and/or end dates that determine the “included” damages period.

Common UI patterns include one or more of the following:

• Accrual date → tool computes an earliest included date = accrual + (SOL rule)
• Filing date / claim date → tool includes damages occurring within the lookback window
• Cutoff date → tool limits damages to that date range

How outputs change when you change these inputs:

• Moving the start date forward typically reduces the time span counted, often lowering time-dependent damages totals.
• Moving the end date forward typically increases the time span counted, often increasing totals.

DocketMath will reflect these changes in whatever breakdown it produces (for example, totals by bucket and/or totals within the SOL window).

5) Run the allocation

After you confirm:

• jurisdiction = US-HI
• SOL window = 5 years (per HRS § 701-108(2)(d))
• all damages component inputs are filled

Click Calculate (or the equivalent action). Then review:

• Total allocated damages
• Allocated amounts by bucket
• Any SOL-window-limited subtotals (if shown)

If the tool displays a timeline or filtered “included period,” confirm it matches the dates you intended.

6) Validate quickly using a “sanity check”

Before exporting or sharing results, do a quick consistency check:

• Are the included dates aligned to the 5-year window you expected?
• Do bucket totals match your inputs (within any allocation method rules)?
• Did the tool subtract excluded time periods (if it applies the SOL filter)?

If anything looks off, adjust dates first—SOL-window logic is typically the most common driver of unexpected changes.

Common pitfalls

Use these checks to prevent the most frequent errors when running Damages Allocation in Hawaii.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Capture the source for each input so another team member can verify the same result quickly.

Pitfall: Using the wrong SOL period (or inventing a sub-rule)

This workflow uses Hawaii’s general default 5-year SOL under HRS § 701-108(2)(d). Since no claim-type-specific sub-rule was found for this template, selecting a specialized period would likely create inconsistency.

Pitfall: Date inputs that don’t match the tool’s SOL-window logic

If DocketMath uses a pattern like:

• “lookback from filing date,” but you enter an “event date” as the filing date, or
• an “accrual date” that is actually the “discovery date,”

…then the included/excluded damages period can shift and change totals.

Pitfall: Mixing aggregated and component damages without aligning the structure

If you enter:

• a single total amount but the calculator expects component amounts (or vice versa),

…the allocations may look plausible while being internally inconsistent. Make sure your input structure matches the calculator’s expected structure.

Pitfall: Overlooking SOL effects on time-dependent amounts

Some cases have damages that change over time (even if your inputs are ultimately lump sums). If DocketMath applies time filtering, you need to reflect that through:

• the correct date range, and
• consistent bucket structuring.

Try it

Here’s a practical mini-workflow you can follow immediately inside Damages Allocation for Hawaii (US-HI).

Open the Damages Allocation calculator and follow the steps above: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Quick checklist (use these in order)

What to watch for in the output

After calculation, compare:

• Total allocated damages (overall)
• Any SOL-window-limited subtotals (if shown)
• Bucket splits (ensure each bucket aligns with your inputs)

If you rerun with a different filing/cutoff date:

• expect the SOL-limited subtotal to move first
• bucket splits may remain stable if you provided consistent component amounts

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