Why Alimony Child Support results differ in Washington

The top 5 reasons results differ

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

If you’re seeing different alimony / spousal support and child support figures in Washington (US-WA) when you run the DocketMath calculator (or when different people share different numbers), the cause is usually not “math mistakes.” It’s typically jurisdiction-aware rules and different inputs that change the outcome.

Here are the top 5 reasons Washington results differ:

1. **Different income inputs (gross vs. net, and what counts as “income”)

   • Child support and spousal support outcomes can change materially when the “income” you enter differs (for example: overtime vs. base pay, bonuses, or deductions).
   • DocketMath will reflect the income model and values you select. So two runs with the same agreement date can still diverge if the entered pay details differ.

2. Different parenting-time / custody assumptions

   • Even small changes in how parenting time is allocated can shift the child-support portion (and can indirectly affect how people treat related financial burdens in spousal-support analysis).
   • If you’re using different schedules (e.g., 50/50 vs. 60/40), the child-support output often changes first.

3. Different interpretation of “support vs. other obligations”

   • People sometimes bundle expenses (health insurance, childcare, extraordinary costs) into the support estimate, while others enter them separately.
   • DocketMath output tracks what you enter. If one scenario includes additional cost categories and the other doesn’t, results can differ even when the base incomes match.

4. Spousal-support duration / modification assumptions

   • Spousal support outcomes can differ depending on assumptions about how long support should run and whether changes are expected.
   • In the alimony-child-support workflow, DocketMath can produce different numbers when the spousal-support parameters are different.

5. **Time-based legal context (and the clock you’re using)

   • People often compare results calculated for different timeframes—such as an order effective date vs. a “back to filing” estimate.
   • Washington’s general statute of limitations is 5 years, tied to RCW 9A.04.080. No claim-type-specific sub-rule was found in the context of this brief, so the 5-year period should be treated as the default/general period when discussing time windows for adjustments and enforcement timing.

If you want to generate a Washington-specific scenario quickly, start here: /tools/alimony-child-support.

How to isolate the variable

To find what’s driving the difference, use a “single change” workflow. The goal is to run DocketMath multiple times while changing one input group at a time.

Single-change isolation checklist (recommended order):

• Lock income
  Use the exact same income numbers for both scenarios. If results still differ, income isn’t the driver.
• Lock parenting time / custody model
  Make sure the same schedule (or the same structure of time allocation) is used in both runs.
• Lock shared expense categories
  Confirm whether health insurance, childcare, and extraordinary expenses are included in one scenario but not the other.
• Lock spousal-support parameters
  Compare any toggles or fields tied to spousal-support structure (including duration assumptions). If those differ, alimony/spousal support may shift.
• Lock effective date / time assumptions
  If one estimate is treated as “current” and another as “retroactive,” the outputs may be compared on mismatched timing assumptions.

Practical tip: keep a mini log of each run:

• Run A: baseline
• Run B: change income only
• Run C: change parenting time only
• Run D: change expense categories only
• Run E: change spousal-support parameters only

Then check the movement pattern:

• Only child support moves → parenting time or child-cost inputs are likely different.
• Spousal support moves more than child support → spousal-support parameters or income characterization may differ.
• Both move together → income inputs or global support configuration may differ.

Next steps

1. Re-run with consistent inputs in DocketMath

   • Start from a baseline set of facts.
   • Change one input group at a time and re-run.

2. Validate what’s included

   • Make sure you’re comparing the same expense categories and the same parenting-time model.
   • If someone else’s numbers don’t line up, ask for the input assumptions (instead of arguing the math).

3. Use the 5-year default timing lens when comparing time-based estimates

   • When comparing figures tied to enforcement or adjustment windows, keep the 5-year general period in mind under RCW 9A.04.080.
   • As noted above, this brief reflects the general/default period, not claim-type-specific sub-rules.

4. Save the comparison evidence

   • Screenshot or record the DocketMath inputs you used. This makes it much easier to pinpoint which field caused the result shift.

Related reading

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