How to run Alimony Child Support in DocketMath for Florida

Step-by-step

Here’s a practical way to run Alimony + Child Support calculations in DocketMath for Florida (US-FL) using jurisdiction-aware defaults. This walkthrough focuses on how to enter inputs so the tool output updates correctly.

1) Open the correct DocketMath calculator

1. Go to ** /tools/alimony-child-support
2. Confirm the jurisdiction setting shows Florida (US-FL) (or select it if the tool prompts you).

2) Gather the key numbers before typing anything

For a clean run, collect:

• Each parent’s gross income (or the amounts you intend to use)
• Any additional income inputs the calculator requests (for example, overtime or bonuses—if those fields exist in the tool)
• The child details the tool requires (commonly the number of children; sometimes other child-related fields such as age or parenting arrangement inputs depending on the calculator design)

If you’re missing an item, you can still run a scenario—but label it clearly (for example, “Scenario A: using only base wages”).

3) Enter the income fields and verify the period/dates

As you fill out the calculator:

• Double-check the time period matches for both parents (for example, monthly vs. yearly).
• Watch for units: some tools accept annual income and convert internally, while others expect monthly numbers.
• If you’re modeling an income change effective on a certain date, don’t force it into the wrong field. Instead, run separate scenarios if the tool supports multiple periods or date-based changes.

A good workflow is:

• Scenario A: current income
• Scenario B: adjusted income
• Scenario C: income change effective on a later date (only if the tool includes a date/timeline field)

4) Add parenting/child-related inputs (if prompted)

DocketMath’s alimony + child support calculation commonly depends on inputs like:

• Number of children
• Any custody-time / parenting allocation fields the tool includes

Enter these exactly as the tool expects. If you expect the parenting schedule to change, treat each schedule as its own scenario so your results stay comparable.

5) Run the calculator and review the breakdown

After you click calculate:

• Review the line-item outputs. Many tools show separate components (often a child support portion and an alimony portion).
• Run the scenarios and compare results to see which input affects the outcome the most.

Practical checks while reviewing:

• If child support changes a lot, re-check children count and any parenting-time fields.
• If alimony changes a lot, re-check the income inputs and any alimony-relevant modifiers/flags the tool includes.

6) Apply jurisdiction-aware timing context (Florida collections/limitations)

When you’re thinking about timing and how long unpaid amounts might remain subject to collection or action, Florida has a limitation period for certain actions.

In the jurisdiction data provided here, Florida’s general limitation period is:

• 4 years under Florida Statute § 775.15(2)(d)
• Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

Important clarity for this walkthrough:
No claim-type-specific sub-rule was found in the provided jurisdiction data. That means the 4-year general/default period is the only limitation period stated here. Use it as general timing context, not an assurance that every legal question in your case will follow the exact same timing rule.

7) Translate outputs into a scenario report you can reuse

Once you have a result you like, record:

• The income amounts you entered (or any exportable values the tool provides)
• The child details used (for example, number of children)
• The parenting-time / schedule inputs
• The final estimated monthly outputs shown by the tool

This lets you adjust one variable at a time later—for example, changing one parent’s income from $6,500/month to $7,250/month—without losing track of what changed.

8) Use the primary CTA to rerun quickly

If you need to iterate, return to the tool directly:

• ** /tools/alimony-child-support

That way, you can test input changes quickly without rebuilding your scenario from scratch.

Common pitfalls

These are the most common issues that cause confusing or inconsistent results when running alimony + child support scenarios in DocketMath for Florida.

1. Mixing income periods

   • Example: entering one parent’s income as annual and the other as monthly (or vice versa).
   • Fix: ensure both parents use the same frequency before running.

2. Incorrect child count or missing child-related inputs

   • The number of children (and any required child fields) can significantly affect the child support component.
   • Fix: confirm the children count field matches the scenario you’re modeling.

3. Using the wrong parenting schedule assumptions

   • Parenting time/custody allocation inputs can strongly influence support outputs.
   • Fix: create separate scenarios when schedules differ.

4. Not labeling scenarios

   • When you run multiple iterations, it’s easy to forget what you changed.
   • Fix: label each run (for example, “Scenario A: current income,” “Scenario B: income reduced,” etc.).

5. Over-applying the Florida 4-year general limitation period

   • The only limitation period stated in the provided jurisdiction data is the general/default period: 4 years under Florida Statute § 775.15(2)(d).
   • Fix: treat it as general timing context, not as a claim-type-specific rule for every legal question.

Try it

Use DocketMath now to run a Florida (US-FL) scenario:

• Open ** /tools/alimony-child-support
• Start with Scenario A (current income):

  • Enter both parents’ gross income using the same time basis
  • Enter child details and any parenting schedule inputs exactly as the tool requires
• Then run Scenario B (adjusted income):

  • Change only one variable (for example, one parent’s income)
  • Keep all other inputs the same
• Compare the outputs side-by-side and note which component (alimony vs. child support) shifts most

Florida timing context you can keep in mind while organizing outcomes:

• General/default limitations context: 4 years under Florida Statute § 775.15(2)(d)
• Jurisdiction note: only the general/default period was provided here; no claim-type-specific sub-rule was identified in the jurisdiction data.

Related reading

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