What this calculator does

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

DocketMath’s Breakup & Fee Clauses Calculator helps you estimate how certain “breakup” and fee-related provisions can affect timelines and costs in Washington (US-WA) matters. In plain terms, the tool calculates outputs you can use to model scenarios around enforceability windows and related timing—especially when clauses are tied to when something must be acted on.

Because Washington’s deadlines can be triggered by different events (and can be shortened by specific exceptions), the calculator is designed to pair your inputs with Washington’s statute of limitations framework so you can spot timing risk early.

Key Washington timing reference used by the calculator includes:

• 5-year statute of limitations (general rule)

  • RCW 9A.04.080 — 5 years
• Named sub-rules and exceptions the tool accounts for:

  • RCW 9A.04.080 — 5 years — exception P1
  • RCW 9A.04.080(1)(j) — 3 years — exception V1
  • null — 3 years — exception V2

How the tool is structured (inputs → outputs)

When you use /tools/breakup-fee-clauses, you’ll typically provide information such as:

• the relevant clause type (breakup provision vs. fee shifting / fee exposure)
• the trigger event date (or expected trigger date)
• the estimated enforcement or demand date
• any clause details that determine which limitation bucket the calculator should use

Then the tool produces:

• a modeled deadline based on the applicable limitation period (e.g., 5 years vs. 3 years)
• a compliance/timing check showing whether the modeled demand/enforcement falls within the limitation window
• a scenario summary you can reuse when comparing alternatives (e.g., different trigger dates or exception selection)

Washington timing logic at a glance

The calculator’s limitation-period logic in Washington is built around the RCW 9A.04.080 framework:

Because the exceptions change the outcome, you’ll get the most value by entering facts carefully—especially dates and trigger descriptions.

When to use it

Use the DocketMath Breakup & Fee Clauses Calculator when you want to evaluate timing and fee exposure connected to contract clauses that can function like “breakup” economics (termination-related payoffs, penalty-style language, reimbursement or fee-shifting mechanics, etc.).

Common situations include:

• You’re evaluating whether a demand could be time-barred under Washington’s RCW 9A.04.080-based framework.
• A clause’s enforceability depends on when the underlying event occurred, and you need to model alternatives (e.g., different trigger interpretations).
• Negotiations are centered on fee exposure, and you want a quick “what if” comparison of timelines and risk.
• A dispute timeline is already underway, and you need an operational view of deadlines to coordinate evidence collection and communications.

Practical triggers for calculator use

Check whether your work involves any of the following:

• A termination event with an attached payment obligation (breakup-style language)
• A fee-shifting clause tied to enforcement or collection
• A potential claim that depends on a specific event date (not just when you learned about it)
• Multiple events where the “trigger” could reasonably be argued as one date or another

When not to rely on the calculator alone

Avoid using the calculator as your only source when:

• there are multiple distinct triggers (e.g., several alleged breaches with different dates)
• the clause language is ambiguous enough that trigger selection is uncertain
• you’re missing the exact dates needed to model the window (trigger date vs. demand date)

In these cases, the tool still helps you structure assumptions, but you’ll want to validate the assumptions behind your input choices.

Tips for accuracy

• Confirm the trigger definition in the contract. Many disputes turn on whether the “clock” starts from notice, termination, breach, or performance failure—use the clause text, not recollection.
• Use source documents for dates. Prefer timestamps from notices, emails, declarations, invoices, or termination letters over memory.
• Run multiple plausible triggers. If the trigger date is arguable, re-run /tools/breakup-fee-clauses with each defensible option and compare the boundary between 3-year and 5-year outcomes.
• Keep your framing consistent. If you choose a 3-year assumption, ensure the trigger date you entered matches the event that would start that limitation period in your theory.
• Record assumptions in scenario notes. Treat the output as a model of your chosen facts; document what you assumed so others can audit the scenario quickly.

Step-by-step example

Below is a full walkthrough you can mirror in /tools/breakup-fee-clauses.

Scenario: Modeling a termination-related breakup payment and potential fee exposure

Assume:

• The agreement includes a breakup provision requiring a payment upon termination.
• The dispute hinges on a claimed trigger event date.
• A demand is planned later, and you want to model timing risk.

Given facts

• Trigger event date: January 15, 2020
• Planned demand/enforcement date: March 1, 2023
• Washington context: Use RCW 9A.04.080 limitation logic with the appropriate exception selection

You will compare two limitation possibilities that the tool accounts for: 5 years vs. 3 years.

Step 1: Open the calculator and select the tool inputs

Go to /tools/breakup-fee-clauses and enter:

• Clause category: breakup / fee exposure (select the closest option shown in the tool)
• Trigger event date: 01/15/2020
• Demand/enforcement date: 03/01/2023
• Exception selection: choose the bucket you are modeling (the tool reflects:

  • 5 years under RCW 9A.04.080
  • 3 years under RCW 9A.04.080(1)(j) or the tool’s V2 rule)

Step 2: Run the “5-year” model (general rule)

Using the 5-year window:

• Start: 01/15/2020
• End of modeled period: 01/15/2025

Demand date: 03/01/2023
Result: falls within the 5-year window.

What this means for your model:

• Under the 5-year assumption, the demand/enforcement is timed within the limitation window.

Step 3: Run the “3-year” model (exception-based)

Now model a 3-year window:

• Start: 01/15/2020
• End of modeled period: 01/15/2023

Demand date: 03/01/2023
Result: falls after the modeled 3-year window.

What this means for your model:

• Under a 3-year exception assumption (e.g., RCW 9A.04.080(1)(j) as reflected in tool logic, or the tool’s V2), the same demand date becomes timing-problematic.

Step 4: Interpret the output using a decision checklist

After running both models, capture what the calculator shows in your scenario notes. Use this quick decision checklist:

Common scenarios

Not every dispute looks like the simple example. Here are common patterns where the calculator’s outputs help you run faster comparisons.

1) “Trigger date” disputes (same contract, different dates)

A very frequent issue in clause-timing modeling is what qualifies as the trigger.

Typical versions:

• Trigger as the first breach date
• Trigger as the termination date
• Trigger as the notice date
• Trigger as the date performance failed in a material way

Calculator value: it lets you re-run quickly with alternate dates to see whether you cross the 3-year boundary (under RCW 9A.04.080(1)(j) or the tool’s V2) or stay within 5 years under RCW 9A.04.080.

Checklist:

2) Fee-sh

Sources and references

Start with the primary authority for Washington and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

• Breakup & Fee Clauses Calculator Guide for Alabama
• Breakup & Fee Clauses Calculator Guide for Arizona
• Breakup & Fee Clauses Calculator Guide for California