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 Application Development.

1. Application scope

  1. Your Order or Statement of Work will define:
    • the purpose and main features of the Application;
    • any key integrations (for example payment gateways, CRM, ERP or identity providers);
    • the target user groups and usage patterns; and
    • any technology constraints (for example specific frameworks or hosting platforms).
  2. We will design and build the Application within this agreed scope.

2. Architecture and technologies

  1. We may propose or choose technologies, frameworks and libraries suited to the Application, taking into account:
    • your requirements and constraints;
    • long-term maintainability; and
    • security and performance considerations.
  2. Where you require specific technologies, we will highlight any risk or limitations this may create.

3. Integrations and dependencies

  1. Where the Application integrates with Third-Party Services, we will:
    • build the integrations as described in your Order; and
    • work with sandbox or test environments where available.
  2. You are responsible for:
    • obtaining and maintaining licences and subscriptions for Third-Party Services;
    • providing access credentials and configuration details; and
    • any changes or fees imposed by third parties.
  3. If an external API or service changes in a way that breaks or degrades functionality, we may treat the remediation as additional work unless we agree otherwise.

4. Performance and scalability

  1. We will take reasonable steps, within scope and budget, to design the Application so it performs acceptably for the expected number of users and transactions agreed with you.
  2. Formal performance testing, load testing or capacity modelling is not included unless your Order explicitly states otherwise.
  3. If usage grows beyond the initial assumptions, we may recommend architectural changes or performance improvements, which may be delivered as additional work.

5. Logging and diagnostics

  1. Where appropriate, we may build in logging and diagnostic features to support troubleshooting and support.
  2. Advanced logging, monitoring or application performance management tools may need separate licensing and setup.

6. Testing and acceptance

  1. We will test the Application in line with Annex A (Acceptance and Testing Criteria) and any specific test plan agreed in your Order.
  2. For complex Applications, we may agree structured test cases or scripts to run during UAT.