How Settlement Allocator rules vary in Hawaii

What varies by jurisdiction

Settlement allocation rules aren’t one-size-fits-all because the “who gets what” math can depend on the forum’s procedural framework—especially when the allocation is tied to class action membership, notice, and settlement administration.

For Hawaii (US-HI), the primary rules source you should anchor to is Haw. R. Civ. P. 23 (Hawaii Rules of Civil Procedure, Rule 23). You can find the rule text here: https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.htm.

Using DocketMath’s Settlement Allocator, (tool: /tools/settlement-allocator), the calculator still performs the core allocation mechanics. What changes is the jurisdiction-aware layer—i.e., how DocketMath maps and verifies your inputs against the Hawaii procedural expectations (without changing the underlying arithmetic).

Hawaii-specific practical impact (what changes the allocator inputs)

Even when the allocation formulas are similar across jurisdictions, jurisdiction can affect which parameters you must confirm before running the allocator. In Hawaii:

• Governing procedural framework: Settlement treatment in a class context should be tied to Haw. R. Civ. P. 23.
  Source: https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.htm
• No claim-type-specific sub-rule detected: Based on the Hawaii materials referenced for Rule 23, no claim-type-specific sub-rule was found that would create different timing/notice rules inside Rule 23 based on claim category.
  Practical consequence: when your rule-mapping needs a “default” period, use the general/default period rather than searching for claim-type-specific carveouts within Rule 23.

How DocketMath should be configured for Hawaii

When you run /tools/settlement-allocator for US-HI, configure the jurisdiction-aware rules to:

• identify the governing anchor as Haw. R. Civ. P. 23, and
• treat timing/notice logic as general/default where no claim-type carveout is found.

From a workflow standpoint, the “variation” for Hawaii is less about a different arithmetic formula and more about the verification step that determines which parameters are valid for your run (e.g., the class definition and the eligible member roster you rely on).

What to verify

Before relying on the results from DocketMath’s Settlement Allocator, verify that your inputs match what Hawaii’s Rule 23 framework expects for class settlement administration. This isn’t legal advice—use this as a practical checklist to improve input quality and auditability.

1) Confirm the settlement is governed by Rule 23 class action mechanics

DocketMath can calculate allocations, but the jurisdiction-aware justification depends on whether the settlement is actually operating under class action mechanics.

Checklist:

• Settlement involves a class (not merely individual party resolutions)
• Settlement documentation references or is consistent with Haw. R. Civ. P. 23 proceedings
• The allocation is intended for class members under the class settlement framework

Source to use: Haw. R. Civ. P. 23
https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.htm

2) Use the general/default period (no claim-type carveout detected)

Per the note in the brief: no claim-type-specific sub-rule was found in the Hawaii Rule 23 materials provided. That means your configuration should generally not branch into different “default periods” depending on claim category.

Operational guidance for your DocketMath run:

• If DocketMath prompts for a “rule period” or similar timing input, select the general/default period mapped to Rule 23
• Avoid applying claim-type-specific timing logic in Hawaii unless you later locate an explicit express rule text or an order-specific instruction in the settlement record

3) Validate allocator inputs against Rule 23 class boundaries

Even if the number of claimants is the same, different class boundaries can change the outcome.

Verify:

• The class definition used in your dataset aligns with the settlement’s Rule 23 class concept
• Any time-limited eligibility language in the settlement aligns cleanly with the default timing approach you used
• Claimant data you feed into DocketMath (units/categories/damages measures) corresponds to the class membership scope you intend to allocate to

4) Confirm the court approval context reflected in your settlement data

Settlement allocations rely on what your record says the court and parties approved—so ensure your input set is consistent with Rule 23 settlement administration.

Verify:

• Settlement materials you rely on describe the allocation/eligibility process in the context of Rule 23 class settlement proceedings
• Your allocation mechanics mirror the settlement’s stated rules for what data qualifies and how values are determined

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations

Sources and references

• Haw. R. Civ. P. 23 (Hawaii Rules of Civil Procedure), Rules text (Rule 23). https://www.courts.state.hi.us/docs/court_rules/rules/hrcp.htm