Choosing the right Alimony Child Support tool for Arizona

Choose the right tool

If you’re using a DocketMath calculator to estimate alimony and child support outcomes in Arizona (US-AZ), the fastest way to get reliable numbers is to pick the tool that matches what you’re trying to measure—then feed it the correct, jurisdiction-aware inputs.

Even with the best estimator, the accuracy of any output depends on two things:

• Jurisdiction rules (Arizona-specific calculations, terminology, and typical input requirements)
• Your input quality (income figures, time periods, and which support component you’re modeling)

Start by matching your goal to the “alimony-child-support” tool

Use the DocketMath Alimony Child Support tool when your worksheet includes both:

• Spousal/partner support concepts (alimony), and
• Child support concepts (support tied to children’s needs and parental incomes)

That’s the core fit for the tool-selector: it’s designed to handle the combined workflow instead of forcing you into separate passes that can drift out of alignment.

Confirm you’re not mixing estimation with deadlines

Arizona has a general statute of limitations (SOL) rule that often comes up when people are trying to understand how far back certain actions or claims may reach.

For Arizona, the general SOL period is 2 years, under:

• A.R.S. § 13-107(A) (general rule; applies as the default when no claim-type-specific rule is found)

If your workflow includes timing—like whether you’re consolidating history, reconciling past obligations, or assembling documentation—you’ll want your calculation plan to reflect what actions are realistically impacted by time limits.

Gentle reminder: SOL context can affect what time period a dispute may cover, but it does not automatically determine the amount of support for a month. Support amounts depend on the underlying financial and case inputs.

Use a quick input checklist to avoid “garbage in, garbage out”

Before you run DocketMath → alimony-child-support, collect inputs in a format the tool expects. While the exact fields can vary depending on the UI, the practical categories are usually consistent.

Income inputs

• Gross or net income (use the same basis consistently for both parties)
• Pay frequency (weekly/biweekly/monthly) if the tool asks
• Any supplemental income you plan to include

Time horizon

• Whether you’re modeling a monthly amount across a defined period
• Whether you want one snapshot or multiple runs

Child-related inputs

• Number of children (if requested)
• Custody/parenting time variables (if requested)

Support parameters

• Any toggles the tool provides (e.g., estimating one component vs both)

To keep your run reproducible, use this checklist every time:

For direct access, start here: alimony-child-support.

How outputs should change when you adjust inputs

A useful way to validate your run is to change one input at a time and see whether the output moves in the direction you’d expect.

Use these directional expectations as a sanity check:

If you see the opposite trend after a small adjustment, pause and re-check:

• whether you’re using the intended “Party A” vs “Party B” roles
• whether you entered annual vs monthly values
• whether you switched income basis (gross vs net) between scenarios

Don’t ignore SOL context when building your dataset

Even if you’re primarily using DocketMath for estimation, SOL context can affect how much history you gather.

Arizona’s general rule is 2 years under A.R.S. § 13-107(A) for the general/default limitation period. Since no claim-type-specific sub-rule was identified in the brief context, use the 2-year baseline to organize records:

• prioritize pay records and related documentation within the 2-year window
• keep “outside the window” materials in a separate folder if you’re unsure whether they affect timing

Again, SOL context can influence what time periods are disputable, but it doesn’t replace the need for accurate income and case assumptions for the calculator.

Next steps

Once you’ve chosen the correct tool (DocketMath → alimony-child-support), your next goal is to run a workflow that produces defensible estimates you can explain and refine.

1. Open the tool and lock jurisdiction

   • Go to: **alimony-child-support
   • Ensure the jurisdiction is set to Arizona (US-AZ) if the tool provides a selector.

2. Enter baseline inputs as “best available current numbers”

   • Start with what you can support with documents (pay stubs, tax summaries, consistent income statements).
   • If a value is estimated, keep a note of it so you can run a revised scenario later.

3. Run at least 2 scenarios

   • Scenario A (baseline): your best available current figures
   • Scenario B (sensitivity): change one key variable (commonly income or parenting-time assumptions)

   This helps you understand how much the estimate depends on a single input.

4. Create a “decision-ready” summary of what you ran Capture these details before moving on:

   • which inputs you used for each party
   • any toggles or interpretation settings in the tool
   • the dates/timeframe you modeled

5. Use SOL context to organize your documentation When you’re dealing with time-related questions, Arizona’s general/default SOL is 2 years under A.R.S. § 13-107(A).

   • Build your record folder around that baseline window.
   • Keep a separate “outside the window” folder if you’re unsure whether something will matter for timing.

6. Check output consistency before you act If your estimates look extreme, revisit the basics:

   • Did you swap party roles?
   • Did you enter monthly amounts as annual?
   • Did you omit a recurring income source the tool expects?

If you want to cross-check your broader case workflow, you can explore DocketMath’s other tools via /tools before finalizing your estimates.

Related reading

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