Schedule adherence is the share of an agent's scheduled time that they spent doing what the schedule said. Divide the minutes in adherence by the minutes scheduled and multiply by 100. The arithmetic is one line, and it is the only part of this metric everyone agrees on.
Three published definitions are in circulation and they do not put the same thing in the numerator. Underneath that sit the measurement window, the threshold settings in your workforce management tool, and your exception policy. What follows is one agent's eight-hour day scored four ways, a spec sheet so your team picks a definition on purpose, the arithmetic that turns an adherence target into a headcount decision, and the pairing that stops the number being gamed.
What is schedule adherence in a call center?
Schedule adherence measures whether agents were where the schedule put them, interval by interval, across the working day. It is a timing measure rather than a productivity one. An agent can be perfectly adherent and handle very few contacts, and an agent who handles plenty of contacts at the wrong times of day can score badly.
Timing is the whole point, because service capacity cannot be stored. Managers vary the number of available agents to track the predictable variation in arrival rates, which is why capacity planning happens interval by interval rather than by the day (Gans, Koole and Mandelbaum, Telephone Call Centers: Tutorial, Review, and Research Prospects, Manufacturing and Service Operations Management 5, 2003). Nothing you do at 11:00 recovers the callers who abandoned at 9:40. That is also why adherence belongs in the same intervals the staffing model used, which is the part most definitions skip.
Three published formulas, three different numerators
The formula is stable and the numerator is not. Each of these is in current use, and each counts a different set of minutes as adherent, so one agent day produces a different percentage depending on which one your tool implements.
| Source | Published formula | What counts in the numerator |
|---|---|---|
| TechTarget's contact center definition, June 2024 | (actual time available for calls / total time scheduled to work) x 100 | Only time the agent could take a contact |
| Assembled's workforce management guide, March 2022 | total minutes worked / total minutes scheduled x 100 | Any time at work, on or off the phones |
| Call Centre Helper's calculation guide, 2017 | (minutes in adherence / total scheduled minutes) x 100 | Time that matched the scheduled activity, including meetings and training |
All three were published and current when we read them on October 17, 2026.
The gap between the first and the other two is an agent doing scheduled off-phone work. Under the first definition that agent is non-adherent for every minute of it. Under the other two they are adherent. On a team with regular training or back-office blocks, that one choice moves the reported number further than any coaching program will.
Find out which definition your workforce management platform calculates before you set a target. The target your team inherited was almost certainly set against a different one.
The two losses that one percentage hides
An agent can fail the schedule in two unrelated ways, and most reporting adds them together. The research literature keeps them apart. A standard ACD report records three separate sources of lost agent productivity, and only the last two are about the schedule at all (Gans, Koole and Mandelbaum, 2003).
| Loss | How the report expresses it | Usual cause | What actually fixes it |
|---|---|---|---|
| Idle time | 100 percent minus occupancy | Random variation in when calls arrive | The staffing model, not the agent |
| Logged in but unavailable | 100 percent minus the on-production percentage | Off-phone work, long after-call work, a system problem | Procedure and tooling |
| Not logged in at all | 100 percent minus the schedule-available percentage | Late starts, long breaks, absence | Scheduling and management |
In that report, the schedule-available figure "relates the actual time spent logged-in to the original plan," and the paper notes that the last two measures "are often monitored to diagnose perceived disciplinary problems." The word carrying the weight there is perceived. A 25-minute gap caused by a frozen desktop and a 25-minute gap caused by a long lunch land in the same cell of most adherence reports, and the fix for one has nothing to do with the fix for the other.
Separating them is a reporting change rather than a new tool. Report unavailable-while-logged-in apart from not-logged-in-at-all, and most of the coaching argument resolves itself.
One agent's day, scored four ways
Here is a full shift. The agent is scheduled 8:00 to 16:00 with a 15-minute break at 10:00, a 30-minute lunch at 12:00 and a 15-minute break at 14:00, which leaves 420 scheduled on-phone minutes.
| When | What happened | Minutes away from the plan |
|---|---|---|
| 8:00 to 8:07 | Started seven minutes late | 7 |
| 10:15 to 10:22 | Came back from the morning break seven minutes late | 7 |
| 12:30 to 12:35 | Came back from lunch five minutes late | 5 |
| 13:30 to 13:55 | Logged in, desktop frozen, could not take calls | 25 |
| 16:00 to 16:20 | Stayed on calls 20 minutes past the end of the shift | None scheduled |
Two choices decide the score. The first is whether any time at work counts or only time available for contacts. The second is whether the day is totaled up and compared with the plan, or matched interval by interval so that work outside a scheduled window earns no credit.
| Totaled across the shift | Matched interval by interval | |
|---|---|---|
| Any time at work counts | 421 of 420 minutes, reported as 100 percent | 401 of 420 minutes, 95.5 percent |
| Only time available for contacts counts | 396 of 420 minutes, 94.3 percent | 376 of 420 minutes, 89.5 percent |
The top left cell is the one to watch. The 20 minutes the agent stayed late cover the 20 minutes they were missing earlier, so a shift total says the day was perfect. The staffing model disagrees, because the seven minutes missing at 8:00 were seven minutes missing from the 8:00 interval, and no amount of 16:10 fixes that.
Configuration then moves the number again. Amazon Connect, to take one platform's published behavior, lets you set an allowable variance of 1 to 10 minutes on each activity and reports adherence with and without those thresholds (Schedule Adherence, AWS administrator guide). Put a five-minute threshold on each activity and the strictest cell above rises from 89.5 to 93.1 percent. Exception code the frozen desktop out of the schedule instead and it reads 95.2 percent. Do both and the same day scores 99.0 percent.
One shift, no disagreement about the facts, and a defensible range from 89.5 to 100 percent. None of those numbers is wrong. They answer different questions, and a team that has not written down which question it is asking will spend its time arguing about the answer.
A schedule adherence definition spec sheet
Seven decisions produce your number. Settle each one in writing and store it next to the dashboard, because changing any of them resets the trend you were reading.
| Decision | The options | Why it moves the number |
|---|---|---|
| Numerator | Available for contacts only; any time in the scheduled activity, including meetings and training | Worth 6 points on the day above once the window is interval matched, and more on a team with regular off-phone work |
| Window | Shift total; interval matched at the length your staffing model uses, usually 30 minutes | A shift total lets time worked late repay time missed in a peak |
| Cap | Credit capped at the scheduled minutes in each interval; overflow allowed to offset other intervals | Without the cap, interval matching collapses back into a shift total |
| Thresholds | None; an allowable variance per activity, commonly 1 to 10 minutes; reported with, without, or both | Five minutes of grace per activity moved the strict score by 3.6 points |
| Exceptions | Which codes remove time from the denominator, who approves them, and the filing deadline | Removing one 25-minute outage moved the strict score by 5.7 points |
| Scope | Per agent, per team, per interval, and which of those anyone is held to | Per-agent publication turns a planning statistic into a performance review |
| Review | Who can change the six rows above, and how often | A definition change in the middle of a quarter destroys the comparison |
The spec sheet matters more than the settings you pick. A team that measures the strict way and knows it will manage a 90 percent number sensibly. A team that cannot say which of four numbers is on the report will chase the wrong agents.
Schedule adherence and conformance answer different questions
Conformance asks whether an agent worked the total amount of time they were scheduled to work. Adherence asks whether they worked it at the scheduled times (Call Centre Helper, 2017). The day above conforms perfectly, at 421 minutes against a 420-minute plan, while scoring 89.5 percent on strict adherence. Separating those two cases is the reason both metrics exist.
| The question | The metric | Read it when |
|---|---|---|
| Did we have the coverage the plan called for in each interval? | Adherence, interval-matched | You are diagnosing missed service level in specific half hours |
| Did the agent work the hours they were paid for? | Conformance | You are looking at timekeeping rather than coverage |
| Were agents busy during the time they were available? | Occupancy | You are judging whether the schedule is sustainable |
| Did the team follow the rules while handling contacts? | Compliance, scored through quality assurance | You are reviewing how calls were handled, not when |
Compliance gets confused with adherence often enough to earn its own row. It covers the rules followed during the work rather than the timing of the work.
What is a good schedule adherence target?
No research benchmark exists to point at. The literature treats the figure as a local operating standard that each center maintains for itself rather than a published number (Gans, Koole and Mandelbaum, 2003), and the range repeated most often in the industry, 85 to 95 percent, carries the explicit caveat that no universal benchmark exists (Call Centre Helper, 2017). Derive your target from what a missing agent costs you in your worst interval.
The conversion is straightforward. If an interval needs 20 agents available, the schedule has to carry more than 20 people to deliver them.
| Adherence in the interval | Agents to schedule for 20 available | Extra schedule slots |
|---|---|---|
| 95 percent | 22 | 2 |
| 90 percent | 23 | 3 |
| 85 percent | 24 | 4 |
| 80 percent | 25 | 5 |
Treat that as a planning heuristic rather than a benchmark. It assumes adherence loss spreads evenly across the interval, which it does not, and it rounds up because you cannot schedule a fifth of a person. What it does show is that the distance between an 85 percent team and a 95 percent team in one peak interval is two schedule slots, which is a cost you can price against the management effort needed to close the gap.
One trap before you add that buffer. If your shrinkage factor was estimated from historical actuals rather than from planned time off, it already contains the adherence loss. The gross-up factor that turns required agents into scheduled agents is commonly estimated from the same on-production and schedule-available statistics adherence comes from (Gans, Koole and Mandelbaum, 2003). Applying a shrinkage factor built that way and then adding an adherence buffer on top books the same lost time twice. Our guide to workforce management covers where shrinkage belongs in the staffing arithmetic.
The number that keeps adherence honest
Adherence averages across intervals and the cost of a missing minute does not. A team at 95 percent whose deviations all land in the two busiest half hours is in worse shape than a team at 90 percent whose deviations sit in a quiet afternoon, and the headline number cannot tell them apart.
Two corrections cover most of it:
- Weight each interval by the agents it required, so a shortfall in a peak counts for more than one in a dead hour. The weighted number comes out lower than the unweighted one, and it is the one that explains your service level.
- Pair adherence with the share of callers who waited at all in the same intervals. If adherence improves and that share does not, either the deviations were never in the intervals that mattered or the staffing requirement itself was wrong. Both of those readings are in our guide to call center metrics.
There is a gaming problem worth naming too. Under the availability definition, an agent sitting in an available state and taking very little work scores 100 percent. Reading adherence next to contacts handled per scheduled hour closes that gap without turning either number into a target of its own.
What changes when AI agents cover part of the day
Adherence only exists where a schedule does. Contact centers point a Telvana agent at a slice of their volume in one of four ways: an option in the phone menu, overflow and after hours, a dedicated line for a program or a client, or outbound campaigns. Three of those take intervals off the roster rather than making them easier to staff.
Nights and weekends are where that lands hardest. Those intervals run the thinnest coverage with the least slack, so one late return is the difference between an answered call and an abandoned one, and they are the hardest shifts to get people to take. Covering them with an agent removes the schedule, not just the deviation.
It also invalidates your interval weights. When a call type leaves the human queue, the intervals that bind move, and a target weighted against last quarter's peaks is aimed at the wrong half hours. Rerun required agents per interval before you renegotiate anything, using the deflection-adjusted staffing worksheet rather than scaling the old plan down by the share of calls that went away.
The limit is worth stating plainly. Calls that need a person transfer to your team under rules you set, so the intervals receiving those transfers still need people in them, and those are the intervals to weight most heavily in whatever target you land on. For which call types an agent can finish on its own, start with our guide to adding AI agents to a call center. For the numbers this one sits next to, the metrics and operations guides cover the rest of the dashboard.
Frequently asked questions
What is schedule adherence?
Schedule adherence is the share of an agent's scheduled time spent doing what the schedule called for, expressed as a percentage. It measures timing and coverage rather than output. An agent who works a full shift at the wrong times scores badly, because the staffing plan needed them available in specific intervals.
How do you calculate schedule adherence?
Divide the minutes in adherence by the total scheduled minutes and multiply by 100. The result depends on what you count as adherent and on whether you total the shift or match interval by interval. Write both choices down before you compare agents or set a target against the number.
What is a good schedule adherence target?
No published research sets one, and the 85 to 95 percent range quoted across the industry carries the caveat that no universal benchmark exists. Derive yours from coverage instead: work out how many extra schedule slots each adherence point costs you in your busiest interval, then decide what that is worth.
What is the difference between schedule adherence and conformance?
Conformance asks whether an agent worked the right total amount of time. Adherence asks whether they worked it at the scheduled times. An agent who starts late and stays late conforms perfectly and adheres poorly, so a center chasing coverage reads adherence while a center chasing timekeeping reads conformance.
Is schedule attainment the same as schedule adherence?
No. Schedule attainment is a manufacturing term for the share of a production plan completed in a period. The contact center pair is adherence and conformance. If attainment turns up in a contact center report, check how it has been defined locally, because it is not standard usage here.
Should breaks count against schedule adherence?
Scheduled breaks are part of the schedule, so taking them on time is adherent under every definition in use. Overrunning them is not. What varies between platforms is the allowable variance, often configurable from 1 to 10 minutes per activity, so a five-minute overrun may or may not reach the number at all.
How do you improve schedule adherence?
Start by splitting the two losses, because unavailable-while-logged-in is usually a tooling or procedure problem and not-logged-in is usually a scheduling or management one. Then fix the exception process so system failures leave the number. Individual patterns are the last place to look, not the first.
Where to start
Pull one week of adherence for one team and recalculate it the strict way, interval matched and counting only time available for contacts. Compare that with the number on your report. The distance between them tells you what your current target actually means. If the strict number falls apart in specific intervals rather than across the whole day, you have a coverage problem, and the first question is which call types have to be in that queue at all.
Telvana builds AI agents that answer calls, texts and web chats for contact centers, and transfers to your team under rules you set. Pricing starts from $399 a month based on call volume, plus a one-time setup fee. Book a demo with your busiest intervals and the call types in them, and you will see which ones an agent can take and hear it handle one.