IT Contract Disputes: Failed Technology Projects
IT contract disputes follow a familiar pattern: a delayed or failed implementation, competing narratives about scope and responsibility, and a liability cap that limits recovery. Canadian courts resolve them through contract interpretation, Tercon's test for exclusion clauses, good-faith principles and independent expert evidence on delay and defects.

Key takeaways
- Most IT contract disputes are really disputes about scope and change control.
- Objective acceptance criteria and defect logs are often the decisive evidence.
- Tercon (2010 SCC 4) sets the test for enforcing limitation and exclusion clauses.
- Wrongful termination for cause can turn the customer into the party in breach.
- Duties of honest performance and good-faith discretion apply to project conduct.
- Independent experts must meet the White Burgess standard of impartiality.
Why IT contract disputes arise
IT contract disputes usually begin with a technology project that runs late, over budget or never delivers what the business expected: an ERP implementation that cannot process payroll, a core banking migration that stalls, a SaaS platform that fails acceptance, or a systems integrator that blames the customer's data. By the time lawyers are involved, both sides typically have a narrative. The customer says the vendor overpromised and underdelivered; the vendor says the customer kept changing requirements, failed to provide decisions and data on time, and refused to accept working software. The contract, the project record and expert evidence on delay and defects decide who is right.

This insight explains the recurring legal issues in IT contract disputes in Canada: scope and change control, acceptance testing, limitation of liability clauses, termination for convenience or cause, escalation and dispute resolution clauses, the duty of good faith and expert evidence. It is general information, not legal advice; technology contracting is covered on our technology transactions and outsourcing page.
Scope, requirements and change orders
Most IT contract disputes are scope disputes. The statement of work, functional specifications, assumptions and dependencies define what the vendor promised. Vague descriptions such as "implement the standard solution configured to the customer's business processes" invite conflict, because the customer expects its processes to be supported while the vendor expects the customer to adapt to the product.
Change control provisions are therefore critical. A well-run project documents every change request, its effect on price and schedule, and its approval. In practice, many changes happen informally through workshops and emails. When the dispute arrives, the vendor claims additional compensation for out-of-scope work, and the customer argues the work was always included or was needed to fix defects.
Courts interpret these contracts using the modern approach from Sattva Capital Corp. v. Creston Moly Corp., 2014 SCC 53: the words read in light of the surrounding circumstances known to both parties at the time of contracting, without allowing those circumstances to overwhelm the text. Pre-contract proposals and requirements documents may form part of that context or, if incorporated, of the contract itself.
| Issue | Customer's typical position | Vendor's typical position | Key evidence |
|---|---|---|---|
| Scope | Functionality was included in the SOW or proposal | Requirement was new or customer-specific | SOW, requirements traceability, proposal, workshop records |
| Delay | Vendor resourcing and defects caused delay | Customer decisions, data and dependencies were late | Project plans, status reports, RAID logs, critical path analysis |
| Acceptance | System failed acceptance criteria | Criteria were met or customer refused acceptance unreasonably | Test scripts, defect logs, severity classifications |
| Liability cap | Cap does not apply (e.g. wilful default, repudiation) | Cap and exclusions apply as written | Contract wording, conduct evidence |
Acceptance testing
Acceptance provisions decide when deliverables are complete and payment milestones are earned. Common elements include defined acceptance criteria, test environments, severity levels for defects, timelines for testing and re-testing, and deemed acceptance if the customer does not reject within a set period or puts the system into production use. Disputes arise when criteria are incomplete or subjective, when the customer goes live with known defects for business reasons, or when severity classifications are contested.
Customers should be cautious about deemed acceptance through production use, and vendors should ensure the criteria are objective and tied to the agreed specifications rather than to the customer's evolving expectations. Detailed defect logs with timestamps and severity are often the most important evidence in IT contract disputes.
Limitation of liability caps and exclusions
Technology contracts almost always cap the vendor's liability, often at fees paid or payable over a period, and exclude indirect, consequential and lost-profit damages. Customers seeking to recover the cost of a failed program, replacement system and business disruption must overcome these clauses. In Tercon Contractors Ltd. v. British Columbia (Transportation and Highways), 2010 SCC 4, the Supreme Court set out a three-step approach to exclusion clauses: (1) does the clause, properly interpreted, apply to the circumstances; (2) if so, was it unconscionable at the time of contracting; and (3) if not, should the court nevertheless decline to enforce it because of an overriding public policy that outweighs the strong public interest in enforcing contracts.
Commercial parties will rarely succeed at the second and third steps; most disputes are won or lost on interpretation.
Interpretation questions include whether the cap applies per claim or in aggregate, whether it covers refunds of fees as well as damages, what counts as "direct" versus "consequential" loss (costs of re-procurement are often argued to be direct), and whether carve-outs for wilful misconduct, gross negligence, data breach, confidentiality or IP indemnities apply. Our insight on limitation of liability clauses covers drafting in more detail.
When a project starts to fail, read the liability cap and carve-outs before deciding on strategy. If damages above the cap are likely, the dispute may turn on whether the vendor's conduct falls within a carve-out, so the project record on that conduct should be preserved and developed carefully.
Termination for convenience and for cause
Many customers, especially public bodies, reserve a right to terminate for convenience on notice, paying for work done and sometimes wind-down costs. This can be the cleanest exit from a failing project, but it usually gives up claims against the vendor for poor performance and may require payment of amounts that would not be owed on termination for cause.
Termination for cause requires a material breach, often after notice and a cure period. A customer that terminates without satisfying the contractual conditions risks being found to have repudiated the contract itself, exposing it to the vendor's lost-profit claim. Before terminating, the customer should document the breaches, give compliant notices, allow the cure period to run and confirm that its own obligations are satisfied. Transition assistance, data return and escrow release provisions should be activated at the same time to protect business continuity.
Data migration and third-party components
Many IT contract disputes involve responsibilities that sit between the parties. Data migration is a frequent flashpoint: the customer is usually responsible for the quality of its legacy data, while the vendor is responsible for migration tools and processes, and failures often reflect both. Projects also depend on third-party software, cloud platforms, integration partners and the customer's other vendors. Contracts should allocate responsibility for these dependencies and specify what happens when a third-party product changes or fails. In disputes, the party that controlled the dependency, and whether it gave timely notice of problems, often determines who bears the cost.
SaaS and cloud contract specifics
Software-as-a-service arrangements shift the dispute landscape. Instead of a one-time implementation, the customer depends on ongoing service levels, availability, security and support. Disputes centre on service-level credits (often stated to be the sole remedy), the vendor's right to change features unilaterally, data portability on exit and responsibility for security incidents. Customers should check whether service credits exclude damages claims, whether chronic service-level failures give a termination right, and whether exit assistance and data export in usable formats are guaranteed. Vendors typically rely on standard-form online terms, which courts will generally enforce between businesses if they were properly incorporated into the contract.
Notice requirements and limitation periods
IT contracts often require notice of claims within short periods, and some purport to shorten limitation periods. In Ontario, the basic two-year limitation period under the Limitations Act, 2002 can be varied by business agreements, so contractual time bars should be reviewed early. Internal escalation meetings do not stop the clock. Ontario's Act suspends the limitation period while the parties pursue an agreed process in which an independent third party resolves the claim or assists them, but its conditions are technical, so a written standstill or tolling agreement is the safer course while negotiations continue.
Good faith, escalation and dispute resolution clauses
Canadian contract law imposes a duty of honest performance (Bhasin v. Hrynew, 2014 SCC 71; C.M. Callow Inc. v. Zollinger, 2020 SCC 45) and requires that contractual discretion be exercised in good faith, consistently with the purposes for which it was granted (Wastech Services Ltd. v. Greater Vancouver Sewerage and Drainage District, 2021 SCC 7). In IT contract disputes, these principles can apply to misleading status reports, concealment of known defects, or discretionary decisions on acceptance and change approvals. See our insights on Bhasin v. Hrynew and Wastech.
Most IT contracts contain tiered dispute resolution: project-level escalation, executive meetings, mediation, and then arbitration or litigation. Courts generally enforce these steps, and failure to follow them can delay proceedings. Expert determination is sometimes used for technical questions such as whether a deliverable met specifications. Choosing arbitration can protect confidentiality and allow a tribunal with technical expertise, while court litigation may be better where urgent injunctive relief or third-party discovery is needed.
Expert evidence on delay and defects
Experts are central to IT contract disputes. Delay experts reconstruct the planned and actual schedules, identify the critical path and attribute delay to particular events. Software quality experts review code, configuration, test results and defect data to assess whether the system was fit for purpose and how much remediation would cost. Quantum experts assess wasted expenditure, replacement costs and lost benefits.
Under White Burgess Langille Inman v. Abbott and Haliburton Co., 2015 SCC 23, experts owe a duty to the court to be fair, objective and non-partisan, and evidence from experts who cannot meet that duty may be excluded or given little weight. Retaining independent experts early, preserving project repositories, ticketing systems and environment snapshots, and avoiding experts who were involved in the project itself all strengthen the evidentiary record.
Preventing IT contract disputes
- Invest in precise requirements, assumptions and dependencies before signing.
- Run disciplined change control with documented approvals.
- Use objective acceptance criteria and clear defect severity definitions.
- Align payment milestones with accepted deliverables rather than effort.
- Negotiate liability caps and carve-outs that reflect the real risk of program failure.
- Hold regular steering committee meetings with minutes that record decisions and disagreements.
- Build step-in, transition and data-return rights into the contract, and test them before they are needed.
AI-enabled systems add further issues around model performance, data rights and changing outputs, which contracts should address expressly.
How TRW & Co helps
We advise customers and vendors on Canadian IT contract disputes, from early warning signs through settlement, arbitration or litigation. Our work includes reviewing contracts and project records, assessing scope, acceptance and delay positions, analyzing liability caps and termination rights, preparing notices and cure letters, coordinating independent technical and delay experts, and negotiating transition arrangements that protect operations. We also help organizations draft technology agreements that reduce the risk of disputes. Where court proceedings require counsel licensed in a province, we work with locally licensed litigation counsel. See our commercial litigation page or contact us.
Frequently asked questions
Who is usually responsible when an IT project fails?
It depends on the contract and the project record. Courts examine the scope documents, change requests, dependencies the customer had to meet, acceptance results and status reports. Responsibility is often shared, and expert analysis of the critical path and defects is used to attribute delay and cost.
Can a customer recover more than the liability cap?
Only if the cap does not apply on its proper interpretation, or a carve-out applies, such as for wilful misconduct or certain indemnities. Under Tercon, courts will rarely refuse to enforce a clear cap between commercial parties on grounds of unconscionability or public policy.
Should we terminate for cause or for convenience?
Termination for convenience is cleaner but usually waives performance claims and may require payments to the vendor. Termination for cause preserves claims but must follow the contract's notice and cure requirements; getting it wrong can make the customer liable for repudiation.
Does good faith apply to technology contracts?
Yes. Parties must perform honestly and exercise contractual discretion, such as approving changes or accepting deliverables, consistently with the purposes for which it was granted. Misleading status reports or concealing known defects can breach these duties.
What evidence matters most in IT contract disputes?
Contract documents, statements of work, change requests, steering committee minutes, project plans, defect logs, test results and code repositories. Preserve them early and retain independent experts on delay, quality and quantum.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


