Ideally, SLAs will be tailored to the products and
WRITING VENDOR SLAS services the third party is providing. As you’re doing your vendor due diligence, you should make notes of WHAT IS AN SLA? things that you’ll need to see follow-up documentation Who Is Involved in Drafting? on and items where you’ll want ongoing reporting or A service level agreement, or commonly An SLA should be developed between all parties perhaps standards of conduct you need the vendor to shortened to SLA, is a key component of every involved — typically your organization and the third ascribe to. All of these will help you determine what contractual relationship with your third parties to party. You'll often see business managers, vendor sort of SLA language to include. maintain a certain level of performance. managers and legal teams providing their feedback. Some SLA examples by vendor type are: It's important that everyone works together to ensure An SLA is a documented its not only comprehensive, but also accurate and agreement that establishes consistent with risk management practices. expectations between the What Is Included Within? customer and service Core processor: Call center: reporting The SLA includes the products or services to be provider/vendor. delivered, responsibilities and contacts, timing and reporting on accuracy, on speed of answer availability and technical and call abandon rates frequency and metrics by which to measure, monitor response time and approve process effectiveness.
The information dictated in the SLA will vary heavily
based on the product or service provided, but a SLA is very crucial.
8 SLA BEST PRACTICES
Here are a few SLA best practices to be aware of:
3 Decide how the SLAs will be measured.
This means determining how frequently, what type of metrics 2 Agree on specific standards. and what kind of reports will be provided to your Work with your team to decide management team. Request that robust reporting be what the specific standards are. developed and sent without needing reminders. While it’s Whether it’s system uptime, your responsibility to track and analyze the reports provided, reliability or speed of answer, you shouldn’t need to go and ask for them each time. 1 Make sure the SLA is very straightforward. they should be consistent and Your SLAs should be specific across the board. written in layman’s terms, yet contain 4 Identify the appropriate enough detail so that point person. your organization and This goes for each side of the third party know the relationship, as well as what is expected. an escalation or alternate person if the point person is unavailable.
5 Consider procedures for
dispute resolution. 8 Review SLAs to ensure the Make sure there are pre-agreed vendor is providing what you upon procedures on how to expect and/or requested. handle disputes in any portion of It’s also a good practice to 6 Ensure provisions for the relationship – such as review early on that the items 7 Don’t forget about change management. situations in which vendors aren’t you receive from the vendor are non-compliance and Consider factors that meeting a particular standard as precisely what you’ve termination provisions. may allow for any well as scenarios where the requested. Keep your eye on You’ll want to be sure that number of changes, vendor disagrees on this the SLAs throughout the there are clear terms around such as shifts in the evaluation. Also, consider how process. Each time you receive SLA non-compliance, team, terms of the disputes will be resolved and a report, take a couple of escalation procedures or any agreement or in disaster ownership/processes for moments to make sure the behaviors that could ultimately circumstances which complaint management. vendor is actually performing lead to the termination of the may waive the SLA as expected. relationship. altogether.
Download free sample SLAs are a powerful tool to help manage