Last updated: 23 July 2026. View change log.

This Annex forms part of the Web Development Master Services Agreement and describes the scope, responsibilities and limitations that apply to Acceptance and Testing Criteria.

1. Acceptance Criteria

  1. Acceptance Criteria may be:
    • described in your Order or Statement of Work; and/or
    • agreed during discovery and design.
  2. They typically cover:
    • key features and user journeys;
    • design and brand alignment;
    • basic performance and responsiveness; and
    • correct behaviour under normal usage.

2. Testing by us

  1. Before we give you a version for your UAT, we will carry out internal testing suited to the Project, which may include:
    • unit or component testing;
    • integration testing; and
    • basic cross-browser or cross-device checks.
  2. Our internal testing is meant to catch obvious issues. It does not replace your own UAT.

3. User acceptance testing (UAT)

  1. We will give you access to a test or staging version of the Deliverables for UAT.
  2. You are responsible for:
    • carrying out UAT within a reasonable time period; and
    • checking that the Deliverables meet the agreed Acceptance Criteria.
  3. You should log issues in the agreed format (for example through our ticketing system), giving clear steps to reproduce them where possible.

4. Defect categories

  1. For acceptance, we usually classify issues as:
    • Severity 1 – Critical: a defect that prevents core functionality from working or makes the system unusable, with no reasonable workaround.
    • Severity 2 – Major: a defect that affects important functionality or a large group of users but has a workaround.
    • Severity 3 – Minor: a defect that does not significantly affect core functionality (for example small layout issues or minor content errors).
  2. We will aim to fix Severity 1 and Severity 2 defects before acceptance wherever practical.
  3. Severity 3 issues may be:
    • fixed before acceptance where time allows; or
    • agreed as post-launch improvements or handled under a retainer.

5. Acceptance and “go-live”

  1. Deliverables are considered accepted when:
    • you confirm in writing (for example by email) that you accept them; or
    • they have been deployed to the Live Environment at your request; or
    • a defined UAT period has ended without you raising any material Severity 1 or 2 defect, where that UAT period starts only once we have notified you that the Deliverables are ready for you to test.
  2. Where material Severity 1 or 2 defects are found during UAT:
    • we will work with you to correct them; and
    • acceptance happens once those defects are resolved to a reasonable standard.

6. Warranty period

  1. There may be a defined warranty or post-launch support period (for example 30 days) during which we will correct defects that:
    • mean the Deliverables do not meet the agreed Acceptance Criteria; and
    • are clearly attributable to our work, and not to later changes or third-party actions.
  2. Changes in requirements, new features or issues caused by third parties are not treated as defects under the warranty.