Inputs you need for Alimony Child Support in Tennessee

6 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

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

To run DocketMath’s Alimony Child Support calculator for Tennessee (US-TN), gather the inputs below before you click /tools/alimony-child-support. These inputs typically fall into three buckets: family details, income/earning capacity, and any case-specific adjustments.

Note: This guide is for planning and calculation inputs—not legal advice. Court orders depend on the case record and the judge’s findings.

A. Case and parenting context

  • ☐ **Filing county / court location (optional but helpful)
  • How many children the order will cover
  • Current parenting schedule (even a rough description helps)
  • Any child-related expenses you expect to be relevant to the calculation (if your workflow captures them)

B. Income inputs (most important)

For each parent (Mother/Father or “Parent A/Parent B”), collect:

  • Gross monthly income
  • Any additional income sources (bonus, commission, rental income, overtime—whatever applies)
  • Regular work hours / employment status (employed, self-employed, seasonal)
  • Recent pay stubs or year-to-date figures (used to estimate monthly totals)

If a parent is self-employed, also collect:

  • Business income details (profit vs. gross receipts—use what your records support)
  • Last 12 months of summaries (bank deposits, tax figures, or accounting summaries)

C. Support-relevant numbers

  • Requested or expected alimony term goal (e.g., temporary vs. longer-term planning—use your case posture)
  • Marital duration (start/end dates or total time)
  • Any health-related or disability constraints affecting income (if you can document them)

D. Timing and documentation strategy (don’t skip this)

Tennessee has a general default limitations period of 1 year for the type of claim that would otherwise be governed by Tennessee Code Annotated § 40-35-111(e)(2). Because your workflow may involve enforcement-related questions, track timelines carefully so your planning assumptions stay consistent.

  • Date of the event triggering the clock (e.g., the relevant decision date or when the issue arose)
  • When the unpaid amount began accumulating
  • How far back you’re planning to calculate/seek recovery for planning purposes

The “default” nature matters: no claim-type-specific sub-rule was found, so the period described above is the general baseline rather than a tailored rule for every scenario.

Warning: Using an outdated “lookback” window can make the numbers seem inconsistent with what may be enforceable later. DocketMath can help you model amounts, but your timeline still needs to line up with the governing limitations period.

Where to find each input

Use this checklist to quickly locate the data you’ll plug into DocketMath.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Income and earnings

  • Pay stubs (last 4–6 stubs): gross pay, deductions, YTD totals
  • Year-to-date statements / employer summaries: confirm consistency
  • W-2s / 1099s / self-employment schedules: support estimates for months where pay fluctuates
  • Bank statements (self-employed or irregular income): corroborate deposits

2) Parenting context

  • Parenting plan documents (current schedule, holiday allocations)
  • Proposed schedule (if you’re calculating for planning during negotiations)
  • Any prior court order: use the most recent schedule that controls day-to-day life

3) Marriage and timeline facts

  • Marriage certificate date for marital start
  • Date of separation and/or filing date depending on what your preparation is modeling
  • Any decree or order already entered (if you’re updating numbers)

4) Any special considerations

  • Medical/disability documentation that affects work capacity (if available)
  • Evidence of additional recurring payments (childcare payments, transportation, extraordinary costs) if your input workflow captures them

5) Limitations period planning (Tennessee baseline)

For limitations planning, locate:

  • ☐ The date the issue started (or the relevant event date tied to your paperwork)
  • ☐ The current date you’re modeling from

Then apply the general baseline that corresponds to Tennessee Code Annotated § 40-35-111(e)(2) (general 1-year period).

Reminder: The content above reflects a general/default baseline. It may not cover every situation if a different fact pattern or rule is applied in your specific case.

Run it

Start by going to /tools/alimony-child-support. DocketMath uses the inputs you provide to compute projected alimony and child support amounts (based on the calculator’s Tennessee-aware jurisdiction configuration).

To get accurate outputs, follow this order:

  1. Enter each parent’s gross monthly income
    • If one parent’s income changes seasonally, use a monthly average for the period you’re modeling.
  2. Add additional income sources
    • Bonus/commission/overtime can materially shift projected support.
  3. Set children count and parenting context
    • Even small schedule differences can affect results when the tool accounts for parenting time structure.
  4. Add marital duration inputs
    • Longer marriages often produce a different modeling range than shorter ones.
  5. Include any case adjustments you track
    • If DocketMath asks for them, enter only what your records support.

How outputs typically change when inputs change

Use these “sensitivity” rules while you model scenarios:

  • Higher income for Parent A → generally increases the support obligation attributed to Parent A (and vice versa).
  • Increased parenting time for the paying parent → may reduce the amount because the calculator may attribute more direct child support via time.
  • More children → increases total child support needs reflected in the computation.
  • New or corrected income numbers → often causes the biggest swings—recheck pay stubs before rerunning.

Pitfall: Don’t round incomes aggressively. If the calculator accepts only whole numbers, round conservatively from the most reliable YTD figure; rounding can compound across monthly and annual assumptions.

Modeling multiple scenarios (recommended)

If you’re preparing for discussions or drafting, run at least two scenarios:

  • Scenario 1: Current documented income
  • Scenario 2: Adjusted income (e.g., after a job change or expected overtime/bonus changes)

Then compare results month-to-month (or order-of-magnitude) to understand what drives the outcome most in Tennessee.

Related reading