Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides 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. For contract terms more broadly, see Contract dates and reminders. For the API, see 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.

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. 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

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.

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. 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

The vendor record

The vendor page, its tabs including Performance, and services.

Findings and remediation

What happens to the finding a breached SLA opens.

Email and notifications

Turning on the SLA measurement due reminder email.

Vendor SLAs API

Create, update and list SLAs, and record values, from another system.