How to run Alimony Child Support in DocketMath for Tennessee

Step-by-step

This guide walks you through running Alimony + Child Support in DocketMath for Tennessee (US-TN) using jurisdiction-aware rules. It’s designed to help you operate the /tools/alimony-child-support calculator, understand which inputs matter, and see how the outputs change as you adjust them.

1) Open the correct calculator

1. Go to Alimony Child Support in DocketMath.
2. Confirm the jurisdiction context is Tennessee (US-TN).

   • If the tool allows jurisdiction selection, choose Tennessee (US-TN) before entering numbers.

2) Gather the baseline inputs the calculator needs

Before you type anything in, collect information in these categories (field labels may vary slightly in the tool):

• Income information

  • Each parent’s gross income (or whatever income type the tool requests, if it offers net/available income options).
  • Income frequency (weekly or monthly), if the calculator asks for it.

• Child information

  • Number of children.
  • Any custody/parenting-time inputs (if the tool includes them), such as a split or time allocation.

• Support intent / type selections

  • The tool may ask whether you’re estimating:

    • child support,
    • alimony, or
    • a combined estimate (often with separate sections).

• Alimony-specific parameters (if your run includes alimony)

  • Marriage length (or how the tool defines duration).
  • Any duration/period/category inputs the UI provides.
  • Any fields that define whether alimony is modeled as time-limited (duration/term) versus another structure.

If you’re missing an input, avoid guessing blindly. Instead:

• run once using your best-known values,
• then rerun after you add the missing detail,
• and compare how the results change.

3) Enter inputs and watch how the output changes

As you complete fields, DocketMath’s outputs typically update in predictable ways:

• Changing income values

  • Higher income generally increases estimated support amounts.
  • Even “small” income changes can produce larger differences if the tool uses tiers/thresholds or derived calculations.

• Changing custody/parenting-time selections (if available in the tool)

  • More time with the child for one parent often changes the child support estimate.
  • Expect the tool to recompute totals when you toggle these settings.

• Changing marriage length for alimony-related fields

  • Longer durations (as modeled by the tool) typically move alimony estimates upward and may affect modeled term/duration assumptions—depending on what the UI asks for.

If you want a range instead of a single estimate, do two runs:

• Run A (conservative assumptions): lower income figures, fewer credits/adjustments (based on what you believe is most likely).
• Run B (higher assumptions): higher income figures and more favorable settings (again, based on your best understanding). Compare the differences rather than forcing one number too early.

4) Review the breakdown output in the tool

After you submit or the tool auto-updates, look for an output section that commonly includes:

• Child support estimate (monthly—sometimes weekly depending on the UI)
• Alimony estimate (monthly and, where available, a duration/term)
• Total monthly combined estimate
• A line-item breakdown or summary table

Practical tip: if the tool provides multiple time formats (e.g., monthly and annualized), choose the one you need for comparison and keep it consistent across runs.

5) Understand the Tennessee timing framework shown (or implied) by the tool

Some DocketMath workflows show time-based logic or reference timing contexts in a results explanation.

For Tennessee, the provided jurisdiction data indicates:

• General SOL Period: 1 years
• Tennessee Code Annotated § 40-35-111(e)(2) as the referenced general statute/limitation framework

Crucially, the jurisdiction data also states:
No claim-type-specific sub-rule was found. That means the 1-year period should be treated as the general/default period, not a claim-specific SOL that automatically changes based on the type of claim.

So, if the tool surfaces “SOL” or timing language:

• treat it as general timing context in line with the jurisdiction data, and
• align it with your specific facts outside the calculator (since the tool can’t replace legal analysis).

6) Save or copy results for later comparison

If DocketMath provides options like download, share, or copy summary, use them.

To model scenarios cleanly:

• label each run (e.g., “TN baseline,” “TN higher income”),
• keep track of the inputs you changed,
• and record the outputs you care about:

  • monthly child support
  • monthly alimony (if included)
  • total monthly combined
  • any duration/term information shown by the tool

Checklist before closing the tab:

Common pitfalls

Even with a jurisdiction-aware calculator, the most common mistakes are usually input-related and then compounded by misunderstandings of what the output represents.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Input pitfalls that skew results

• Entering the wrong income time unit

  • Annual income entered into a monthly field (or vice versa) can distort the estimate dramatically (by roughly a factor of 10–12).

• Incorrect child count

  • Miscounting children—or accidentally double-counting—directly changes the child support portion.

• Running a combined estimate without fully completing alimony fields

  • Some tools may fill defaults if fields are missing.
  • That can yield an internally consistent result that still doesn’t match your intended scenario.

• Mismatched assumptions for parenting time/custody (if included)

  • Small changes to time-split inputs can create noticeable shifts in the child support output if the calculator recomputes based on that split.

Tennessee timing misunderstanding (SOL context)

Because the jurisdiction data provides a general/default timeframe and notes that no claim-type-specific sub-rule was found, be cautious about overgeneralizing:

• The “1-year general default” context should not automatically be treated as a universal timing rule for every situation.
• If the tool references timing, use it as general context and confirm how it applies to your specific facts outside the calculator.

Try it

Use this quick “two-run” method to sanity-check your DocketMath inputs for Tennessee (US-TN):

1. **Run 1 (Baseline)

   • Enter the best-known income figures.
   • Enter the correct number of children.
   • Fill in alimony fields if you want an alimony estimate included.

2. **Run 2 (Sensitivity check)

   • Change one variable only.

     • Example: adjust one parent’s income slightly.
   • Keep every other input the same.

Compare the output totals:

• If the numbers barely change, confirm the field you edited is actually connected to the output you’re observing (or that the tool is using that input as you expect).
• If the numbers shift dramatically, double-check:

  • you used the correct income frequency/unit (monthly vs annual),
  • the parent assignment is correct,
  • and the tool recalculated as expected.

When you’re ready to run for real scenarios, start here:

• **Primary CTA: Run Alimony Child Support in DocketMath

If you want to compare multiple scenarios, capture for each run:

• monthly child support estimate
• monthly alimony estimate (if included)
• total monthly combined figure
• any duration/term information shown by the tool

Related reading

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