Worked example: Alimony Child Support in Hawaii
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Below is a worked example showing how you can use DocketMath’s alimony-child-support calculator for Hawaii (US-HI). This example focuses on the general statute of limitations (SOL) framework that the tool uses to translate a payment dispute into a time window that you can reference in a filing workflow.
Note: This walkthrough explains how a calculator and ruleset may be applied to a scenario. It’s not legal advice, and it doesn’t replace review by a qualified Hawaii family-law professional.
You can run the same type of analysis here: Primary CTA: /tools/alimony-child-support
Scenario (facts you would enter)
Use these as the “example inputs” for the calculator:
- Jurisdiction: Hawaii (US-HI)
- Payor’s payment type (context): combined alimony + child support calculation context
- Alleged underpayment period start date: January 1, 2018
- Alleged underpayment period end date: December 31, 2021
- Date the issue is raised (filing/claim trigger date): March 15, 2024
- Frequency assumption for calculation: monthly
- Amount basis (for demonstration):
- Child support “target” amount: $1,200 / month
- Alimony “target” amount: $400 / month
- Actual paid (for demonstration):
- Child support actually paid: $1,050 / month
- Alimony actually paid: $400 / month
Example run
Now run the example through DocketMath (alimony-child-support) using the inputs above. Since the tool is designed to evaluate arrears within the SOL window, the key outputs typically break into:
- Months included by SOL window
- Monthly shortfall
- Total shortfall inside the window
- Notes about excluded months (outside the SOL window)
Step 1: Identify the Hawaii SOL rule the tool is applying
For Hawaii, the jurisdiction configuration uses a general/default SOL period:
- General SOL Period: 5 years
- General Statute: Hawaii Revised Statutes (HRS) § 701-108(2)(d)
Important clarification: No claim-type-specific sub-rule was found in the provided jurisdiction data. That means the calculator treats the SOL window as the general/default 5-year period, rather than narrowing it based on a specific support-claim category.
Step 2: Convert the trigger date into a “lookback” time window
With a trigger date of March 15, 2024 and a 5-year general SOL:
- Lookback window begins: March 15, 2019
- Practical meaning: payments before March 15, 2019 are outside the general/default SOL window used by the calculator.
So, in this worked example, the calculator’s “covered period” will generally include months that fall on/after the boundary and exclude months in 2018 and early 2019 (depending on the tool’s month allocation convention).
Step 3: Define which months are counted (month-allocation convention)
Your alleged period runs:
- January 2018 → December 2021
Because the SOL boundary is mid-March 2019, early 2019 months may be excluded or partially allocated.
To keep this example concrete, we’ll use this counting approach:
- 2018: excluded (fully outside the 5-year window)
- Jan–Mar 2019: excluded or partially excluded depending on the tool’s day-to-month handling
- Apr 2019–Dec 2019: included
- All 2020: included
- All 2021 (through Dec 2021): included
Step 4: Compute the monthly shortfall inside the window
From the demonstration inputs:
Child support
- Target: $1,200 / month
- Paid: $1,050 / month
- Shortfall: $1,200 − $1,050 = $150 / month
Alimony
- Target: $400 / month
- Paid: $400 / month
- Shortfall: $400 − $400 = $0 / month
Total shortfall per month (combined):
- $150 + $0 = $150 / month
Step 5: Multiply by the included month count
Using the example month counts implied by the included months:
- Apr–Dec 2019: 9 months
- 2020: 12 months
- 2021: 12 months
- Total included months: 33 months
Total shortfall inside the SOL window:
- $150 × 33 = $4,950
Step 6: Interpret how the tool’s “covered time” changes the output
The core jurisdiction-aware effect is this:
- The same alleged underpayment (2018–2021) does not automatically produce a full-period arrears total.
- Instead, DocketMath restricts arrears to the months within the general/default 5-year SOL window based on HRS § 701-108(2)(d).
- As a result, months outside the boundary (e.g., most of 2018 and early 2019) do not contribute to the totals shown in the SOL-bounded output.
Practical “what to look for” in the results panel
When you review the results in DocketMath, look for elements like:
- Covered period (months/days within the SOL window)
- A calculation summary showing arrears inside the window for:
- child support within the window
- alimony within the window
- combined shortfall within the window
- Explanatory text confirming that the SOL period used is the general/default 5-year rule (consistent with the lack of a claim-type-specific sub-rule in the jurisdiction data)
Warning: If you change the trigger date (for example, from March 15, 2024 to May 1, 2024), the covered months can shift, and that typically changes the “arrears within window” total—even if the monthly shortfall remains the same.
Practical checklist for your own run
- Confirm jurisdiction is Hawaii (US-HI)
- Enter the alleged underpayment start and end dates
- Enter the trigger date (date the issue is raised)
- Input monthly target amounts and monthly actual amounts
- Verify that the SOL basis shown by the tool is the general/default 5-year period (because no claim-type-specific sub-rule was found)
Sensitivity check
This example is designed to show what changes the result most: (1) the SOL boundary (trigger date) and (2) the monthly shortfall (actual vs. target payments).
1) Change the trigger date by ~6 weeks
- Original trigger date: March 15, 2024
- New trigger date: May 1, 2024
With a 5-year window, the lookback start shifts from about March 15, 2019 to about May 1, 2019.
Expected impact in this example:
- You may exclude 1 additional month near the boundary.
- With a monthly combined shortfall of $150, that implies approximately −$150 from the SOL-bounded total.
So the total might move from:
- $4,950 → about $4,800 (directionally; exact value depends on how the calculator allocates partial months around boundary dates).
2) Change only actual child support paid
Keep dates fixed, but update:
- Child support actually paid: $1,100 / month (instead of $1,050)
- New child support shortfall: $1,200 − $1,100 = $100 / month
- Included months: still 33 months (SOL window unchanged)
Recompute total inside SOL window:
- $100 × 33 = $3,300
Expected impact:
- Total decreases by $1,650, which matches the reduction in monthly shortfall ($150 − $100 = $50) times 33 months.
3) Introduce an alimony underpayment
Now assume alimony was also short:
- Alimony actually paid: $350 / month (instead of $400)
- Alimony shortfall: $400 − $350 = $50 / month
- Monthly combined shortfall becomes: $150 (child) + $50 (alimony) = $200 / month
- Included months: still 33 months
Total inside SOL window:
- $200 × 33 = $6,600
Expected impact:
- Total increases by $1,650 relative to the original case, because you add $50/month across 33 included months.
Bottom-line sensitivity takeaway
- The SOL window mainly controls how many months are counted.
- The payments control the monthly shortfall, which scales the total.
- Together, these determine the SOL-bounded arrears figure DocketMath reports.
