Worked example: Alimony Child Support in Pennsylvania

Example inputs

Below is a worked example showing how you can model alimony + child support in Pennsylvania with DocketMath using jurisdiction-aware rules.

Assumptions for the example

To keep the math concrete, the parties and timeline are simplified:

• County / court context: not specified (the example focuses on the DocketMath calculator and Pennsylvania general rules)
• Filing posture: not specified
• Income type: wages for both parties (simplified)
• Health insurance costs: not included (kept out to focus on the core support inputs)
• Retroactivity: not included

Inputs (example numbers)

Use these as the “facts” you’ll enter into DocketMath → alimony-child-support.

Household income inputs

• Payor gross monthly income (before deductions): $6,500
• Recipient gross monthly income (before deductions): $3,200

Child facts

• Number of children: 2
• Children ages: 7 and 12

Alimony inputs (modeling choice)

• Alimony goal for the model run: include an alimony component in addition to child support (so you see combined cashflow)
• Monthly alimony amount to compare: $800

Duration (for SOL context)

Pennsylvania’s general statute of limitations (SOL) information is included here as a general timing reference used in the tool’s jurisdiction-aware logic:

• General SOL period: 2 years
• General Statute cited: 42 Pa. Cons. Stat. § 5552
  Source: https://www.legis.state.pa.us/WU01/LI/LI/US/PDF/2000/0/0136..PDF

Important clarity: No claim-type-specific sub-rule was found in the available jurisdiction data, so this is presented as the general/default period rather than a narrower category-specific SOL.

Quick checklist (so your run is reproducible)

Example run

You can reproduce this run directly in DocketMath by visiting:

• Primary CTA: /tools/alimony-child-support

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.

How the tool is applying Pennsylvania jurisdiction-aware defaults (general SOL)

Pennsylvania’s general/default period shown in the tool is based on the general statute of limitations:

• 2 years under 42 Pa. Cons. Stat. § 5552
• Important clarity: No claim-type-specific sub-rule was found in the available jurisdiction data, so the tool uses the general/default period rather than a narrower category-specific SOL.

Running the scenario (example inputs → example outputs)

Inputs recap:

• Payor: $6,500/month gross
• Recipient: $3,200/month gross
• Children: 2 (ages 7 and 12)
• Modeled alimony: $800/month
• Jurisdiction: Pennsylvania (US-PA)

Example output you should expect from DocketMath (illustrative structure):

• Child support (monthly): calculated from the calculator’s PA child support logic using the income + child facts you provided
• Alimony (monthly): $800/month (as modeled for comparison)
• Combined total (monthly): child support + modeled alimony

Because the precise numeric child-support output depends on the calculator’s internal PA formula implementation and any wage-credit/deduction modeling choices you’ve selected in the tool interface, treat the key takeaway as the relationship between inputs and outputs:

What the numbers are doing conceptually

• Child support typically increases when:

  • payor income rises,
  • recipient income falls,
  • the number of children increases,
  • children are in higher-cost age brackets (as applicable in the tool’s Pennsylvania logic).
• Alimony affects only the alimony portion of the monthly total in this modeled example; it doesn’t automatically “replace” child support.

Cashflow comparison (combined payments)

In a combined model, your monthly outgoing obligation is effectively:

• **Combined monthly obligation = (Child support) + (Alimony)

So with:

• Alimony = $800, your combined total is always at least the child support amount plus $800.

Timing note: SOL (general) implications for collections planning

With 42 Pa. Cons. Stat. § 5552 providing a 2-year general SOL period (based on the jurisdiction data available here), the practical planning idea is:

• If you’re thinking about how far back collection efforts may reach under general timing rules, the relevant window referenced by the tool is 2 years.
• Again, the tool’s SOL logic is general/default in this dataset because no claim-type-specific sub-rule was found.

Sensitivity check

Now that you have one baseline run, test how changes in inputs affect the combined output. This is where DocketMath helps you see directionality—not just a single number.

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 scenario A: Raise payor income by 10%

Keep everything the same except:

• Payor income: $6,500 → $7,150 (+$650 / month)
• Recipient income: $3,200 unchanged
• Children: 2 (ages 7 and 12) unchanged
• Modeled alimony: $800 unchanged

Expected effect:

• Child support increases (because the payor’s resources increased)
• Alimony stays the same in this modeled setup (since we held $800 constant)
• Combined total increases (the increment is driven mainly by the change in child support)

Use it to answer:

• “If the payor’s wages rise, how much of the combined payment moves with child support versus staying fixed with modeled alimony?”

Sensitivity scenario B: Increase alimony by $300/month

Reset to baseline incomes, then change only:

• Modeled alimony: $800 → $1,100 (+$300/month)

Expected effect:

• Child support stays the same in the simplified modeling where alimony doesn’t alter child support inputs inside the calculator
• Combined total increases by $300/month, because the alimony component is directly added to the total

Use it to answer:

• “How sensitive is the combined cashflow to the alimony assumption alone?”

Sensitivity scenario C: Add a child (2 → 3)

Return to baseline incomes. Change:

• Number of children: 2 → 3
• Ages: if your tool requires specific ages for all children, enter plausible ages for the third child (e.g., 4 years old) consistent with your fact pattern.

Expected effect:

• Child support increases meaningfully (more dependents)
• Alimony stays the same in this modeled setup ($800)

Use it to answer:

• “How dependent is the combined payment amount on the child count inputs?”

Quick sensitivity summary table (directional)

SOL reminder for planning windows

Even when you adjust monthly obligations, the general/default SOL referenced by the jurisdiction data remains:

• 2 years under 42 Pa. Cons. Stat. § 5552
• Tool logic used here: general period only, because no claim-type-specific sub-rule was found.

Related reading

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