Choosing the right Damages Allocation tool for Arizona

Choose the right tool

Run this scenario in DocketMath using the Damages Allocation calculator.

If you’re allocating damages in an Arizona matter, the first practical decision is selecting the right process (and tool) for how your numbers should be split. DocketMath’s Damages Allocation calculator is designed to help you work through allocations consistently—but it can’t replace judgment about which allocation framework fits your case facts.

Because this is Arizona (US-AZ), it’s worth aligning your workflow with the Arizona legal timing backdrop. Even when your immediate work is “damages math,” timing can affect which claims (and which amounts) are actually in play for your allocation.

1) Confirm the time window before you allocate

Arizona’s general statute of limitations (SOL) for bringing criminal actions is 2 years under A.R.S. § 13-107(A). This statute is the general/default period. In other words, you should not assume a shorter or longer claim-specific rule applies unless you’ve identified one based on the claim type and allegations.

• General/default period: 2 years
• Citation: **A.R.S. § 13-107(A)
• Source: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html

2) Use DocketMath when you need allocation consistency

DocketMath is useful when you have multiple damages components (for example, categories that must be apportioned) and you want a repeatable output.

A typical Damages Allocation workflow in DocketMath looks like this:

• You provide the relevant damage inputs (often category totals, amounts, or percentages).
• You choose the allocation approach supported by the calculator.
• DocketMath outputs an allocation breakdown you can carry forward into reporting, exhibits, or settlement discussions.

Because the calculator is for calculations, your job is mostly to ensure your inputs match what your chosen dispute framework requires—especially the set of amounts that are “in the pool” for allocation.

3) Match the tool to your allocation method (the real selector)

Use these checkpoints to decide whether DocketMath’s Damages Allocation tool is the right starting point:

Checklist: does your situation fit the tool?

If you tick those boxes, DocketMath’s Damages Allocation tool is a strong fit for “get the numbers organized” work.

4) Arizona timing can change what you should include in the calculation

Here’s a practical way Arizona SOL timing affects your allocation inputs—even though the calculator is about damages, not SOL:

• Claims that fall outside the 2-year general SOL may be excluded from what you allocate (depending on how your dispute is framed and what is being sought).
• That means the SOL window can change the starting dataset you feed into DocketMath.

To keep your allocation grounded, document:

• The date of accrual/the triggering event you’re using (for your internal workflow),
• The date of filing or target date, and
• Whether the alleged conduct falls inside or outside the 2-year window under A.R.S. § 13-107(A).

This matters because the allocation output is only as relevant as the set of amounts you decide are part of the recoverable pool.

5) Understand what changes when you change inputs

Before you run the calculator, decide which inputs you’re treating as “fixed” and which are “scenario variables.”

Common scenario variables that drive allocation changes:

• Category totals (e.g., revise one component amount)
• Allocation basis (e.g., change proportional weights)
• Constraints (e.g., minimums/maximums used by your chosen method)

Once you run DocketMath, look for:

• Whether outputs shift proportionally when you adjust category inputs
• Whether rounding materially affects the final totals (especially with many line items)
• Whether the calculator’s allocation approach matches how you intend to present the breakdown

For your workflow, the practical CTA is straightforward: start with DocketMath’s Damages Allocation tool.

• Primary action: /tools/damages-allocation
• If you’re preparing to gather inputs first, you may also find value in reviewing other workflow aids in /tools

6) Quick jurisdiction-aware workflow (Arizona)

Use this sequence for Arizona:

1. Set your SOL baseline: assume 2 years under A.R.S. § 13-107(A) as the general/default rule.
2. Build your damage pool: include only amounts you’re treating as timely/recoverable for the scenario you want to model.
3. Run DocketMath with your chosen allocation approach.
4. Scenario-test: change one input at a time (amounts, proportions, or the included pool) and compare outputs.

Reference: Arizona SOL baseline used in this workflow

• A.R.S. § 13-107(A) — General/default SOL: 2 years

Next steps

You’ll get the most useful output from DocketMath by treating your work like a mini “data pipeline.” Here’s a practical next-step plan you can follow immediately.

Use the Damages Allocation tool to produce a first pass, then share the output with the team for review. You can start directly in DocketMath: Open the calculator.

Step 1: Decide the scenario you’re allocating

Pick one of these targets:

• Scenario A: Current filing assumptions (what you intend to seek now)
• Scenario B: Narrowed pool (exclude anything outside the 2-year window under A.R.S. § 13-107(A))
• Scenario C: Alternative allocation method (if your inputs support more than one allocation approach)

Step 2: Gather the exact inputs DocketMath needs

Before you open the calculator, assemble:

• The damage components you plan to allocate (category amounts or values)
• The allocation basis your method uses (e.g., proportions/weights, or categorical mapping)
• Any totals that must reconcile (e.g., category sum = overall total)

If you’re missing one input, the output may still look “clean,” but it won’t be meaningful for your actual allocation purpose. Fix inputs first, then run.

Step 3: Run DocketMath and sanity-check outputs

After you run /tools/damages-allocation, do these checks:

• Do allocated line items sum to the expected overall total?
• When you adjust one input, do results move in the direction you expect?
• Do you see unusually large swings that suggest a mismatch in the allocation basis?

Step 4: Document the SOL baseline that governed inclusion

Even if you’re not running SOL analysis inside the calculator, write down the assumption you used:

• “We applied A.R.S. § 13-107(A) general/default 2-year SOL period as the inclusion baseline because no claim-type-specific sub-rule was identified in the provided materials.”

That brief explanation helps others understand why your damages pool has the size it does.

Step 5: Save outputs for comparison

A practical habit:

• Save the outputs for two runs (e.g., Scenario A and Scenario B).
• Compare the delta in totals and category allocations.
• Decide which scenario best reflects your intended submission or internal evaluation.

Step 6: Keep the jurisdiction anchor visible

Since your workflow is Arizona-specific, keep A.R.S. § 13-107(A) (general/default SOL: 2 years) visible in your working notes while you allocate. This avoids a common workflow failure: allocating a damages pool without knowing which timeliness assumption produced it.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules