Pre/Post-Offer Damages Split Guide for Arizona

What this calculator does

Run this scenario in DocketMath using the Pre Post Offer Damages calculator.

DocketMath’s Pre/Post-Offer Damages Split guide helps you separate damages into two time periods commonly used in Arizona litigation math:

• Pre-offer damages: amounts that accrue before a formal damages-related “offer” date.
• Post-offer damages: amounts that accrue on/after the offer date, often used when calculating a time-based split (for example, when the claim’s damages continue to run after an offer).

This guide focuses on the Arizona 2-year statute of limitations baseline and the mechanics you’ll use to split totals by time. It is not legal advice—treat the output as a calculation aid for case planning, not a substitute for attorney review.

Arizona limitations framework referenced by this guide

Arizona’s limitations rule for many civil claims (depending on claim type) includes:

• A.R.S. § 13-107(A) — 2 years (exception O2)
  Source (context): https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

• A.R.S. § 13-107 — 3 years (exception P3)

Because your brief specifies SOL Period: 2 years and points to A.R.S. § 13-107(A), this guide is written around a 2-year baseline unless you have a clearly applicable alternative (3 years / exception P3) for your specific claim category.

When to use it

Use DocketMath’s pre-post-offer-damages calculator when you have at least these three things:

1. A known offer date

   • The “offer” can be a document date, a service date, or another case-specific date you’re using for the split.
2. A damages accrual pattern over time

   • Common patterns include daily/weekly accrual, monthly rates, or a spreadsheet of amounts by date.
3. A total damages figure that can be broken into periods

   • Even if you start with a single total, you’ll usually need a rate or timeline to allocate properly.

You should also consider using the split when the limitations period matters for which damages are included.

How the Arizona SOL timing often affects which damages you include

With a 2-year SOL baseline under A.R.S. § 13-107(A), your damages window is often capped in practice by:

• Accrual start (or earliest relevant transaction/date), and
• Filing/trigger date (not provided by the brief, but required for any limitations analysis),
• …with the calculator doing the date math for your split.

Because the brief requires the 2-year SOL Period, many teams will:

• exclude damages that fall outside the relevant 2-year window, then
• split the remaining amounts into pre/post-offer buckets.

If exception P3 (3 years) applies in your scenario, the damages window expands accordingly under A.R.S. § 13-107—which will change your included pre/post totals.

Step-by-step example

Below is a concrete walkthrough using typical inputs for a pre/post-offer damages split in Arizona.

Example setup

Assume:

• Offer date: 2025-01-15
• Claim damages accrue at a steady daily rate
• Daily damages rate: $125/day
• Accrual period you are counting (after you apply any SOL window logic):

  • Start: 2024-01-15
  • End: 2025-02-15 (inclusive in your model—be consistent)

You want:

• Pre-offer damages = from 2024-01-15 up to (but not including) 2025-01-15
• Post-offer damages = from 2025-01-15 through 2025-02-15

Step 1: Define the date boundary rule

Decide whether “post-offer” includes the offer date.

Common conventions:

• Post includes offer date: pre ends the day before
• Post excludes offer date: pre includes offer date

For this example, we’ll use:

• Pre: up to 2025-01-14
• Post: from 2025-01-15 to 2025-02-15

Step 2: Calculate the number of days in each bucket

Pre-offer days

• 2024-01-15 through 2025-01-14

That is 365 days (2024–2025 spans a year; because 2024 includes Feb 29, careful day counting matters—your calculator should handle this consistently).

Post-offer days

• 2025-01-15 through 2025-02-15
• That’s 32 days (January 15–31 is 17 days; February 1–15 is 15 days; total 32)

Step 3: Multiply by the daily rate

Step 4: Reconcile totals to your source numbers

If you started from a spreadsheet or contract schedule, verify that:

• The total computed ($49,625) matches (or closely matches) your existing total, accounting for:

  • inclusive/exclusive date conventions,
  • any rounding (daily vs. monthly),
  • non-accrual days if your model excludes them.

Step 5: Use the SOL baseline to limit the accrual window (Arizona-specific step)

Since your brief specifies:

• SOL Period: 2 years
• and references A.R.S. § 13-107(A) as the 2-year baseline (exception O2),

you’d typically only include damages accruing within the relevant 2-year window before your claim’s filing/trigger date (not provided here).

In practice, many teams do:

1. Determine the latest allowable earliest date based on the relevant trigger and A.R.S. § 13-107(A) (2 years).
2. Clip your accrual timeline to that boundary.
3. Then run the pre/post split on the clipped timeline.

If exception P3 applies and the applicable limitation period is 3 years under A.R.S. § 13-107, repeat the clipping with the longer window—your pre/post totals will generally increase because more early accrual dates are included.

Common scenarios

The pre/post split is used across several common damages setups in Arizona case work. Here are the most frequent patterns and what changes in the output.

Scenario 1: Linear (steady) accrual rate

Facts pattern

• Daily/monthly damages are constant.

Calculator impact

• Output changes mostly with:

  • offer date position in the timeline,
  • your chosen inclusive/exclusive boundary rule,
  • how you clip to the 2-year SOL baseline under A.R.S. § 13-107(A).

Scenario 2: Step-changes in rate

Facts pattern

• Damages rate increases or decreases on specific dates (e.g., contract milestones, repair completion dates, or revised rent/usage terms).

Calculator impact

• You must provide the rate schedule (or a date-to-amount table).
• The split will aggregate the appropriate sub-period amounts into:

  • pre-offer totals,
  • post-offer totals.

Scenario 3: Accrual tied to discrete invoices or events

Facts pattern

• Each invoice/event has its own date and amount.

Calculator impact

• Splitting becomes event-date driven:

  • events before the offer date go to pre,
  • events on/after go to post.
• If SOL clipping is needed, you may drop entire events outside the limitation window under the 2-year baseline (A.R.S. § 13-107(A)) or 3-year alternative (A.R.S. § 13-107 / exception P3).

Scenario 4: Partially unknown timelines (missing end date)

Facts pattern

• You know the offer date and early accrual start, but the accrual end is uncertain.

Calculator impact

• Your post-offer number becomes estimate-based.
• Consider running multiple versions:

  • Version A: end date = “expected settlement date”
  • Version B: end date = “projected judgment date”
• This produces a range of post-offer totals for settlement discussions and internal planning.

Scenario 5: Different SOL window assumptions (2 years vs 3 years)

Facts pattern

• Your case may plausibly fall under the 2-year rule in A.R.S. § 13-107(A) (exception O2) or a 3-year rule under A.R.S. § 13-107 (exception P3).

Calculator impact

• You’ll likely see:

  • higher pre-offer amounts under the 3-year window,
  • higher overall totals (and thus potentially higher post-offer amounts as well, depending on where the offer date sits relative to the expanded window).

This is one reason many teams compute both versions as part of early case evaluation.

Tips for accuracy

These practical checks help ensure your pre/post numbers are defensible as calculations.

1) Lock the inclusion rule for the offer date

Pick one and stick to it:

• Option A: post includes offer date
• Option B: post excludes offer date

Then apply it consistently across every tool run and every spreadsheet copy.

Related reading

• Pre/Post-Offer Damages Split Guide for Alabama
• Pre/Post-Offer Damages Split Guide for California
• Pre/Post-Offer Damages Split Guide for Colorado