IT warranty: identifying and proving a defect

On this page

Published by horak. Attorneys at law / Patent attorneys

Archive · First published 2018-08-23. Editorial revision: 12 November 2026. The original date is retained; the text below distinguishes historical context from present-day application.

A performance complaint becomes a legal claim only after the relevant promise and remedy have been identified. Different contractual models can lead to different rules on acceptance, cure and payment.

How to use this archived article

Technical evidence should show the failure, the relevant environment and its operational effect. A record of tickets, versions and attempted fixes can be important when causation or responsibility is disputed.

Questions for a current matter

Which contractual version and legal regime apply? What happened, when did the parties become aware of it, and which documents preserve the relevant facts? Identify the desired outcome and any procedural deadline before choosing a response.

Four practical examples

Illustrative scenarios, not reports of client mandates. The appropriate response depends on the facts and applicable law.

Missing integration

Delivered software cannot connect to the promised system. We compare specifications and test results.

Slow performance

A system meets functional requirements but fails under load. We review capacity commitments and evidence.

Repeated failed repairs

Several fixes do not resolve a critical defect. We assess whether further cure must be allowed.

Lost production revenue

An outage causes business interruption. We analyse recoverable loss, causation and contractual limits.

Current guidance

Software defects, warranty & damages