How to run Alimony Child Support in DocketMath for Oregon

Step-by-step

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

Below is a practical, Oregon-specific workflow for running Alimony + Child Support in DocketMath using jurisdiction-aware rules (US-OR). This is a how-to for the tool—not legal advice—so use it to organize scenarios and understand how different inputs can change outputs.

1) Start the calculator in DocketMath (Oregon / US-OR)

1. Open DocketMath: /tools/alimony-child-support
2. Confirm the jurisdiction is set to Oregon (US-OR).
3. Read the scenario assumptions shown in the interface. DocketMath generally uses your entries to estimate obligations based on the selected program.

What changes with this step: Selecting US-OR helps ensure the calculator uses Oregon-focused logic and the way the results are presented.

2) Enter parent/household basics

Fill in the demographic and household data requested by the calculator, such as:

• Number of children included in the calculation
• Whether the calculation is for combined alimony + child support (if the tool separates components, follow the combined mode shown)
• Any fields that indicate which parent is paying versus receiving (or how the tool defines “payor” and “recipient”)

DocketMath tip: Keep naming consistent. If you switch “payor” roles midstream, your estimated amounts can flip because the calculator is effectively changing who owes support.

3) Add income inputs (often the biggest driver)

Locate the income section and enter values the tool asks for (commonly including gross income and/or adjusted income fields).

Typical categories you may see:

• Payor income
• Payee income
• Pre-tax deductions or special adjustments the tool supports

If DocketMath supports multiple income types (for example, base salary plus variable income), enter them using the structure the tool provides.

What changes with this step: Income inputs typically have a direct, sometimes non-linear impact on:

• Child support estimates
• Alimony estimates (which depend on relative financial circumstances, not just one party’s numbers)

4) Provide parenting time / custody information (for child support)

For the child support portion, DocketMath will ask for the structure of custody or parenting time, such as:

• Overnights or percentage time for each parent
• Shared vs. primary placement options, depending on how the calculator asks

Enter the values that match your scenario—for example, “about 2 nights/week” versus “roughly 50/50,” if those are offered as choices.

What changes with this step: Parenting time can significantly alter the child support estimate because the calculator uses the time split to model each parent’s support-related obligations.

5) Select the alimony scenario inputs

Move to the alimony section and enter the fields the calculator requires. Common inputs include:

• Whether the request is ongoing versus limited duration (if the tool offers this)
• Marital duration or date-based inputs (if requested)
• Any special-factor fields that DocketMath includes (for example, items related to need and ability to pay—only use what the tool actually provides)

If DocketMath uses toggles like “type of alimony” or “duration,” pick the option that best matches your facts and the information you have entered consistently elsewhere in the form.

What changes with this step: In Oregon, alimony outcomes can be sensitive to:

• Need and ability to pay
• Timing/length of marriage inputs as the tool incorporates them
• Income and support obligations already reflected in the overall calculation inputs

6) Run the calculation and review component outputs

Click Calculate (or the tool’s equivalent action).

DocketMath should display results broken down by component, typically including:

• Estimated child support amount (often monthly)
• Estimated alimony amount (often monthly, with possible ranges/durations depending on the tool)
• A combined monthly total if the tool supports it

Also review any “assumptions summary” or “inputs used” section, if shown.

What to check in the output:

• Whether child support changes when you adjust parenting time
• Whether alimony changes when you adjust income, marital duration, or alimony parameters
• Any notes explaining how your entries were interpreted

7) Run sensitivity checks (fast comparisons)

To see how realistic changes affect the estimate, run “what-if” scenarios where you change inputs in controlled ways:

• Change one input at a time (for example, parenting time from one increment to another, or payor income by a specific percentage)
• Re-run and compare outputs

In many cases, the biggest movers are income and parenting time, but the tool’s results will tell you what matters most for your inputs.

Checkbox checklist for scenario testing

8) Save or export results (if available)

If DocketMath offers saving, downloading, or copying:

• Save the Oregon (US-OR) scenario outputs
• Export a version that captures the exact inputs you used

What changes with this step: Saving an input snapshot reduces confusion when you compare multiple scenarios, especially after updating income or parenting time.

Common pitfalls

These issues commonly cause incorrect results or make the Oregon-focused outputs harder to interpret:

1. Mis-entering parenting time

   • Swapping primary vs. shared time
   • Choosing “shared custody” while entering numbers that effectively reflect near-total time with one parent
   • Rounding parenting time in a way that doesn’t match the tool’s question phrasing

2. Inconsistent income formatting

   • Entering annual numbers into a field that expects monthly (or vice versa)
   • Mixing gross vs. net income between payor and payee fields if the tool expects a consistent type
   • Forgetting to add variable income in the separate field the tool provides (if available)

3. Skipping alimony scenario fields

   • Leaving an alimony option set to a default that doesn’t match your facts
   • Entering marital duration inconsistently with the date inputs the tool asks for

4. Over-relying on one “combined” number

   • Child support and alimony may respond differently to the same input changes
   • For planning, compare components separately so you can see what drove changes

5. Not running one-variable checks

   • Updating multiple inputs at once makes it unclear what caused the output movement
   • Run at least 2–3 scenarios where only one input changes

Try it

Ready to calculate? Start here:

• Use DocketMath: /tools/alimony-child-support

Quick test scenario (recommended):

1. Enter a baseline using your best estimates.

2. Create two follow-ups:

   • One with parenting time adjusted (using the smallest increment DocketMath supports)
   • One with payor income adjusted (for example, +10% or the next realistic step based on your data)

3. Compare:

   • Child support estimate change
   • Alimony estimate change
   • Combined total change (if the tool shows it)

Goal: identify which inputs dominate the result for your fact pattern.

Related reading

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