Worked example: Damages Allocation in Arizona
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Damages Allocation calculator.
This worked example shows how DocketMath can allocate damages exposure using Arizona’s general statute of limitations (SOL) rules as a time-filter for which amounts are counted. It is designed to be practical, not to provide legal advice—use it as decision-support illustration.
Jurisdiction-aware rule used (Arizona, general/default):
- General SOL period: 2 years
- General statute: **A.R.S. § 13-107(A)
- No claim-type-specific sub-rule was found in the provided jurisdiction data, so the 2-year period is treated as the default/general rule for this example.
Note: Arizona’s A.R.S. § 13-107(A) sets a 2-year general limitations period. This example assumes there is no special SOL category overriding that rule because no claim-type-specific sub-rule was provided.
(Reference used in this example source note: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai)
Scenario setup (worked example facts)
Assume a plaintiff claims they suffered three categories of damages, each tied to dated conduct events:
Event categories
- Medical costs (amounts incurred on specific dates)
- Lost wages (pay periods)
- Out-of-pocket expenses (receipts)
Filing date: March 1, 2026
Jurisdiction: **Arizona (US-AZ)
Event timeline
- Medical costs: incurred Jan 10, 2024, May 15, 2024, Aug 20, 2024
- Lost wages: pay periods Mar 1–Mar 31, 2024 and Apr 1–Apr 30, 2024
- Out-of-pocket expenses: incurred Dec 5, 2023 and Feb 14, 2024
Amounts associated with each event
| Category | Event date(s) | Amounts |
|---|---|---|
| Medical costs | Jan 10, 2024 | $6,000 |
| Medical costs | May 15, 2024 | $4,500 |
| Medical costs | Aug 20, 2024 | $3,200 |
| Lost wages | Mar 2024 | $7,800 |
| Lost wages | Apr 2024 | $6,400 |
| Out-of-pocket expenses | Dec 5, 2023 | $900 |
| Out-of-pocket expenses | Feb 14, 2024 | $1,600 |
DocketMath inputs (what you’d enter)
Use DocketMath → damages-allocation to apply a time-based allocation.
If you’re following along in the tool, open:
- /tools/damages-allocation
In the calculator, you typically enter:
- Jurisdiction: US-AZ
- Filing date: 2026-03-01
- SOL rule to apply: Arizona general/default SOL (2 years) per **A.R.S. § 13-107(A)
- Damages line items: for each line item:
- Category label
- Event date (or date range for period items like wages)
- Dollar amount
Example run
DocketMath allocates damages by building a lookback window using the general SOL period, then counting line items that fall inside vs. outside that window.
Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Compute the SOL lookback window (2 years)
- Filing date: March 1, 2026
- SOL period: 2 years (general/default under A.R.S. § 13-107(A))
So for this example, the window counted is events on or after approximately:
- March 1, 2024 through March 1, 2026
(inclusive/exact boundary handling may depend on DocketMath’s implementation).
Because your fact dates include early 2024 and late 2023, the key question is which line items fall before or on/after March 1, 2024.
Pitfall: Many calculators and real-world pleadings treat cutoff boundaries slightly differently (for example, exact-day inclusion). Review the DocketMath output to confirm how the tool treats events exactly on the cutoff date.
Step 2: Classify each line item as within or outside the window
Using the window starting March 1, 2024:
Medical costs
- Jan 10, 2024 → outside (before Mar 1, 2024)
- May 15, 2024 → inside
- Aug 20, 2024 → inside
Lost wages (modeled here as pay periods)
- Mar 1–Mar 31, 2024 → inside (starts Mar 1, 2024)
- Apr 1–Apr 30, 2024 → inside
Out-of-pocket expenses
- Dec 5, 2023 → outside
- Feb 14, 2024 → outside
Step 3: Summarize totals by category (timed allocation)
Amounts within the SOL window
- Medical costs: $4,500 + $3,200 = $7,700
- Lost wages: $7,800 + $6,400 = $14,200
- Out-of-pocket expenses: $0 (both dates outside) = $0
Total inside window: $7,700 + $14,200 + $0 = $21,900
Amounts outside the SOL window
- Medical costs: $6,000 (Jan 10, 2024) = $6,000
- Lost wages: $0 outside = $0
- Out-of-pocket expenses: $900 + $1,600 = $2,500
Total outside window: $6,000 + $0 + $2,500 = $8,500
Step 4: Output-style allocation (what DocketMath displays)
A practical way to present the result is “inside vs. outside,” and “net counted” (inside) as the amount that survives the SOL time-filter in this model.
| Category | Inside SOL window | Outside SOL window | Net counted (inside) |
|---|---|---|---|
| Medical costs | $7,700 | $6,000 | $7,700 |
| Lost wages | $14,200 | $0 | $14,200 |
| Out-of-pocket expenses | $0 | $2,500 | $0 |
| Total | $21,900 | $8,500 | $21,900 |
Takeaway: Under the general 2-year rule from A.R.S. § 13-107(A) (and no special sub-rule provided), DocketMath would allocate $21,900 as “within time” and $8,500 as “outside time” for this timeline.
How changing inputs would change results (preview)
The biggest driver is how close dates are to the cutoff. Moving even one line item across the cutoff (for example, from Feb 14, 2024 to Mar 1, 2024) can swing the totals substantially.
Sensitivity check
Test robustness by changing one input at a time while holding everything else constant (same amounts; same jurisdiction; same baseline filing date 2026-03-01), then observe how the inside/outside split changes.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity A: Shift one medical cost date across the cutoff
- Change Medical costs Jan 10, 2024 ($6,000) to **Mar 1, 2024 ($6,000)
Before: $6,000 outside
After: $6,000 inside
Updated totals:
- Total inside becomes $21,900 + $6,000 = $27,900
- Total outside becomes $8,500 − $6,000 = $2,500
Result: Net counted increases by $6,000.
Sensitivity B: Change only the filing date by ~30 days
Change filing date from 2026-03-01 to 2026-03-31, keep all event dates the same.
- The window begins roughly 2024-03-31 instead of 2024-03-01 (boundary behavior can vary).
- The Mar 2024 pay period (Mar 1–Mar 31) is then much more likely to be partially or fully outside depending on how the tool models period items.
Two implementation-dependent approaches (important for wages/ranges):
- If DocketMath uses the pay period start date: Mar 1, 2024 may fall outside, potentially reducing lost wages by $7,800
- If it uses midpoint/end date for the period: Mar 31, 2024 may fall inside, potentially keeping much of the $7,800 counted
Result: Filing-date shifts can create step changes around:
- monthly boundaries, and
- period-item modeling (start vs. end vs. midpoint).
Caution: For period items like wages, ensure your input format (start date/end date vs. single date representation) matches your underlying facts; otherwise, the cutoff impact may be distorted.
Sensitivity C: Add a new out-of-pocket expense just after the cutoff
Add:
- Out-of-pocket expense on Mar 2, 2024 for $300
That is after Mar 1, 2024, so it lands inside the window.
Updated totals:
- Total inside becomes $21,900 + $300 = $22,200
- Total outside remains $8,500
Result: Net counted increases by $300.
