Why Damages Allocation results differ in Arizona

The top 5 reasons results differ

In Arizona, DocketMath’s damages-allocation outputs can diverge between cases even when the entered facts look similar. The most common driver is that jurisdiction-aware rules change the time window you’re effectively measuring, which then affects the allocation math downstream.

Here are the top 5 reasons you’ll see different results in US-AZ:

1. Different “start date” assumptions

   • DocketMath may compute or infer the relevant measurement period. If your inputs treat the “start date” as an event date vs. discovery date vs. filing date, the damages window shifts—often producing different totals even with the same overall damage amounts.

2. **Arizona limitation period applied (2 years)

   • Arizona’s general statute of limitations is 2 years under A.R.S. § 13-107(A) (your provided jurisdiction data).
   • Because no claim-type-specific sub-rule was found for this jurisdiction prompt, the general/default period is the controlling limitation period used for time-based calculations in these runs.
   • Practically: if the tool’s derived time window changes (because dates or assumptions change), the effective “covered” portion can change proportionally.

3. Cross-jurisdiction inputs

   • If you run the calculator with dates or a jurisdiction selection that doesn’t match US-AZ, rule selection can change (including which limitation period basis is applied). Even small mismatches—like using AR dates but a non-AR jurisdiction code—can alter the time-window logic.

4. Aggregation method and period chunking

   • Damages allocation often depends on how amounts are grouped into time slices (for example, monthly or other period “chunks”).
   • Two inputs can share the same grand total, but if one run allocates those amounts across period boundaries differently, the output can shift because each slice may be weighted or adjusted in the allocation algorithm.

5. Allocation categories map differently

   • The output may be sensitive to how you categorize inputs (e.g., mapping amounts into “covered” vs. “non-covered” time or equivalent internal categories).
   • Small categorization differences can produce large differences because each category can interact with the limitation-adjusted time window.

How to isolate the variable

Use this diagnostic checklist to pinpoint what changed between runs inside DocketMath.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

1) Verify jurisdiction and time window

• Per your jurisdiction data, no claim-type-specific sub-rule was found, so the general/default period should remain the controlling basis.

2) Compare the limitation period inputs (date-by-date)

Create a quick diff between Run A and Run B:

3) Keep everything constant, change only one variable

Use a “one-switch” approach:

If the totals shift significantly after only the start date changes, the discrepancy is likely time-window driven—consistent with the 2-year default under A.R.S. § 13-107(A).

4) Use the DocketMath workflow to reduce mismatches

If you’re repeatedly comparing runs, use the calculator from the same starting point each time to reduce data-entry drift:

• Open the damages allocation tool

Next steps

1. Lock down the dates

   • Write down which date you used as the start date and why (e.g., event vs. discovery) for each run.

2. Re-run with identical date definitions

   • Make sure both runs share the same date definitions before changing amounts or categories.

3. Confirm the default SOL basis

   • Under your Arizona jurisdiction data, DocketMath should use the general 2-year limitations period under A.R.S. § 13-107(A).
   • Since no claim-type-specific sub-rule was found, the expectation is that the default period drives time-based adjustments.

4. Record outputs with a “reason tag”

   • After each run, note what you changed, such as:

     • “Changed start date”
     • “Reassigned category mapping”
     • “Switched jurisdiction code”

This makes it easier to converge on the single input difference causing the allocation totals to move.

Not legal advice: This is a diagnostic workflow to help you understand how tool outputs vary. If you need advice for a specific matter, consult a qualified attorney.

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