This schedule (S3) applies to projects we carry out for you under a Statement of Work, such as SharePoint intranets, Teams roll-outs, migrations, Dynamics 365 and Business Central implementations, Power Platform solutions and Microsoft Fabric and Azure work. It forms part of your Contract with our Customer Agreement.
Key points
- Each project is defined by a signed Statement of Work, which sets out scope, deliverables, milestones and price.
- Changes to scope go through written change control.
- Deliverables are accepted after 10 Business Days, or on live use.
- We fix defects reported within 30 days of acceptance at no extra cost.
- For migrations, you are responsible for the quality of your source data and for deciding what moves.
1. Statements of Work
1.1 We carry out projects under a Statement of Work signed by both parties. It sets out the scope, Deliverables, acceptance criteria, milestones, Charges, assumptions and your responsibilities.
1.2 Fixed-scope projects with published prices on our website are carried out on the scope published at the date of your Order, unless your Order says otherwise.
2. Pricing
2.1 A Statement of Work is priced either:
- on a fixed price basis, covering the agreed scope only or
- on a time and materials basis, at the day rates in the Statement of Work.
2.2 For time and materials work, a day means 7.5 working hours on a Business Day, unless the Statement of Work says otherwise. We record time and report it with each invoice. Any cap in the Statement of Work is a limit on what we charge without your written approval, not a fixed price.
2.3 Work you ask us to carry out outside Business Days or outside the working hours stated in the Statement of Work is charged at the rates in the Statement of Work.
3. How we deliver
3.1 We name a lead for each project, who is your main point of contact. We decide which of our staff and subcontractors work on the project, and may change them, as long as the project is not adversely affected.
3.2 We follow the delivery approach in the Statement of Work and report progress as it describes.
3.3 Where we work on your systems, we follow your reasonable security and change management rules that you have told us about in advance.
4. Your responsibilities and dependencies
4.1 Projects depend on you. In addition to clause 6 of the Customer Agreement, you will:
- name a decision-maker who is available to make decisions on time,
- give us access to your systems, environments, data and people as set out in the Statement of Work,
- have the Microsoft licences and environments the project needs,
- review and comment on documents and designs within the times in the Statement of Work or, if none is stated, within 5 Business Days and
- manage your other suppliers and coordinate them with us where the project needs it.
4.2 If a dependency is late or missing, the timetable moves and we may charge for extra time and costs under clause 6.2 of the Customer Agreement. We will tell you promptly when this happens.
5. Change control
5.1 Any change to the scope, Deliverables, timetable or Charges of a project follows clause 8 of the Customer Agreement.
5.2 Each change is recorded in a change request that describes the change and its effect on Charges and timetable. We keep a change register for each project. No change takes effect until both parties approve it in writing.
6. Acceptance and warranty
6.1 Deliverables are accepted under clause 9 of the Customer Agreement, using the acceptance criteria in the Statement of Work.
6.2 If you report a defect within 30 days after a Deliverable is accepted, we will fix it at no extra cost. A defect means a failure of the Deliverable to meet its acceptance criteria or description. This does not cover problems caused by use outside the agreed purpose or by changes made by Microsoft to its platform or by anyone other than us.
6.3 After the warranty period, support is available under our Managed Services Schedule or at our then-current rates.
7. Migrations
7.1 This clause applies to projects that move data, such as email, files, sites or records, from one system to another.
7.2 You are responsible for:
- deciding what data is migrated and what is left behind or deleted,
- the quality, accuracy and lawfulness of the source data, including any data that is corrupt, incomplete or duplicated at source and
- telling users about the migration and any changes to how they work.
7.3 We agree a migration plan with you, including cut-over dates, a freeze on changes during cut-over and the checks we will carry out afterwards. You must check migrated data within the period in the plan and report any issues during that period.
7.4 We use specialist migration tools, such as AvePoint, where suitable. Some data, such as permissions, version history or metadata, may not migrate exactly because of differences between systems. We will tell you about any known limitations in the migration plan.
7.5 You must keep the source system available, read-only, for at least 30 days after cut-over unless we agree otherwise in writing. We are not responsible for loss of data that keeping the source system available would have avoided.
8. Microsoft platform changes
8.1 Microsoft regularly changes its products, including features, limits and user interfaces. We design Deliverables for the Microsoft platform as it is when we build them. Work to adapt a Deliverable to a later Microsoft change is outside the project scope, unless the Statement of Work includes it.
9. Documentation and handover
9.1 At the end of each project, we provide the documentation set out in the Statement of Work, such as design documents, configuration records and user guides.
9.2 Handover of Deliverables and documentation, and the transfer of Intellectual Property Rights in them, follows clauses 12.4 and 13.3 of the Customer Agreement.