Statute of repose in Hawaii

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Hawaii’s general statute of repose is 5 years under HRS § 701-108(2)(d).

In practice, that means—subject to any narrowly tailored rule that may apply to your specific situation—certain criminal claims must be brought no later than 5 years after the applicable triggering event/date, even if the normal statute of limitations period would otherwise allow a later filing.

What you need to know

A statute of repose is often confused with a statute of limitations (SOL), but they work differently:

• Statute of limitations (SOL): typically counts forward from accrual (sometimes linked to discovery or the end of the offense, depending on context).
• Statute of repose: sets an outside cut-off measured from a specific event (often an act date or other measuring event), and it generally applies even if the claim wasn’t discovered yet.

For Hawaii, what we have (and what we don’t)

For US-HI, the jurisdiction data provided sets the general/default period as:

• 5 years under **HRS § 701-108(2)(d)

Also, important workflow clarification:

• No claim-type-specific sub-rule was found in the provided dataset.
  So treat 5 years as the default unless you have additional, clearly applicable authority that changes the analysis for your specific matter.

Why this matters for your timeline

When you use DocketMath, your main decision is:

• What “trigger date” will the tool use for the repose calculation?

Because repose is measured from a measuring event/date, the wrong trigger date can shift the deadline by months or years—changing whether a filing is timely under the repose cut-off.

Step-by-step

Use this workflow to apply Hawaii’s 5-year general repose period with DocketMath.

1) Choose the trigger date (the measuring event/date)

Pick the date your workflow treats as the repose trigger. The jurisdiction data provided confirms the duration (5 years) but does not supply a special measuring-event rule for specific claim types.

Common candidates (depending on charge framing and case facts) may include things like:

• the date of the relevant act,
• the last day of a relevant ongoing/continuing act (if applicable),
• or another fact date tied to the measuring event in your specific scenario.

Operational takeaway: document why your chosen trigger date matches the case facts you’re coding.

2) Set the jurisdiction and apply the default period

• Set jurisdiction to US-HI
• Apply the general/default repose period:

  • 5 years under **HRS § 701-108(2)(d)

Because the dataset did not identify claim-type-specific sub-rules:

• do not assume a shorter/longer period for a specific sub-category unless you have additional authority clearly supporting that change.

3) Convert the period into a deadline date

Your deadline date is calculated as:

• Repose deadline = Trigger date + 5 years

DocketMath performs this transformation for you once you input the trigger date and the period.

4) Compare the filing date to the deadline

Compute or retrieve:

• Filing date
• Repose deadline

Then evaluate:

• If Filing date ≤ Repose deadline → deadline not passed
• If Filing date > Repose deadline → deadline exceeded

5) Record your inputs so the workflow is explainable

For auditability, keep a short record of:

• jurisdiction (US-HI),
• statute (HRS § 701-108(2)(d)),
• period used (5 years),
• trigger date chosen,
• calculated deadline date from DocketMath.

Key statutes and citations

• HRS § 701-108(2)(d) — provides the general/default 5-year period referenced in the US-HI jurisdiction data.

Because the provided dataset did not identify any claim-type-specific sub-rule:

• HRS § 701-108(2)(d)’s 5-year period is used as the default workflow assumption,
• and should be overridden only with additional authority that clearly changes the controlling period or measuring event.

Common pitfalls

These are the most frequent issues that break repose calculations in real workflows:

• Using the wrong start/trigger date

  • Repose is measured from a specific measuring event/date.
  • If the start date is moved from “act date” to a “service/notice/discovery” date, the deadline can materially change.

• Assuming repose automatically equals SOL

  • SOL and repose can overlap in some scenarios, but their measuring points are not always the same.
  • A case can be barred by repose even when an SOL argument might still exist elsewhere.

• Ignoring the “default vs. claim-type-specific” uncertainty

  • The dataset explicitly notes no claim-type-specific sub-rule was found.
  • That means your automation should use 5 years by default, not because it’s universally applicable to every sub-category—only because it’s the default period provided.

• Computing the deadline but not comparing filing date

  • Some tools or teams generate a “deadline date” but forget the final comparison.
  • Build the workflow step that always checks filing date vs. deadline date.

Pitfall callout: Treating “filing-adjacent” dates (like notice dates or docket entry dates) as the statute’s measuring event is a common cause of incorrect repose deadlines.

Run the numbers

Use DocketMath’s statute-of-limitations calculator in US-HI mode to compute a repose deadline using the 5-year default from HRS § 701-108(2)(d).

Scenario A: Filing after the repose deadline

• Trigger date: Jan 15, 2019
• Repose period: 5 years
• Repose deadline: Jan 15, 2024
• Filing date: Mar 1, 2024

Result: Filing date is after the repose deadline → repose deadline exceeded.

Scenario B: Filing on or before the repose deadline

• Trigger date: Jan 15, 2019
• Repose deadline: Jan 15, 2024
• Filing date: Jan 15, 2024

Result: Filing date is on the repose deadline → deadline met for this simplified workflow.

Scenario C: Changing the trigger date changes the deadline

If your team initially used:

• Trigger date: Jan 15, 2019 → deadline Jan 15, 2024

But later corrects to:

• Trigger date: Jun 1, 2019 → deadline Jun 1, 2024

Impact: Correcting the trigger date extends the deadline by ~4.5 months, which can affect scheduling and filing decisions.

Recommended checklist for your inputs

To run it now: /tools/statute-of-limitations

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator