Worked example: Alimony Child Support in Louisiana

Example inputs

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

Below is a worked example showing how DocketMath can produce a jurisdiction-aware estimate for alimony and child support calculations in Louisiana. This example is designed to help you understand the mechanics of the tool, not to provide legal advice.

Scenario (example only)

Assume a Louisiana divorce where:

• Filing/judgment date (for SOL timing purposes): January 10, 2026
• Monthly earned income (combined estimate for calculations):

  • Paying spouse (Payor): $6,500/month gross income
  • Receiving spouse (Payee): $3,000/month gross income
• Children: 2 children
• Parenting time:

  • Payor has 30% overnights (example value used for the calculator’s schedule logic)
• Health insurance:

  • Payor pays $450/month for children
• Other adjustments (example):

  • Child care: $300/month
• Alimony type:

  • Example uses the calculator’s alimony-child-support workflow (no claim-specific customization was provided in the brief)

Using Louisiana jurisdiction rules in the background

DocketMath applies a general/default jurisdiction rule where a claim-type-specific sub-rule was not found. For any general timing context (such as measuring or forecasting based on statutory periods), the example uses:

• General statute: La. Rev. Stat. Ann. § 9:2800.9
• General SOL period: 1 year
• Source link provided in this brief: https://louisianabaptists.org/resources/sexual-abuse-response-resources/sexual-abuse-definitions-and-louisiana-statutes/?utm_source=openai

Note (important): This 1-year “general SOL period” is the default used here because the brief explicitly indicates no claim-type-specific sub-rule was found. That means the timing logic should be treated as a baseline, not as a specialized rule for every possible support-related claim category.

What you’ll enter in DocketMath (checklist)

If you want to run this exact structure yourself, use the primary CTA: /tools/alimony-child-support.

Example run

Here’s what the DocketMath run is intended to illustrate: how the tool turns your inputs into a structured output that separates child support components and alimony-related components.

Run the Alimony Child Support calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Income baseline

DocketMath starts with the income inputs you provide:

• Payor: $6,500/month
• Payee: $3,000/month

Total combined gross baseline (example framework): $9,500/month

This matters because support estimates generally track relative ability to pay and the children’s needs. Even if your final numbers depend on additional statutory factors, changes to income inputs typically create the largest swings in monthly outcomes.

Step 2: Children + parenting time effect

With 2 children and 30% parenting time for the Payor (example overnights), the tool applies parenting-time logic to adjust the portion attributable to the Payee’s household.

Practical effect:

• Higher parenting time for the Payor often reduces the Payor’s child-support responsibility (because the children spend more time in Payor’s care).
• Lower parenting time generally increases the amount attributed to the Payee’s household.

Step 3: Direct expense add-ons

The example includes two common add-on inputs:

• Health insurance for children: $450/month
• Child care: $300/month

Those costs typically increase the combined monthly obligation attributable to the children’s needs (though the exact treatment can vary by calculation method and the tool’s model).

Step 4: Alimony model integration

DocketMath also integrates alimony considerations in the alimony-child-support workflow. In this worked example, the point is not to predict a court outcome, but to show how outputs behave when you change the same levers (income, time, and child-related expenses).

Step 5: Timing context (1-year default period)

Because the brief’s jurisdiction data provides a general SOL period of 1 year and references La. Rev. Stat. Ann. § 9:2800.9, DocketMath’s timing context uses:

• General period: 1 year
• General statute: La. Rev. Stat. Ann. § 9:2800.9

If the relevant event date used by your scenario is 01/10/2026, the default one-year baseline would run through 01/10/2027 for any general-timing logic within the tool’s model.

Sample output structure (illustrative)

Your actual DocketMath numbers will depend on the calculator’s internal formulae and any settings you select. However, the output typically separates totals like:

To confirm the exact dollar figures, run the tool at /tools/alimony-child-support using the inputs listed above.

Sensitivity check

Use this section to see how outcomes usually change when you adjust inputs—without assuming any one adjustment will behave identically in every model. In DocketMath, the goal is to understand which variables most affect your monthly totals.

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.

1) Parenting time: 30% → 40%

Keep everything else the same, but change Payor parenting time:

• Payor parenting time: 30% → 40%

Expected direction:

• Child support responsibility for the Payor generally decreases as parenting time increases (the children spend more time with the Payor).

What to look for in the tool output:

• “Total child support” should move downward.
• “Combined estimate” should move downward unless alimony increases in your selected model due to relative income/time inputs.

2) Payor income: $6,500 → $7,200

Update only Payor gross monthly income:

• Payor income: $6,500 → $7,200

Expected direction:

• Child support estimate typically increases because ability to pay rises.
• Alimony estimate may also increase, depending on how the alimony workflow weighs relative income levels.

3) Child care: $300 → $0

Set child care to zero while keeping insurance unchanged:

• Child care: $300/month → $0/month

Expected direction:

• Child-related add-ons should drop by approximately the amount of child care removed (though the calculator’s treatment may include caps/weighting rules).
• Total child support should decrease correspondingly.
• Alimony is usually less directly tied to child care costs than to income, so alimony may shift less—or not at all—depending on model assumptions.

4) Timing context: confirm the 1-year default baseline

Change the timing date used in your scenario:

• Date input: 01/10/2026 → 02/01/2026

Expected direction:

• The one-year default endpoint shifts accordingly (by about 22 days).
• The key takeaway is that the timing component is a calendar baseline, not a support formula driver like income or parenting time.

Related reading

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