Breakup & Fee Clauses Calculator Guide for Arizona

8 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

Run this scenario in DocketMath using the Breakup Fee Clauses calculator.

DocketMath’s Breakup & Fee Clauses Calculator (Arizona) helps you model typical “breakup” and “fee” clause outcomes using inputs such as clause type, relevant dates, and whether certain trigger events occurred.

Because contracts can be drafted in many ways, this tool does not “decide” a dispute. Instead, it gives you an organized way to translate clause language into concrete numbers and timelines—so you can spot issues early, especially around how long a party may wait before bringing a claim.

A key Arizona timeline concept used in the calculator’s guidance is Arizona’s criminal statute of limitations, which appears in A.R.S. § 13-107(A):

  • Default SOL period: 2 years (per the jurisdiction data provided)
  • The statute also includes other timeframes depending on exceptions (notably listed as “exception P3” in the jurisdiction data)

Note: Even though this calculator focuses on contract-style clause mechanics, Arizona timing rules can still affect whether a claim is timely. If your matter involves any criminal allegations, timing analysis may require separate review.

The practical outputs you can expect

Depending on your inputs, DocketMath’s calculator can help you estimate:

  • Whether a claim window may still be open under a given Arizona limitation period
  • How changing a trigger date (e.g., termination, breach, notice) changes the “latest plausible” date to file
  • How clause structure (e.g., fee shifting vs. fixed breakup amount) changes the way totals might build

Core Arizona timing rule referenced in this guide

Your calculator guidance uses this Arizona statute reference:

  • A.R.S. § 13-107(A): 2 years — designated in the provided data as exception O2
  • A.R.S. § 13-107: 3 years — designated in the provided data as exception P3

Source: https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

(If your inputs correspond to a different exception than the one you select, your modeled outcome will change.)

When to use it

Use DocketMath’s Breakup & Fee Clauses Calculator guide when you want to translate contract clause language into a timeline-and-cost picture in an Arizona context.

Good times to use the calculator

  • You’re drafting or reviewing a clause and want to see how date-driven triggers can impact timing outcomes.
  • You’re evaluating exposure after termination, breach, or failed conditions.
  • You’re preparing a dispute checklist to compare your timeline against a specified limitations window.
  • You’re comparing versions of clause language (e.g., “fees upon breach” vs. “fees upon termination”) to see how trigger dates affect the model.

Cases where you should slow down before relying on the output

  • Your agreement has multiple claims types (e.g., fees, damages, indemnity, restitution) that may be subject to different limitation rules.
  • The contract uses ambiguous trigger events (e.g., “material breach,” “default,” “incurred expenses”) without a clear date.
  • You have competing timelines (e.g., notice required before fees become due).

Warning: A calculator can’t replace careful reading of your agreement. If your contract defines “effective date,” “termination date,” or “breach date” differently than you assume, your modeled timeline can be wrong.

Tips for accuracy

  • Use the contract’s defined terms. If your agreement defines “breach date” or “termination date,” select the trigger that matches the definition.
  • Check the “start” event carefully (termination vs. breach vs. notice vs. cure end). Small date mismatches can shift the modeled deadline by weeks or months.
  • Confirm how the clause treats fees (e.g., fees “incur” immediately vs. accrue only after notice/cure).
  • Run multiple models if facts are disputed (e.g., earliest alleged breach date vs. later alleged breach date).
  • Validate with counsel if the stakes are high or if you see any mismatch between contract mechanics and the applicable timing rule you selected.

Step-by-step example

Below is a realistic walkthrough of how a user might set inputs and interpret outputs using DocketMath’s /tools/breakup-fee-clauses.

Scenario: Termination, then fee recovery request

Facts you’re modeling (example):

  • Contract: Arizona-governed agreement
  • Clause idea: If one party terminates due to the other’s breach, the breaching party may owe a breakup amount and reimburse certain fees
  • Termination date (trigger): 2024-06-15
  • Date of alleged breach: 2024-05-20
  • Date notice sent: 2024-06-20
  • Today’s modeling date (for “latest plausible” calculations): 2026-03-22

Step 1: Open the calculator and choose clause mechanics

Go to: /tools/breakup-fee-clauses

In the calculator, select inputs that match what your contract does, such as:

  • Clause type: breakup amount + fee recovery (or fixed breakup only, depending on your drafting)
  • Trigger date basis: termination date vs. breach date vs. notice date

Key modeling choice: the calculator will shift the timeline based on which event you treat as starting the limitations analysis.

Step 2: Select the Arizona limitation period rule

Using the jurisdiction data provided for this guide, you’ll see options aligned to the Arizona limitation periods:

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

Pick the option that best corresponds to the situation you’re modeling.

If you choose 2 years (O2):

  • You’re modeling a tighter claim window.

If you choose 3 years (P3):

  • You’re modeling a longer claim window.

Step 3: Compute the “latest plausible” date to file (modeled)

Assume the calculator uses termination date (2024-06-15) as the trigger.

Option A — Model using 2-year period (A.R.S. § 13-107(A), exception O2)

  • Trigger: 2024-06-15
  • Modeled window length: 2 years
  • Latest plausible modeled date: 2026-06-15

Option B — Model using 3-year period (A.R.S. § 13-107, exception P3)

  • Trigger: 2024-06-15
  • Modeled window length: 3 years
  • Latest plausible modeled date: 2027-06-15

Step 4: Compare “today” to the modeled deadline

Today (for this example): 2026-03-22

  • Under Option A (2 years): March 22, 2026 is before June 15, 2026 → modeled as potentially within the window.
  • Under Option B (3 years): also within the window.

Step 5: Model clause amounts (breakup/fees) and output interpretation

Next, enter clause amounts and any reimbursement categories if the calculator supports them, such as:

  • Fixed breakup amount (e.g., $25,000)
  • Fee reimbursement cap or multiplier (if the agreement specifies one)
  • Expenses included vs. excluded (e.g., attorney fees, expert fees, filing fees)

The key is consistency:

  • If your clause says fees are due after notice and cure, then using notice date (2024-06-20) as the trigger may change the calculated timeline compared to using termination date.

Output you should look for

Typically, you’ll want to identify:

  • Which trigger date the calculator used
  • Which limitations period (2-year vs. 3-year) was selected
  • The modeled deadline date
  • Any computed totals based on breakup + fees logic

Pitfall: Selecting the wrong trigger date is one of the biggest sources of error. “Breach date,” “termination date,” and “notice date” can be 10–60+ days apart in real disputes.

Common scenarios

The most frequent disputes involving breakup and fee clauses often revolve around timing and clause-trigger mechanics. Here are several common scenario patterns and how they change the calculator inputs and outputs.

1) Termination-triggered breakup amount

Pattern: Contract says a breakup amount is due upon termination for cause.

Calculator input focus:

  • Trigger basis: termination date
  • Fee clause timing: whether fees are tied to termination or to a separate “breach notice” event

Output impact:

  • Deadline shifts to match the termination date.
  • Totals can be computed sooner or later depending on whether the fee component depends on a post-termination event.

2) Notice-and-cure required before fees accrue

Pattern: Fees only become recoverable after a notice and cure period ends.

Calculator input focus:

  • Trigger basis: end of cure period or notice date, depending on how your clause defines it
  • Add the cure period length (e.g., 15 business days, 30 calendar days)

Output impact:

  • The modeled deadline moves later when trigger is “cure end,” which may change whether the claim is within a chosen limitations window.

3) Dispute over whether the “breach date” was actually established

Pattern: One party claims breach occurred on a certain day, while the other argues breach occurred later or not at all.

Calculator input focus:

  • Use both dates as alternative models:
    • Model using earliest alleged breach date
    • Model using later alleged breach/trigger date

Output impact:

  • You’ll likely see multiple modeled deadlines, helping you understand the range of risk.

4) Clause includes attorney fees vs. “all costs”

Pattern: Agreement distinguishes attorney fees from other expenses.

Calculator input focus:

  • Fee categories: attorney fees only vs. broader costs
  • Caps or exclusions: sometimes fees are limited to amounts “incurred” after a trigger

Output impact:

  • Totals can vary materially depending on what you include.
  • Timeline may still depend on the same

Related reading