> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vendor SLAs

> Track the service levels a vendor commits to: adding an SLA, the SLAs Coverbase creates from contracts, recording a value each period, reading the history, how Measurement due moves forward, statuses, owners and reminders.

For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.

> [!NOTE]
>
> This guide is part of the [User Guides](https://docs.coverbase.com/user-guides/overview.md) collection. It covers the SLAs column on a vendor's or service's **Performance** tab. For the rest of the vendor page, see [The vendor record](https://docs.coverbase.com/user-guides/vendor-record.md). For contract terms more broadly, see [Contract dates and reminders](https://docs.coverbase.com/user-guides/contract-dates-and-reminders.md). For the API, see [Vendor SLAs](https://docs.coverbase.com/api-reference/assessment-administration.md#vendor-slas).

An SLA is a measurable service level a vendor has committed to, such as "99.9% monthly uptime" or "P1 first response within 30 minutes". Each SLA has a target, an owner on your side, a measurement due date and a status. Each time someone measures it, they record the value, and Coverbase keeps every value with the target and status it had at that point.

The mistake people make most often is editing the SLA and overwriting the current value each month. That still works and the old value is kept, but the new value is dated today, so last month's figure reads as this month's. Use **Record value** instead: it asks which date the value covers.

## Where SLAs live

* A vendor's page, **Performance** tab: the **SLAs** column lists every SLA on the vendor, including the ones scoped to a single service. Each card shows the service it belongs to.
* A service's page, **Performance** tab: the same column, limited to that service's SLAs. An SLA you add here is scoped to the service.

Each card shows the metric, **Target**, **Current** (the newest value recorded), **Owner** and **Measurement due**, with the status on the right. Hover a card to edit or delete it.

## Adding an SLA

Click **Add SLA** at the top of the column and fill in what you know. Only **Name** is required.

| Field | What to enter |
| - | - |
| **Name** | What the SLA is called, for example "Platform uptime". |
| **Status** | Where the SLA stands today. See [Statuses](#statuses). New SLAs start **On track**. |
| **Service** | **All services**, or the one service the SLA applies to. Hidden when you add from a service's page. |
| **Category** | Optional. A risk domain, so the SLA can be grouped with others in the same area. |
| **Metric** | What is measured, for example "P1 first response time". |
| **Target** | The committed level as the contract states it, for example `99.9` or `< 1 hour`. Free text. |
| **Current value** | The latest value, if you already have one. Later values are better entered with **Record value**. |
| **Unit** | For example `%`, `min` or `hours`. Shown after the target and every value. |
| **Frequency** | How often the vendor reports or you measure it, for example `Monthly`. See [How Measurement due moves forward](#how-measurement-due-moves-forward) for the wording Coverbase understands. |
| **Measurement due** | When the next value is expected. This drives the reminders. |
| **Owner** | A person or a user group. A group resolves to one accountable person, and the card shows both. |
| **Description** | Anything else, such as the contract clause it comes from. |

## SLAs created from contracts

When Coverbase analyzes a contract and finds service level terms, it creates an SLA for each one. Its name, metric, target, unit, frequency and description come from the contract. It has no value, owner or measurement due date, so nobody is reminded about it until you add them.

Where the SLAs go depends on what the contract is linked to:

* **The contract is linked to services.** Each linked service that has no SLAs of its own gets a copy of every SLA found. A service that already has any SLA is skipped.
* **The contract is not linked to a service.** The SLAs are added to the vendor, but only if the vendor has no vendor-wide SLAs yet.

Coverbase never edits or replaces an SLA that already exists. If a renewal changes a target, update the SLA by hand.

After a contract is analyzed, open the vendor's **Performance** tab and give each SLA you plan to track an **Owner** and a **Measurement due** date. Delete the ones you will not track.

## Recording a value

1. On the SLA's card, click **Record value**.
2. Enter the **Value**. The unit is in the field label, and the target is shown below it for comparison.
3. Set **Measured on** to the date the value covers. For a monthly report, use the last day of that month. It defaults to today.
4. Choose the **Status** the value puts the SLA in. It defaults to the current status.
5. Optionally add a **Note**, for example why a target was missed.
6. Click **Save**.

If the value is the newest one by **Measured on** date, it becomes the SLA's **Current** value and the SLA takes the status you chose. A value dated earlier than the newest one goes into the history without changing **Current**, the status or the due date. That is how you fill in months you missed.

**Record value** is not offered on an SLA measured from a vendor status page. Those values are recorded automatically.

Typing a new value into **Current value** in **Edit SLA** also adds it to the history, dated today, with the SLA's status at that moment. It moves **Measurement due** the same way, unless you change the due date in the same edit.

## Reading the history

Click **History** on an SLA's card to see every value, newest first. Each entry shows:

* the value and the status recorded with it
* the **Measured on** date, the target the SLA had when the value was recorded, and who recorded it
* the note, if there is one

The target is the one in force at the time, so changing the target later does not rewrite how earlier months compared. A value that was on the SLA before history was kept shows **Earlier entry** instead of a name.

To remove a value entered by mistake, hover it and click the delete icon. If it was the newest value, the value before it becomes **Current** again, and if it was the only value, **Current** is cleared. Deleting a value does not change the SLA's status or due date.

## How Measurement due moves forward

When you record the newest value and the SLA has both a **Measurement due** date and a frequency Coverbase understands, the due date moves forward one period.

| Frequency wording | Period |
| - | - |
| `Daily` | 1 day |
| `Weekly` | 1 week |
| `Bi-weekly`, `Fortnightly` | 2 weeks |
| `Monthly`, `Once a month` | 1 month |
| `Bi-monthly` | 2 months |
| `Quarterly` | 3 months |
| `Semi-annual`, `Half-yearly`, `Twice a year` | 6 months |
| `Annual`, `Annually`, `Yearly` | 1 year |
| `Every 2 weeks`, `Every 6 months`, and other `every <number> <days, weeks, months, quarters or years>` | That interval |

Capitalization does not matter. When the wording is understood, the **Record value** dialog says that Measurement due will move forward.

A value only counts toward the due date when its **Measured on** date is less than one period before that due date. For example, with a monthly SLA due on November 5, a value measured on October 31 moves the due date to December 5. A value measured on August 31 goes into the history and leaves the due date on November 5.

If the next due date is still in the past, for example because nothing was recorded for three months, it keeps moving forward one period at a time until it is after today. If the frequency is something like "Per incident", or the SLA has no due date, set **Measurement due** by hand in **Edit SLA**.

## Statuses

| Status | Use it when |
| - | - |
| **On track** | The latest value meets the target. New SLAs start here. |
| **At risk** | The value is close to the target, or trending toward a miss. |
| **Breached** | The vendor missed the target. |
| **Met** | The commitment is fulfilled, for example a one-time delivery SLA. |

You set the status. Coverbase does not compare the value with the target, because targets are free text such as `< 1 hour` or `4 business days`.

When an SLA changes to **Breached**, Coverbase opens a finding on the vendor titled `SLA breached: <SLA name>`, assigned to the SLA's owner and due on the SLA's measurement due date. It opens one finding each time the status changes to **Breached**, not for every value recorded while it stays there. Work the finding as described in [Findings and remediation](https://docs.coverbase.com/user-guides/findings-and-remediation.md).

## Owners and reminders

The SLA's owner gets a reminder 7 days before **Measurement due**, 1 day before it, and 1 day after it. An SLA with no owner or no due date sends no reminders.

Reminders arrive as in-app notifications. The email version is off by default. Each person can turn it on under **Account → Notifications**, row **SLA measurement due reminder**. See [Email and notifications](https://docs.coverbase.com/user-guides/email-notifications.md#the-notification-catalog).

Because recording a value moves **Measurement due** forward, the reminders follow the SLA's cadence without anyone resetting the date.

## Deleting an SLA

Hover the card and click the delete icon. The SLA leaves the list along with its history, and it stops sending reminders. Findings it opened stay open.

## Troubleshooting

| Problem | What to do |
| - | - |
| "I recorded a value and **Current** did not change." | The value's **Measured on** date is earlier than the newest value in the history, so it was filed as an earlier month. Check the date, or delete it and record it again with the right one. |
| "**Measurement due** did not move." | The SLA has no due date, its frequency is not one Coverbase understands, the due date was changed in the same edit, or the value is dated one period or more before the due date. Set the frequency to one of the words in [How Measurement due moves forward](#how-measurement-due-moves-forward), or set the due date by hand. |
| "There is no **Record value** or **History** button." | The SLA is measured from a vendor status page, and its values are recorded automatically. |
| "The owner never got a reminder." | The SLA needs both an owner and a **Measurement due** date. Email reminders are off by default; check **Account → Notifications**. |
| "Contract analysis did not create SLAs for a service." | That service already had at least one SLA. Coverbase only fills a service or vendor that has none. Add the missing SLAs by hand. |
| "The SLA is breached but no finding appeared." | The finding opens when the status changes to **Breached**. If the SLA was already **Breached** when created, change it to another status and back, or open a finding by hand. |

## Related

> [card] [The vendor record](https://docs.coverbase.com/user-guides/vendor-record.md)
>
> The vendor page, its tabs including **Performance**, and services.

> [card] [Findings and remediation](https://docs.coverbase.com/user-guides/findings-and-remediation.md)
>
> What happens to the finding a breached SLA opens.

> [card] [Email and notifications](https://docs.coverbase.com/user-guides/email-notifications.md)
>
> Turning on the SLA measurement due reminder email.

> [card] [Vendor SLAs API](https://docs.coverbase.com/api-reference/assessment-administration.md#vendor-slas)
>
> Create, update and list SLAs, and record values, from another system.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.