How to run Damages Allocation in DocketMath for Arizona

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Arizona (US-AZ) using jurisdiction-aware rules. You’ll see where Arizona-specific timing rules apply, what inputs most affect the output, and how to verify your setup before you rely on results.

Start with the DocketMath calculator:
Primary CTA: /tools/damages-allocation

1) Gather the dates you’ll feed into the calculator

Damages Allocation is driven by the allocation timeline you select. For Arizona, the provided jurisdiction data indicates the tool should use the general/default allocation period, anchored to these statutes:

• A.R.S. § 12-2505 (comparative negligence framework; referenced in allocating fault and related damages)
• A.R.S. § 12-2506 (severalty / “nonparty at fault” concepts; used to allocate damages across multiple actors)

Before you open the tool, confirm you have:

• the event / injury / occurrence date(s) you’re working from
• any damages start/end dates you want to allocate over
• the jurisdiction selection set to US-AZ (Arizona)

Important: This Arizona setup uses the general/default period. No claim-type-specific sub-rule was found in the provided jurisdiction data, so the calculator applies the general allocation window rather than a specialized alternative. If your matter requires a different, claim-type-specific period, you’ll need to adjust inputs based on your legal requirements (this guide is informational, not legal advice).

2) Open DocketMath Damages Allocation

Go to: /tools/damages-allocation

Then:

• Select Arizona (US-AZ) in the jurisdiction selector (if the interface offers one).
• Confirm you’re using the Damages Allocation calculator (Template/Calculator: damages-allocation).

3) Enter allocation inputs (what changes the output)

DocketMath typically requires a set of inputs that determine how much gets allocated and to whom/when. While the exact labels can vary by UI, look for the following categories:

• party/actor identifiers (who is included in the allocation)
• the allocation basis (how your contributors/fault/damages contributors are represented in the model)
• the timeline boundaries (start/end of the allocation period)
• damage figures to allocate (either as a single total or in time slices, depending on what the tool supports)

Use this checklist to avoid missing the input that usually changes results the most:

• I selected US-AZ / Arizona jurisdiction rules
• I entered a consistent allocation period (start date and end date)
• I entered damages amounts for the period (or the supported aggregation level)
• I entered allocation contributors (all actors I want included)
• I checked whether the calculator expects one total vs. multiple entries (time-sliced amounts)

4) Confirm the allocation period uses Arizona’s general/default rule

For the Arizona configuration in this guide, DocketMath uses a general/default allocation period aligned with the provided statutes:

• A.R.S. §§ 12-2505, 12-2506

Because no claim-type-specific sub-rule was identified in the provided jurisdiction data, you should not expect the tool to automatically swap in a specialized period. If you expected that behavior, it’s a signal to revisit your assumptions and confirm the dates you entered reflect the period you intend to allocate.

5) Run the calculation and review the allocation breakdown

After you submit:

• Verify the output total matches the damages you entered (accounting for rounding or how the tool aggregates values).
• Review how DocketMath distributes damages across:

  • actors/parties (if your inputs are actor-based), and/or
  • time slices within the allocation period (if you provided start/end boundaries that result in segmentation)

A quick sanity check table you can use while reviewing results:

6) Iterate: adjust inputs that drive major changes

If results don’t match expectations, change one driver at a time. The biggest levers are usually:

• the allocation start/end dates
• which actors are included/excluded
• the damages entry granularity (single total vs. multiple/time-sliced entries, if supported)

Track the difference (delta) between runs so you can explain what changed and why.

Common note: The most frequent calculation error is inconsistent dates. If your damages start date is later than the date you believe the damages began, DocketMath will allocate over a shorter window—often reducing or reshaping the distribution.

7) Save/export your results for your workflow

To make your work reusable:

• capture the inputs snapshot (dates, actors, amounts)
• keep the allocation breakdown
• record what you changed between runs

If DocketMath offers an export option, use it so you can attach the allocation outputs to your case documentation process without re-entering details.

Common pitfalls

Below are the most common issues when running Damages Allocation for Arizona (US-AZ) in DocketMath.

1. Accidentally using the wrong jurisdiction code

• If US-AZ isn’t active, the tool may use another state’s framework.
• Fix: verify the jurisdiction indicator before calculating.

1. Date window mismatch

• The allocation period must match your intended timeline.
• Fix: confirm your start/end dates align with the period you want to allocate over.

1. Forgetting this uses the general/default period

• Because no claim-type-specific sub-rule was found in the provided data, the calculator uses the general/default period.
• Fix: if you expected a specialized period, confirm your assumptions and adjust inputs accordingly.

1. Omitting an actor/party

• If an actor is left out, the model may redistribute shares depending on how it allocates across contributors.
• Fix: include all relevant contributors you want reflected.

1. Over-aggregating damages

• If your damages are inherently time-specific but you enter a single lump sum, you may lose the shape across the timeline.
• Fix: use the granularity DocketMath supports for time-sliced entry (if available).

1. Misinterpreting which breakdown you’re looking at

• Results may show different levels such as:

  • overall totals,
  • per-actor allocations,
  • and/or time-slice allocations.
• Fix: match each output line/section to the interpretation you intend to use.

Try it

Ready to run your Arizona allocation?

1. Open the tool: /tools/damages-allocation
2. Confirm US-AZ jurisdiction is selected.
3. Enter:

   • your allocation period dates
   • your damages amount(s)
   • your allocation contributors (actors)
4. Click calculate, then review:

   • total allocated vs. input damages
   • actor/time breakdown consistency

If you want to validate the setup first, do a “dry run”:

• use a shorter, conservative date window
• enter a simplified damages total
• include two actors

Once you see the output structure behaving as expected, expand to your full scenario.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance