Technology Project Dispute Toolkit: Notice of Breach Letters, Cure Plans, and Project Record Protocols

Summary. This toolkit provides ten working templates for customers and vendors in a troubled or failed software implementation, from the go-live reservation of rights through the final settlement and transition agreement. Each template states its purpose, owner, and timing, uses bracketed placeholders, and is followed by drafting commentary tied to the governing authority, including material breach and cure doctrine, UCC acceptance and adequate assurance, Rule 37(e) preservation duties, copyright assignment requirements, Rule 408, and the case law on limitation-of-liability carve-outs. The templates include a change order log, a notice of material breach and demand for cure, a vendor response, a cure plan, a project record protocol and litigation hold notice, a termination notice with transition demand, a tolling and standstill agreement, a damages model outline, and a settlement and transition agreement. A running example involving an outdoor retailer and its order management integrator shows how the documents fit together. An index table at the top lets the reader go directly to the template needed.

How to use this toolkit

The documents in a failed technology project dispute are written under pressure, usually by people who are also trying to keep a business running. They become exhibits. A notice of breach that lists the wrong breaches, a cure plan with dates nobody could meet, or a go-live email that says "we accept" can decide the case more surely than any later brief.

These templates are starting points. Adapt them to the actual contract (notice addresses, cure periods, defined terms, governing law) and to the facts. Each one begins with Purpose / Owner / When to use, presents the template with [BRACKETED PLACEHOLDERS], and ends with drafting commentary tied to authority. For the substantive law, see Failed Software Implementations: Contract, Fraud, and Warranty Claims When an IT Project Goes Wrong. For the sequence of steps, see Pursuing or Defending a Failed Technology Project Claim: A Practical Guide and Troubled Technology Project Checklist: A Practical Checklist.

Template index

Running example: Halden Outdoor Supply and Quillstone Consulting

Halden Outdoor Supply, a retailer with 60 stores and a growing e-commerce business, hired Quillstone Consulting to implement a cloud order management system (OMS) connecting its web store, stores, and two distribution centers. The MSA is governed by New York law and requires arbitration before the AAA in New York. SOW 3 (fixed fee, $2.75 million, paid by milestone with a 10% holdback) covered design, build, integration, and data migration, with go-live set for February 1. The MSA caps liability at fees paid under the applicable SOW in the prior twelve months, excludes consequential damages and lost profits, carves out gross negligence, willful misconduct, and breach of confidentiality, and requires 30 days' written notice and opportunity to cure before termination for cause. SOW 3 names a lead solution architect as key personnel and requires Halden's approval of any replacement. The OMS subscription is licensed directly from its publisher under a separate agreement. The templates below are filled in, where useful, with Halden's facts.

Template 1: Go-live reservation of rights memorandum

Purpose: Preserve the customer's claims when business necessity requires production use of a system that has not met acceptance criteria. Owner: Customer counsel drafts; executive sponsor signs; vendor project director countersigns if possible. When to use: Before cutover, whenever known severe defects remain open.

[CUSTOMER LETTERHEAD]

[DATE]

To: [VENDOR PROJECT DIRECTOR NAME], [VENDOR NAME]
Copy: [VENDOR NOTICE ADDRESSEE PER MSA SECTION [X]]

Re: Production Use of [SYSTEM NAME] Under SOW [NUMBER]; Reservation of Rights

1. [CUSTOMER] will begin production use of [SYSTEM] on [DATE] because
   [BUSINESS REASON, e.g., expiration of the legacy system contract on [DATE]].

2. Production use is not Acceptance of any Deliverable under Section [X]
   of the MSA or Section [X] of SOW [NUMBER]. No Acceptance Certificate
   has been or will be signed until the acceptance criteria in
   [SOW SECTION / EXHIBIT] are met.

3. As of this date, the following defects remain open: [LIST OR ATTACH
   DEFECT LOG EXTRACT WITH IDS, SEVERITY, DESCRIPTION]. [VENDOR] has
   agreed to resolve Severity 1 defects by [DATE] and Severity 2 defects
   by [DATE].

4. [CUSTOMER] reserves all rights and remedies under the Agreement and
   applicable law, including rights to reject or revoke acceptance,
   to withhold disputed payments under Section [X], to recover damages,
   and to terminate. Nothing in this memorandum, in production use, or in
   any payment waives any right or remedy.

5. Please countersign below to confirm [VENDOR]'s agreement to paragraphs
   2 and 3.

[CUSTOMER SIGNATORY NAME, TITLE]

Acknowledged and agreed as to paragraphs 2 and 3:
[VENDOR SIGNATORY NAME, TITLE]   Date: [DATE]

Commentary. Many MSAs provide that production use constitutes acceptance, or that a deliverable is deemed accepted if not rejected within a fixed period. A written statement that production use is not acceptance, ideally countersigned, is the best answer to those clauses. Under Article 2, if it applies (cited here through California's enactment, whose section numbers track the uniform text), acceptance occurs when the buyer signifies acceptance or fails to reject after a reasonable opportunity to inspect (Cal. Com. Code § 2606); revocation of acceptance is available for nonconformities that substantially impair value if the buyer accepted on the reasonable assumption they would be cured (Cal. Com. Code § 2608). Paragraph 3's list of open defects with agreed dates makes that "reasonable assumption" provable. Courts disagree about whether implementation services fall within Article 2 at all (compare Advent Systems Ltd. v. Unisys Corp., 925 F.2d 670 (3d Cir. 1991), with Conwell v. Gray Loon Outdoor Marketing Group, Inc., 906 N.E.2d 805 (Ind. 2009)), so draft the memorandum to work under the contract's own acceptance clause regardless.

Vendor version. A vendor should ask for the opposite: written confirmation that production use is acceptance, or at least a defined list of open items whose resolution triggers acceptance automatically. If the customer refuses both, the vendor should document the go-live decision as the customer's.

Halden example. Halden's legacy OMS contract expires January 31. Halden goes live February 1 with 22 open Severity 1 and 2 defects. Its CFO signs Template 1; Quillstone's project director countersigns paragraphs 2 and 3, committing to Severity 1 fixes by February 21.

Template 2: Change order log

Purpose: Create a single, contemporaneous record of every scope, schedule, and price change, approved or not. Owner: Each side's project management office maintains its own copy; the two are reconciled monthly. When to use: From kickoff. If the project is already troubled, reconstruct it immediately.

Monthly reconciliation note (append to log):

Change Order Log Reconciliation, [MONTH YEAR]

Reviewed by: [CUSTOMER PMO LEAD] and [VENDOR PMO LEAD]
Approved changes this period: [CR NUMBERS]; cumulative price impact [$X];
  cumulative schedule impact [X WEEKS].
Disputed items: [CR NUMBERS], with each party's position summarized in
  the Notes column.
Work performed before approval: [CR NUMBERS]. The parties [agree / do not
  agree] that this work is [in scope / a change].
This reconciliation does not waive either party's position on disputed
  items or the requirements of Section [X] (Change Control).

[SIGNATURES]

Commentary. Most scope fights turn on whether informal requests changed the contract. When an MSA requires signed change orders but the parties routinely proceeded on emails, courts sometimes find the written-change requirement waived by conduct and sometimes enforce it strictly; the result often depends on whether the customer knew of and accepted the extra work. The column "work started before approval" is the one that will matter most. A log reconciled and signed monthly is a business record likely admissible under Fed. R. Evid. 803(6), and a large log can be presented at trial through a summary under Fed. R. Evid. 1006. For drafting change control in the first place, see Negotiating a Master Services Agreement and Statement of Work; for agile projects without formal change orders, see MC Law's article on legal issues in agile software development.

Halden example. Halden's reconstructed log shows 31 change requests. Quillstone and Halden agree that 17 were approved, 6 were in scope at no charge, and 8 are disputed, including a buy-online-pick-up-in-store feature that Quillstone built after an email from Halden's e-commerce director.

Template 3: Notice of material breach and demand for cure

Purpose: Formally identify breaches, start the contractual cure period, and frame any later termination and claim. Owner: Customer counsel. When to use: When recovery efforts have failed and termination is a real possibility. Complete any mandatory escalation step first.

[CUSTOMER LETTERHEAD]

[DATE]

BY [DELIVERY METHOD REQUIRED BY MSA SECTION [X], e.g., OVERNIGHT COURIER
AND EMAIL]

[VENDOR NAME]
Attn: [NOTICE ADDRESSEE PER MSA]
[ADDRESS]
Copy: [COPY-TO ADDRESSEE PER MSA]

Re: Notice of Material Breach and Demand for Cure: Master Services
    Agreement dated [DATE] (the "MSA") and Statement of Work No. [X]
    dated [DATE] (the "SOW")

Dear [NAME]:

This letter is [CUSTOMER]'s notice under Section [X] of the MSA that
[VENDOR] is in material breach of the MSA and the SOW. [If applicable:
The parties completed executive escalation under Section [X] on [DATE]
without resolution.]

1. Breaches. [VENDOR] has breached the following obligations:

   (a) [Milestone/acceptance breach.] Section [X] of the SOW required
       [VENDOR] to deliver [DELIVERABLE] meeting the acceptance criteria
       in [EXHIBIT] by [DATE]. As of today, [DELIVERABLE] has failed
       [NUMBER] of [NUMBER] acceptance test scripts, including [EXAMPLES],
       as reflected in [DEFECT LOG / TEST REPORT DATED [DATE]].

   (b) [Key personnel breach.] Section [X] of the SOW designates
       [NAME] as [ROLE] and requires [CUSTOMER]'s prior written approval
       of any replacement. [VENDOR] removed [NAME] on or about [DATE]
       without approval and has not provided a replacement meeting the
       qualifications in Section [X].

   (c) [Service level / performance standard breach.] [DESCRIBE, WITH
       MEASUREMENT AND CONTRACT REFERENCE.]

   [LIMIT TO THE BREACHES THAT ARE MATERIAL AND PROVABLE.]

2. Materiality. Individually and collectively, these breaches are
   material [under Section [X] of the MSA / considering the Agreement
   as a whole], because [EXPLAIN IN ONE OR TWO SENTENCES: e.g., the
   order management system cannot reliably release orders across
   distribution centers, which is the core function the SOW required].

3. Cure required. To cure, [VENDOR] must, within [30] days after
   receipt of this notice: [MEASURABLE CURE CRITERIA, e.g., (i) resolve
   all open Severity 1 defects listed in Attachment A; (ii) pass test
   scripts [X-Y] in a test cycle witnessed by [CUSTOMER]; (iii) assign
   a replacement [ROLE] approved by [CUSTOMER]].

4. Cure plan. Please provide a written cure plan within [10] business
   days identifying the actions, named resources, dates, and exit
   criteria by which [VENDOR] will cure. [CUSTOMER] will review the plan
   in good faith and will make [its personnel / test environments /
   data] available as reasonably required.

5. Payments. Under Section [X], [CUSTOMER] disputes invoices [NUMBERS]
   totaling [$AMOUNT] for the reasons stated above and will pay
   undisputed amounts when due. [CUSTOMER] will continue to withhold the
   [10]% holdback under Section [X].

6. Preservation. [CUSTOMER] anticipates that this matter may result in
   a dispute. Please preserve all documents and electronically stored
   information relating to the project, including email, Slack/Teams
   messages, Jira and Confluence content, code repositories, test
   records, staffing records, and internal status reports and risk
   registers. Please provide, within [5] business days, a complete
   export of the [PROJECT TOOL] instance hosted on [VENDOR]'s account.

7. Reservation of rights. [CUSTOMER] reserves all rights and remedies,
   including the right to terminate under Section [X] if the breaches
   are not cured within the cure period, to recover damages, and to
   assert any other claims. [CUSTOMER]'s continued performance,
   cooperation, and payment of undisputed amounts are without waiver.
   Nothing in this letter is an election of remedies.

Sincerely,

[NAME, TITLE, AUTHORIZED SIGNATORY PER MSA]

Attachment A: [Open defect list with IDs and severity]

Commentary.

• Mechanics. Follow the notice clause exactly. A notice sent by the wrong method or to the wrong addressee may not start the cure period.
• Fewer, stronger breaches. Restrict the list to breaches that are material and provable. A later termination letter should rely on the same breaches; adding new ones invites the argument that the vendor never had a chance to cure them.
• Materiality. Where the contract defines materiality, use its language, because that standard governs (State v. International Business Machines Corp., 51 N.E.3d 150 (Ind. 2016)). Where it is silent, courts use Restatement (Second) of Contracts § 241, which weighs the likelihood of cure, so a notice that specifies achievable cure criteria strengthens a later termination.
• Measurable cure. Cure criteria tied to test scripts and named roles make it possible to show objectively that cure failed.
• Adequate assurance. If Article 2 may apply, add a sentence demanding adequate assurance of performance under Cal. Com. Code § 2609 (UCC § 2-609); failure to provide it within a reasonable time not exceeding 30 days may be treated as repudiation under Cal. Com. Code § 2610.
• No fraud accusations without documents. A notice that alleges fraud signals litigation and may end any cure effort. If fraud is a real possibility, reserve "all claims, including claims relating to the inducement of the Agreement," and develop the facts first. Fraud must eventually be pleaded with particularity under Fed. R. Civ. P. 9(b).
• Preservation demand. Paragraph 6 doubles as a request for the vendor-hosted tool export, which the customer may lose access to on termination.

Halden example. Halden's notice cites three breaches: failure of the cross-distribution-center order release scripts (19 of 64 failing), unapproved removal of the lead solution architect in November, and failure to complete migration of open customer orders. It demands cure within 30 days and a cure plan within 10 business days.

Template 4: Vendor response to notice of breach

Purpose: Answer the notice on the record, propose a cure where appropriate, dispute what is wrong, and identify the customer's own open obligations. Owner: Vendor counsel, with the delivery lead. When to use: Within the response or cure-plan period stated in the notice or the MSA.

[VENDOR LETTERHEAD]

[DATE]

BY [METHOD REQUIRED BY MSA]

[CUSTOMER NAME]
Attn: [NOTICE ADDRESSEE]

Re: Response to Notice of Material Breach dated [DATE]

Dear [NAME]:

[VENDOR] received [CUSTOMER]'s notice dated [DATE] on [DATE]. [VENDOR]
is committed to the success of [PROJECT] and responds as follows.

1. Item 1(a) [acceptance testing]. [VENDOR] [acknowledges that test
   scripts [X] remain open / disputes the characterization]. [EXPLAIN
   FACTS.] [If applicable: Scripts [X-Y] depend on [CUSTOMER DATA /
   DECISION] that SOW Section [X] makes [CUSTOMER]'s responsibility,
   which was requested on [DATES] and provided on [DATE] / remains
   outstanding.] [VENDOR] proposes to resolve the remaining items as
   set out in the enclosed cure plan.

2. Item 1(b) [key personnel]. [STATE FACTS, e.g., [NAME] resigned from
   [VENDOR] effective [DATE]; [VENDOR] notified [CUSTOMER] on [DATE] and
   proposed [REPLACEMENT], whose qualifications are attached.] [VENDOR]
   requests [CUSTOMER]'s approval under Section [X] by [DATE].

3. Item 1(c). [RESPOND.]

4. Customer obligations. To complete the cure plan, [VENDOR] requires
   the following from [CUSTOMER] under SOW Sections [X]: [LIST, e.g.,
   sign-off on design decisions [IDS] within [5] business days; cleansed
   payer/customer master data by [DATE]; availability of [ROLES] for
   [HOURS] per week].

5. Change requests. Change requests [NUMBERS] remain unsigned. [VENDOR]
   has performed work on [NUMBERS] at [CUSTOMER]'s written direction
   dated [DATES] and reserves its right to payment.

6. Invoices. [VENDOR] disputes [CUSTOMER]'s withholding of invoices
   [NUMBERS] to the extent they relate to [UNDISPUTED WORK], and
   requests payment of [$AMOUNT] by [DATE].

7. Preservation. [VENDOR] has implemented a litigation hold and will
   provide the requested [PROJECT TOOL] export by [DATE]. [VENDOR]
   requests that [CUSTOMER] likewise preserve all project records.

8. Reservation of rights. [VENDOR] reserves all rights and remedies,
   including with respect to payment, change requests, and any
   termination. Nothing in this letter is an admission of breach or of
   materiality.

Sincerely,
[NAME, TITLE]
Enclosure: Cure Plan (Template 5)

Commentary. Silence or a one-line denial reads as acknowledgment. A point-by-point response that offers a cure where the criticism is fair and disputes the rest with specific references gives the vendor three advantages: it shows good faith (a Restatement § 241 factor), it documents customer-caused delay (the prevention defense), and it preserves the fee claim. Avoid unqualified acknowledgments such as "we accept the issues raised." A vendor that removed named key personnel without approval should address it directly, because it is one of the easiest breaches for a customer to prove. Notify the errors and omissions carrier if it has not been notified already. If the vendor's internal records show the project in worse condition than its reports to the customer, the response is not the place to repeat optimistic reporting; consult counsel about the fraud exposure before signing.

Template 5: Cure plan

Purpose: Convert the cure obligation into a measurable, dated plan both sides can test. Owner: Vendor delivery lead drafts; both sides' sponsors sign. When to use: During the cure period, in response to Template 3.

Cure Plan Terms

1. This Cure Plan responds to the Notice dated [DATE]. Completion of all
   exit criteria by [DATE] will constitute cure of the breaches
   identified in items [X] of the Notice.
2. Status will be reported [twice weekly] in writing using the table
   above. Any missed date will be reported within [1] business day with
   the reason and a revised date.
3. Customer dependencies are listed in the table. Delay in a dependency
   will extend the affected dates day for day, provided [VENDOR] gives
   written notice within [2] business days of the delay.
4. Agreement to this Cure Plan does not waive either party's rights,
   including [CUSTOMER]'s right to terminate if cure is not achieved and
   [VENDOR]'s position that [ITEMS] are not breaches.
5. [OPTIONAL: Commercial terms during cure, e.g., [VENDOR] will perform
   cure work at no additional charge; [CUSTOMER] will pay invoices
   [NUMBERS] on completion of WS-[X].]

[SIGNATURES]

Commentary. The cure plan will be the yardstick for any later termination. For the customer, objective exit criteria (test scripts passing in a witnessed cycle, written approval of a replacement, reconciled data counts) make failure provable. For the vendor, listing customer dependencies with named owners and a day-for-day extension clause protects against termination for delays the customer caused. Neither side should agree to dates it knows are unrealistic: a missed cure plan is powerful evidence of material breach, and a plan the customer refuses to support is powerful evidence of prevention. The non-waiver paragraph prevents either side from arguing that agreeing to the plan modified the contract. Where the contract is silent on materiality, courts weigh the likelihood of cure and the breaching party's good faith under Restatement (Second) of Contracts § 241; a credible, honestly reported cure plan is the vendor's best evidence on both.

Halden example. Quillstone's plan assigns a new lead architect from another region, adds two integration engineers, and sets exit criteria for each breach. Halden approves the architect in two days. By day 30, WS-2 is complete, WS-3 is complete, and WS-1 has 7 of 20 scripts still failing.

Template 6: Project record protocol and litigation hold notice

Purpose: Preserve the project record, including collaboration tools, ticketing systems, repositories, and devices, and document the steps taken. Owner: Counsel for each side, with IT administrators. When to use: As soon as litigation is reasonably anticipated, typically at or before the first notice of breach.

Part A: Litigation hold notice to custodians

PRIVILEGED AND CONFIDENTIAL: ATTORNEY-CLIENT COMMUNICATION

To: [CUSTODIAN LIST]
From: [COUNSEL NAME, TITLE]
Date: [DATE]
Re: Legal Hold: [PROJECT NAME] / [COUNTERPARTY]

[COMPANY] reasonably anticipates a dispute with [COUNTERPARTY] about the
[PROJECT]. You must preserve all documents and data relating to the
project, from [START DATE, e.g., first RFP contact] to the present and
going forward, until counsel releases this hold in writing.

This includes, wherever stored:
- Email, calendar entries, and attachments
- Slack, Microsoft Teams, and other chat messages (channels, direct
  messages, group messages), including on mobile devices
- Text messages and messaging apps (iMessage, WhatsApp, Signal, etc.)
  used for any project communication
- Jira/[TICKETING TOOL] tickets, comments, and attachments
- Confluence/SharePoint pages and their version history
- Code, configuration, and commit history in [REPOSITORY]
- Test plans, scripts, results, and defect logs
- Status reports, steering committee decks, minutes, risk registers,
  RAID logs, and project plans
- Contracts, SOWs, change requests, invoices, and timesheets
- Personal notes, notebooks, and recordings of project meetings

Do not delete, edit, "clean up," or move any of these items. Do not
change auto-delete settings back on. If you use disappearing-message
features for project communications, stop now and tell counsel.

Do not discuss the merits of the dispute in email or chat. Direct
questions to [COUNSEL CONTACT].

Please confirm receipt and compliance by [DATE] by replying to this
message.

Part B: Systems preservation protocol (for IT and counsel)

Commentary. The duty to preserve attaches when litigation is reasonably anticipated, and counsel must take affirmative steps to identify and preserve relevant information (Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003)). If ESI that should have been preserved is lost because a party failed to take reasonable steps, a court may order curative measures, and, on a finding of intent to deprive, may presume the information was unfavorable or enter default (Fed. R. Civ. P. 37(e)). The verification column matters: a hold that was issued but not implemented is little defense. Collect chat data in a format that preserves threads, timestamps, and edit history so that it can later be authenticated under Fed. R. Evid. 901. For broader preservation steps, see Litigation Hold and Evidence Preservation Checklist: A Practical Checklist; for collecting messaging data specifically, see Digital Message Evidence Toolkit: Collection Protocols, Authentication Declarations, and Rule 902 Certifications.

Template 7: Termination notice with transition demand

Purpose: Terminate for cause (or on another basis) in compliance with the MSA, invoke transition assistance, and demand deliverables, code, and data. Owner: Customer counsel. When to use: After the cure period expires without cure, and only once the exit is secured.

[CUSTOMER LETTERHEAD]

[DATE]

BY [METHOD REQUIRED BY MSA]

[VENDOR NAME], Attn: [NOTICE ADDRESSEE]; Copy: [COPY-TO]

Re: Notice of Termination of Statement of Work No. [X] for Cause;
    Demand for Transition Assistance

Dear [NAME]:

1. Termination. [CUSTOMER]'s Notice of Material Breach dated [DATE]
   (the "Notice") identified material breaches of the MSA and SOW
   No. [X]. The cure period under Section [X] expired on [DATE].
   [VENDOR] has not cured the breaches identified in items [X] of the
   Notice: [ONE-SENTENCE SUMMARY PER ITEM, TIED TO CURE PLAN EXIT
   CRITERIA]. Under Section [X] of the MSA, [CUSTOMER] terminates SOW
   No. [X] for cause, effective [DATE].

2. [Alternative basis, if permitted and advised: Without limiting the
   foregoing, and solely in the alternative if it is determined that
   termination for cause was not available, this notice also
   terminates SOW No. [X] for convenience under Section [X], effective
   [DATE]. CONSULT COUNSEL BEFORE USING.]

3. Surviving agreements. This notice does not terminate the MSA [or
   SOW Nos. [X]], which remain in effect.

4. Transition assistance. [CUSTOMER] invokes transition assistance
   under Section [X] for [PERIOD]. Please confirm within [3] business
   days your transition lead and a meeting to agree the transition plan.

5. Deliverables, code, and documentation. Under Sections [X] (Ownership)
   and [X] (Effect of Termination), deliver by [DATE]: (a) all source
   code, configurations, scripts, and build instructions for custom
   development, with full repository history; (b) all work in progress;
   (c) design, interface, and architecture documentation; (d) test
   scripts, results, and defect logs; (e) all credentials and
   administrative access for environments under [VENDOR]'s control.

6. Data. Export all [CUSTOMER] data from [VENDOR]-controlled
   environments in [FORMAT] by [DATE], and thereafter certify deletion
   under Section [X] after [CUSTOMER] confirms receipt.

7. Payments and holdback. [CUSTOMER] will pay [undisputed amounts /
   amounts due under Section [X]] and retains the holdback under
   Section [X] pending resolution.

8. Reservation of rights. [CUSTOMER] reserves all claims and remedies,
   including damages for breaches before termination and all claims
   relating to the inducement of the Agreement. [VENDOR]'s obligations
   under Sections [CONFIDENTIALITY, IP, TRANSITION, DATA, AUDIT] survive.

Sincerely,
[AUTHORIZED SIGNATORY]

Commentary. The termination should rely on the same breaches identified in the notice and measure failure against the cure plan's exit criteria. A termination for an immaterial breach is itself a repudiation, and courts apply the contract's materiality standard where one exists (State v. IBM). The alternative-basis paragraph is a judgment call: it can limit exposure if cause is not proven, but some courts and counterparties treat it as a concession, and convenience terminations often trigger fees. Paragraph 5 rests on the ownership clause. Contractor-written software usually is not a work made for hire under 17 U.S.C. § 101 and 17 U.S.C. § 201(b), so ownership depends on a signed written assignment under 17 U.S.C. § 204(a). Without one, the customer usually still holds an implied nonexclusive license to use and modify what it paid for (Asset Marketing Systems, Inc. v. Gagnon, 542 F.3d 748 (9th Cir. 2008)). If the vendor refuses contractual transition cooperation, emergency relief may be available under Fed. R. Civ. P. 65 or from an emergency arbitrator, depending on the dispute resolution clause; see Obtaining Emergency or Interim Relief in Arbitration: A Practical Guide.

Vendor note. A vendor receiving this notice should perform transition obligations even while disputing cause. Withholding code or data, or disabling hosted environments, without clear contractual authority can create claims beyond contract, including under 18 U.S.C. § 1030.

Halden example. On day 34, with WS-1 still failing 7 scripts, Halden terminates SOW 3 for cause, keeps the MSA and a support SOW in force, and invokes 90 days of transition assistance. SOW 3 contains a present assignment of "all Deliverables," with a license to Quillstone's preexisting integration accelerators.

Template 8: Tolling and standstill agreement

Purpose: Stop limitations clocks (including short contractual periods) while the parties negotiate, without either side filing. Owner: Counsel for both sides. When to use: When negotiations, transition, or mediation will extend past any limitations period or contractual claim deadline.

TOLLING AND STANDSTILL AGREEMENT

This Agreement is made [DATE] between [CUSTOMER] and [VENDOR].

1. Tolled Claims. All claims, counterclaims, and defenses arising out of
   or relating to the MSA dated [DATE], SOW No. [X], or the [PROJECT]
   (the "Claims"), whether in contract, tort, statute, or otherwise.

2. Tolling. Any statute of limitations, statute of repose, contractual
   limitations period (including Section [X] of the MSA), laches, or
   other time-based defense applicable to the Claims is tolled from
   [EFFECTIVE DATE] through the Termination Date. This Agreement does
   not revive any Claim already time-barred on the Effective Date.

3. Standstill. Neither party will commence arbitration or litigation on
   the Claims before the Termination Date, except to seek interim relief
   [under Section [X] / from an emergency arbitrator] where necessary to
   prevent irreparable harm.

4. Termination Date. The earlier of (a) [DATE], or (b) [30] days after
   either party gives written notice terminating this Agreement.

5. Dispute resolution steps. The parties agree that [executive
   escalation / mediation] under Section [X] [is satisfied / will occur
   during the standstill period].

6. No admission. This Agreement is not an admission by either party and
   is inadmissible except to enforce its terms.

7. Governing law and forum. Sections [X] and [X] of the MSA apply.

[SIGNATURES]

Commentary. Many technology contracts shorten the period to sue to one or two years, and Article 2 allows parties to reduce its four-year period to not less than one year (Cal. Com. Code § 2725). Repair efforts do not necessarily toll the clock; in Triangle Underwriters, Inc. v. Honeywell, Inc., 604 F.2d 737 (2d Cir. 1979), the vendor's continuing attempts to fix a computer system did not extend the four-year UCC period. Some states restrict tolling agreements entered before a claim accrues or require particular formalities; confirm the governing law. If the MSA requires arbitration, keep the standstill from becoming a waiver argument by limiting it to a defined period and expressly preserving arbitration rights; waiver of arbitration no longer requires prejudice (Morgan v. Sundance, Inc., 596 U.S. 411 (2022)).

Template 9: Damages model outline

Purpose: Organize every category of loss, test it against the limitation-of-liability clause, and identify the proof needed. Owner: Counsel, with an internal finance lead and later a damages expert. When to use: From the first month of the dispute; refine through expert reports.

Part A: Customer damages worksheet

Part B: Cap analysis

1. Cap formula (MSA Section [X]): [e.g., fees paid under the applicable
   SOW in the 12 months preceding the event giving rise to the claim].
2. Measurement date(s): [DATE OF EACH CLAIM EVENT].
3. Cap amount: [$].
4. Per-claim or aggregate: [ ].
5. Does the cap apply to the vendor's fee claims? [Y/N; cite].
6. Exclusion wording: [QUOTE]. Does it list "lost profits," "lost
   savings," "cost of cover," "re-procurement"? [ ].
7. Carve-outs: [QUOTE]. Defined terms? [e.g., is "willful misconduct"
   defined?].
8. Customer recovery scenarios:
   (a) Contract only, cap enforced: [$]
   (b) Contract, A2 treated as direct and A5 excluded: [$]
   (c) Fraud proven (cap and exclusion inapplicable): [$]
9. Vendor counterclaim: [$], less offsets [$].
10. Net range: [$] to [$].

Part C: Vendor worksheet

Commentary.

• Direct versus consequential. Courts look at whether the loss flows directly from the breach of the particular contract. Lost profits can be general damages where they are the natural and probable result of the breach (Tractebel Energy Marketing, Inc. v. AEP Power Marketing, Inc., 487 F.3d 89 (2d Cir. 2007); Biotronik A.G. v. Conor Medsystems Ireland, Ltd., 22 N.Y.3d 799 (2014); Penncro Associates, Inc. v. Sprint Spectrum, L.P., 499 F.3d 1151 (10th Cir. 2007)). The same reasoning supports treating A2 (cost to complete the promised scope) as direct. Under Article 2, cover is a buyer's remedy in its own right (Cal. Com. Code § 2712), and incidental and consequential damages are separately defined (Cal. Com. Code § 2715). Courts often decide these characterizations at summary judgment rather than on the pleadings; the court in Hertz Corp. v. Accenture LLP, No. 19-cv-3508 (S.D.N.Y. Oct. 25, 2019), declined to resolve whether the consulting agreement limited the customer's damages at the motion to dismiss stage.
• Carve-outs. Under New York law, a "willful acts" exception does not reach a vendor's intentional nonperformance motivated by economic self-interest (Metropolitan Life Insurance Co. v. Noble Lowndes International, Inc., 84 N.Y.2d 430 (1994)), and exculpatory clauses are unenforceable against gross negligence or conduct smacking of intentional wrongdoing (Kalisch-Jarcho, Inc. v. City of New York, 58 N.Y.2d 377 (1983)). Scenario 8(c) should be modeled only if the documents support a fraud claim that can survive the economic loss rule or duplication doctrine and any non-reliance clause (Bridgestone/Firestone, Inc. v. Recovery Credit Services, Inc., 98 F.3d 13 (2d Cir. 1996); Danann Realty Corp. v. Harris, 5 N.Y.2d 317 (1959)).
• Certainty. Lost profits (A5) must be proven with reasonable certainty and, as consequential damages, must have been within the parties' contemplation at contracting (Kenford Co. v. County of Erie, 67 N.Y.2d 257 (1986)). Once the fact of damage is established, the wrongdoer bears the risk of uncertainty in amount (Story Parchment Co. v. Paterson Parchment Paper Co., 282 U.S. 555 (1931)).
• Expert admissibility. The final model will be presented by an expert whose methods must satisfy Fed. R. Evid. 702 and Daubert v. Merrell Dow Pharmaceuticals, Inc., 509 U.S. 579 (1993). The most common attack is that A2 prices a larger scope than the original contract, so map each line of the replacement quote to the original SOW. See Proving Damages in Civil Litigation: Certainty, Causation, and the Numbers That Survive and Damages Proof and Expert Model Checklist: A Practical Checklist.

Halden example. Halden's model: A1 $1.1 million (milestones 4 and 5, never accepted); A2 $1.6 million (replacement integrator, original scope only, after removing $350,000 for a returns-portal feature Halden added); A3 ($275,000 holdback); A4 $420,000; A5 $1.3 million in lost margin and customer credits; A6 $140,000. The cap (SOW 3 fees paid in the prior twelve months) is $2.2 million. Contract-only recovery is capped near $2.2 million; A5 is likely excluded. Quillstone's counterclaim: $310,000 for disputed change requests, including the buy-online-pick-up-in-store build.

Template 10: Settlement and transition agreement (key terms)

Purpose: Resolve the dispute and structure the exit so that the customer receives what it needs and releases become effective only when it does. Owner: Counsel for both sides. When to use: At settlement, whether during cure, at termination, or after discovery.

SETTLEMENT AND TRANSITION AGREEMENT: KEY TERMS

Parties: [CUSTOMER]; [VENDOR]; [OPTIONAL: VENDOR PARENT AS GUARANTOR].

1. Recitals. Reference the MSA, SOW No. [X], the Notice dated [DATE],
   the termination dated [DATE], and the [arbitration/action] [CAPTION,
   NUMBER], if filed.

2. Payment. [VENDOR] pays [CUSTOMER] [$AMOUNT] by [DATE] by wire.
   [OR: credit of [$] against future services under SOW No. [X].]

3. Invoices. [VENDOR] withdraws invoices [NUMBERS] totaling [$]. [CUSTOMER]
   pays invoices [NUMBERS] totaling [$] for [UNDISPUTED WORK] by [DATE].
   The holdback under Section [X] is [released to VENDOR / retained by
   CUSTOMER].

4. Transition deliverables. By [DATE], [VENDOR] delivers: [LIST, e.g.,
   complete source code repository with history; build and deployment
   instructions; interface specifications; data migration scripts; test
   assets; documentation; credentials]. [VENDOR] provides [NUMBER] hours
   of knowledge transfer to [CUSTOMER] and [REPLACEMENT VENDOR] by
   [DATE] at [no charge / $RATE].

5. Transition acceptance. [CUSTOMER] will confirm receipt and
   completeness of each deliverable within [10] business days, or
   identify deficiencies, which [VENDOR] will correct within [10]
   business days.

6. Intellectual property. [VENDOR] confirms and, to the extent not
   already assigned, hereby assigns to [CUSTOMER] all right, title, and
   interest in the Deliverables listed in Schedule [X]. [VENDOR] grants
   [CUSTOMER] and its contractors a perpetual, irrevocable, royalty-free,
   nonexclusive license to use, copy, modify, and maintain [VENDOR]'s
   preexisting materials embedded in the Deliverables, solely for
   [CUSTOMER]'s internal business purposes.

7. Data. [VENDOR] returns all [CUSTOMER] data in [FORMAT] by [DATE] and,
   after [CUSTOMER]'s written confirmation of receipt, deletes it and
   certifies deletion within [30] days, except as required by law.

8. Continuing services (optional). [VENDOR] continues [SUPPORT SOW] for
   [PERIOD] at [RATE/DISCOUNT].

9. Releases. Effective on the Release Date, mutual releases of all
   claims arising from the MSA, SOW No. [X], and the [PROJECT], except:
   (a) obligations under this Agreement; (b) confidentiality and data
   protection obligations; (c) IP indemnity obligations for third-party
   claims; (d) [OTHER CARVE-OUTS]. "Release Date" means the later of
   payment under Section 2 and [CUSTOMER]'s confirmation of completion of
   transition deliverables under Section 5.

10. Third parties. The releases do not release [SOFTWARE PUBLISHER] or
    any other third party [unless expressly listed].

11. Dismissal. Within [5] business days after the Release Date, the
    parties file [a stipulation of dismissal with prejudice / a joint
    notice of withdrawal of the arbitration].

12. No admission; confidentiality; non-disparagement; agreed statement.
    [TERMS.]

13. Insurance. [VENDOR] represents that it has obtained any consent
    required from its insurers.

14. Governing law; dispute resolution for this Agreement. [TERMS.]

[SIGNATURES]

Commentary. The critical design choice is paragraph 9's Release Date. Releasing claims at signing, before the code, documentation, and data are delivered, gives away the customer's leverage. Paragraph 6 fixes ownership problems that may exist in the original contract; a confirmatory assignment must be in writing and signed by the vendor to satisfy 17 U.S.C. § 204(a). Paragraph 10 matters where the customer has separate claims against the software publisher; a broad definition of released "affiliates, partners, and subcontractors" can release them unintentionally. If the vendor or publisher may become insolvent, the license in paragraph 6 should be drafted as a license of "intellectual property" so the customer can rely on 11 U.S.C. § 365(n), and Mission Product Holdings, Inc. v. Tempnology, LLC, 587 U.S. 370 (2019), confirms that a debtor's rejection of a license operates as a breach rather than a rescission. Settlement negotiations leading to the agreement are generally inadmissible to prove liability or amount under Fed. R. Evid. 408. If an arbitration is pending, the parties may also ask the tribunal to record the settlement as a consent award, which can be confirmed under the Federal Arbitration Act; see Confirming and Vacating Arbitration Awards: The Narrow Door of FAA Review. For general settlement drafting, see Drafting a Settlement Agreement and Release: A Practical Guide and Settlement Toolkit: Term Sheets, Releases, Offers of Judgment, and Enforcement.

Halden example. At mediation, Halden and Quillstone settle: Quillstone pays $900,000, withdraws $310,000 in disputed change-request invoices, and delivers the full repository and documentation with 120 hours of knowledge transfer to Halden's new integrator; Halden releases the holdback; Quillstone confirms the assignment of all SOW 3 deliverables and licenses its embedded accelerators perpetually. Releases take effect only after Halden confirms the transition deliverables are complete. Halden's separate claims against the OMS publisher are expressly preserved.

Drafting pitfalls across the templates

1. Inconsistent breach lists. The notice (Template 3), the cure plan (Template 5), and the termination (Template 7) must address the same breaches.
2. Missing notice formalities. Every formal notice must follow the MSA's method and addressee requirements.
3. Admissions in cure documents. Vendors should avoid unqualified acknowledgments; customers should avoid conceding that the vendor's dependencies were unmet.
4. No reservation of rights. Every interim agreement (go-live, cure plan, change reconciliation, standstill) needs one.
5. Holds without verification. A hold notice that no one implemented is weak protection under Rule 37(e).
6. Damages that buy upgrades. Map every line of the replacement quote to the original scope.
7. Releases before delivery. Tie releases to confirmed transition.
8. Overlooking short contractual limitations. Use Template 8 early.
9. Arbitration waiver. Do not litigate the merits in court when the MSA requires arbitration, and keep standstills from looking like a choice of court.
10. Ownership assumptions. Do not assume "work made for hire" language transferred custom code; get a written assignment.

For forum issues if the dispute does proceed, see Selecting and Drafting an Arbitration Clause and the enforcement mechanics in 9 U.S.C. § 4; for valuing a settlement against the cap, see Settlement Negotiation Toolkit: Case Valuation Worksheets, Concession Plans, and Offer Letters.

This document is general information, not legal advice for any particular situation; the law changes, and the facts matter.

Related Documents

Related Articles

• Failed Software Implementations: Contract, Fraud, and Warranty Claims When an IT Project Goes Wrong: the substantive law behind every template.
• Negotiating a Master Services Agreement and Statement of Work: drafting the contract terms these templates enforce.
• Indemnification and Limitation of Liability: The Risk Allocation Engine of Every Contract: the cap and carve-out analysis in Template 9.
• Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case: the law behind Template 6.

Related Guides

• Pursuing or Defending a Failed Technology Project Claim: A Practical Guide: when and how to use each template in sequence.
• Drafting a Settlement Agreement and Release: A Practical Guide: general settlement drafting for Template 10.
• Obtaining Emergency or Interim Relief in Arbitration: A Practical Guide: forcing transition cooperation while an arbitration is pending.

Related Checklists

• Troubled Technology Project Checklist: A Practical Checklist: the phase-by-phase checklist these templates support.
• Litigation Hold and Evidence Preservation Checklist: A Practical Checklist: preservation steps beyond Template 6.
• Damages Proof and Expert Model Checklist: A Practical Checklist: testing the Template 9 model.
• Settlement Agreement Checklist: A Practical Checklist: reviewing Template 10 before signature.

Related Toolkits

• Contract Construction Toolkit: Canons, Clauses, and Dispute Positioning: interpretive arguments over SOW and MSA language.
• Digital Message Evidence Toolkit: Collection Protocols, Authentication Declarations, and Rule 902 Certifications: collecting and authenticating chat evidence.
• Settlement Toolkit: Term Sheets, Releases, Offers of Judgment, and Enforcement: term sheets and enforcement of settlements.
• Clean Room Toolkit: Protocols, Team Certifications, and Specification Records: protecting a replacement build from the departing vendor's proprietary material.