Why Alimony Child Support results differ in Hawaii

The top 5 reasons results differ

When you run DocketMath’s alimony-child-support calculator for Hawaii (US-HI), two people can end up with noticeably different results even when the facts look “similar.” Most differences come from (1) which jurisdiction-aware rules apply and (2) how sensitive the outputs are to specific inputs and assumptions.

Here are the top 5 reasons you’ll see divergence in Hawaii:

1. **Timing and what falls inside the accounting window (SOL and enforcement reality)

   • Hawaii uses a general statute of limitations (SOL) period of 5 years for many claims.
   • This is tied to HRS § 701-108(2)(d), and it affects which amounts are treated as included when you compare “what is owed” versus “what is owed in the last X years.”
   • Important clarification: No claim-type-specific sub-rule was found for this discussion, so treat this 5-year period as the general/default SOL under the statute referenced (HRS § 701-108(2)(d)).
   • If one run effectively includes older periods and another run does not, totals can swing significantly.

2. Income inputs: gross vs. net, overtime, and averaging

   • Small changes in income fields can materially change outputs, especially when the calculator treats certain income types differently.
   • Examples that commonly drive differences:

     • gross vs. net selection,
     • whether overtime is included or excluded,
     • whether variable income is averaged or treated differently over time.

3. **Custody structure assumptions (time allocation inputs)

   • Even when custody is “shared,” slight differences in schedule assumptions can change the allocation used for calculations.
   • Typical drivers include:

     • number of overnights,
     • primary placement assumptions (if applicable),
     • how the schedule is summarized and entered.

4. Health insurance and work-related cost assumptions

   • Adding, removing, or reassigning an expense (like a health insurance premium) can shift the allocation.
   • The direction and magnitude of the change depends on who is assumed to pay each cost category and whether the expense is included in the relevant calculation step.

5. Rounding, caps, and the order deductions are applied

   • Two results that look close “by intuition” can still differ due to:

     • rounding rules,
     • any caps the calculator applies (if configured for a jurisdictional workflow),
     • the sequence in which deductions/adjustments are applied.

How to isolate the variable

To pinpoint why two DocketMath runs differ in US-HI, use a diagnostics workflow: change one input at a time, keep everything else constant, and compare the output deltas.

Use this checklist:

• Use the same calculation start date and calculation end date for both runs.

• Reason: Hawaii’s general 5-year SOL (referenced by HRS § 701-108(2)(d)) influences what is included in the analysis window.

• Reference point: General SOL Period = 5 years (general/default).

• Ensure both runs use the same structure for income inputs:

  • wages vs. self-employment,
  • overtime included vs. excluded,
  • monthly vs. annualization (or whatever consistent method you’re using).

• If you change the income amount, confirm you did not also change the income method.

• Match schedule details or summaries between runs:

  • overnights,
  • placement assumptions,
  • any change-of-circumstance dates that affect when schedule changes occur.

• Align the expense categories and who pays them:

  • health insurance premium logic,
  • daycare/work-related costs (if included),
  • any cost-sharing or assignment assumptions.

• Instead of focusing only on the final total, compare which category moves:

  • child support calculation line,
  • alimony-related components (if applicable),
  • and any downstream adjustments (including deductions and rounding).

A practical approach:

1. Run Scenario A with all inputs identical.
2. Run Scenario B with one changed field (date or income or custody inputs or expenses).
3. Identify which change creates the largest output difference.
4. Repeat until the “driver” variable is clear.

For a quick launch, use the tool here: /tools/alimony-child-support.

Gentle reminder: This is about explaining calculator behavior and input sensitivity—not providing legal advice about a specific case or enforcement strategy.

Next steps

Once you identify the driver input, you can make the result more stable and easier to explain—especially if you’re comparing outputs across drafts, edits, or revisions.

1. Write a short change log

   • Dates: calculation start/end, and any modification effective dates you entered
   • Income: gross/net selections, overtime inclusion, monthly vs annual
   • Schedule: overnights and schedule summaries
   • Costs: insurance premium and work-related costs assumptions

2. Run two “reality checks”

   • Sanity check #1: Change only the date window width to see whether the result shifts in a way consistent with the 5-year general/default horizon under HRS § 701-108(2)(d).
   • Sanity check #2: Change only income or only custody-time inputs to see whether the result jumps accordingly.

3. Keep one version as the baseline

   • Use the baseline for future comparisons.
   • Every later run should clearly state which field changed (so you can explain “why it moved”).

4. If sharing results, cite the jurisdiction rule used

   • For this discussion, Hawaii’s behavior is tied to the general 5-year SOL referenced by HRS § 701-108(2)(d).
   • Because no claim-type-specific sub-rule was identified here, treat it as the general/default period for the analysis window.

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado