← sources

First time setting SLA tiers for our internal ticket queue - please tear it apart

source: reddit (reddit:sysadmin)published 2026-09-16 16:37ingested 2026-09-17 02:38

retained text

Small support team, first time putting real SLA tiers on our ticket queue. Before this goes in front of my team I'd rather get picked apart here than find out later what's unrealistic, here's the draft in text.

|Tier|What it covers|Response|Resolution/mitigation|
|:-|:-|:-|:-|
||
|||||
|P0|System down, payroll-impacting|1hr biz / 2hr after-hours|Workaround same day|
|P1|Blocking a business process|4hr biz / next business day|1-3 business days|
|P2|Config/security/report request|1 business day|Scoped within 3 days|
|P3|Enhancement, nice-to-have|3 business days|Roadmap/backlog|

Specifically want to know:

* Does P0's "same day" promise sound realistic, or is that the kind of thing that looks fine on paper and falls apart the first time it's tested?
* How do you handle the clock when you're waiting on the requester? Right now we pause it and follow up every 10 business days, but I have no idea if that's normal.
* If any of you are Workday admins specifically: do you even have formal SLAs for your ticket queue, or is it all informal? Could not find a single public writeup of how a Workday/ERP team does this, which is part of why I'm asking strangers instead.

Go ahead and please rip it apart

document fetched 2026-09-17 00:38 · canonical https://reddit.com/r/sysadmin/comments/1wi2dih/first_time_setting_sla_tiers_for_our_internal