Spreadsheet checks before running Alimony Child Support in Tennessee

What the checker catches

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

Before you run a Tennessee alimony/child support calculation in DocketMath, do a quick “spreadsheet hygiene” pass. Most spreadsheet mistakes aren’t caused by the law—they come from mismatched inputs, stale values, and unit/date issues that quietly change outputs.

DocketMath’s alimony-child-support checker is built to catch common spreadsheet issues that can skew results in US-TN workflows. Use it to find problems early, before you rely on totals or proceed with any next-step calculations.

Common checks (and what they prevent)

• Date inconsistencies

  • Examples: a typo like 2025-13-01, or mixing 03/01/2024 with 01/03/2024.
  • Why it matters: even a small date shift can change timeline calculations and downstream support totals.

• Missing or mismatched income fields

  • Examples: entering gross income in a column that should be net (or vice versa), or leaving overtime/bonus blank when your paystub includes it.
  • Why it matters: support often starts from the “baseline” income—if that input is wrong or incomplete, the rest can cascade.

• Frequency mismatches

  • Example: entering an annual salary as if it were monthly.
  • Why it matters: monthly outputs can be off by a factor of 12 (or the reverse).

• Cell formatting and unit problems

  • Examples: entering a percentage as 10 instead of 0.10, or having currency/number fields stored as text.
  • Why it matters: calculations may multiply incorrectly, or a formula may fail in a way that doesn’t look obviously broken.

• Age / eligibility-related date windows

  • Example: a child’s birth date doesn’t match the worksheet you’re using elsewhere.
  • Why it matters: eligibility timing can affect how durations are treated and how totals are prorated.

• Spreadsheet “copy-forward” mistakes

  • Example: copying a row but forgetting to update a child’s birth date or an income source.
  • Why it matters: you may be calculating using the wrong demographic or earnings profile.

• **Silent blanks (empty cells referenced by formulas)

  • Example: a formula references a cell that’s blank (or contains an old value).
  • Why it matters: depending on the spreadsheet logic, blanks can act like zeros or bypass validation.

Jurisdiction-aware rule note (Tennessee)

Tennessee’s general statute of limitations period is 1 year under Tennessee Code Annotated § 40-35-111(e)(2). In the absence of a claim-type-specific sub-rule in the provided jurisdiction data, the checker uses this general/default 1-year SOL as its validation framework.

Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

That means: if your spreadsheet inputs imply timeliness issues, the checker will apply the general 1-year SOL default rather than attempting a narrower carve-out.

Gentle disclaimer: This checker helps you avoid data and formatting problems. It doesn’t replace a legal review, and it can’t account for every scenario not represented in your spreadsheet inputs.

When to run it

Run the checker at three points in your workflow—like quality gates—so problems don’t make it into the final numbers.

1. Before entering numbers into DocketMath

   • Goal: confirm your spreadsheet columns and date formats match what the calculator expects.
   • Practical moves:

     • Use a consistent date format (e.g., YYYY-MM-DD).
     • Confirm income frequency (weekly/biweekly/monthly/annual).

2. Right after you paste or import worksheet values

   • Goal: catch transcription errors immediately.
   • Practical moves:

     • Verify the number of children and income streams match what you intended.
     • Don’t rely on a single “looks right” output—use the checker to validate structure.

3. After any “small” edits

   • Goal: detect knock-on effects from changes that seem minor.
   • Practical moves:

     • If you update a date (like commencement/start date) or refresh one income component, rerun checks even if the sheet “looks the same.”

Quick “input readiness” checklist (run before trusting results)

Try the checker

Ready to test the process? Follow this simple workflow in DocketMath:

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Recommended workflow (US-TN)

1. Open the tool

   • Use the primary CTA to go to the calculator page: /tools/alimony-child-support
2. Paste or enter your spreadsheet values

   • Keep each variable aligned with how you calculated it in your spreadsheet (don’t mix gross/net assumptions).
3. Run the spreadsheet checks

   • Fix validation issues before reviewing the results.
4. Re-check after each fix

   • Update one input at a time (for example, income frequency or one key date), then rerun.

How outputs typically change when a checker finds problems

Related reading

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