Uptime SLA Checklist: Review Availability, Exclusions and Incident Evidence

An uptime SLA is easier to review when a team can answer four questions: what service is covered, how availability is measured, which events are excluded, and what evidence supports an incident discussion. A percentage alone does not answer those questions.

This guide provides general B2B operational guidance for reviewing uptime wording in a SaaS or other service agreement. It is not legal, security, procurement or product advice. Read the complete agreement and obtain appropriate advice for decisions that carry material risk.

What is an uptime SLA?

An uptime SLA is a service-level commitment about the availability of a defined service during a stated measurement period. It may appear in a service schedule, order form, support policy or other document incorporated into the agreement.

The useful review task is to connect the stated target to the service people actually use. A target may be relevant to a whole service, a named component, a particular location or a limited group of users. The agreement should make that scope understandable.

For a broader explanation of the term, see what an SLA means in a contract.

Use an availability review checklist

Before accepting or relying on an uptime commitment, collect the current agreement, service description, SLA, amendments and referenced support materials. Then review these areas together.

• Service scope: Identify the service, components, users or locations covered by the commitment.
• Measurement method: Check how availability is calculated, which source is used and when the measurement period starts and ends.
• Downtime definition: Clarify what counts as unavailable and whether partial or degraded service is included.
• Exclusions: Note planned maintenance, customer dependencies, third-party services and other stated exclusions.
• Incident route: Confirm where an issue is reported, who receives updates and how the relevant facts are recorded.
• Remedy and claim process: Read the agreed response to a missed target alongside any notice, evidence or timing requirements.
• Change and review point: Revisit the wording when the service, dependency chain or business use changes.

Make the measurement understandable

A percentage is only useful when a reader can reconstruct it. The agreement should connect the target to a measurement period, a definition of downtime, the treatment of maintenance and a source of evidence. If a provider and customer use different monitoring sources, the agreement should make clear which source governs an SLA discussion.

For example, a team reviewing a customer-facing scheduling service could ask whether the uptime commitment concerns the whole service or only sign-in access. It could then record the relevant service, owner, measurement source, exclusions and next review point alongside the agreement. That record does not replace the contract; it helps the team find the right wording and context when a question arises.

Separate availability from the wider service relationship

Availability is one part of a service relationship. A review may also need to consider service scope, support contacts, change handling, commercial terms, dependencies and the document order of precedence. Avoid treating an uptime headline as a complete view of delivery expectations.

When a proposed service agreement needs cross-functional preparation, the SaaS agreement checklist can help structure the broader decision context. For a live negotiation, a contract negotiation tracker can keep open points, document references, owners and next actions together.

Set an incident evidence routine

When an availability concern occurs, start with the applicable agreement version and the event facts. Record the observed issue, relevant time period, service scope, sources consulted, people involved, open questions and the next decision. Keep fact-finding separate from assumptions about whether a target has been missed.

1. Locate the current SLA and every document it references.
2. Confirm which service scope and measurement method apply.
3. Collect the available incident information and relevant time period.
4. Check exclusions, notice requirements and the agreed escalation route.
5. Assign an owner for the next action and retain the decision context with the agreement.

Common review mistakes

• Comparing headline percentages without comparing the underlying definitions.
• Assuming a user-impacting issue automatically meets the agreement’s downtime definition.
• Separating the SLA from the service description, amendments or support materials it relies on.
• Recording an incident without the agreement version or evidence source.
• Waiting until a dispute to identify the owner and escalation route.

Keep uptime commitments usable

A useful uptime SLA connects service expectations to an accountable operating record: the current agreement, scope, measurement source, exclusions, owner and next review. ClearContract supports organisations in receiving, reviewing, filing, monitoring and managing contracts under customer-defined rules, while people retain decision and approval authority. If you are evaluating a more consistent way to handle contract work around service relationships, Book a demo.

Key takeaways

• An uptime SLA should be reviewed as a defined service commitment, not just a percentage.
• Scope, measurement, downtime definitions, exclusions and evidence sources shape what the target means in practice.
• Keep the current document set and incident context connected to the accountable owner and next action.
• Review the wording when service scope, dependencies or business use changes.