Service Level Agreement
SLA and service priority — clear commitments, every time
Brocent commits to defined response and resolution times for every support request. Our P1–P5 priority system ensures the right engineer and urgency level is applied to every incident.
STANDARD SERVICE WINDOW
8×5
Monday–Friday, 9 business hours per day. Emergency extension available for non-business hours and weekends.
PREMIUM SERVICE WINDOW
24×7
Available 24 hours, 7 days a week. Supports P1/P2 emergencies with 4-hour onsite response at any time.
Every project has different SLA requirements, and we can agree a project-level SLA to fit your project's needs.
Priority Definitions
P1–P5 response & resolution commitments
| Priority | Definition | First Response | Remote Support | Onsite | Resolution |
|---|---|---|---|---|---|
| P1 | Critical System service halted or severely degraded. Users cannot access any business resources. | 15 min | 30 min | 4 BH or Planned | 8 BH |
| P2 | High Part of the system halted or degraded. Users can access the system but encounter errors. | 15 min | 30 min | 4 BH or Planned | 24 BH |
| P3 | Medium Some users or systems have trouble accessing the system, but critical components are working. | 30 min | 60 min | NBD or Planned | 48 BH |
| P4 | Low Some system features have a problem or need improvement, but users can operate normally. | 60 min | 120 min | NBD or Planned | 48 BH |
| P5 | Routine No system issue — planned or routine IT request. | 60 min | 240 min | NBD or Planned | 72 BH |
BH = Business Hours. NBD = Next Business Day. Response times are subject to service window (8×5 or 24×7) and contract T&C.
Priority examples
Critical
- Some users cannot log in to critical systems
- Common IT tools (Email, Finance, HRIS) inaccessible
High
- System data cannot be read or written
- System performance very slow with obvious errors
Medium
- Some users face system errors
- Isolated access issues not affecting the wider team
Low
- User does not know how to use a system feature
- System feature improvement request
Routine
- New IT installation or settings
- IT offboarding tasks
- Password reset / user management
Priority Matrix
Impact × Urgency → Priority
Priority is determined by combining business impact level and urgency. Our service desk automatically applies this matrix when triaging every incoming ticket.
| Business Impact ↓ / Urgency → | Critical | High | Medium | Low |
|---|---|---|---|---|
| Critical | P1 | P1 | P2 | P4 |
| Serious | P1 | P2 | P3 | P4 |
| Medium | P2 | P2 | P3 | P4 |
| Minor | P2 | P3 | P3 | P4 |
Change Management
System change categories
EMERGENT
Must be made immediately to prevent business impact. Technical assessment and client approval mandatory before change.
HIGH
May cause limited impact. Change made immediately when client is available. Technical assessment and client approval required.
MEDIUM
Preventive change to address known issues or potential risk. Can be planned jointly with client.
LOW
Performance improvement change. Can be planned jointly with client with no urgency.
Guides & resources
SLA & service-desk concepts explained
IT Support SLA Priority Levels Explained: P1, P2, P3 & P4 Response and Resolution Times
A plain-English guide to IT support priority levels — how P1, P2, P3 and P4 are defined, calculated from impact and urgency, and tied to the response and resolution targets in your SLA.
Read the guide →Severity vs Priority in IT Incidents: How the Impact and Urgency Matrix Works
Severity says how bad an IT incident is; priority says what gets worked first. Learn the impact urgency matrix, with a worked example and a rollout checklist.
Read the guide →L1, L2 and L3 Support Levels Explained: Who Does What and How Tickets Move Between Them
What level 1, level 2 and level 3 IT support each handle, how tickets are handed over, and how to split the tiers when you outsource your service desk.
Read the guide →IT Escalation Matrix Template: Functional and Hierarchical Escalation, Contacts and Time Limits
An IT escalation matrix template you can copy: functional and hierarchical escalation, contacts, time limits and notification steps, written as numbered lists.
Read the guide →Incident Management Process: The Lifecycle from Report to Closure, with Roles and Time Limits
The incident management process step by step: log, categorise, prioritise, diagnose, resolve, close. With roles, example time limits and a ticket template.
Read the guide →Major incident management: the process, roles and communication plan
Major incident management explained: how to declare one, the step-by-step process, roles, communication cadence, and how it differs from problem management.
Read the guide →MTTR, MTBF and MTTA meaning: definitions, formulas and worked examples
MTTR meaning explained with MTBF and MTTA: what each stands for, the formulas, worked examples, and which ones belong in an IT support SLA report.
Read the guide →First Call Resolution (FCR): Definition, Formula and How to Improve Your FCR Rate
First call resolution (FCR) for IT support: the definition, how to calculate the FCR rate, what pushes it up or down, and practical ways to improve it.
Read the guide →SLA vs OLA vs UC: How the Three Agreements Fit Together in Outsourced IT
SLA vs OLA explained, plus the underpinning contract (UC): who signs each, what each promises, and how they stack up when IT support is outsourced.
Read the guide →Service Request vs Incident: Three Questions to Tell Them Apart, With 20 Examples
Service request or incident? Use three decision questions, 20 classified examples and the different handling flow for each, so tickets reach the right queue.
Read the guide →What Is an SLA in IT Support? Meaning, Contents and What to Check Before You Sign
What is an SLA in IT support? The meaning, what a service level agreement contains, how response and resolution times differ, and what to check before signing.
Read the guide →Service Credits and a Performance Bond: What an Enforceable IT SLA Looks Like at Renewal
For the CFO or group operations director of a Hong Kong trading and distribution group renewing an IT contract whose SLA was met on paper and missed in practice. Why the measurement layer — clock start, pause rules, reclassification, auditable ticket data — matters before any credit rate; how service credits, caps, earn-back and set-off against invoices work as mechanisms; when a performance bond or parent guarantee is proportionate; and the exit and documentation clauses that often matter more. A commercial guide, not legal advice.
Read the guide →
Want to discuss your SLA requirements?
Every Brocent engagement is backed by a written SLA. Talk to our team to discuss response times, service windows, and the right plan for your business.
Related research