How to run Alimony Child Support in DocketMath for Ohio

Step-by-step

Use DocketMath’s Alimony Child Support calculator with Ohio (US-OH) so your inputs flow into the right worksheets and any applicable deviation modeling. Ohio child support uses the income-shares model, built from a basic-obligation schedule and then converted to the worksheet amount through a statutorily required process.

Before you start: Ohio’s child support statutes are centered in Ohio Rev. Code § 3119.021 (basic child support schedule), § 3119.022 (child support worksheet), and § 3119.04 (deviations). Spousal support is addressed in § 3105.18.

1) Open the correct tool in DocketMath

1. Go to the primary calculator: /tools/alimony-child-support
2. Confirm the jurisdiction is set to Ohio (US-OH).
3. Start a new calculation run (or create a new scenario/iteration if your workflow supports it).

2) Enter the child support inputs tied to Ohio’s worksheet model

DocketMath should lead you through the core factors that feed Ohio’s worksheet process under Ohio Rev. Code § 3119.022, while using the basic-obligation schedule codified in § 3119.021.

Enter inputs carefully—especially anything that affects worksheet construction:

• Number of children covered by the order
• Parent income(s) (use the incomes you want reflected in the worksheet)
• Child-related adjustments that the tool supports (for example, fields for healthcare insurance costs, if available)
• Parenting-time / allocation inputs, if the tool provides them (because Ohio worksheet modeling can be sensitive to the parenting-time structure)

How Ohio’s statutes map to the calculator (and what you should expect to see conceptually):

• Schedule: Ohio Rev. Code § 3119.021 contains the basic-obligation schedule used in Ohio’s income-shares approach.
• Worksheet: Ohio Rev. Code § 3119.022 prescribes the worksheet method for converting the schedule and income factors into the worksheet obligation.
• Deviations: Ohio Rev. Code § 3119.04 governs when and how the court may adjust away from the worksheet amount based on specified factors.

3) Add spousal support inputs under Ohio Rev. Code § 3105.18

Because this DocketMath tool is specifically “Alimony Child Support,” you’ll also provide inputs that the tool models as spousal support under Ohio law.

Ohio spousal support is addressed in Ohio Rev. Code § 3105.18. In practice, your inputs may include:

• Spousal income information (or figures the tool uses to model need and ability to pay)
• Duration / timing details, if requested by the tool
• Any agreed or court-structured parameters the tool allows you to enter

If the tool’s spousal-support section looks less detailed than your court filing, that usually means you’re limited to the fields the calculator can model—it doesn’t automatically mean the legal framework is wrong. Treat results as estimates based on available inputs.

4) Confirm Ohio deviation settings (child support) using § 3119.04

Ohio allows deviations from the worksheet under Ohio Rev. Code § 3119.04. Many calculators effectively separate:

• the worksheet amount (the baseline), from
• any deviation adjustment (optional and factor-driven)

In DocketMath:

• Look for deviation-related toggles, checkboxes, or a “deviation” panel.
• If you don’t see a direct field for a particular statutory factor, run the baseline worksheet first, then only add adjustments when the tool provides an input that matches the deviation pathway.

5) Run the calculation and review outputs in a structured order

After you click Calculate, review results in a sequence that matches the statutory concepts:

1. Child support baseline / worksheet result

   • This aligns most closely with § 3119.021 + § 3119.022.
2. Any parenting-time or worksheet-related breakdown

   • If DocketMath shows how parenting-time affects the allocation, compare results before/after changes to parenting-time inputs.
3. Deviation result (if applicable)

   • Confirm what the tool applied and whether the deviation inputs align with § 3119.04.
4. Spousal support result

   • This aligns to § 3105.18, as implemented in the tool’s modeling.

6) Run “what-if” scenarios to understand sensitivity

Ohio worksheet calculations are formula-driven. Small input changes can move results noticeably—so validate how your numbers behave.

Try at least these scenario checks:

• Change number of children (for example, 2 → 1 or 3) to see schedule shift under § 3119.021
• Adjust income figures by a small amount (for example, ±$2,000/month if you’re entering monthly amounts) to see responsiveness under § 3119.022
• Modify parenting-time fields (if supported) to observe direction of change
• Toggle deviation inputs only if DocketMath offers fields that correspond to deviation considerations under § 3119.04

7) Save the scenario and export your numbers

Use DocketMath’s scenario saving/export (if available) to:

• compare baseline worksheet vs deviation model
• preserve the inputs used for each run
• quickly re-run if you update income or expense facts

Common pitfalls

Here are the issues that most often lead to incorrect or confusing outputs when running Ohio alimony + child support in DocketMath:

• Confusing the baseline worksheet with deviation

  • Ohio’s starting point is the basic schedule (§ 3119.021) and the worksheet (§ 3119.022). Deviations only apply when the tool (and the facts you enter) support deviation modeling under § 3119.04.
• Omitting or mis-entering parenting-time inputs

  • If DocketMath asks for parenting-time structure and you leave it blank, the calculator may use a default that doesn’t reflect your situation.
• Using mismatched income types

  • The worksheet depends on how each parent’s income is entered. Mixing annual vs monthly, or before vs after adjustments (if the tool expects consistent types), can skew results.
• Expecting a claim-type-specific sub-rule inside the calculator

  • No claim-type-specific sub-rule was found. For running the tool, use the general/default period unless your Ohio-specific facts and the tool’s structure clearly require something beyond the standard workflow.
• Expecting spousal-support outputs to match a court order exactly

  • DocketMath can model outcomes, but Ohio spousal support under § 3105.18 can depend on facts and findings that aren’t captured by every calculator input set. Treat outputs as estimates, not guarantees.

Try it

Run a quick Ohio test workflow in DocketMath to validate your process:

• Set jurisdiction to Ohio (US-OH)
• Enter the number of children
• Input both parents’ income figures
• Add parenting-time values if the tool requests them
• Leave deviation-related fields off for the first run (baseline only)
• Click Calculate
• Review the child support result first (worksheet-level)
• Re-run with one change at a time (for example, adjust parenting-time or income) to confirm the direction of movement
• Then run a spousal-support scenario using the inputs required for Ohio Rev. Code § 3105.18 modeling

If results look counterintuitive:

• verify you didn’t swap monthly/annual income fields
• confirm parenting-time fields were entered in the expected format
• check whether DocketMath applied a default when a required input was left blank

Once the baseline looks consistent with your expectations, consider adding deviation inputs consistent with Ohio Rev. Code § 3119.04—and save both runs so you can compare them.

Related reading

• How Alimony Child Support rules vary in New York — What varies by jurisdiction
• How to calculate Alimony Child Support in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Alimony Child Support in Philippines — Worked example with real statute citations