What this calculator does

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

DocketMath’s Breakup & Fee Clauses Calculator (Indiana) helps you estimate how long a breakup clause can keep running and how fee or payment triggers may affect timing and cost when the clause is tied to statutory deadlines.

Because contract language often interacts with statutory limitations periods, this tool focuses on one key Indiana rule for timing:

• Indiana Code § 35-41-4-2 provides a 5-year limitations period.
• A specific exception (V3) is noted in the calculator’s jurisdiction configuration.

In practical terms, you can:

• Enter a clause start/trigger date (and any relevant dates you have).
• Add the clause’s “window” assumptions (for example, when a payment right vests or when a dispute is deemed to accrue).
• See an estimated latest date for clause-related actions based on the 5-year statutory period.

What you’re likely calculating

Breakup & fee clauses show up in multiple deal contexts, such as:

• termination for convenience or breach,
• buyout / unwind provisions,
• fee shifting, liquidated damages, or reimbursement triggers,
• “notice-and-cure” cycles that affect when a claim is considered live.

This calculator is designed for scenarios where the clause (or the right to enforce it) is linked to a limitations framework, including the 5-year period in Indiana Code § 35-41-4-2.

The core timing rule in Indiana

• Limitations period: 5 years
• Statute: Indiana Code § 35-41-4-2
• Reference: https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/

The calculator uses that 5-year configuration, with an exception labeled “V3” according to the jurisdiction dataset.

Inputs you’ll typically provide (and why)

Depending on the tool’s field set, common inputs include:

• Trigger date (the date the breakup clause is considered to start or become actionable)
• Action date (the date you plan to enforce, notify, or file)
• Clause type assumptions (if your version includes toggles such as “fee trigger,” “unwind,” or “dispute”)
• Optional adjustment fields (sometimes used to reflect a specific “exception” pathway or accrual logic)

Outputs usually include:

• a computed expiration date based on the 5-year limitations period,
• a pass/fail timing result (e.g., whether an action date falls inside the window),
• and fee-related timing effects based on the clause structure you entered.

When to use it

Use DocketMath’s calculator when you have a date-driven clause and you want a clean, reproducible estimate for the latest enforceable timeline that a 5-year limitations period might impose.

Best-fit situations include:

• You’re reviewing an agreement and want to map termination / breakup mechanics to a 5-year clock.
• You’re preparing a dispute timeline for internal review (not courtroom filings) and want a consistent way to calculate cutoff dates.
• Your clause ties enforcement or payment rights to “within X years,” “after notice,” or a “claim period” that you suspect aligns with statutory timing.
• You’re assessing a historical scenario (e.g., termination happened years ago) and need to determine whether a claim-like enforcement attempt could still be timely under the Indiana Code § 35-41-4-2 configuration.

Focus areas that commonly benefit from a limitations check

Check this tool particularly if your documents include any of the following mechanics:

• “If the agreement terminates, Buyer/Company may recover …”
• “Within [X] days after notice, [party] may demand …”
• “Payment due upon termination/trigger/event”
• “Fee or liquidated damages payable if termination occurs after a certain milestone”

Even if the clause itself states a deadline, the statutory limitations period can still matter when you’re thinking about enforcement timing.

Step-by-step example

Below is a concrete walkthrough using the typical logic set the calculator is designed around: a 5-year window under Indiana Code § 35-41-4-2.

For reference:

• Statute used: Indiana Code § 35-41-4-2
• Limitations period: 5 years
• Dataset note: includes a V3 exception path

Scenario: termination-triggered breakup and a fee demand

Assume these facts from an agreement record:

• The contract breakup clause is triggered when a termination event occurs.
• The termination event happened on January 15, 2021.
• You want to know whether an enforcement-style demand (or related action tied to the clause) on January 20, 2026 would fall within the 5-year window.

Step 1: Enter the trigger date

• Trigger date: 2021-01-15

Why it matters:

• The tool treats this as the start point for the clock used in the 5-year calculation under Indiana Code § 35-41-4-2.

Step 2: Enter your action date

• Action date: 2026-01-20

Why it matters:

• The tool compares your action date to the computed expiration date.

Step 3: Confirm clause assumptions (fee trigger / breakup window)

If your calculator interface includes a toggle or dropdown for fee mechanics, choose the closest match. For example:

• Fee clause assumption: “Termination-triggered fee”
• If there’s a switch for exception logic, select “standard” unless your facts clearly match the V3 path.

Step 4: Review the computed results

With a 5-year limitations period, a straightforward calculation yields an expiration around:

• Expiration date (estimated): 2026-01-15 (5 years from 2021-01-15)

Then compare:

• Action date: 2026-01-20
• Expiration: 2026-01-15

Result interpretation (as a planning estimate):

• Action date is ~5 days after the estimated expiration.
• The tool should flag that this is outside the standard 5-year window.

Step 5: Adjust inputs to test timing sensitivity

Try two common variations to see how outputs change:

1. If the action date were 2026-01-14, it should fall inside the window.
2. If the trigger date were documented as 2021-01-20 instead of 2021-01-15, the expiration shifts accordingly.

This “input sensitivity” is often the fastest way to understand how document ambiguity (notice date vs. termination date vs. claim accrual date) changes the calculated cutoff.

Common scenarios

DocketMath’s breakup & fee clauses tool is most useful when your clause facts can be expressed as dates and event triggers. Here are common patterns—along with what to watch for in the calculator’s timing logic.

1) Termination date is clear, but fee demand date is later

Typical pattern

• Termination occurs on March 1, 2019
• Fee demand is sent on March 5, 2024
• You want to know whether it’s within the limitations-derived timing.

Calculator approach

• Use termination as the trigger/clock start if the clause treats it as the relevant event.
• Use fee demand as your action date (if that’s how your workflow frames enforcement timing).

2) Notice-and-cure provisions create multiple candidate dates

Typical pattern

• Notice issued: May 10, 2020
• Cure period ends: June 25, 2020
• Breakup/termination effective: July 1, 2020

What changes

• Your estimated expiration date can shift depending on which event you treat as the clock start.
• If your agreement says “breakup becomes enforceable upon termination becoming effective,” you’ll likely choose July 1, 2020 as trigger.
• If instead “claim accrues upon notice,” you’d input May 10, 2020.

Use the calculator to compare

• Run 2–3 variants and see which trigger produces a realistic cutoff aligned with your clause text.

3) Fee is tied to a milestone rather than termination

Typical pattern

• Breakup clause triggers on termination, but
• A fee becomes due when a milestone is “achieved” (or missed) after termination.

How to model

• Enter the milestone date as the clock start if your facts indicate the fee right is enforceable from that event.
• Otherwise, keep termination as the trigger and use the milestone date as a later “action date.”

4) Exception-labeled pathways (V3)

Your Indiana configuration includes an exception V3 path.

Use it when

• Your clause and facts match the exception’s intended scenario in the calculator’s jurisdiction logic.
• If you’re unsure, run the calculator twice: once with the default path and once with the V3 path, then compare outputs.

Interpretation caution

• Exceptions can be sensitive to how claims accrue and the clause’s specific structure. Treat the V3 output as a “fact-matching check,” not a guarantee of how a court will decide accrual.

Related reading

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