Service Level Agreement Template for IT Services

Created November 15, 2026 · Updated November 15, 2026

This service level agreement is a customer-friendly contract for the IT services industry, for a business that buys hosting or cloud services, managed IT and software support from one provider. The provider commits to 99.95% uptime and a 24/7 help desk for all incidents, with priority levels that set response and resolution times. The agreement covers maintenance windows, backups, disaster recovery with recovery time objectives, and notice of security incidents. Service credits are not the customer's only remedy, chronic failures give the customer extra rights, and the provider must assist with transition when the agreement ends.

Use it when your business runs on systems someone else hosts and supports, and you need strict availability, fast help at any hour, and a plan for data loss, security incidents and switching providers.

The agreement has 18 sections. Scope of Services and Service Commencement sets up the services. Service Availability and Uptime Commitment sets 99.95%. Incident Classification and Priority Levels and Response and Resolution Time Obligations set the speed of response. Help Desk Support and Escalation Procedures provides round-the-clock support. Scheduled Maintenance and Emergency Maintenance Windows limits downtime. Data Backup, Disaster Recovery and Recovery Time Objectives protects data. Information Security and Security Incident Notification covers breaches. Service Level Measurement, Monitoring and Monthly Reporting and Service Credits and Calculation Methodology measure and compensate. Remedies, Chronic Failure and Customer Rights Reserved keeps other remedies. Exclusions and Excused Performance, Customer Responsibilities and Cooperation, Service Review Meetings and Continuous Improvement, Term, Termination and Transition Assistance, Limitation of Liability and Indemnification and Governing Law and Dispute Resolution complete it.

Fill in the services, the priority definitions, the response and resolution times, the maintenance windows, the recovery time objectives and the credit amounts. Test the disaster recovery plan, not just its description. The governing law is deliberately left blank, so the agreement can be adapted to your country.

It is a template, not legal advice.

IT SERVICE LEVEL AGREEMENT

This IT Service Level Agreement (the "Agreement") is entered into as of [Effective Date] (the "Effective Date"), by and between:

[Customer Legal Name], a company duly organized and existing under the laws of [Jurisdiction], having its registered office at [Customer Address] (the "Customer"); and

[Provider Legal Name], a company duly organized and existing under the laws of [Jurisdiction], having its registered office at [Provider Address] (the "Provider").

The Customer and the Provider are each referred to herein as a "Party" and together as the "Parties".

WHEREAS, the Provider is engaged in the business of providing hosting, managed IT and software support services to business customers;

WHEREAS, the Customer wishes to obtain, and the Provider wishes to supply, such services on the basis of defined and measurable service levels; and

WHEREAS, the Parties wish to set out the terms and conditions on which the Provider shall perform the Services and the consequences of any failure to meet the agreed service levels;

NOW, THEREFORE, the Parties agree as follows:

  1. Definitions and Interpretation

    1. "Affiliate" means, with respect to a Party, any entity that directly or indirectly controls, is controlled by, or is under common control with that Party, where "control" means the power to direct the management and policies of an entity, whether through ownership of voting securities, by contract or otherwise.

    2. "Available" means that the Hosted Environment and each Service component is fully operational, accessible and functioning in accordance with the Specifications and this Agreement, and "Availability" shall be construed accordingly.

    3. "Business Day" means any day other than a Saturday, a Sunday or a public holiday in [Customer Jurisdiction].

    4. "Customer Data" means all data, content, records, files, software and information, in any form, that are owned, supplied, generated or processed by or on behalf of the Customer or its Affiliates in connection with the Services, including all outputs derived from such materials.

    5. "Downtime" means any period during which the Hosted Environment or any Service component is not Available, excluding only Permitted Downtime.

    6. "Hosted Environment" means the servers, storage, network, virtualization, platform and application infrastructure, whether physical or virtual, operated by or for the Provider and used to deliver the Services, as further described in the Specifications.

    7. "Incident" means any unplanned interruption to, degradation of, or failure in the Services, or any event that has not been planned and that affects or threatens to affect the quality or Availability of the Services.

    8. "Monthly Uptime Percentage" means the percentage calculated for each Service Month in accordance with the formula set out in the section of this Agreement entitled Service Availability and Uptime Commitment.

    9. "Permitted Downtime" means Downtime that is caused by Scheduled Maintenance performed in compliance with this Agreement or that is expressly designated as excused under the section of this Agreement entitled Exclusions and Excused Performance.

    10. "Priority Level" means the classification assigned to an Incident, namely Priority 1, Priority 2, Priority 3 or Priority 4, in accordance with the section of this Agreement entitled Incident Classification and Priority Levels.

    11. "Recovery Point Objective" or "RPO" means the maximum period of Customer Data loss, measured backward from the time of an Incident or disaster, that is acceptable under this Agreement.

    12. "Recovery Time Objective" or "RTO" means the maximum period within which the Services must be restored following a disaster or major Incident.

    13. "Resolution" means the permanent correction of an Incident or the implementation of a workaround accepted in writing by the Customer, in each case restoring the Services to the performance required by this Agreement.

    14. "Security Incident" means any actual or reasonably suspected unauthorized access to, or acquisition, use, disclosure, alteration, loss or destruction of, Customer Data or the systems on which Customer Data is stored or processed, or any compromise of the security, confidentiality or integrity of the Services.

    15. "Service Credit" means the amount credited or payable to the Customer, calculated in accordance with this Agreement, in respect of a failure by the Provider to meet a Service Level.

    16. "Service Levels" means the performance standards, including those for Availability, response, Resolution, recovery and reporting, set out in this Agreement.

    17. "Service Month" means each calendar month, or part thereof, during the Term in which the Services are provided.

    18. "Services" means the hosting, managed IT and software support services described in this Agreement and in the Specifications, together with any related services, functions or responsibilities that are inherent in, or necessary for, the proper performance of those services.

    19. "Specifications" means the technical, functional and operational description of the Services agreed in writing by the Parties and set out in [Service Description Document Reference].

    20. "Term" means the Initial Term and any Renewal Term, as defined in this Agreement.

    21. In this Agreement, unless the context otherwise requires: headings are for convenience only and do not affect interpretation; the singular includes the plural and vice versa; "including" means "including without limitation"; references to a "section" are to a section of this Agreement; references to writing include email; and references to times of day are to [Time Zone].

    22. In the event of conflict between the body of this Agreement and any document referred to in it, the body of this Agreement shall prevail, unless the other document expressly provides more favorable terms to the Customer, in which case those terms shall prevail.

  2. Scope of Services and Service Commencement

    1. The Provider shall provide the Services to the Customer throughout the Term in accordance with this Agreement, the Specifications and good industry practice, including hosting of the Customer's applications and systems, managed IT infrastructure services and software support as described in [Description of Services].

    2. The Services shall commence on [Service Commencement Date] (the "Service Commencement Date"). The Provider shall complete all onboarding, migration, configuration and testing activities required for commencement by that date, in accordance with the plan set out in [Onboarding Plan Reference].

    3. The Service Levels shall apply from the Service Commencement Date. If the Provider fails to commence the Services by the Service Commencement Date for any reason other than a breach by the Customer, the Customer may, without prejudice to its other rights, claim [Delay Credit Amount] for each day of delay and, if the delay exceeds [Number] days, terminate this Agreement upon written notice without liability.

    4. The Provider shall perform the Services using suitably qualified, trained and experienced personnel, with due skill, care and diligence, and in compliance with all laws applicable to the Provider and the Services.

    5. The Customer may, by written notice, request changes to the scope, volume or nature of the Services. The Provider shall respond within [Number] Business Days with a written proposal setting out the effect of the change on the fees, the Service Levels and the timetable. No change shall be binding unless agreed in writing and signed by authorized representatives of both Parties.

    6. The Provider shall not subcontract any part of the Services without the Customer's prior written consent. The Provider shall remain fully responsible for the acts and omissions of its subcontractors as if they were its own.

    7. The fees for the Services shall be as set out in [Fees and Payment Terms], payable in [Currency] within [Number] days following receipt of a correct invoice. The Customer may withhold payment of amounts disputed in good faith without being in breach, provided that it notifies the Provider of the dispute.

  3. Service Availability and Uptime Commitment

    1. The Provider shall ensure that the Hosted Environment and the Services achieve a Monthly Uptime Percentage of not less than 99.95% in each Service Month (the "Uptime Commitment").

    2. The Monthly Uptime Percentage shall be calculated as: (Total Minutes in the Service Month minus Downtime Minutes in the Service Month) divided by Total Minutes in the Service Month, multiplied by 100. Permitted Downtime shall be excluded from Downtime Minutes only to the extent that it complies with this Agreement.

    3. Downtime shall commence at the earlier of the time the Incident is detected by the Provider's monitoring tools and the time the Incident is reported by the Customer, and shall end when the Services are restored and confirmed Available.

    4. Partial unavailability, including material degradation of performance, loss of a material function, or unavailability affecting some but not all users or locations, shall constitute Downtime for the affected portion of the Services in proportion to the impact, or in full where the Services are unusable for their intended purpose in the Customer's reasonable judgment.

    5. Where the Services are delivered through multiple components, the Uptime Commitment shall apply separately to each component identified in the Specifications as business critical, and a failure of any such component shall constitute a failure of the Uptime Commitment.

    6. The Provider shall design, implement and maintain the Hosted Environment with such redundancy, fault tolerance, capacity and monitoring as are necessary to meet the Uptime Commitment, and shall promptly notify the Customer upon becoming aware of any risk to Availability.

    7. The Uptime Commitment is a minimum standard. The Provider's achievement of the Uptime Commitment shall not relieve it of its obligations in respect of any other Service Level.

  4. Incident Classification and Priority Levels

    1. Each Incident shall be assigned a Priority Level by the Customer acting reasonably, or, where the Customer has not done so, by the Provider in consultation with the Customer. In the event of disagreement, the higher Priority Level proposed by the Customer shall apply pending resolution of the disagreement.

    2. Priority 1 (Critical) means an Incident that causes complete unavailability of, or severe degradation to, a production system or business-critical Service, affects all or a substantial number of users, causes or threatens material financial loss, data loss or reputational harm, or constitutes a Security Incident affecting Customer Data.

    3. Priority 2 (High) means an Incident that causes significant degradation or loss of a major function of the Services, affects a significant group of users, and for which no acceptable workaround exists, but which does not amount to a Priority 1 Incident.

    4. Priority 3 (Medium) means an Incident that causes limited impairment of the Services or affects a small number of users, or for which an acceptable workaround is available.

    5. Priority 4 (Low) means a minor Incident, query or request that has no material impact on the operation of the Services, including requests for information and cosmetic defects.

    6. The Priority Level of an Incident may be raised by the Customer at any time upon reasonable grounds, including where the impact of the Incident increases or the Incident is not resolved within the applicable time. The Provider may lower a Priority Level only with the Customer's written agreement.

    7. The Provider shall record the Priority Level, time of detection, time of reporting, and all material actions taken in respect of each Incident in its ticketing system, to which the Customer shall have read access at all times.

  5. Response and Resolution Time Obligations

    1. The Provider shall respond to and resolve each Incident within the times set out below, measured from the earlier of detection by the Provider and notification by the Customer, and measured continuously (24 hours a day, 7 days a week) irrespective of Business Days.

    2. For Priority 1 Incidents: response within [Number] minutes; status updates every [Number] minutes; and Resolution within [Number] hours.

    3. For Priority 2 Incidents: response within [Number] minutes; status updates every [Number] hours; and Resolution within [Number] hours.

    4. For Priority 3 Incidents: response within [Number] hours; status updates every [Number] Business Days; and Resolution within [Number] Business Days.

    5. For Priority 4 Incidents: response within [Number] Business Days; and Resolution within [Number] Business Days or such other period as the Customer may agree.

    6. "Response" means that a qualified Provider engineer has acknowledged the Incident, begun active diagnosis and made contact with the Customer's reporting representative. Automated acknowledgment shall not constitute a response.

    7. The Provider shall work continuously on Priority 1 and Priority 2 Incidents until Resolution, allocating all necessary resources. Following Resolution of any Priority 1 or Priority 2 Incident, the Provider shall deliver a written root-cause analysis within [Number] Business Days, including corrective and preventive measures, and shall implement such measures within a timetable reasonably approved by the Customer.

    8. A temporary workaround shall stop the Resolution clock only where the Customer has accepted it in writing, and the underlying cause shall nevertheless be permanently corrected within [Number] days.

  6. Help Desk Support and Escalation Procedures

    1. The Provider shall maintain a help desk staffed by suitably qualified personnel, available 24 hours a day, 7 days a week, 365 days a year, for the reporting of and response to all Incidents of every Priority Level.

    2. The help desk shall be accessible by telephone at [Help Desk Telephone Number], by email at [Help Desk Email Address] and through [Online Portal], and shall provide support in [Language]. Telephone calls shall be answered by a live person within [Number] seconds in at least [Percentage] of cases.

    3. Each reported Incident shall be logged immediately, assigned a unique ticket number, and communicated to the Customer's reporting representative. The Provider shall provide first-line support and shall escalate to second-line and third-line specialists as required without delay or additional charge.

    4. If an Incident is not resolved within the applicable time, or if the Customer is dissatisfied with its handling, the following escalation shall apply: Level 1, the help desk team leader, upon the lapse of [Number] percent of the Resolution time; Level 2, the Provider's service delivery manager, upon breach of the Resolution time; Level 3, the Provider's [Senior Officer Title], upon breach of the Resolution time by more than [Number] hours or upon the Customer's request.

    5. The Provider shall notify the Customer's designated contacts, identified in [Customer Contact Details], of every Priority 1 Incident immediately upon detection and shall maintain an up-to-date escalation matrix with names, roles and contact details of its personnel, delivered to the Customer within [Number] days of the Effective Date and updated upon any change.

    6. Escalation shall not affect the running of any Service Level time or the accrual of any Service Credit.

  7. Scheduled Maintenance and Emergency Maintenance Windows

    1. The Provider may perform scheduled maintenance of the Services and the Hosted Environment ("Scheduled Maintenance") only within the maintenance window of [Day and Time Range] in [Time Zone], not exceeding [Number] hours per Service Month in aggregate.

    2. The Provider shall give the Customer not less than [Number] days' prior written notice of any Scheduled Maintenance, describing its nature, expected duration, potential impact and rollback plan. The Customer may, acting reasonably, require that Scheduled Maintenance be postponed where it coincides with a critical business period notified to the Provider.

    3. Scheduled Maintenance shall constitute Permitted Downtime only if performed within the maintenance window, upon the required notice, and within the notified duration. Any Downtime exceeding the notified duration, or occurring outside the maintenance window, shall count as Downtime.

    4. The Provider shall use all reasonable efforts to minimize the impact of Scheduled Maintenance, including by use of redundancy, rolling updates and pre-testing in a non-production environment, and shall verify the proper functioning of the Services upon completion.

    5. Emergency maintenance, being maintenance that is necessary to prevent or remedy an imminent threat to security, integrity or Availability and that cannot reasonably be deferred to the next maintenance window ("Emergency Maintenance"), may be carried out upon such notice as is reasonably practicable. The Provider shall notify the Customer before commencing, or if impossible, immediately after commencing, Emergency Maintenance.

    6. Emergency Maintenance shall count as Downtime unless the need for it arose from a cause outside the Provider's reasonable control and not attributable to the Provider's failure to perform preventive maintenance or apply security patches in a timely manner.

    7. The Provider shall bear all costs of maintenance and shall not charge the Customer for any maintenance activity unless expressly agreed in writing.

  8. Data Backup, Disaster Recovery and Recovery Time Objectives

    1. The Provider shall perform backups of all Customer Data and system configurations as follows: full backups at least [Frequency]; incremental or differential backups at least [Frequency]; and transaction log or equivalent continuous backups where applicable.

    2. Backups shall be encrypted in transit and at rest, retained for not less than [Retention Period], stored in at least one geographically separate location from the primary Hosted Environment at [Backup Location], and protected against unauthorized access, alteration and deletion.

    3. The Provider shall test the restoration of backups at least [Frequency] and shall provide the Customer with written results of each test within [Number] Business Days. Any failed restoration shall be treated as an Incident of Priority 2 or higher, and corrected without delay.

    4. The Provider shall maintain, and keep current, a written disaster recovery plan covering all Services, shall provide it to the Customer upon request, and shall test it in full at least [Frequency], with the Customer entitled to observe and receive a written report of the results.

    5. In the event of a disaster or major Incident, the Provider shall restore the Services within a Recovery Time Objective of [Number] hours and shall ensure that the loss of Customer Data does not exceed a Recovery Point Objective of [Number] minutes.

    6. Failure to meet the RTO or RPO shall constitute a failure of a Service Level, giving rise to Service Credits and the Customer's other rights under this Agreement, and shall be treated as a Priority 1 Incident for all purposes.

    7. Customer Data shall remain the exclusive property of the Customer. The Provider shall not use, access or disclose Customer Data except as necessary to perform the Services and shall return or delete it as directed by the Customer in accordance with this Agreement.

  9. Information Security and Security Incident Notification

    1. The Provider shall implement and maintain administrative, technical and physical safeguards that are no less rigorous than [Security Standard] and good industry practice, designed to protect the confidentiality, integrity and availability of Customer Data and the Services.

    2. Such safeguards shall include, at a minimum: encryption of Customer Data in transit and at rest; role-based access controls and multi-factor authentication; logging and monitoring of access; timely application of security patches; vulnerability scanning and penetration testing at least [Frequency]; network segmentation; and background-screened personnel bound by written confidentiality obligations.

    3. The Provider shall notify the Customer of any Security Incident without undue delay and in any event within [Number] hours after becoming aware of it, by telephone and email to the Customer's designated security contact set out in [Customer Security Contact].

    4. The notification shall include, to the extent known: the nature and scope of the Security Incident; the categories and volume of Customer Data affected; the likely consequences; the measures taken or proposed to contain and remedy it; and a contact for further information. The Provider shall supplement the notification as further information becomes available.

    5. The Provider shall, at its own cost, immediately take all steps necessary to contain, investigate and remediate the Security Incident, preserve relevant evidence, cooperate fully with the Customer and any competent authority, and provide a written root-cause report within [Number] days.

    6. The Provider shall bear all reasonable costs arising from a Security Incident attributable to its breach of this Agreement, including costs of investigation, notification of affected persons and authorities, credit monitoring or similar remediation, and regulatory fines to the extent permitted by applicable law. The Provider shall not make any public statement regarding a Security Incident identifying the Customer without the Customer's prior written approval, save as required by law.

    7. The Customer or its appointed auditor may, upon [Number] days' notice and not more than [Number] times per year (or at any time following a Security Incident), audit the Provider's compliance with this section. The Provider shall provide reasonable assistance and promptly remedy any deficiency identified.

  10. Service Level Measurement, Monitoring and Monthly Reporting

    1. The Provider shall continuously monitor the Services and the Hosted Environment using appropriate automated tools capable of measuring each Service Level accurately, and shall retain all measurement data for not less than [Retention Period].

    2. The Provider shall deliver to the Customer, within [Number] Business Days following the end of each Service Month, a written report (the "Monthly Report") at no additional charge.

    3. Each Monthly Report shall include: the Monthly Uptime Percentage and all Downtime events with start and end times and causes; all Incidents by Priority Level, with response and Resolution times against the Service Levels; the results of backup and recovery tests; Scheduled Maintenance and Emergency Maintenance performed; Security Incidents and remedial actions; Service Credits accrued; trends, root causes and proposed corrective actions; and any other information reasonably requested by the Customer.

    4. The Customer shall be given real-time access to a dashboard or equivalent tool displaying current Service performance and Incident status, to the extent technically feasible.

    5. The Customer may, upon reasonable notice, audit or verify the Provider's measurement tools, methodologies and underlying data. If the audit reveals that any Service Level was misreported, the Provider shall correct the report, pay all Service Credits due, and reimburse the reasonable costs of the audit.

    6. In the absence of manifest error, the Customer's records of Downtime and Incident times shall be taken into account together with the Provider's data. Where the Parties' data differ, the data more favorable to the Customer shall prevail until the discrepancy is resolved.

    7. Failure by the Provider to deliver a Monthly Report when due shall constitute a failure to meet a Service Level, and any Service Credit shall be calculated on the basis of the Customer's reasonable estimate until the report is delivered.

  11. Service Credits and Calculation Methodology

    1. For each Service Month in which the Monthly Uptime Percentage falls below 99.95%, the Provider shall credit the Customer a percentage of the monthly fees for the affected Services as follows: below 99.95% but at least 99.9%: [Percentage]; below 99.9% but at least 99.0%: [Percentage]; below 99.0% but at least 95.0%: [Percentage]; below 95.0%: [Percentage].

    2. For each Incident for which the Provider fails to meet the applicable response or Resolution time, the Provider shall credit the Customer [Percentage] of the monthly fees for the Priority 1 Incident, [Percentage] for the Priority 2 Incident, and [Percentage] for the Priority 3 Incident, together with an additional [Percentage] for each full [Number] hours of continuing delay.

    3. Service Credits shall also accrue for failure to meet the RTO or RPO, failure to give timely notice of a Security Incident, and failure to deliver Monthly Reports, in each case in the amounts of [Percentage] of the monthly fees per failure.

    4. Service Credits for different Service Levels are cumulative, subject to an aggregate cap of [Percentage] of the monthly fees in any Service Month. The Provider shall calculate all Service Credits and show them in the Monthly Report, without any need for a claim by the Customer.

    5. Service Credits shall be applied as a deduction against the next invoice or, where no further invoice is due, paid to the Customer within [Number] days following the end of the Term. Service Credits are a price adjustment reflecting the reduced value of the Services and are not a penalty.

    6. Service Credits shall be calculated on the monthly fees for all Services affected, and where an affected component impairs the Services as a whole, on the total monthly fees.

    7. The Customer's entitlement to Service Credits shall not be subject to any minimum claim period, and shall not be affected by the Customer's late payment of undisputed sums of less than [Number] days.

  12. Remedies, Chronic Failure and Customer Rights Reserved

    1. Service Credits are not the Customer's sole or exclusive remedy for a failure to meet the Service Levels. Service Credits are without prejudice to, and shall be set off against only to the extent of duplication in, any damages or other remedies available to the Customer under this Agreement or otherwise.

    2. In addition to Service Credits, the Customer shall be entitled to require the Provider to prepare and implement, at the Provider's cost, a written corrective action plan within [Number] Business Days of any Service Level failure, and to claim damages for any loss caused by the failure exceeding the Service Credits paid.

    3. A "Chronic Failure" occurs if: the Monthly Uptime Percentage falls below 99.95% in any [Number] Service Months in any rolling period of [Number] Service Months; the Monthly Uptime Percentage falls below [Percentage] in any single Service Month; any Priority 1 Incident remains unresolved beyond [Number] hours; or any Resolution or response time is missed in respect of [Number] or more Incidents in any Service Month.

    4. Upon a Chronic Failure, the Customer may, in its sole discretion and without liability, by written notice: terminate this Agreement in whole or in part with immediate effect or from a date specified; require enhanced governance and remediation at the Provider's cost; engage a third party to perform or remedy the affected Services and recover the reasonable additional costs from the Provider; and suspend payment of fees for the affected Services until remediation.

    5. The Customer may also terminate this Agreement for material breach if the Provider fails to remedy that breach within [Number] days following written notice, or immediately where the breach is incapable of remedy, including a material Security Incident caused by the Provider's breach.

    6. All rights and remedies of the Customer under this Agreement are cumulative and in addition to those provided by law. No delay or failure by the Customer in exercising any right shall operate as a waiver, and acceptance of Service Credits shall not constitute a waiver of any other right or remedy.

    7. The Customer reserves the right to set off any Service Credits or damages due from the Provider against any amount payable by the Customer to the Provider.

  13. Exclusions and Excused Performance

    1. The Provider shall not be liable for a failure to meet a Service Level to the extent, and only to the extent, that the failure is directly caused by: Scheduled Maintenance performed in accordance with this Agreement; a breach by the Customer of its obligations under this Agreement; or the Customer's unauthorized modification of the Services or the Hosted Environment, in each case provided that the Provider has notified the Customer promptly and used reasonable efforts to mitigate the effect.

    2. The Provider shall likewise be excused where the failure is caused by a Force Majeure Event, meaning an event beyond the reasonable control of the affected Party that could not have been prevented or avoided by reasonable precautions, including natural disaster, war, terrorism, civil disturbance and governmental action. The following shall not constitute a Force Majeure Event: failure of the Provider's subcontractors or suppliers (unless themselves affected by a Force Majeure Event); equipment failure; cyberattack that could have been prevented by compliance with this Agreement; labor disputes involving the Provider's personnel; and any event that the Provider's disaster recovery plan is designed to address.

    3. A Force Majeure Event shall not excuse the Provider from implementing its disaster recovery plan and meeting the RTO and RPO. If a Force Majeure Event prevents the performance of the Services for more than [Number] consecutive days, the Customer may terminate this Agreement upon written notice without liability.

    4. The Provider shall bear the burden of proving that an exclusion or excuse applies. The Provider shall notify the Customer in writing within [Number] hours of becoming aware of any circumstance on which it intends to rely and shall provide supporting evidence.

    5. During any period of excused performance, the Customer shall not be required to pay fees for Services not provided, and the Provider shall continue to perform all Services unaffected by the excusing event.

    6. The exclusions in this section shall be construed narrowly. The Provider shall not rely on any exclusion in respect of a Security Incident or loss of Customer Data attributable to the Provider's failure to comply with this Agreement.

  14. Customer Responsibilities and Cooperation

    1. The Customer shall provide the Provider with such access to its relevant premises, systems, information and personnel as is reasonably necessary for the Provider to perform the Services, subject to the Customer's security and confidentiality policies as notified to the Provider.

    2. The Customer shall designate an authorized representative and a security contact, as set out in [Customer Contact Details], for communication regarding the Services, and may replace them upon written notice.

    3. The Customer shall report Incidents to the Provider through the help desk and shall provide such information about the Incident as it reasonably has available and as the Provider reasonably requests.

    4. The Customer shall use reasonable efforts to ensure that its users comply with the Provider's reasonable acceptable use requirements, notified in writing and consistent with the Specifications.

    5. The Customer shall pay the undisputed fees in accordance with this Agreement.

    6. The Provider shall promptly notify the Customer in writing if it considers that any failure by the Customer to comply with this section is likely to affect its performance, specifying the failure and its anticipated effect. The Provider may rely on such failure as an excuse only if it has given such notice within [Number] Business Days of becoming aware of it.

    7. The Customer's obligations under this section are the sole responsibilities of the Customer in connection with the Services and shall not be construed to limit the Provider's responsibility for performing the Services in accordance with this Agreement.

  15. Service Review Meetings and Continuous Improvement

    1. The Parties shall hold service review meetings at least [Frequency], and in any event following a Chronic Failure or Priority 1 Incident, at a time and place (or by video conference) agreed by the Parties.

    2. The Provider shall be represented at each meeting by its service delivery manager and such other personnel as are necessary, and shall circulate a written agenda, the Monthly Reports and supporting analyses at least [Number] Business Days beforehand.

    3. Each meeting shall review: performance against the Service Levels; Incidents, root causes and trends; Service Credits; Scheduled Maintenance; security posture; capacity and forecast requirements; risks; outstanding corrective actions; and any proposed changes to the Services.

    4. The Provider shall keep written minutes and a log of agreed actions, owners and deadlines, to be circulated within [Number] Business Days. Minutes shall be deemed approved unless the Customer objects within [Number] Business Days. No minutes shall vary this Agreement.

    5. The Provider shall continuously seek to improve the quality, efficiency and performance of the Services, shall propose at least annually improvements in technology, process and Service Levels, and shall implement those accepted by the Customer. Cost savings resulting from improvements shall be shared as follows: [Savings Allocation].

    6. The Parties shall review the Service Levels at least annually. Service Levels shall not be reduced without the Customer's written agreement, but may be increased by the Customer upon [Number] days' notice where justified by the Provider's demonstrated performance or the Customer's changing business needs.

  16. Term, Termination and Transition Assistance

    1. This Agreement shall commence on the Effective Date and, unless terminated earlier in accordance with its terms, shall continue for an initial term of [Initial Term] from the Service Commencement Date (the "Initial Term"), and shall thereafter renew for successive periods of [Renewal Period] (each a "Renewal Term") unless the Customer gives notice of non-renewal not less than [Number] days before the end of the then-current term. The Provider may elect not to renew only upon not less than [Number] days' prior written notice.

    2. The Customer may terminate this Agreement for convenience, in whole or in part, upon [Number] days' written notice to the Provider, subject to payment of fees for Services performed up to the termination date and [Early Termination Charge, if any].

    3. Either Party may terminate this Agreement upon written notice if the other Party commits a material breach that is not remedied within [Number] days after notice, or becomes insolvent, is subject to bankruptcy or similar proceedings, or ceases to carry on business. The Customer's additional termination rights are set out elsewhere in this Agreement.

    4. The Provider may terminate this Agreement for non-payment only if undisputed fees exceeding [Amount] remain unpaid for more than [Number] days after a written notice of default stating its intention to terminate, and the Provider shall not suspend the Services pending such termination.

    5. Upon expiry or termination for any reason, the Provider shall, for a period of up to [Number] months (the "Transition Period") at the Customer's request, continue to provide the Services on the terms of this Agreement, including the Service Levels, and shall provide all reasonable assistance to transfer the Services to the Customer or a replacement provider, with minimal disruption.

    6. Transition assistance shall include: delivery of all Customer Data in a commonly used, machine-readable format; documentation, configuration details and credentials; knowledge transfer; cooperation with the replacement provider; and parallel running of the Services as required. Where the Agreement is terminated due to the Provider's breach, transition assistance shall be provided at no charge; otherwise, at the rates set out in [Transition Rates].

    7. Following confirmed successful transfer, the Provider shall securely delete all Customer Data and certify such deletion in writing within [Number] days. The Provider shall not withhold any Customer Data or the Services on account of any dispute. Accrued rights and the provisions that by their nature should survive termination shall survive.

  17. Limitation of Liability and Indemnification

    1. Nothing in this Agreement limits or excludes either Party's liability for fraud, willful misconduct, gross negligence, death or personal injury caused by negligence, or any liability that cannot lawfully be limited or excluded.

    2. Subject to the preceding clause, the total aggregate liability of the Provider arising out of or in connection with this Agreement in any contract year shall not exceed the greater of [Amount] and [Number] times the fees paid and payable in that year.

    3. Subject to the first clause of this section, the total aggregate liability of the Customer arising out of or in connection with this Agreement in any contract year shall not exceed the fees paid and payable by the Customer under this Agreement in the [Number] months preceding the event giving rise to the claim.

    4. The limitations in this section shall not apply to the Provider's obligations under the following clause, to the Provider's breach of its confidentiality, data protection or information security obligations, or to the Provider's abandonment or wrongful suspension of the Services. Service Credits paid shall not count towards any limit on the Provider's liability.

    5. The Provider shall defend, indemnify and hold harmless the Customer, its Affiliates and their respective officers, directors, employees and agents from and against all losses, damages, liabilities, fines, costs and expenses, including reasonable legal fees, arising out of any third-party claim relating to: infringement or misappropriation of intellectual property rights by the Services; a Security Incident or breach of the Provider's data protection or confidentiality obligations; the Provider's negligence or willful misconduct; or the Provider's breach of applicable law.

    6. The Customer shall defend and indemnify the Provider against third-party claims arising from the Customer's use of the Services in violation of this Agreement or the Customer Data infringing the rights of a third party, subject to the limit in this section.

    7. The indemnified Party shall give prompt notice of any claim, allow the indemnifying Party to control the defense with counsel reasonably acceptable to it, and provide reasonable cooperation at the indemnifying Party's expense. The indemnifying Party shall not settle any claim imposing liability or admitting fault on the indemnified Party without its prior written consent.

    8. The Provider shall maintain throughout the Term, with reputable insurers, professional indemnity, cyber liability and general liability insurance of not less than [Amount] per claim, and shall provide evidence of coverage upon request.

  18. Governing Law and Dispute Resolution

    1. This Agreement and any non-contractual obligations arising out of or in connection with it shall be governed by and construed in accordance with the laws of [Governing Law Jurisdiction], without regard to its conflict of laws principles.

    2. The Parties shall first attempt in good faith to resolve any dispute arising out of or in connection with this Agreement by referring it to their respective service managers, who shall meet within [Number] Business Days of a written dispute notice.

    3. If the dispute is not resolved within [Number] days after the dispute notice, it shall be escalated to senior executives of each Party with authority to settle it, who shall meet within [Number] Business Days.

    4. If the dispute is not resolved within [Number] days after escalation to senior executives, either Party may refer it to mediation administered by [Mediation Institution], and the Parties shall share the mediator's costs equally.

    5. If the dispute is not resolved by mediation within [Number] days of its commencement, it shall be finally settled by [arbitration under the rules of [Arbitration Institution] by [Number] arbitrator(s) seated in [Seat], conducted in [Language] / the courts of [Jurisdiction], to whose exclusive jurisdiction the Parties submit].

    6. Nothing in this section shall prevent either Party from seeking urgent injunctive or interim relief from a court of competent jurisdiction, in particular to protect Customer Data, confidential information or the continuity of the Services.

    7. Pending resolution of any dispute, the Provider shall continue to perform the Services in accordance with this Agreement, and the Customer shall continue to pay undisputed fees. The Provider shall not suspend or withhold any Services or Customer Data on account of a dispute.

    8. If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall continue in full force. This Agreement constitutes the entire agreement between the Parties regarding its subject matter and may be amended only in writing signed by both Parties. Notices shall be in writing and delivered to the addresses set out below or as otherwise notified.

The Parties have executed this Agreement through their duly authorized representatives as of the Effective Date.

CUSTOMER

[Customer Legal Name]

Signature: [Signature]

Name: [Authorized Signatory Name]

Title: [Title]

Date: [Date]

Address for notices: [Customer Notice Address]

Email: [Customer Notice Email]

PROVIDER

[Provider Legal Name]

Signature: [Signature]

Name: [Authorized Signatory Name]

Title: [Title]

Date: [Date]

Address for notices: [Provider Notice Address]

Email: [Provider Notice Email]