How to run Structured Settlement in DocketMath for Hawaii
7 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Structured Settlement calculator.
This guide walks you through running a Structured Settlement calculation in DocketMath configured for Hawaii (US-HI). The steps below focus on how to enter inputs, what the output means, and how jurisdiction-aware rules (including Hawaii’s general statute-of-limitations period) affect your setup.
Note: This is a workflow explanation for using DocketMath—not legal advice. Use the results as a decision-support tool and confirm assumptions for your specific situation.
1) Open the structured settlement calculator
Start at the primary call-to-action:
- /tools/structured-settlement
If your UI supports jurisdiction selection, choose Hawaii (US-HI). If the tool already defaults to US-HI based on your account or settings, verify the jurisdiction label is shown before you enter numbers.
2) Confirm the statute-of-limitations rule used by DocketMath (US-HI)
For Hawaii, the relevant general/default limitations period referenced for this tool is:
- 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
DocketMath should apply this as a general/default period because the provided jurisdiction data indicates no claim-type-specific sub-rule was found. In other words, you should treat 5 years as the baseline the calculator uses unless you override assumptions elsewhere in the tool.
3) Enter the timeline inputs
Structured settlement math typically depends on timing. In DocketMath, look for fields such as:
- Claim/trigger date (the date your timeline starts)
- Valuation or projection start date (sometimes the same as trigger date)
- Payment schedule start (when payments begin)
- Number of periods / years / payment cadence (monthly, quarterly, yearly)
If the calculator includes a step like SOL window or limit horizon, make sure the start date you use is consistent with how you’re interpreting the trigger. Because Hawaii’s default SOL is 5 years, your “available window” length may be computed automatically from the date you enter.
What you’re trying to control: whether your projected schedule aligns with the 5-year baseline horizon derived from HRS § 701-108(2)(d).
4) Enter the payment structure inputs
Next, define the structure of the settlement. Common fields include:
- Initial lump sum amount (if any)
- Periodic payment amount
- Periodic payment frequency (e.g., monthly vs. annual)
- Number of payments (or an end date)
- Escalators (if the tool supports step-ups, such as an annual increase)
As you change these values, watch how outputs update. For example:
- Increasing the periodic payment amount generally increases the total payout and any present-value figures.
- Changing frequency can increase or decrease totals and the discounting effect (more frequent payments may shift present value).
- Increasing the number of payments often extends the time-weighted value of the stream.
5) Set discount rate / interest / present value assumptions
Many structured settlement calculators require an assumption to convert future payments into today’s value (i.e., a discount rate). DocketMath may label these as:
- Discount rate
- Interest/return rate
- Present value method
If you have a specific actuarial or finance assumption you’re using, enter it consistently across scenarios. If not, keep the rate consistent between runs so you can compare “scenario A vs. scenario B” without the discount rate confounding the comparison.
6) Run the calculation and interpret outputs
After inputs are complete, click Calculate (or the tool’s equivalent).
Key outputs you should expect to see (labels may vary by calculator version):
- Total nominal payout (sum of all payments)
- Present value (discounted value)
- Schedule summary (often a table or chart)
- SOL-related window indicator (if the tool ties projections to Hawaii’s general/default period)
Because Hawaii’s default rule is 5 years under HRS § 701-108(2)(d), any SOL-window computation should reflect that baseline unless DocketMath provides an override or an alternate horizon input.
7) Use scenario comparisons (change one thing at a time)
To make the output actionable, rerun the calculator with controlled variations. A practical pattern:
- Scenario A: baseline payment schedule
- Scenario B: increase periodic payment by a fixed amount
- Scenario C: delay start date by 6 months
- Scenario D: adjust discount rate by 0.5%
Then compare outputs side-by-side. If DocketMath includes export options, save scenarios for later discussion.
8) Document assumptions for repeatability
Before you close the tool, capture:
- The dates you used (trigger/start/payment start)
- The payment structure (lump sum, periodic amount, frequency)
- The discount rate
- Confirmation that the limitation window used is the default 5-year baseline tied to **HRS § 701-108(2)(d)
This makes your work auditable and repeatable, especially if you need to rerun after new facts.
Common pitfalls
Structured settlement runs fail most often due to timing inconsistencies or mismatched assumptions. Watch for these issues:
- Using a claim-type-specific limitations period without evidence in the tool
The provided Hawaii guidance indicates no claim-type-specific sub-rule was found, so the tool should treat the 5-year general/default SOL as the baseline under HRS § 701-108(2)(d). - Confusing “trigger date” with “payment start date”
The timeline that drives SOL-window logic may be different from the timeline that drives cashflow projections. - Changing too many variables between runs
If you adjust date, frequency, and discount rate in one pass, you won’t know which change caused the output swing. - Mismatch between payment frequency and number of payments
Example: setting monthly payments with an end date intended for yearly cadence can distort totals. - Unclear discount rate assumption
Present value is sensitive to the discount rate. Switching rates between scenarios can make comparisons misleading.
Pitfall: If your run shows a “SOL window” number that doesn’t equal 5 years for Hawaii, double-check your selected jurisdiction (US-HI) and confirm you’re using the default/general horizon rather than an override.
Here’s a quick consistency checklist you can use before clicking Calculate:
| Input area | What to verify | Hawaii-specific baseline |
|---|---|---|
| Jurisdiction | US-HI selected | Required for HRS § 701-108(2)(d) baseline |
| SOL window logic | Default/general SOL used | 5 years |
| Trigger/timeline | Trigger date entered consistently | SOL uses the entered trigger |
| Payment cadence | Monthly/quarterly/yearly matches payment count | Avoids schedule distortion |
| Discount rate | Same rate used across scenario comparisons | Changes PV significantly |
Try it
If you want to test-drive the workflow, start with a minimal scenario in DocketMath and then refine:
- Open /tools/structured-settlement
- Set jurisdiction to **Hawaii (US-HI)
- Enter a single, simple structure:
- No lump sum (set to $0)
- One periodic payment amount
- One payment frequency
- Choose a start date and let the tool generate the schedule
- Keep the discount rate fixed
- Run the calculation and review:
- Total nominal payout
- Present value
- Any SOL-window indicator derived from 5 years under **HRS § 701-108(2)(d)
To explore sensitivity quickly, rerun only one change at a time:
- Change payment start date by +6 months
- Keep all else equal
- Observe how PV and totals react
If you later want to deepen your approach, you can return to the structured settlement tool and compare other input combinations using the same repeatability checklist above.
