Worked example: Alimony Child Support in Maine

Example inputs

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

Below is a worked example for Maine using DocketMath’s alimony-child-support calculator (jurisdiction: US-ME). This is a practical walkthrough of the mechanics—not legal advice. Outcomes depend on the full case record and the specific orders sought.

Scenario (example facts)

Assume the court is working with these monthly figures for the parties:

• Payor’s gross monthly income: $5,500
• Payor’s allowable monthly expenses (if applicable in your inputs): $1,200
• Payee’s gross monthly income: $3,200
• Number of children: 2
• Child’s ages: 6 and 10
• Health insurance costs (monthly): $220
• Out-of-pocket childcare (monthly): $180
• Standard visitation adjustment factor: none (use default)
• Any spousal support request: yes (alimony/maintenance included in the run)

Time-related rule used for this example

For Maine, this example illustrates how DocketMath can incorporate jurisdiction-aware timing concepts. The brief timing input used here comes from the general default period:

• General SOL period (default): 0.5 years
• General Statute cited: Title 17-A, § 8
• Source: https://legislature.maine.gov/statutes/17-a/title17-asec8.html?utm_source=openai

Important clarification: No claim-type-specific sub-rule was found. The content below therefore uses the general/default 0.5-year period as a baseline. If the relevant claim category differs in a real case, the timing inputs (and any timing-driven outputs) could change.

What you would enter into DocketMath

In DocketMath, you’d typically set:

• Jurisdiction: Maine (US-ME)
• Income fields: payor and payee gross monthly income (and any expense-related inputs if your worksheet uses them)
• Children: number of children + ages (so child-related logic aligns)
• Child-related costs: health insurance (monthly) and childcare (monthly)
• Spousal support: enable the alimony/maintenance portion (since this example includes a spousal support request)

If you’re following along in the app, start from the calculator page at /tools/alimony-child-support.

Example run

Let’s run the example with the scenario numbers above.

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.

DocketMath configuration (US-ME)

• Jurisdiction-aware logic: US-ME
• Default timing period used in this example: 0.5 years based on Title 17-A, § 8
• Supports included:

  • Child support (driven by incomes, number/ages of children, and child-related costs)
  • Alimony/maintenance (enabled because the spousal support request flag is on)

What DocketMath outputs (worked demonstration)

Because DocketMath’s calculations are numeric and input-dependent, your exact totals will reflect the exact values you enter. For a worked demonstration, imagine DocketMath produces a monthly combined support estimate like this:

Treat the table as an illustration of how outputs often break down—not a guarantee of identical figures for your inputs or your court’s order.

Applying the timing logic (the 0.5-year default)

In this walkthrough, the jurisdiction-aware “timing” component uses the general/default SOL period of 0.5 years tied to Title 17-A, § 8.

Practical interpretation for this run:

• If you’re modeling a question involving a general limitations-period concept, DocketMath uses the 0.5-year baseline rather than a longer/shorter claim-type-specific period.
• If the case involves a different claim category, DocketMath’s timing-driven outputs could shift even if the monthly math inputs remain the same.

Common pitfall: People often change income numbers but forget to revisit jurisdiction settings and timing assumptions. In Maine-focused runs, the default 0.5-year period from Title 17-A, § 8 can affect “when” a modeled event is considered, which may matter depending on what you’re trying to estimate.

Where the numbers usually move the most

In most support modeling, the biggest swings typically come from:

• Payor income (higher income generally increases support pressure)
• Payee income (higher income generally reduces support pressure)
• Number and ages of children (affects the child-support component)
• Health insurance and childcare amounts (often appear as separate adjustments/add-ons)
• Whether alimony is enabled (spousal support can add a significant monthly amount)

Sensitivity check

Now test how changing a few inputs changes the result. The goal isn’t to predict a final court order—it’s to understand which inputs drive the model output.

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.

Sensitivity test A: Increase payor income by $500/month

• Change: Payor gross monthly income from $5,500 → $6,000
• Everything else stays the same.

Expected direction: higher combined support output (increased ability to pay).

Example outcome (illustrative):

• Total estimated monthly support: $2,350
• Change vs. baseline: +$250/month

Sensitivity test B: Increase payee income by $500/month

• Change: Payee gross monthly income from $3,200 → $3,700
• Everything else stays the same.

Expected direction: lower combined support output (increased ability/contribution on the payee side).

Example outcome (illustrative):

• Total estimated monthly support: $1,900
• Change vs. baseline: -$200/month

Sensitivity test C: Add one more child (from 2 → 3)

• Change: Number of children: 2 → 3
• Ages: keep the first two as 6 and 10; add a third with age 4 (example)
• Keep incomes and costs unchanged.

Expected direction: higher child-support component (often increases base and may adjust add-ons).

Example outcome (illustrative):

• Total estimated monthly support: $2,500
• Change vs. baseline: +$400/month

Sensitivity test D: Health insurance increases

• Change: Health insurance $220 → $300
• Everything else stays the same.

Expected direction: total increases because the insurance line item rises.

Example outcome (illustrative):

• Total estimated monthly support: $2,180
• Change vs. baseline: +$80/month

Sensitivity test E: Timing assumption reminder (SOL logic)

If you keep all financial inputs identical but adjust the jurisdiction timing category (when applicable in a future run), you’re testing “when” concepts tied to Maine’s general/default 0.5-year baseline.

• This example uses 0.5 years because no claim-type-specific sub-rule was found.
• If the claim category differs in your fact pattern, timing-driven outputs may change even if the monthly support component appears similar.

Quick checklist before trusting a run

Before you rely on a DocketMath output, verify:

• Default used here: 0.5 years from Title 17-A, § 8

A simple sanity check: increasing payor income should generally raise support, and increasing payee income should generally reduce support. If you see the opposite, re-check that each input is assigned to the correct party.

Related reading

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