Worked example: Alimony Child Support in Oregon

Example inputs

This worked example shows how DocketMath (calculator: alimony-child-support, jurisdiction: Oregon / US-OR) can turn real-world facts into estimated guidance for alimony (spousal support) and child support outcomes.

Scenario (assumptions for the example)

We’ll model a divorcing Oregon household with two children and moderate, stable incomes.

Parties

• **Spouse A (paying support)

  • Gross monthly income: $6,500
  • Work-related / payor-side expenses: the tool may allow optional inputs for certain categories (enter only what you have and what the tool requests).
• **Spouse B (receiving support)

  • Gross monthly income: $3,000
• Children

  • Child 1: age 10
  • Child 2: age 7

**Parenting time (time allocation)

• Spouse A has 78 overnights per year (roughly 21%)
• Spouse B has the remaining ~79%

Support inputs

• Child support portion: DocketMath uses Oregon’s guideline framework (jurisdiction-aware).
• Alimony portion: DocketMath uses an Oregon-specific workflow for spousal support factors and timing assumptions.
• Health insurance / childcare

  • Health insurance cost paid by Spouse A: $250/month
  • Childcare costs: $150/month
  • DocketMath allows you to include these so the worksheet reflects them (when applicable to the tool’s input categories).

Agreement / legal posture

• We assume the matter is handled using guideline-style computations for child support and factor-driven spousal support modeling for Oregon.

What you’d enter in DocketMath

If you’re using the tool directly, the example inputs map roughly to these categories:

• Income

  • Spouse A gross monthly: $6,500
  • Spouse B gross monthly: $3,000
• Children

  • Number of children: 2
  • Ages: 10 and 7
• Parenting time

  • Overnights per year for Spouse A: 78 (use the unit the tool expects)
• Ongoing costs

  • Health insurance: $250/month
  • Childcare: $150/month
• Spousal support assumptions

  • Start date: modeled using the tool’s timing convention (e.g., first full month after separation, depending on the tool setup)
  • Duration: modeled based on typical factor outputs rather than a universal fixed term

**Setup checklist (to avoid common input mistakes)

Example run

Below is a representative output structure from a single run in DocketMath. Exact dollar amounts can shift depending on how you enter income details, whether you include optional cost fields, and what the tool’s Oregon-specific assumptions and factor inputs are set to.

Step 1: Child support computation (Oregon guideline modeling)

Given:

• 2 children (ages 10 and 7)
• Spouse A time share: about 21%
• Added monthly costs: $250 health insurance + $150 childcare = $400

How the tool approaches it (conceptually):

1. Uses Oregon’s schedule to estimate a baseline child support amount.
2. Applies parenting time allocation.
3. Incorporates certain additional child-related expenses if you enter them in the supported fields.

Illustrative outcome (for this example):

• Estimated child support: $1,420/month

(Treat this as a baseline estimate under these assumptions—especially the incomes, the parenting time unit, and whether insurance/childcare are included.)

Step 2: Alimony / spousal support modeling (Oregon factor workflow)

DocketMath’s alimony module uses an Oregon-aware workflow. Rather than treating alimony as a single rigid formula, it models alimony using decision structure categories such as:

• need and ability to pay,
• factors related to length of marriage (if provided),
• income disparity,
• and other modeled statutory considerations represented in the tool.

Assumptions used for this example:

• Marriage length: 8 years
• No major disability or exceptional flags entered
• A meaningful income gap ($6,500 vs. $3,000)

Illustrative outcome (for this example):

• Estimated alimony: $750/month

Step 3: Combined support total

Putting the modeled components together:

• Child support: $1,420/month
• Alimony (spousal support): $750/month
• Total monthly estimate: $2,170/month

Breakdown view:

Quick sanity check (what to look for)

• If you increase parenting time for Spouse A, child support generally decreases (because the parenting-time allocation shifts).
• If you increase Spouse A income, both components often move upward because ability to pay increases.
• If you increase Spouse B income, alimony often decreases first; child support can also adjust depending on how the guidelines and time share interact.

Sensitivity check

In practice, planning usually comes down to “What happens if one input changes?” DocketMath is designed for exactly this kind of quick scenario testing.

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.

Scenario A: Parenting time increases for Spouse A

Change:

• Overnights from 78 → 120 per year

Expected direction:

• Child support decreases, because Spouse A is exercising more of the parenting time allocation.
• Alimony may change less, because time affects child support more directly than spousal support in many modeled situations (unless the tool ties other need/expense inputs to time assumptions).

Illustrative directional result:

• Child support: $1,420 → ~$1,250/month
• Alimony: ~$750/month
• Total: ~$2,000/month

Scenario B: Spouse B income increases

Change:

• Spouse B gross monthly from $3,000 → $4,200

Expected direction:

• Alimony decreases as the receiving spouse’s need/ability profile shifts.
• Child support adjusts too as guideline math reflects the new income level.

Illustrative directional result:

• Child support: $1,420 → ~$1,300/month
• Alimony: $750 → ~$450/month
• Total: ~$1,750/month

Scenario C: Health insurance costs removed from the input

Change:

• Health insurance: $250/month → $0
• Childcare remains $150/month, so added costs fall from $400 → $150

Expected direction:

• Child support decreases when insurance is included as part of the tool’s child-related cost inputs.
• Alimony may not change much unless the tool’s inputs for need/expense are linked to those categories.

Illustrative directional result:

• Child support: $1,420 → ~$1,300/month
• Alimony: ~$750/month
• Total: ~$2,050/month

A practical way to run sensitivity checks in DocketMath

Use a repeatable checklist:

If the biggest change comes from one field (like overnights), you’ve identified where both the math and data accuracy matter most.

If you want to run your own scenario, open the tool here: alimony-child-support.

Related reading

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