Worked example: Alimony Child Support in Indiana

Example inputs

Below is a jurisdiction-aware worked example for calculating alimony and/or child support in Indiana using DocketMath’s alimony-child-support tool.

Jurisdiction settings (Indiana)

DocketMath applies an Indiana context (US-IN). For legal timelines, Indiana uses a general 5-year period under Indiana Code § 35-41-4-2. In this article, that limitation is mentioned to show how jurisdiction rules can appear alongside support calculations in practical workflows—but the tool’s math focuses on the support inputs you provide.

• Statute for general 5-year period: Indiana Code § 35-41-4-2
  Source: https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/?utm_source=openai
• Default applied period: 5 years
• Claim-type-specific rule: No claim-type-specific sub-rule was found for this article. So the general/default period is used (not a specialized limitation).

Example facts (numbers you can plug into DocketMath)

Use these example inputs as if they were the parties’ verified, monthly figures:

Income and allowances

• Payor (Parent A) gross monthly income: $6,500
• Payee (Parent B) gross monthly income: $2,500
• Payor (Parent A) allowable deductions (for calculation purposes): $600
• Payee (Parent B) allowable deductions (for calculation purposes): $150

Parenting time / custody (example structure)

DocketMath’s tool typically needs a parenting-time or custody indicator. This example uses:

• Parenting-time split: Parent A = 35%, Parent B = 65%
  (Example assumption for illustration; use your actual schedule.)

Case context

• Number of children: 2
• Request type selection inside the tool: Alimony + Child Support
  (If you run only one category, the tool will output only that component.)

Adjustment inputs (example)

• Special child-related costs (medical/childcare category): $0
• Hardship / deviation adjustment: $0
  (Zero adjustments keep the run “baseline.” You can test changes in the sensitivity section.)

Example run

You can reproduce this calculation directly in DocketMath using the primary CTA:

• Run the same tool: /tools/alimony-child-support

Step-by-step: what you enter

In DocketMath’s alimony-child-support interface, enter the example inputs:

1. Choose jurisdiction: Indiana (US-IN)
2. Enter Parent A monthly income:

   • $6,500 gross
   • $600 deductions
3. Enter Parent B monthly income:

   • $2,500 gross
   • $150 deductions
4. Enter parenting-time split: Parent A 35% / Parent B 65%
5. Enter number of children: 2
6. Add adjustment fields: keep “special costs” and “deviations” at $0 for baseline
7. Select components: Alimony + Child Support
8. Run calculation

Example output (illustrative)

Because DocketMath’s exact internal computation depends on the tool’s methodology settings and your entry structure, treat the following as a format guide for what to expect—your exact dollar figures will be calculated based on the tool’s current algorithm and your entries.

Here’s a typical set of outputs from the tool workflow:

How to interpret the totals

When you see Total Support, it’s just the combined output of the tool’s selected components. If you rerun with only Child Support, you’ll likely get a smaller monthly total; similarly, selecting only Alimony isolates the alimony component.

Also, the parenting-time split can shift the child-support portion more sharply than the alimony portion, depending on the tool’s weighting.

Jurisdiction-aware timeline note (Indiana)

Separately from the monthly math, your case may involve Indiana procedural timelines. Indiana’s general 5-year period is commonly referenced through Indiana Code § 35-41-4-2. The key point for your workflow:

• No claim-type-specific sub-rule was found in the information available for this article.
• Therefore, the tool/workflow references the general/default 5-year limitation rather than a specialized period.

This matters if you’re planning document collection, enforcement/adjustment readiness, or recordkeeping tied to timing.

Sensitivity check

A worked example is only useful if you test how outcomes respond to changes. Below are targeted sensitivity runs that show which inputs tend to move the numbers.

Run these in DocketMath using the same baseline facts from the “Example inputs” section, then adjust only one variable at a time.

Sensitivity set A: parenting-time shift (Parent A 35% → 50%)

Change: Parent A parenting time increases from 35% to 50% (and Parent B drops from 65% to 50%)
Keep constant: incomes, deductions, children = 2

Expected impact:

• Child Support: typically decreases when the noncustodial share increases (because the tool accounts for time-based support allocation).
• Alimony: may change less dramatically; however, it can still shift due to tool logic tied to income needs and resource distribution.

Practical action:

• If your actual schedule is closer to 50/50, rerunning with that split is often the fastest way to understand the direction of movement.

Sensitivity set B: payor income increase ($6,500 → $7,200)

Change: Parent A gross monthly income increases from $6,500 to $7,200
Keep constant: deductions ($600), Parent B ($2,500), parenting time (35/65), children = 2

Expected impact:

• Child Support: tends to increase because the income gap widens.
• Alimony: often increases as well, because alimony calculations frequently track the relative income difference and capacity.

Practical action checklist:

• Verify the income you entered is gross monthly (or the tool’s expected base).
• If your numbers are annual figures, convert consistently before entering.

Sensitivity set C: deductions change (Parent A deductions $600 → $900)

Change: Parent A allowable deductions increase from $600 to $900
Keep constant: gross income stays $6,500

Expected impact:

• Child Support: may decrease if deductions reduce the calculated net/available income.
• Alimony: may also decrease for the same reason—depending on how the tool applies deductions in the alimony component.

Sensitivity set D: adding special child costs ($0 → $200)

Change: Special child-related costs increase from $0 to $200/month
Keep constant: everything else

Expected impact:

• Child Support: typically increases to reflect added recurring child-related expenses.
• Alimony: may remain unchanged if the tool treats the special costs as only affecting child support needs.

Related reading

• Browse the blog