* Electronic copy only (pdf)

Problems surrounding the ideas of delivery and acceptance in relation to complete systems and to software: need for clear definitions and proper practice.

Objectives:

• To enable customers for bespoke and customised software to avoid having errorprone or non-performing software ostensibly delivered, and being drawn into a lengthy so-called acceptance procedure during which errors are identified and rectification is attempted
• To provide contractual means of applying objective criteria to software quality before delivery and acceptance processes start, and a means of identifying breaches of contract

*This Legal Guidance Note is only available as a pdf, which will be sent as an email attachment.