This Schedule forms part of the Web Development Master Services Agreement and describes the scope, responsibilities and limitations relating 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 agreed 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 designs in response to your feedback within a reasonable number of revision rounds described in your Order.
  2. You will:
    • review designs promptly and provide 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 require 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 benefits stability and supportability.
  4. We will keep you updated on progress through agreed channels.

5. Content and copy

  1. Unless explicitly included in your Order, 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
    • provide guidance on content structure and layout.
  3. Where we provide copywriting or content creation, this will be described and priced separately.

6. Testing and acceptance

  1. We will carry out internal testing before providing 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. Acceptance, defects and “go-live” are handled 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 prevent the Deliverables meeting the agreed Acceptance Criteria; and
    • provide reasonable assistance to stabilise the Website or Application.
  3. Changes after launch that are not defect fixes (for example new features or design changes) will be 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:
    • provide a copy of the source code and deployment instructions; and/or
    • handover documentation or walkthroughs.
  3. Substantial training, documentation or handover beyond what is specified in your Order may be provided as additional work.