What varies by jurisdiction

In Indiana, “alimony” and “child support” are handled under different legal frameworks, so what varies by jurisdiction (and by case facts) often splits along those same lines.

Indiana baseline: two different buckets

Child support: governed by the Indiana Child Support Guidelines, authorized under Ind. Code § 31-16-6-1.
Maintenance (commonly called “alimony”): governed by Ind. Code § 31-15-7-2.

Even when people use one umbrella term (“alimony/child support”), Indiana courts apply distinct statutory purposes and different calculation mechanics to each.

How DocketMath handles jurisdiction awareness (US-IN)

DocketMath’s alimony-child-support workflow is jurisdiction-aware for US-IN. That means:

It uses Indiana’s framework for child support (guidelines-based).
It uses Indiana’s statutory factors framework for maintenance (rather than adopting another state’s approach).

In practice, inputs like income, custody/parenting time, and child-related expenses can affect child support differently than they affect maintenance—even when the same real-world facts are driving both.

The most noticeable “variation” inside Indiana cases

Within Indiana, the biggest “what changes the result” drivers are typically:

Whether you’re calculating child support, maintenance, or both
Which incomes and expenses are used (for example, how deductions/allowable adjustments are treated, plus health insurance and childcare costs)
Parenting-time / custody structure, which commonly affects child support
Maintenance factors, which can shift based on items like earning capacity, need/ability to pay, and the circumstances relevant under Ind. Code § 31-15-7-2

Pitfall: “Same numbers” does not mean “same result.” Indiana child support and Indiana maintenance can respond differently to the same change in income or expenses because they’re governed by different rules and goals.

Default period note (important)

No claim-type-specific sub-rule was found for the period selection logic beyond the general default. In other words, DocketMath’s default period should be treated as the general/default period, not a claim-specific override.

For the tool you can run here: /tools/alimony-child-support.

What to verify

Before you rely on DocketMath outputs in Indiana (US-IN), verify the inputs you provide—Indiana results tend to be sensitive to the same categories courts consider in Ind. Code § 31-16-6-1 (child support) and Ind. Code § 31-15-7-2 (maintenance), as operationalized by the Indiana Child Support Guidelines.

(Quick reminder: this is an estimate and not legal advice.)

1) Confirm the case category you’re measuring

Make sure your inputs match what you’re trying to estimate:

Child support (guidelines-driven)
Maintenance / “alimony” (factors-driven)
Both, with results kept separate

Why it matters: Indiana uses different lenses for each category. Mixing categories can create mismatched expectations.

2) Gather and check the income data the tool needs

Indiana outcomes are sensitive to the income figures included in the analysis. When you enter income in /tools/alimony-child-support, verify:

Pay frequency matches what you enter (weekly/biweekly/monthly)
Income is consistent (or clearly treated for variable income like commissions/bonuses)
Your “monthly” equivalents match how you’re inputting amounts into the tool

Child support is tied to the court’s ability to order a “reasonable amount” for the child’s support under Ind. Code § 31-16-6-1, and the Guidelines operationalize how that “reasonable amount” is quantified. Maintenance is guided by the statutory considerations in Ind. Code § 31-15-7-2.

3) Verify parenting-time inputs (child support impact)

Indiana child support calculations often depend on the custody/parenting-time structure. Before running DocketMath, confirm:

The time split matches the expected arrangement
The schedule reflects actual parenting time (not what you wish it were)
Any relevant special circumstances are represented in the way the Guidelines account for costs

4) Validate childcare and insurance cost inputs (child support impact)

Child-related expenses can affect the overall child support computation. In the tool, verify:

Health insurance premiums for the child (if applicable)
Childcare expenses (if applicable)
Time period consistency (e.g., monthly equivalents)

5) Understand maintenance factors (Ind. Code § 31-15-7-2)

Maintenance in Indiana is not typically a “pure formula-only” outcome in the way many readers expect from guidelines-based child support. Instead, Ind. Code § 31-15-7-2 sets out statutory factors that courts consider.

So in DocketMath, maintenance results will be influenced by how your inputs map to factor categories such as:

earning capacity and employment circumstances
financial need and ability to pay
duration and other circumstances relevant to the situation

Gentle disclaimer: DocketMath can help you model scenarios, but it doesn’t replace a full legal review or the fact-specific discretion of a court.

How Alimony Child Support rules vary in Indiana