Worked example: Alimony Child Support in California

Example inputs

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

Below is a worked example of how DocketMath (jurisdiction-aware rules for California (US-CA)) can be used to model alimony-style spousal support and child support together. This is a modeling example, not legal advice—use it to understand how inputs can affect outputs.

Scenario (California, US-CA)

• Filing date / case start reference: 2024-06-01

• Filing jurisdiction: California (US-CA)

• Parties’ gross monthly incomes

  • Parent A (paying): $8,500/month
  • Parent B (receiving): $5,200/month

• Child-related

  • Number of children: 2
  • Children’s ages: 7 and 11
  • **Time split (overnight/primary parenting time proxy)

    • Parent A: 40%
    • Parent B: 60%

• **Support-related adjustments (inputs used for modeling)

  • Parent A health insurance premium (monthly): $350
  • Parent B health insurance premium (monthly): $120
  • Childcare costs (monthly, attributable): $300
  • Any additional documented income sources (monthly): $0

• Spousal support modeling preference

  • Use DocketMath default spousal support parameters (tool-driven, rule-based)
  • Length of support: modeled as ongoing (until changed by the court; modeling only)

Important boundary about “jurisdiction-aware rules”

DocketMath applies California-specific jurisdiction settings (US-CA) and uses the tool’s rule set for calculating modeled obligations. Where a statute or rule is general (not claim-type-specific), the tool uses the general/default period.

Note on timing rule availability: In this brief, only a general/default timing rule was provided. No claim-type-specific sub-rule was provided, so this example uses the general default for timing.

Timing input used for this example (for illustration)

Even though support calculations don’t turn solely on statutes of limitation, DocketMath may include timing variables for related procedural modeling. For this example, we anchor to the information provided:

• General SOL (statute of limitations): 2 years
• Citation: CCP § 335.1
• Source used in this example: Nolo summary of California limitations (general)
  https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

For this worked example, treat the SOL as a general default of 2 years with no claim-type-specific override, because none was provided.

Example run

Run the Alimony Child Support calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Open the tool

Use DocketMath’s alimony + child support calculator here:
/tools/alimony-child-support

Step 2: Enter the example inputs

In the DocketMath alimony-child-support calculator (US-CA), enter:

• Parent A gross monthly income: 8500
• Parent B gross monthly income: 5200
• Children: 2
• Ages: 7, 11
• Parenting time (proxy): 40% / 60% (Parent A / Parent B)
• Health insurance premiums (monthly): 350 (A), 120 (B)
• Childcare: 300
• Additional income sources: 0
• Spousal support: tool default parameters
• Timing/anchoring: SOL default = 2 years, CCP § 335.1

Step 3: Run the calculation

Click Calculate / Run. DocketMath typically returns modeled results split into:

1. **Child support obligation (monthly)
2. **Spousal support obligation (monthly)
3. **Total combined support (monthly)

Because the exact layout can vary by interface updates, the key is to look for the two components + combined monthly total.

Example output (modeled)

Here is a representative output structure for the scenario above:

Timing model add-on (illustrative)

Using the general SOL default provided in the brief:

• General SOL: 2 years
• Citation: CCP § 335.1
• Applied as: general/default period (no claim-type-specific override)

If the tool displays a timing window, it would look like:

• Filing reference: 2024-06-01
• **→ 2026-06-01 (2 years)

Gentle caution: The SOL rule (CCP § 335.1) is used here as a timing/legal anchor based on the information provided. Support obligations and enforcement can involve multiple doctrines beyond a single limitations period.

Sensitivity check

Now rerun the model by changing one input at a time. The goal is to see what tends to move the monthly totals the most.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Parenting time shift: 40% → 55% for Parent A

• Change: Parent A parenting time 40% → 55%
• Keep everything else the same

Expected direction: Child support often shifts more when parenting time changes (because each household’s share of the child-related burden changes). Spousal support may move as well depending on how the tool models needs/capacity.

Takeaway: Parenting time changes often impact child support most.

2) Income change: Parent A gross monthly $8,500 → $9,500

• Change: Parent A income 8500 → 9500
• Keep everything else the same

Expected direction: Child support generally increases when the payor’s income increases. Spousal support can increase too because the modeled balance of financial need and ability to pay changes.

Takeaway: Income deltas typically drive large changes in both components in a combined model.

3) Childcare change: $300 → $600

• Change: childcare 300 → 600
• Keep everything else the same

Expected direction: Child support usually increases when childcare costs increase. Spousal support may adjust modestly depending on tool logic.

Takeaway: Childcare commonly affects child support more than spousal support.

4) SOL / timing anchor check (no change to monthly numbers)

If DocketMath lets you adjust the timing anchor, try changing only the SOL value.

• Change: timing anchor from 2 years to a different value
• Do not change incomes, parenting time, or expenses

Expected direction: Monthly guideline-style support amounts usually do not change because SOL is primarily a timing/enforcement/eligibility concept—not an income/expense formula ingredient.

Pitfall to avoid: Don’t assume that changing CCP § 335.1’s general 2-year period changes the amount of support. In typical modeling workflows, it affects timing-related outputs (or related procedural framing), not the underlying monthly calculation logic.

Related reading

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