Common Alimony Child Support mistakes in Florida

The top mistakes

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

Below are common Florida mistakes people make when calculating alimony and child support—and how those errors typically show up in real disputes. This is practical guidance for improving your inputs and document trail (not legal advice).

1) Mixing up alimony and child support categories

In Florida, alimony and child support are often discussed together, but they aren’t interchangeable:

• Child support is calculated using Florida’s child support framework and focuses on the child’s needs and each parent’s financial circumstances.
• Alimony addresses spousal support considerations and has its own determination factors.

error pattern: using one number for multiple lines in a spreadsheet, or assuming a payment plan “covers everything” without correctly allocating amounts.

2) Using outdated or incomplete income inputs

DocketMath’s alimony-child-support calculator (and any worksheet approach) is only as accurate as the numbers you feed it. Common failures:

• Omitting bonus, overtime, commissions, or second-job income
• Averaging over too short a period
• Forgetting to update income after job changes

error pattern: entering “current salary only” when the underlying financial picture includes more than base pay.

3) Incorrect handling of retirement, benefits, or non-wage compensation

Families often rely on a mix of:

• retirement payouts or distributions
• insurance-related benefits
• other compensation that isn’t paid like a regular paycheck

error pattern: treating all income as identical and adding it inconsistently (for example, counting it in narrative documents but not in the calculator inputs).

4) Ignoring custody/parenting time reality when it changes calculations

Child support calculations depend heavily on parenting time structure and related factors.

error pattern: using a “standard” schedule in the calculator when actual parenting time differs (for example, alternating weekends plus additional midweek time). Even small schedule differences can change outputs materially when the model accounts for parenting time.

5) Misreading outputs as fixed obligations rather than scenario-based results

DocketMath generates results based on inputs and assumptions. If the facts change, the numbers change.

error pattern: using calculator output as a final determination—then failing to reconcile it with:

• the actual agreement or order language
• future income changes
• parenting time adjustments

6) Not documenting the “why” behind each input

A calculator is fast; evidence is slower. If your inputs can’t be tied to pay stubs, tax returns, or signed schedules, you may face unnecessary friction later.

error pattern: entering numbers from memory or informal notes rather than source documents.

7) Missing the record-keeping window (and creating a timeline problem)

Because the general SOL period is 4 years under Florida Statute § 775.15(2)(d), losing supporting materials can hurt your ability to justify calculations and adjustments.

Pitfall: waiting until disputes arise, then trying to reconstruct income, parenting time logs, or payment history from scratch.

How to avoid them

Use DocketMath to improve both accuracy and defensibility: accurate inputs produce outputs that match your supporting documents, and clear documentation supports consistency across revisions. Start by using the /tools/alimony-child-support calculator with your current facts.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Start with a clean input checklist (before you click calculate)

Create a worksheet with four columns: input, value, source document, date obtained.

Common inputs to collect:

• Income figures by type (base pay, overtime, commissions/bonuses)
• Employment dates (for averaging periods)
• Parenting time schedule (and any confirmed deviations)
• Current child/household facts relevant to the model you’re using
• Any agreed or court-ordered offsets you intend to reflect in the scenario

Then, run the /tools/alimony-child-support calculator with consistent assumptions each time.

Use DocketMath intentionally: run scenarios, don’t “guess once”

A practical workflow:

1. Baseline run: enter the current known facts.
2. Sensitivity run: adjust one variable at a time (e.g., bonus average, parenting time frequency, or income change timing).
3. Reconcile run: ensure your revised inputs match the documents you plan to cite.

This helps you see which inputs move the result most—so you can focus verification efforts where they matter.

Protect your accuracy by validating “income math”

Before entering numbers into DocketMath:

• Convert gross vs. net consistently (don’t mix “take-home” in one line and “gross” in another).
• For variable income (bonus/commission), use a defined averaging method you can explain later (e.g., average over the same period across runs).
• If income is transitioning (job change, reduced hours), document the start date and anticipated adjustment period.

Match the calculator’s assumptions to your parenting-time facts

If your real schedule differs from what you used:

• update the schedule assumptions
• rerun DocketMath immediately
• save the calculation version with a timestamp

This prevents the common “wrong schedule, wrong number” problem that can fuel disputes.

Keep a timeline pack aligned to the 4-year general record window

Because Florida’s general SOL is 4 years under § 775.15(2)(d) (default/general period), organize your documents so you can retrieve them quickly within that window.

A strong timeline pack typically includes:

• pay stubs and employment verification
• tax return summaries (when used)
• parenting time logs or calendars
• payment confirmations and receipts
• copies of agreements/orders and amendments

Use iteration and version control

Each time facts change, treat the calculator output as a new scenario, not an update to an old one.

Practical versioning habits:

• Save a PDF/screenshot of key assumptions and results
• Name files by date and scenario (e.g., “2026-04-15_baseline_income_updated”)
• Keep a short change log: what changed and why

Know your likely most impactful inputs

While the exact sensitivity depends on the calculator model and your fact pattern, these categories frequently drive result changes:

• employment income (especially variable components)
• timing and averaging of income
• parenting time structure
• any inputs related to allocation between child support and alimony

Target verification on those first.

Related reading

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