Legal — force36.net/legal
Service Level Schedule
Applicable to all Statements of Work issued under the Master Services Agreement
- Version
- 2.5
- Last Updated
- 20 May 2026
- Issued By
- Force36 Limited
- Contact
- support@force36.net | 0345 166 7136
Section 1
General Provisions
This Service Level Schedule (“Schedule”) forms part of the Master Services Agreement between Force36 Limited and the Client. It sets out the service levels that apply to services provided by Force36 Limited and governs how incidents are reported, classified, managed, and resolved. The applicable service levels for each service are identified in the relevant Statement of Work.
1.1 Definitions
| Term | Meaning |
| Business Hours | 09:00 to 17:30, Monday to Friday, excluding English bank and public holidays |
| Business Day | Monday to Friday, excluding English bank and public holidays |
| Incident | An unplanned interruption to or reduction in the quality of a service provided under a Statement of Work |
| Service Request | A request for a standard change, configuration update, or administrative action that does not constitute an Incident |
| Automatic Acknowledgement | An immediate automated confirmation issued by Force36's ticketing system upon receipt of an Incident report, confirming the ticket reference number. Automatic acknowledgement does not constitute a Response for SLA measurement purposes. |
| Response | A human triage response from a Force36 engineer confirming that the Incident has been reviewed, a priority assigned, and initial assessment commenced. This is the point from which Target Response Times are measured. |
| Resolution | The Incident has been resolved and the affected service restored to normal operation, as confirmed by Force36 to the Client |
| Target Response Time | The time within which Force36 will provide an initial Response following receipt of an Incident report |
| Target Resolution Time | The time within which Force36 will use commercially reasonable efforts to resolve an Incident |
| Scheduled Maintenance | Maintenance work notified to the Client at least 48 hours in advance, carried out between 23:00 and 07:00 local time |
| TRN | Technical Recommendation Notice issued under clause 5A of the Master Services Agreement |
| SML1 / Standard Care | Openreach Service Maintenance Level 1 — Force36's default service maintenance level for SoGEA and FTTP circuits. Target repair by 23:59 two working days after the fault is formally raised, Monday to Friday, excluding bank holidays |
| SML2 / Premium Care | Openreach Service Maintenance Level 2 — a paid upgrade available on SoGEA and FTTP circuits. Target repair by 23:59 the next working day after the fault is formally raised, Monday to Saturday, excluding bank holidays |
| Provider SLA | The service level agreement of the network provider whose infrastructure underpins a specific circuit, as identified in the relevant Statement of Work |
| Wires Only | A connectivity service where Force36's provision is limited to the physical circuit up to and including the Network Termination Equipment (NTE) at the Client's premises. Force36 has no responsibility for any equipment, configuration, routing, or faults arising beyond the NTE. |
| Network Termination Equipment (NTE) | The point of demarcation between Force36's managed network and the Client's own infrastructure. Under a Wires Only provision this is the boundary of Force36's responsibility. |
| End-to-End Support | A service arrangement under which the Client has taken a connectivity service, a managed network service, and an IT Helpdesk service from Force36 under current Statements of Work. Force36's responsibility is continuous from the physical circuit through to end user devices. There is no demarcation point between service layers and Force36 is the single point of accountability for the full technology stack. |
1.2 How to Report an Incident
All Incidents and Service Requests must be reported to Force36 using one of the following methods. Force36's ticketing system (SysAID) will generate a unique ticket reference upon receipt.
| Channel | Details |
|---|---|
| Email — General | support@force36.net |
| Email — Leased Line Faults | leasedlinefaults@force36.net — use this address to report leased line faults only. Emails to this address are automatically triaged as P1 Incidents and flagged to the Force36 connectivity team immediately. Do not use this address for general support requests or non-leased-line issues. |
| Telephone | 0345 166 7136 (Business Hours) |
| Portal | SysAID self-service portal (link provided at onboarding) |
Where the nature of a fault prevents the Client from sending email (for example a total loss of connectivity), the Client should contact Force36 by telephone. Incidents reported outside Business Hours will be logged and triaged at the start of the next Business Day. Out-of-hours incident management is only available where the relevant Statement of Work expressly includes out-of-hours support cover.
1.3 Priority Definitions
| Priority | Classification | Definition |
|---|---|---|
| P1 | Critical | Total failure of a service, or failure of a component that renders the affected service unusable for more than 50 individual end users for a continuous period of more than 5 minutes |
| P2 | High | Significant reduction in the functionality or performance of a service affecting more than 50 individual end users for a continuous period of more than 5 minutes |
| P3 | Medium | Incident affecting more than five but fewer than 50 users for a continuous period of more than 5 minutes, or a component with limited effect on overall service functionality |
| P4 | Low | Incident affecting five or fewer users for a continuous period of more than 5 minutes, or a Service Request for configuration changes or non-service-affecting loss of functionality |
1.4 Incident Classification and Reclassification
Force36 classifies all Incidents in accordance with the priority framework set out in Section 1.3. Force36's classification is final in the first instance. The Client may request a reclassification review but Force36's assessment governs operationally while any review is considered. Where the Client disagrees with Force36's classification determination, the matter may be escalated through the dispute resolution procedure in the Master Services Agreement.
Where initial triage reveals a fault spans multiple service layers or is of a higher priority than originally classified, Force36 will reclassify the ticket accordingly. The response target is measured from the original point of receipt and is not reset on reclassification. The resolution clock resets from the point of reclassification to the Target Resolution Time applicable to the new priority.
1.5 Measurement and Exclusions
Time is measured from the point at which Force36 receives the Incident report through an approved reporting channel. The following periods are excluded from all measurements:
- Scheduled Maintenance carried out within the notified maintenance window and not resulting in an unplanned fault. Where Scheduled Maintenance causes an unplanned fault, the maintenance exclusion ceases to apply from the point the unplanned fault is identified.
- Periods during which Force36 is awaiting information, access, or authorisation from the Client or a third party nominated by the Client
- Periods during which Force36 is unable to contact the Client's designated contact after repeated attempts
- Periods during which the Client has failed to act on a TRN, where such inaction is the direct or contributing cause of the Incident
- Force Majeure events as defined in the Master Services Agreement
- Incidents caused by the Client, the Client's staff, contractors, or third party systems not managed by Force36
- Incidents affecting services or infrastructure outside Force36's direct management, including third party platform outages covered by Section 5
- Any period during which Force36 is actively waiting on a third party provider, vendor, or supplier to resolve or respond to a fault that has been formally escalated by Force36. The resolution clock is suspended for the entire duration of the third party delay, not limited to the third party's own SLA window.
- Any period outside Business Hours where a fault has been reported outside Business Hours. The acknowledgement, fault raise, and resolution clocks for connectivity faults do not start until the beginning of the next Business Day.
1.6 Repeat Faults
Where the same or substantially similar fault recurs within 10 Business Days of a previous fault being resolved on the same circuit or service, Force36 will treat the recurrence as a continuation of the original Incident rather than a new Incident. Force36 will escalate directly to the network provider or relevant third party without a fresh internal diagnostic window. Where the recurrence is determined to be a new and separate fault, it will be logged as a new Incident and the full fault management process applies from the beginning.
1.7 Service Regrade and Redundancy Refusal
Where Force36 has issued a TRN recommending that the Client upgrade their connectivity service — including a regrade from copper to FTTP where FTTP is available, an upgrade to a higher service maintenance level, or the installation of a resilient backup circuit — and the Client declines to act on that recommendation, Force36's liability for any subsequent fault that would have been prevented by the recommended upgrade is proportionally reduced in accordance with clause 5A(g) of the Master Services Agreement.
A customer on a copper service who has declined an available FTTP regrade accepts the inherent limitations of copper infrastructure. Where the Client has declined Force36's recommendation to install resilient backup connectivity and subsequently suffers an extended outage, Force36's liability is limited to its obligations in respect of the primary circuit only.
1.8 Client Inaction and Technical Recommendations
Where Force36 has issued a TRN and the Client has not implemented the recommended action within the Response Period, Force36's service level obligations shall be reduced proportionally to the extent that the Client's inaction is a direct or contributing cause of any subsequent Incident.
1.9 Force36-Caused Faults
Where a fault is directly attributable to a configuration change, action, or error by Force36, Force36 will use commercially reasonable efforts to resolve the fault as quickly as possible regardless of the time at which the fault occurs. Force36 may at its discretion elect to carry out remediation work outside Business Hours where this is necessary to resolve the fault promptly, at no additional charge to the Client. Force36's agreement to attend out of hours in connection with a Force36-caused fault does not create an ongoing out-of-hours support obligation and does not set a precedent for future requests.
1.10 Client Network Obligations
The Client is responsible for maintaining the integrity of its own network environment in a manner that does not interfere with services provided and managed by Force36.
1.10.1 — Unauthorised Devices on Force36-Managed Networks
This clause applies only where Force36 provides a managed network service under a Statement of Work. It does not apply to services provided on a Wires Only basis. Where Force36 provides a managed network service, the Client must not connect any device, access point, switch, router, repeater, or other network hardware to the Force36-managed network without prior written approval from Force36. Where Force36 identifies an unauthorised device, Force36 will issue a TRN requiring removal and reserves the right to require disconnection as a condition of continued support. Any Incident caused by an unauthorised device constitutes a customer-caused fault under Section 6.2.
1.10.2 — Network Changes
The Client must notify Force36 in writing before making any change to the network infrastructure at a site covered by a Statement of Work. Changes made without notification that result in a fault will be treated as customer-caused faults under Section 6.2.
1.10.3 — Third Party IT Contractors
Where the Client engages a third party IT contractor to carry out work at a site covered by a Statement of Work, the Client must notify Force36 in advance. Force36 accepts no liability for faults caused by third party contractor activity. Any investigation or remediation required as a result of third party contractor activity will be chargeable at Force36's prevailing day rate.
Section 2
IT Helpdesk Service Levels
This section applies to IT Helpdesk services provided by Force36 Limited under a current Statement of Work. The IT Helpdesk operates a tiered support plan model. The response and resolution commitments set out in this section apply specifically to Helpdesk tickets and are distinct from the response and escalation obligations that apply to connectivity services under Sections 3 and 3B and platform administration services under Section 5.
2.1 Scope of Cover
| Environment | Description |
|---|---|
| Production Server | Operational servers required for domain control, file sharing, and email. May be physical or virtualised |
| Production Client | PCs, laptops, tablets, and printers attached to the Production Network |
| Production Network | Network hubs, switches, routers, and cabling within the Client's premises |
Coverage is limited to environments, locations, and equipment specified in the Statement of Work. General consultancy, training, and advisory work are not covered under this SLA and will be charged at Force36's prevailing day rate.
2.2 Support Hours
Standard support is provided during Business Hours: Monday to Friday 09:00 to 17:30, excluding English bank and public holidays. Out-of-hours support is not available to Clients whose Statement of Work does not include an out-of-hours support provision. Where a Client requires Force36 to carry out work at a site outside Business Hours, this may be arranged by mutual agreement and will be quoted on a case by case basis prior to commencement.
2.3 Support Plan Tiers
2.3.1 — Standard Plan
| Priority | Target Response Time | Target Resolution Time |
|---|---|---|
| P1 | By end of next Business Day | 12 Business Hours |
| P2 | By end of next Business Day | 16 Business Hours |
| P3 | By end of next Business Day | 24 Business Hours |
| P4 | By end of next Business Day | 5 Business Days |
2.3.2 — Premium 6 Hour Plan
| Priority | Target Response Time | Target Resolution Time |
|---|---|---|
| P1 | 6 Business Hours | 12 Business Hours |
| P2 | 6 Business Hours | 16 Business Hours |
| P3 | 6 Business Hours | 24 Business Hours |
| P4 | 6 Business Hours | 48 Business Hours |
2.3.3 — Premium 1 Hour Plan
| Priority | Target Response Time | Target Resolution Time |
|---|---|---|
| P1 | 1 Business Hour | 12 Business Hours |
| P2 | 1 Business Hour | 16 Business Hours |
| P3 | 1 Business Hour | 24 Business Hours |
| P4 | 1 Business Hour | 24 Business Hours |
2.4 Per-Incident Escalation
Clients on the Standard Plan may request escalation of a specific ticket to a higher resolution tier on a per-incident basis at any point while the ticket remains open.
| Escalation Tier | Resolution Target from Escalation | Additional Charge |
|---|---|---|
| Premium 6 Hour | 6 Business Hours from clock restart | £250 per incident |
| Premium 1 Hour | 1 Business Hour from clock restart | £500 per incident |
Force36 raises the escalation charge immediately upon receipt of the escalation request. The resolution clock resets from the point Force36 receives confirmed payment or written payment commitment. Force36 will not commence escalated resolution until payment or a formal written commitment to pay has been received.
2.5 Support Plan Upgrades
A Client may permanently upgrade their Helpdesk support plan tier at any time during the contract term. Support plan upgrades are one-way during the contract term — once upgraded to a higher tier the Client will remain on that tier for the remainder of the contract term. A downgrade to a lower support plan tier may only be requested at the point of contract renewal at the end of the minimum term.
2.6 Site Visits
Where remote diagnosis or resolution is not possible, Force36 will dispatch an engineer to the Client's premises at the discretion of the Assigned Support Engineer. Any aborted visit caused by the Client's failure to provide access will be charged at Force36's prevailing day rate.
2.7 Support Lines
| Support Line | Scope |
|---|---|
| First Line | Client-facing helpdesk: incident logging, initial triage, password resets, basic troubleshooting |
| Second Line | Systems administration, business process support, application support. Not client-facing |
| Third Line | Expert knowledge on supported environments. Normally provided to the Client's IT staff only, not directly to end users |
Section 3
SoGEA and FTTP Connectivity Service Levels
This section applies to SoGEA and FTTP broadband services provided by Force36 Limited and delivered over the Openreach network. Physical circuit repair is governed by Openreach's Service Maintenance Level framework.
3.1 Service Maintenance Levels
| Level | Openreach Repair Target | Coverage | Status |
|---|---|---|---|
| Standard Care (SML1) | Fixed by 23:59 two working days after the fault is formally raised with Openreach | Monday to Friday, excluding bank holidays | Default — all circuits |
| Premium Care (SML2) | Fixed by 23:59 the next working day after the fault is formally raised with Openreach | Monday to Saturday, excluding bank holidays | Available on request — additional charge applies |
3.2 Force36 Internal Fault Management Obligations
| Obligation | Target |
|---|---|
| Fault Acknowledgement | Within 1 Business Hour of the fault being reported or detected. Clock starts at beginning of next Business Day for out-of-hours reports. |
| Internal Diagnostics and Formal Fault Raise to Openreach | Within 6 Business Hours of fault identification, measured from the start of the next Business Day where the fault is reported outside Business Hours. The Openreach repair clock does not start until Force36 formally raises the fault. |
| Client Notification of Fault Raise | Force36 will notify the Client when the fault has been formally raised with Openreach, confirming the Openreach ticket reference and the applicable SML repair target |
| Progress Updates — Standard Care | Force36 will provide a status update by end of each working day while the fault remains open |
| Progress Updates — Premium Care | Force36 will provide a status update every 4 hours while the fault remains open |
| Resolution Notification | Force36 will notify the Client immediately upon Openreach confirming resolution of the fault |
Section 3B
Leased Line Connectivity Service Levels
This section applies to leased line connectivity services provided by Force36 Limited under a current Statement of Work. Force36 provides leased line circuits via Openreach, Virgin Media Business, PXC, and Vorboss. The physical circuit repair target is governed by the Provider SLA for the network provider identified in the relevant Statement of Work.
3B.1 Provider SLA Framework
| Provider | Availability Target | Typical Repair Target | Compensation |
|---|---|---|---|
| Openreach | 99.9% or above | As specified in the applicable Openreach Ethernet SLA for the circuit product ordered | Provider SLA credits apply as identified in the relevant Statement of Work |
| Virgin Media Business | 99.9% or above | As specified in the applicable Virgin Media Business SLA for the circuit product ordered | Provider SLA credits apply as identified in the relevant Statement of Work |
| PXC | 99.9% or above | As specified in the applicable PXC SLA for the circuit product ordered | Provider SLA credits apply as identified in the relevant Statement of Work |
| Vorboss | 99.99% (CTX) / 99.9% (RCX) | Target fix within 4 hours. Automatic compensation triggered after 4 minutes of downtime — no claim required from the Client | Automatic: 1 day credit per 12 minutes beyond threshold (CTX). Applied directly by Vorboss without customer action. |
3B.2 Force36 Internal Fault Management Obligations
| Obligation | Target |
|---|---|
| Fault Acknowledgement | Within 2 Business Hours of the fault being reported or detected. Clock starts at beginning of next Business Day for out-of-hours reports. |
| Internal Diagnostics and Formal Fault Raise to Provider | Within 4 Business Hours of fault identification, measured from the start of the next Business Day where the fault is reported outside Business Hours. The Provider repair clock does not start until Force36 formally raises the fault. |
| Client Notification of Fault Raise | Force36 will notify the Client when the fault has been formally raised with the network provider, confirming the provider ticket reference and the applicable repair target |
| Progress Updates | Force36 will provide a status update every 4 Business Hours while the fault remains open, regardless of the applicable Provider SLA tier |
| Resolution Notification | Force36 will notify the Client immediately upon the network provider confirming resolution of the fault |
| Provider Escalation | Where a fault is not resolved within the Provider SLA repair target, Force36 will formally escalate the fault with the provider and notify the Client of the escalation |
Section 4
Network Infrastructure Monitoring
Force36 uses its remote monitoring and management platform to monitor network infrastructure and connectivity for Client sites where this service is included in the relevant Statement of Work.
4.1 What Force36 Monitors
| Monitored | Not Monitored |
|---|---|
| Network infrastructure: switches, routers, and access points supplied and managed by Force36 | End-user devices including PCs, laptops, tablets, and printers |
| Circuit availability and connectivity status for Force36-provisioned broadband and leased line circuits | Software or application performance on end-user devices |
| Alerts generated by Force36-managed Unifi hardware | Third party network equipment not supplied or managed by Force36 |
| Connectivity thresholds triggering automated alert workflows | Customer-side VPN or third party connectivity services |
4.2 Monitoring and Fault Detection
Force36's monitoring capability operates during Business Hours. Where a monitoring alert is generated outside Business Hours, Force36 will investigate at the start of the next Business Day. No out-of-hours monitoring response is provided unless the relevant Statement of Work expressly includes out-of-hours support cover.
4.3 Faults Arising During Scheduled Maintenance
Where Scheduled Maintenance carried out by Force36 results in an unplanned fault or device failure, Force36 will treat the fault as a Force36-caused Incident from the point it is identified. The maintenance exclusion ceases to apply from that point. Force36 will prioritise resolution and where a physical device has failed as a result of maintenance activity, Force36 will arrange dispatch of a replacement device to the Client's site as quickly as practicable. No charge will be levied on the Client for replacement hardware or engineer time required to resolve a fault directly caused by Force36's maintenance activity.
Section 5
Platform Administration Service Levels
This section applies where Force36 provides administration services for third party platforms including Microsoft 365, Mimecast, and Webex. Force36's obligations under this section are limited to the administration layer. Platform availability and performance are governed by the platform vendor's own service level commitments and are expressly excluded from Force36's SLA obligations.
5.1 Microsoft 365
| Matter | Force36 Obligation |
|---|---|
| Administration Requests | Force36 will respond to Service Requests for tenant administration, licence management, user account changes, and configuration updates within the Target Response Times set out in Section 2.3, classified as P4 unless the Client specifies otherwise |
| Platform Fault Escalation | Where a reported fault is determined to be a Microsoft platform issue, Force36 will raise the fault with Microsoft via standard partner support channels and notify the Client |
| Platform SLA | Microsoft's own service level commitments apply to platform availability and application performance. The Microsoft SLA is available at microsoft.com/en-gb/servicesagreement |
| Partner Support Agreement | Force36 does not currently hold a Microsoft partner support agreement. Response times from Microsoft are not within Force36's control and are not covered by this SLA. |
| Data Loss | Force36's liability for any data loss arising from an administrative error, configuration change, or platform fault is governed by the liability and consequential loss exclusion provisions of the Master Services Agreement. The SLA credit regime does not apply to data loss claims. Clients are strongly advised to ensure that appropriate backup provisions are in place under a current Statement of Work. |
| Licence Compliance | The Client is solely responsible for ensuring that all licences are deployed within the scope agreed in the relevant Statement of Work |
5.2 Mimecast Email Security
| Matter | Force36 Obligation |
|---|---|
| Administration Requests | Force36 will respond to Service Requests for Mimecast administration, policy configuration, domain management, and user account changes within the Target Response Times set out in Section 2.3, classified as P4 unless the Client specifies otherwise |
| Platform Fault Escalation | Force36 holds an escalation support contract with Mimecast. Where a reported fault is determined to be a Mimecast platform issue, Force36 will raise the fault via its escalation contract and notify the Client |
| Platform SLA | Mimecast's own service level commitments apply to platform availability, email filtering, and delivery. The Mimecast SLA is available at mimecast.com/contracts |
| Mimecast Escalation Contract | Force36 holds a dedicated escalation contract with Mimecast providing faster access to Mimecast's support teams than standard customer channels |
5.3 Webex Unified Communications
Force36 Limited is a Cisco Webex wholesale partner and the Ofcom-regulated provider of Cisco Webex services to its customers. Force36 provides Webex services within the requirements of Ofcom's General Conditions of Entitlement. As the regulated provider, Force36 sets its own service level commitments for the administration and support of Webex services.
| Matter | Force36 Commitment |
|---|---|
| Regulatory Status | Force36 is the Ofcom-regulated wholesale provider of Cisco Webex services. The service is provided in compliance with Ofcom's General Conditions of Entitlement. Customers contract with Force36 as the provider of record. |
| Administration Requests | Force36 will respond to Service Requests for Webex configuration changes, user provisioning, and call routing updates during Business Hours, classified as P4 unless the Client specifies otherwise |
| Client Self-Administration | The Client has direct portal access to Webex and may carry out certain administrative changes independently of Force36. Changes made by the Client directly are the Client's own responsibility. |
| Platform Fault Escalation | Where a reported fault is determined to be a Cisco Webex platform issue, Force36 will escalate the fault to Cisco via its dedicated wholesale support channel. Force36 will provide progress updates every 4 Business Hours while the fault remains open. |
| Direct Client Contact with Cisco | Cisco does not provide direct support to end customers for Webex services provided through the Force36 wholesale channel. The Client must not attempt to contact Cisco directly. All support requests must be raised with Force36. Where a Client contacts Cisco directly and Cisco makes a change that conflicts with Force36's configuration, any resulting fault will be treated as a customer-caused fault under Section 6.2. |
| Scope of Administration | Force36 administers Webex during Business Hours only. Administration requests received outside Business Hours will be addressed at the start of the next Business Day. |
| Seasonal and Scheduled Message Changes | All relevant materials for phone system message changes, auto-attendant greetings, hunt group routing, or other scheduled changes must be submitted to Force36 a minimum of one calendar month before the required go-live date. Changes submitted with less than one calendar month's notice cannot be guaranteed to be implemented by the required date. Clients may implement such changes themselves via the Webex self-service administration portal. |
Section 6
Service Credits
Service credits are available only where Force36 has failed to resolve an Incident within the applicable Target Resolution Time, subject to the conditions and exclusions set out in this section. Service credits are the Client's sole financial remedy for failure to meet the service levels set out in this Schedule, unless Force36 has committed a material breach of the Master Services Agreement.
Where a connectivity service is provided on a Wires Only basis, service credits apply only in respect of faults on the circuit up to and including the NTE.
6.1 Resolution Clock and Suspension
The Target Resolution Time is measured from the point at which Force36 provides a human triage Response. The resolution clock is suspended during the following periods:
| Suspension Event | Scope of Suspension |
|---|---|
| Third party provider delay | Any period during which Force36 is actively waiting on a network provider, software vendor, hardware manufacturer, or other third party to resolve or respond to a fault that has been formally escalated by Force36. The suspension covers the entire duration of the third party delay, not limited to the third party's own SLA window. |
| Awaiting customer | Any period during which Force36 is waiting for information, access, authorisation, or a decision from the Client |
| Scheduled Maintenance | Any period of Scheduled Maintenance notified at least 48 hours in advance |
| Customer-caused fault investigation | Any period during which Force36 or a third party provider is investigating a fault subsequently determined to have been caused by the Client, the Client's staff, or equipment within the Client's control. Where the fault is confirmed as customer-caused, no credits apply for any part of the Incident. |
| Force Majeure | Any period during which Force36's performance is affected by a Force Majeure event as defined in the Master Services Agreement |
6.2 Customer-Caused Faults
Where a fault is investigated and determined to have been caused by the Client, the Client's staff, or equipment within the Client's control:
- No service credits are payable in respect of any part of that Incident
- Force36 reserves the right to recover the cost of any abortive engineer visit charged to Force36 by a third party provider
- Force36 reserves the right to charge for its own investigation time in accordance with clause 5B of the Master Services Agreement
- Examples include: disconnection of power to network equipment, tampering with Force36-supplied hardware, unauthorised configuration changes, failure to maintain adequate power supply, and connection of unauthorised devices to a Force36-managed network
- Force36's determination of root cause is final in the first instance. Where the Client disputes this determination, the matter may be escalated through the dispute resolution procedure in the Master Services Agreement. Force36's determination stands operationally while any dispute is in progress.
6.3 IT Helpdesk and Platform Administration Credits
| Trigger | Credit | Cap |
|---|---|---|
| Failure to resolve within Target Resolution Time after excluding all suspended periods | One day's equivalent of the monthly fee for the affected service per 12 Business Hours of additional delay | Credits in any calendar month shall not exceed 50% of the monthly fee for the affected service |
6.4 SoGEA and FTTP Connectivity Credits
Credits are available only where the total resolution time, excluding all suspended periods, exceeds Force36's internal fault management obligations. No credits are available in respect of Openreach's failure to meet its own SML repair target, as this constitutes a third party delay excluded from the resolution clock. Where Force36 receives credits from Openreach, Force36 will apply a corresponding credit to the Client's account.
6.5 Leased Line Connectivity Credits
Credits are available only where the total resolution time, excluding all suspended periods, exceeds Force36's internal fault management obligations. No credits are available in respect of a network provider's failure to meet its own repair target. Where Force36 receives credits from a network provider, Force36 will apply a corresponding credit to the Client's account. Where a Vorboss circuit is in place, Vorboss's automatic compensation will be applied directly by Vorboss without the need for a credit claim from the Client.
6.6 Credit Claim Process
- Notify Force36 in writing within 5 Business Days of becoming aware of the failure giving rise to the credit claim
- Reference the relevant SysAID ticket number in the credit claim notification
- Send the credit claim notification to accounts@force36.net
Force36 will review the claim within 5 Business Days of receipt and confirm whether a credit is due. Force36 will provide a written breakdown of the resolution timeline including any suspended periods applied. Credits will be applied to the Client's next invoice. Credits are not redeemable for cash and may not be carried forward beyond 90 days.
6.7 General Credit Limitations
- Missed acknowledgement and response targets do not give rise to credit entitlement
- Service credits are not available where the root cause of the fault is determined to be customer-caused
- Service credits are not available during periods of Scheduled Maintenance
- Service credits are not available where Force36's failure is attributable to the Client's failure to act on a TRN
- Service credits may not be set off against invoices without Force36's prior written consent
- Where aggregate credits in any month reach 100% of the monthly fee for the affected service, the Client may terminate the relevant Statement of Work on 30 days' written notice without early termination charges
6.8 Split-Cause Faults
Where an Incident has both a Force36-attributable cause and a customer-attributable cause, credits are calculated only in respect of the Force36-attributable element. Force36 will resolve its own attributable element within the applicable Target Resolution Time. The customer-caused element is treated separately and a TRN will be issued. Where the relative contribution of each cause cannot be clearly determined, Force36 and the Client will use reasonable commercial efforts to agree an appropriate apportionment.
6.9 Third Party Contractor Damage
Where a third party contractor engaged by the Client causes damage to Force36-managed hardware or infrastructure, the fault is treated as a customer-caused Incident. Force36's investigation and remediation time is chargeable to the Client. The cost of replacing damaged Force36-managed hardware is recoverable from the Client at the current replacement cost.
6.10 Aborted Site Visits
Where Force36 has agreed an engineer visit and the visit cannot be completed due to the Client's failure to provide access, the resolution clock is paused from the point of the failed visit and treated as a customer delay. Force36's abortive visit charge applies. Resolution will not resume until a new appointment has been agreed in writing by both parties and the engineer successfully gains access.
6.11 Performance Reporting
Force36 does not proactively issue SLA performance reports as a standard included service. Clients who require regular SLA compliance reporting should include a reporting provision in their Statement of Work. Monthly reporting charges will apply as agreed in the relevant Statement of Work.
6.12 Quarterly Business Reviews
Quarterly Business Reviews (QBRs) are an optional additional service available to Clients who include a QBR provision in their Statement of Work. QBRs are chargeable and no QBR obligation exists in the absence of a Statement of Work provision. Where a QBR is specified in a Statement of Work, Force36 will conduct QBRs on a mutually agreed quarterly date confirmed in writing. Force36 will provide a written agenda at least 5 Business Days before the agreed date. QBRs do not form part of the credit regime and a missed or delayed QBR does not give rise to a credit entitlement.
Section 7
General Provisions
7.1 Relationship to Master Services Agreement
This Schedule forms part of and is incorporated into the Master Services Agreement. In the event of any conflict between this Schedule and the Master Services Agreement, the Master Services Agreement shall prevail. In the event of any conflict between this Schedule and a Statement of Work, the Statement of Work shall prevail in respect of the specific service to which it relates.
7.2 Updates to this Schedule
Force36 may update this Schedule from time to time. The current version is available at https://www.force36.net/legal/. Force36 will provide the Client with not less than 30 days' written notice of any change to this Schedule that materially reduces the service levels applicable to a current Statement of Work.
7.3 Governing Law
This Schedule is governed by English law. Any disputes arising in connection with this Schedule shall be resolved in accordance with the dispute resolution provisions of the Master Services Agreement.
7.4 Client Insolvency
Where the Client enters administration, liquidation, receivership, or any other insolvency process, Force36 will continue to provide services under current Statements of Work provided that the Client's billing account is up to date at the point insolvency is declared and continues to be settled in accordance with the payment terms in the Master Services Agreement. Force36 is not obliged to provide services on credit to an insolvent estate. Early termination charges under active Statements of Work remain payable as a debt of the insolvent estate.