When a Contractual Right Exists but Cannot Yet Be Used

A contract may permit a party to terminate, suspend service, withhold payment, reject a deliverable, call security, accelerate an obligation, or demand an audit. The clause establishes the right. It may not establish that the right has matured on the present facts.

Consider a termination right that arises only if a missed milestone continues for ten business days after valid notice. The missed date matters, but it is not the entire analysis. The breach must fall within the clause, the notice must satisfy the contract, the cure period must run, and the terminating party must avoid conduct that waived the breach or prevented cure.

The discipline is to test the proposed action in stages.

1. Locate the right and every dependency

Start with the operative clause, then read outward. A termination or suspension provision may depend on definitions, schedules, service levels, acceptance criteria, materiality thresholds, exclusions, knowledge standards, cure rights, or cross defaults in another agreement.

The key questions are:

• What precise event creates the right?
• Must the event be material, continuing, repeated, or incapable of cure?
• Is the event measured objectively, or does the clause permit a stated judgment or reasonable satisfaction standard?
• Is an approval, certification, demand, or notice a condition to exercise?
• Does another clause limit the remedy or make it exclusive?

A summary prepared from memory is not enough. The analysis should quote the relevant language and record every incorporated document in the applicable order of precedence.

2. Distinguish a condition from a promise

Contract terms may distinguish between an obligation and a condition that must be satisfied before another obligation or remedy becomes available. The effect of that distinction depends on the agreement and governing law. Before acting, determine whether the relevant step is a prerequisite to the remedy, what level of compliance is required, and whether either party's conduct affects reliance on it.

3. Separate the event from proof of the event

The business team may be convinced that a breach occurred. A decision maker will ask how the contract defines it and how the record proves it.

For a missed service level, the relevant evidence may include system logs, exclusions for planned maintenance, incident tickets, time zones, and the agreed calculation period. For defective deliverables, it may include acceptance criteria, review comments, test results, and whether the customer supplied required dependencies. For nonpayment, it may include invoice delivery, disputed amounts, credits, withholding requirements, and the due date after receipt.

A useful evidence file should answer:

• What happened?
• When did it happen, under the contract's time zone and business day rules?
• Which clause does it satisfy?
• What contrary explanation is likely?
• Which records are contemporaneous and controlled by a neutral system?
• What evidence still needs to be preserved or obtained?

Cross border performance makes this work more important. Records may sit with affiliates or subprocessors, timestamps may use different zones, and witnesses may be outside the forum.

4. Treat notice and cure as part of the remedy

Notice is not clerical. It can be a contractual condition to the right.

Check the designated recipient, physical and electronic addresses, permitted delivery method, required content, time of deemed receipt, and interaction with weekends, holidays, and time zones. A message to the relationship manager may communicate the problem without satisfying a clause that requires notice to a general counsel at a stated address.

The notice should identify the contract, event, relevant provision, requested cure, and reservation of rights with enough precision for the recipient to respond. Overstatement can create credibility problems. Understatement can leave the trigger unclear.

If a cure period applies, calculate it from the event the contract selects, not from the date the sender prefers. Record delivery and receipt. Avoid instructions or access restrictions that make cure impossible unless the contract clearly permits them.

5. Confirm authority, waiver, and consistency

Confirm that the sender has authority to act for the party and that the notice complies with any contract requirements concerning who may send it.

The file should also address course of performance. Questions include:

• Has the party accepted the same conduct before?
• Did it extend the deadline or promise more time?
• Does the contract require a signed waiver, and how will the governing law treat the parties' conduct?
• Has the party continued to demand full performance in a way that is inconsistent with termination?
• Did its own failure cause or contribute to the event?

A nonwaiver clause helps, but it should not be treated as permission to act inconsistently without analysis.

6. Test the remedy against the aftermath

Using a right changes the relationship. Before acting, trace the immediate and downstream consequences.

For termination or suspension, consider access to systems and data, transition assistance, employee and contractor instructions, licenses, confidentiality, payment, deposits, inventory, customer communications, regulatory notices, and records subject to applicable preservation obligations. For rejection or withholding, consider whether the contract permits correction, replacement, partial acceptance, setoff, or continued use.

As a commercial and dispute risk matter, assess whether the proposed action is proportionate. Separately confirm whether the agreement or applicable law limits the chosen remedy. A service credit may be an exclusive remedy, an indemnity may be limited to third party claims, and the agreement may cap or exclude different categories of loss in different ways. Exercising one remedy may also affect another.

Use a short decision record

Before a material right is exercised, prepare a record that states:

• The clause and every contractual dependency.
• The event relied on and the evidence supporting it.
• Missing or disputed facts.
• The notice, approval, and cure steps required.
• The deadline and the person authorized to act.
• The counterparty's strongest likely argument.
• The remedy selected and any alternatives considered.
• The operational, financial, regulatory, and dispute consequences.

This record need not become a long memorandum. Its value is precision. It forces the team to distinguish a right that exists in the document from a right that has matured, can be proved, and can be used without creating a larger problem.