Why Alimony Child Support results differ in Tennessee
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Alimony Child Support calculator.
If you run DocketMath’s alimony-child-support calculator for Tennessee (US-TN) and notice different-looking numbers across scenarios, it’s usually because of Tennessee law + how the inputs are modeled, not because the tool is “wrong.” Below are the five most common drivers of different results.
Income used for each parent
- Alimony and child support calculations are highly sensitive to which income numbers you enter (for example: gross vs. net, earned vs. imputed, and what deductions you include or exclude).
- Even relatively small changes—like including overtime or adjusting excluded deductions—can shift monthly totals.
Custody and parenting-time assumptions
- Child support outcomes often move when the calculator treats custody-related facts differently—especially the time split you enter.
- Two cases can have the same incomes but different parenting-time inputs, and the outputs may diverge accordingly.
Alimony and child support don’t act like one combined figure
- Results can differ when you model alimony separately from child support (or when your inputs imply different eligibility/structure for alimony).
- That separation matters because the calculator’s alimony component and child support component respond to different input sets.
Rounding and pay-frequency conventions
- Differences can appear when one scenario uses a different pay frequency (e.g., monthly vs. biweekly) or when totals are rounded.
- DocketMath normalizes to its own calculator model; if you compare to another tool or spreadsheet, their normalization/rounding can differ.
**Jurisdiction-aware timing window (SOL-related effects)
- Tennessee applies a general one-year statute of limitations (SOL) period in this general context: Tennessee Code Annotated § 40-35-111(e)(2), with the general SOL period of 1 year as the default.
- Important: You noted that no claim-type-specific sub-rule was found, so treat this as the general/default period.
- Why this affects results: when you’re comparing “estimated support due” across dates, changing the effective date or time window changes “how much time is counted,” which can change totals—even if income/custody facts are identical.
Pitfall: If the only thing you changed between two runs is the effective date (or the time window), you can end up comparing two different “accumulation windows,” creating an apparent mismatch that isn’t really an input error.
How to isolate the variable
Use a controlled diagnostic method in DocketMath to pinpoint what moved the numbers.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
1) Freeze the facts, then change one input
Start with a baseline run (your best estimate), then change only one category at a time:
2) Record the outputs you’re actually comparing
Write down the outputs you’re comparing side-by-side, such as:
- Monthly child support output
- Monthly alimony output (if applicable)
- Any totals tied to the time window used
3) Use a “delta table” to spot sensitivity
Copy results into a small comparison table and compute the change:
| Input changed | Old value | New value | Child support delta | Alimony delta | Total delta |
|---|---|---|---|---|---|
| Income (payor) | |||||
| Parenting time | |||||
| Effective date / window |
4) Keep Tennessee timing assumptions consistent
If your question involves “how much is due over time” rather than only a monthly estimate, keep the dates/time window consistent. The Tennessee general default timing concept you’re working from is:
- General SOL period: 1 year
- Statute reference: Tennessee Code Annotated § 40-35-111(e)(2)
- Note: no claim-type-specific sub-rule was found in the brief, so this is treated as the general/default period
Next steps
Run three scenarios
- Baseline (best estimate of facts)
- Low-end inputs (lower income; adjust parenting time conservatively)
- High-end inputs (higher income; adjust parenting time in the opposite direction)
Compare component-by-component
- If child support changes but alimony does not, the driver is likely income/custody/time modeling for the child component.
- If both move, income normalization or alimony modeling inputs are likely the reason.
Lock your date assumptions before re-running
- If you’re comparing numbers across filings or proposed orders, make sure each run uses the same effective date and time window.
- Tennessee’s general default timing concept to keep in mind is the 1-year period under Tenn. Code Ann. § 40-35-111(e)(2) (general/default handling per the brief note).
Document your “input story”
- In 3–5 lines, record: which parent incomes you used, what parenting-time split you entered, and what dates define the calculation window. This makes it much easier to reconcile differences.
Gentle reminder: DocketMath is a modeling tool to help you understand variables—not a substitute for legal advice. If you’re making decisions for a real case, consider confirming assumptions with a qualified professional.