Disputes and remedies: cure notices, escalation, and claims

Reference article · 6 min read

Most technology contracts that end badly do not collapse in a single moment. A milestone slips, the defect backlog grows, an integration that was sold as configuration turns into custom development, and the agency spends several quarters in status meetings waiting for the vendor to recover. When someone finally asks what the contract actually permits, the answer is often that the strongest remedies were available months earlier and were never invoked, and that the project file holds meeting notes rather than notices.

A remedy ladder is the sequence of steps your contract gives you, from routine and low friction to formal and adversarial. Knowing the ladder before you need it changes how you run the contract day to day, because nearly every rung depends on documentation you either created at the time or did not.

The rungs, and what each one actually gets you

• Withholding or reducing payment. The most direct lever, and usually the fastest. It works only if your payment terms are tied to acceptance or to defined deliverables rather than to elapsed time. What it gets you is attention and leverage, not repair.
• Rejection and non-acceptance. Refusing to accept a deliverable that fails written acceptance criteria keeps the clock and the obligation on the vendor. Many contracts convert silence into acceptance after a set number of days, so the rejection has to be timely and in writing.
• Service credits. Common in hosted and managed services. Credits compensate for availability or response failures at a preset rate. They are modest by design, and in many contracts they are stated as the exclusive remedy for the specific failure they cover, which is why the exclusivity language matters more than the credit percentage.
• Liquidated damages. A preset amount for a defined failure, typically late delivery. They are enforceable when the amount is a reasonable pre-estimate of harm that would be hard to calculate, and unenforceable when they function as a penalty. Rules on this vary by state, so have counsel review the clause before you rely on it.
• Cure notice. A formal statement that performance is deficient, what the deficiency is, and how long the vendor has to fix it. This is the hinge of the ladder. Most contracts require it before termination for cause, and an incomplete or informal cure notice is a common reason a default termination later fails.
• Executive escalation. A contractual path from project leads to named executives on a defined schedule. It gets you access to people with budget authority who have not been living inside the project narrative.
• Mediation or a structured dispute conference. Non-binding, relatively fast, and often the last point at which a working relationship survives. Many public contracts require it before litigation.
• Termination for cause, claims, arbitration, or litigation. These get you money or exit, not a working system. They are slow and expensive, and the agency still has to solve the original problem.

Build the factual record from day one

The record is not created during a dispute. It is created during normal operations by people who do not yet think there is a dispute.

• Send written acceptance or rejection for every deliverable, against the criteria in the contract, within the stated window.
• Log defects in one system with severity, date reported, and date resolved. An exported defect history is worth more than any narrative.
• Confirm material meeting outcomes in a follow-up email that states decisions and commitments. Vendor silence in response to an accurate summary is useful later.
• Keep change orders clean. Note when a change is the vendor's remediation of its own failure rather than new scope, and avoid signing amendments containing broad release language without reviewing it.
• Track your own obligations too. Late agency decisions, missing test data, and unavailable subject matter experts will be the vendor's defense, and you want an accurate account of them before the vendor writes one.

Preserve rights while performance continues

Agencies rarely want to stop work, and continuing performance is usually the right call. The risk is that ordinary cooperation reads later as waiver.

State a reservation of rights in writing when you accept partial performance, grant an extension, or pay an invoice for work you consider deficient. Confirm that the contract has a non-waiver clause and that accepting one late milestone does not forfeit remedies for the next. Watch for deadlines that run against you: notice periods for claims, acceptance windows, and in many jurisdictions a statutory or charter-based deadline for presenting a claim against or by a public entity. Those deadlines are unforgiving and vary widely, so confirm them with your counsel rather than assuming the contract states them all.

Write cure notices that hold up

A cure notice is not an angry email. It should identify the contract and the specific provision breached, describe the deficiency factually with dates and references to the record, state the cure period the contract provides, say what acceptable cure looks like, reserve all rights, and go to the notice address in the contract by the method the contract requires. Send it through the contracting officer, not the project manager, and copy counsel. If the cure period passes without compliance, decide deliberately whether to extend, escalate, or proceed, and document that decision.

When counsel replaces another status meeting

Bring counsel in when any of the following is true: you are considering withholding payment or issuing a cure notice, a vendor has asserted a claim or blamed agency delay in writing, termination or replacement is on the table, or the remaining schedule no longer supports the business need behind the procurement. Early counsel involvement is usually inexpensive relative to a late one. A second consecutive status meeting with the same red items and the same recovery promise is a signal, not a plan.

What to require in the contract before you need it

Ask vendors during negotiation how their standard agreement handles each of these, and require what your jurisdiction allows:

• Objective, written acceptance criteria and a defined acceptance and rejection process with a cure opportunity.
• Payment tied to accepted deliverables, with meaningful retainage or holdback where permitted.
• Service levels with credits that are stated as non-exclusive remedies wherever you can negotiate it.
• A named escalation path with titles, timeframes, and a requirement to meet.
• Termination for convenience and for cause, with transition assistance obligations that survive termination.
• Source code, configuration, and data escrow or export rights, plus a defined data return format.
• Clear ownership of work product and license continuity if the relationship ends.

HQT works with state and local agencies on technology delivery and systems engineering, including the acceptance criteria and documentation practices that make these contract terms usable.

Frequently asked questions