Worked example: Alimony Child Support in Arkansas

Example inputs

This worked example shows how DocketMath can calculate an alimony/child support–style result for a hypothetical case in Arkansas (US-AR) using jurisdiction-aware defaults. It’s a demonstration of mechanics—not legal advice and not a substitute for advice from a qualified attorney.

Scenario (hypothetical)

• Filing date of relevant support request (for timing context): June 1, 2024
• Custody assumption: One parent has primary custody
• Support amounts (entered as assumptions for the calculator run):

  • Mother’s gross monthly income: $3,500
  • Father’s gross monthly income: $4,200
  • Number of children: 2
  • Child-related input for calculator: standard needs assumption (entered exactly as the tool requests)
  • Requested spousal support (“alimony”) starting amount: $0 (to focus the run on child support mechanics)
  • Ongoing spousal support: $450/month (entered as an assumption for demonstration purposes)

Timing context (Arkansas general limitations period)

DocketMath also surfaces timing context for enforcement actions using Arkansas’s general statute of limitations:

• General SOL period: 6 years
• Statute: Ark. Code Ann. § 5-1-109(b)(2)

No claim-type-specific sub-rule was found for this example, so the general/default period applies:

• Default statement for this article: Because no claim-type-specific sub-rule was found, this worked example uses the general six-year period under Ark. Code Ann. § 5-1-109(b)(2) as the default.

Example run

In DocketMath, you’ll use the /tools/alimony-child-support calculator. The steps below reflect how a jurisdiction-aware run typically behaves for US-AR.

Step-by-step inputs (what you’d type/select)

Check the boxes that match your situation (if your UI uses checkboxes):

• Arkansas jurisdiction (US-AR)
• 2 children
• Provide both parents’ gross monthly income
• Provide an alimony/spousal support input (even if you set it to $0 for a focused run)
• Include additional adjustments (only if your DocketMath form requests them)

Values used in this example

What DocketMath outputs (illustrative structure)

Running alimony-child-support with the above inputs produces outputs in a few categories—typically:

1. Child support component (monthly)
2. Spousal support component (monthly), reflecting your alimony input
3. Combined monthly support (child + spousal)
4. Timing/enforcement context (based on the default SOL rule used in this article)

Because the calculator is designed to be jurisdiction-aware, the Arkansas timing context ties back to:

• Ark. Code Ann. § 5-1-109(b)(2) → 6-year general SOL

Example output (how to read it)

Assume the calculator returns the following structure (actual numeric totals depend on the tool’s built-in formulas and the exact form fields you enter):

• Estimated child support: $1,050/month
• Entered/assumed spousal support (alimony): $450/month
• Total estimated combined monthly support: $1,500/month
• Default SOL timing context: 6 years under Ark. Code Ann. § 5-1-109(b)(2)

A quick internal “consistency check”

Even without changing the facts, you can sanity-check the run:

• If you increase the higher-income parent’s income from $4,200 to $4,700, the child support component generally trends upward.
• If you set spousal support input to $0, the child component should not automatically drop just because alimony is $0—these are typically treated as separate components in tools like this.

Practical takeaway from this run

This run demonstrates two key mechanics you can reuse:

• Income + number of children drive the child support component.
• Spousal support is influenced by your alimony/spousal input and stays separate for comparison purposes.
• Arkansas timing context uses the general 6-year default (because no claim-type-specific sub-rule was identified for this example).

Sensitivity check

Now change one input at a time and observe how outputs shift. This is a practical way to understand which levers matter most in your DocketMath run.

Sensitivity 1: Change income gap (child support sensitivity)

Keep everything the same, but adjust father’s income.

• Baseline father income: $4,200
• New father income: $5,000
• Children: 2
• Spousal support input: $450/month (unchanged)

Expected directional result

• Child support component: increases
• Spousal support component: unchanged (because you entered $450)
• Total combined: increases primarily due to child support

Sensitivity 2: Change number of children

Keep incomes the same and change the children count.

• Mother income: $3,500
• Father income: $4,200
• Spousal support input: $450/month
• Children:

  • Run A: 1 child
  • Run B: 2 children
  • Run C: 3 children

Expected directional result

• Child support component: increases as number of children increases
• Spousal support component: unchanged in a pure “input-driven” model
• Total combined: grows with the child support component

Sensitivity 3: Change alimony input (spousal support sensitivity)

Hold child-related inputs constant and vary spousal support input.

• Mother income: $3,500
• Father income: $4,200
• Children: 2
• Spousal support input:

  • Run A: $0
  • Run B: $300
  • Run C: $600

Expected directional result

• Child support component: unchanged (if DocketMath treats alimony input separately)
• Spousal support component: changes exactly to what you enter (or according to the tool’s formula, if it computes)
• Total combined: changes by the difference in spousal support input

Timing sensitivity: SOL default reminder (not monthly math)

To avoid confusion: the 6-year default under Ark. Code Ann. § 5-1-109(b)(2) affects timing/enforcement context, not the monthly support amount.

• Monthly totals come from the support calculation logic.
• SOL context is a separate output or reference point.

Related reading

• Browse the blog