Common Alimony Child Support mistakes in Hawaii

The top mistakes

Run this scenario in DocketMath using the Alimony Child Support calculator.

When families use DocketMath’s alimony-child-support calculator for Hawaii (US-HI), the most common errors tend to fall into predictable buckets: wrong inputs, missing court-order conditions, and misunderstanding how Hawaii time limits affect what can be claimed.

Below are the mistakes we see most often when people calculate alimony (spousal support) and child support together. For quick navigation, you can start with the calculator here: /tools/alimony-child-support.

Friendly reminder: This content is for education and planning. It’s not legal advice, and it can’t replace advice from a Hawaii family law attorney.

1) Assuming timing doesn’t matter for older obligations (SOL/lookback)

A frequent issue is treating claims as if there’s no “clock.” In Hawaii, a key baseline is the general statute of limitations (SOL) for claims—5 years—under HRS § 701-108(2)(d). The FindLaw source frames this as the general/default period, and no claim-type-specific sub-rule was found for the purposes of this brief.

• What goes wrong: People assume an old obligation can’t be challenged based on timing, or they assume there’s a longer lookback window.
• Practical impact: When you calculate arrears exposure or decide which years to include in your review, your number can change materially depending on the 5-year default lookback you apply.

2) Mixing up gross income vs. net income in calculator inputs

DocketMath’s results depend heavily on the income fields you enter. A common error is entering take-home pay (net) when the calculator expects gross income, or doing the reverse.

• What goes wrong:

  • Using net pay where gross is expected
  • Using gross where net is expected
• Practical impact: Support outputs can be overstated or understated. Even small differences can create noticeably different results because support formulas typically scale with income.

Quick fix: Before you run numbers, confirm which income category the calculator is asking for and enter it consistently across scenarios.

3) Forgetting regular income streams (so your “income” is incomplete)

Another common issue is omitting income that affects the support picture. People sometimes leave out consistently recurring items such as:

• overtime paid regularly

• bonuses tied to performance (when they recur)

• self-employment-related income components (as applicable to how you input income)

• What goes wrong: The income input looks “clean,” but it’s missing recurring pay.

• Practical impact: Your output may look plausible but won’t match what a review of actual earning capacity may produce.

Quick fix: Use at least the last 12 months of income records to capture recurring patterns, not just the most recent paycheck.

4) Entering the wrong child count or the wrong custody/placement basis

Child support inputs are sensitive. A small selection error—like the wrong number of children—can create a large change in the output.

• What goes wrong:

  • selecting the wrong child count
  • entering parenting time using the wrong unit (for example, using days when the calculator expects a percentage, or vice versa)
• Practical impact: Results can be far off, especially where the calculator’s method changes based on placement/allocation inputs.

Quick fix: Verify the calculator’s expected parenting-time unit and re-check the child count before trusting the output.

5) Computing arrears over more than the allowed lookback (time-bar risk)

People often total arrears for many years without narrowing to the time window supported by the default SOL approach discussed above.

• What goes wrong: Aggregating obligations beyond the 5-year baseline without applying a lookback rule.
• Practical impact: Your arrears total may be overstated if later amounts are time-barred under the default HRS § 701-108(2)(d) framing.

Quick fix: When you’re estimating arrears, explicitly set a lookback start date tied to the 5-year default approach (then adjust only if you have a reason and support for a different rule).

6) Treating support as one flat number when the court order phases it

Even if inputs are correct, the actual court order can introduce changes over time.

Common order features that require time-phased modeling include:

• step-down schedules (for example, when a child reaches a certain age)

• changes tied to events (such as school/enrollment or emancipation)

• duration limits for alimony/spousal support

• What goes wrong: People assume the obligation stays the same throughout.

• Practical impact: Your results can look stable in the short term but drift from what the order requires over later periods.

Quick fix: If the order changes over time, model each period separately rather than averaging everything into one run.

7) Using the wrong effective date for retroactive changes/modifications

When income changes (or a modification is discussed), people often update income assumptions but apply the wrong effective date.

• What goes wrong: Applying new income too early or too late relative to the effective date logic being tested.
• Practical impact: Outputs can swing, because support can be calculated differently before vs. after the effective date.

Quick fix: Keep the effective date consistent across runs and clearly note what changes on that date.

How to avoid them

Use DocketMath to run fast scenarios, but pair it with a tight input checklist. The goal is to reduce avoidable error before you rely on numbers for discussions, documentation, or planning.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Confirm the SOL baseline and bound your review using it (5 years default)

For timing-related questions, anchor your review to Hawaii’s general SOL:

• General SOL period: 5 years
• Statute: **HRS § 701-108(2)(d)

Practical workflow:

• Decide what years you’re assessing—especially for arrears discussions.
• Set a lookback start date based on the 5-year default approach described above.

2) Use one source of truth for income, and track gross vs. net

Before entering numbers:

• Pull the last 12 months of income information (pay stubs, employer statements, tax summaries).
• Separate regular income from one-time items.
• Pick whether you’re inputting gross or net (as required by the calculator’s fields) and stay consistent.

Checklist idea:

3) Treat custody/placement inputs as exact

For parenting-time or placement structure:

4) Run side-by-side “sanity check” scenarios

A practical way to catch input errors is to test whether the output changes in the direction you expect.

Try:

• A low-income scenario and a high-income scenario
• A scenario with one key input adjusted (income amount or child count) and confirm the output moves meaningfully

If changing a key input barely changes the output, you may have entered information in the wrong field.

5) Align scenario dates with the effective date you’re modeling

If you’re modeling a modification:

• Decide the effective date you’re testing.
• Use it consistently across all runs.
• Compare “pre-change” vs. “post-change” assumptions and note what changed.

6) Model court-ordered time changes with multiple runs

Instead of trying to force everything into a single number:

• If there’s a step-up/step-down schedule, model each period separately.
• Keep a simple note listing the periods you used so you don’t lose track of what changed.

7) Keep an audit trail for every run

For each DocketMath scenario, save your assumptions alongside the output:

• income source(s) and type (gross/net)
• child count and ages assumptions
• parenting-time structure and units
• effective date(s)
• any court-order conditions you incorporated (step-downs, duration limits, etc.)

This makes it much easier to spot mistakes and explain your work.

Related reading

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