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 Deployment and Version Control.

1. Version control

  1. We normally use version control (for example Git) to manage source code and configuration for Websites and Applications.
  2. We may:
    • use branching strategies suited to the size and complexity of the Project;
    • require that all changes go through version control; and
    • limit direct changes on Live Environments to emergency fixes where strictly necessary.
  3. Where you or third parties also contribute code, we may agree standards and workflows to keep the repository stable.

2. Environments

  1. Where your hosting or platform supports it, we may work with separate environments, such as:
    • Development;
    • Staging or UAT; and
    • Live (Production).
  2. We recommend that:
    • new features and changes are deployed to Staging/UAT for testing first; and
    • you carry out UAT in Staging before you approve deployment to Live.
  3. You are responsible for provisioning environments where you control the hosting or platform services.

3. Deployment process

  1. Where we handle deployments, we will:
    • follow a repeatable process suited to the technology stack;
    • aim to minimise disruption to users; and
    • where practical, deploy at agreed times.
  2. We may use:
    • automated deployment tools or scripts; and/or
    • manual steps where automation is not practical.
  3. Emergency fixes may occasionally require direct changes on Live Environments. Where this happens, we will aim to reconcile those changes back into version control promptly.

4. Rollbacks

  1. Where feasible, we will plan for rollbacks so that major issues introduced by a release can be reversed.
  2. Whether we can roll back depends on:
    • how the Application and data are structured;
    • the availability of backups or prior versions; and
    • the constraints of your hosting or platform.
  3. We will discuss rollback options with you as part of the deployment approach for significant changes.

5. Access and credentials

  1. You must provide and manage the access credentials needed for deployments to environments you control.
  2. We recommend:
    • using individual, auditable accounts where possible;
    • granting least-privilege access suited to the tasks; and
    • revoking access promptly when it is no longer needed.
  3. We will handle the credentials you provide with care and will not share them beyond the team members who need them to do the agreed work.