Last updated: 23 July 2026. View change log.

This Schedule forms part of the Web Development Master Services Agreement and describes the scope, responsibilities and limitations that apply to Web Development Projects.

Your Order or Statement of Work will describe the scope, Deliverables, assumptions and pricing for each Project.

1. Project stages

  1. Unless we agree otherwise, Projects follow these stages:
    • discovery and requirements;
    • design and prototyping;
    • build and configuration;
    • testing and user acceptance (UAT); and
    • launch and post-launch support period.
  2. Smaller Projects may combine or simplify these stages.

2. Discovery and requirements

  1. During discovery we will:
    • clarify your objectives and key outcomes;
    • capture high-level requirements and priorities;
    • identify any technical constraints or dependencies; and
    • agree the scope and approach for the Project.
  2. We may produce discovery outputs such as requirements summaries, user journeys or simple wireframes, as described in your Order.

3. Design and prototyping

  1. Where design work is included, we will:
    • create layouts, mock-ups or prototypes for key pages or screens; and
    • refine the designs in response to your feedback, within the reasonable number of revision rounds described in your Order.
  2. You will:
    • review designs promptly and give clear feedback; and
    • confirm when designs are approved (“design sign-off”).
  3. Significant changes after design sign-off (for example a major rebrand or change of direction) may need a Change Request.

4. Build and configuration

  1. We will build the Website or Application in line with the agreed requirements and approved designs.
  2. We may use:
    • industry-standard frameworks and content management systems; and/or
    • custom code where required.
  3. We will aim to reuse sensible patterns and components where this helps stability and supportability.
  4. We will keep you updated on progress through agreed channels.

5. Content and copy

  1. Unless your Order explicitly includes it, you are responsible for providing final content and copy (text, images, video, downloads and other assets).
  2. We may:
    • add your content to the Website or Application; and/or
    • advise on content structure and layout.
  3. Where we provide copywriting or content creation, we will describe and price this separately.

6. Testing and acceptance

  1. We will carry out internal testing before we give you a version for your UAT.
  2. UAT is your opportunity to confirm that the Deliverables meet the Acceptance Criteria set out in Annex A or your Order.
  3. We handle acceptance, defects and “go-live” in line with Annex A.

7. Launch and post-launch support period

  1. We will agree a launch plan with you, which may include:
    • deployment to the Live Environment;
    • switching over DNS or other integration points (where we are responsible for doing so); and
    • post-launch checks.
  2. After launch, there may be a defined post-launch support period (for example 30 days) during which we:
    • correct defects that stop the Deliverables meeting the agreed Acceptance Criteria; and
    • give reasonable help to stabilise the Website or Application.
  3. Changes after launch that are not defect fixes (for example new features or design changes) are treated as Change Requests, or may be handled under a retainer if you have one.

8. Source code and handover

  1. Ownership of code and Deliverables is set out in Annex B.
  2. Where agreed, we may:
    • give you a copy of the source code and deployment instructions; and/or
    • provide handover documentation or walkthroughs.
  3. Substantial training, documentation or handover beyond what your Order specifies may be provided as additional work.