Call Center Outsourced evidence brief · Desk review · Published
How should a Philippines call center measure schedule adherence across client time zones?
A measurement protocol for schedule adherence when the site, the client, and the reporting tool use different clocks.

On this page
- Key stats
- Key takeaways
- Question and scope
- Why adherence needs one clock
- Define scheduled and actual time
- Treat time-zone conversion as data
- Handle daylight-saving transitions
- Allocate cross-zone coverage
- Separate adherence from conformance
- Report exceptions by cause
- Reconcile payroll and phone logs
- Set tolerances by queue state
- Review the overnight window
- Document the client reporting view
- Test the definition with a dry run
- Limits of the evidence
- Manager review questions
- Conclusion
- Put this into a support lane
- Related operating guides
- FAQs
- Sources
Key stats
- 2.67 million U.S. customer service representative jobs in 2025 (BLS)
- $21.53 median hourly wage in May 2025 (BLS)
- 3 years payroll-record retention under DOL rules
Key takeaways
- Write down the reporting clock, interval length, and time-zone identifiers before calculating.
- Map states that exist in one source but not the other, and publish the mapping.
- Separate adherence from conformance and report exception causes beside the percentage.
- Reconcile paid hours, scheduled hours, and phone-log hours with a named bridge.
Question and scope
This brief asks how a contact center in the Philippines should measure schedule adherence when its client and workforce system use different time zones. The population is one site and one client queue during a declared four-week window, and the unit is a scheduled interval for a named agent rather than a shift total. Freeze the interval length, the schedule version, and the time-zone convention before looking at results. The question is whether the agent was in the right state at the right time, not whether the shift looked full. Record every input source so an analyst can reproduce the result, and keep the signed scope note with the extract.
Why adherence needs one clock
Adherence compares the scheduled state with the actual state at a point in time, so both inputs must share one clock. If the schedule is stored in the client's time zone and the phone log in the site's time zone, the comparison can be off by hours without anyone noticing. Convert both inputs to one reporting clock before calculating and store the original values beside the converted ones. A report that cannot show its clock and conversion cannot be audited, and a supervisor cannot defend a disputed exception. Name the owner who approves a clock change.
Define scheduled and actual time
Write down what counts as scheduled work: queue time, meetings, training, breaks, and approved offline tasks. Then define the actual states from the phone system and the workforce tool, including the states that exist in only one source. Publish a mapping rule with examples so supervisors apply it the same way, and review the mapping whenever a tool or break policy changes. Ambiguous states are the main source of false adherence exceptions, so the definition deserves more attention than the calculation. Include a worked example for the overnight shift.
Treat time-zone conversion as data
Record the source time zone, target time zone, and conversion method for every extract. Use named time-zone identifiers rather than fixed offsets because offsets change with daylight saving in some client locations. The Philippines does not observe daylight saving, but the client may. Test the conversion on a date when the client clock changes, because a conversion that works in June may fail in November. Keep the conversion script under version control so a later change can be explained, and log the conversion time for each extract.
Handle daylight-saving transitions
Some client regions shift their clocks twice a year, creating a missing or repeated hour in the local schedule. Decide in advance how the site will represent that hour in both the schedule and the phone log. Document whether the repeated hour is counted once or twice and which state owns it. Run a test file through the reporting pipeline on the transition date instead of discovering the rule after payroll closes. Publish the rule with the monthly report so the client can reconcile its own view, and keep a copy of the transition test file.
Allocate cross-zone coverage
A site may cover a client queue that spans two client time zones. Allocate each scheduled interval to the queue it serves, not to the agent's home time zone. If one agent covers both zones, split the shift at the published boundary and label each part. Show the allocation in the report so a reader can see why the same hour appears twice, because an unlabeled split looks like double counting. Keep the allocation rule stable across the comparison period, and review the split rule with the client each quarter.
Separate adherence from conformance
Adherence asks whether the agent was in the scheduled state at the scheduled time, while conformance asks whether total time matched the schedule over a period. A shift can conform while the agent was late, and it can be adherent while total hours differ because of an approved extension. Report both measures with their definitions and show one example of each. Combining them into one score hides the operating problem and makes coaching harder to target. Show both measures on the same monthly page.
Report exceptions by cause
Group exceptions into late start, early departure, extended break, unapproved offline time, system outage, and schedule change. Each cause has a different owner and a different fix, so a system outage should not be coached as an agent behavior issue. Publish the cause counts beside the adherence percentage and review the top cause with the supervisor each week. The cause mix is more actionable than the headline number because it points to the control that failed. Send the top cause to the client with the case examples.
Reconcile payroll and phone logs
Compare paid hours, scheduled hours, and logged-in hours before publishing adherence. Differences may come from rounding, break policy, manual adjustments, or an approved schedule change. Build a bridge that names each adjustment and its owner, and keep the bridge with the monthly report. Do not force the numbers to match by editing the phone log, because an unexplained gap is a finding rather than a rounding error. Resolve the largest gap before the client review, and ask payroll to sign the reconciliation before release.
Set tolerances by queue state
A strict start-time tolerance may fit a scheduled queue opening but not a shift that begins during a system outage. Define tolerance bands by queue state and document the reason for each band. A two-minute grace period for a normal start and a fifteen-minute window for a declared outage are different rules. Apply the rule that was in force at the time, not the rule published after the fact, and record the approval for any exception. Store the tolerance version with each exception decision.
Review the overnight window
Overnight shifts cross the date boundary and often cross a client time zone. Assign the shift to one reporting date and state the rule. Check that the phone system and the workforce tool use the same date boundary. Review the first and last intervals separately because handoffs and breaks cluster there, since a daily total can look acceptable while the handoff hour is uncovered. Report the overnight window as its own line in the client summary, and compare the handoff hour across the last four weeks.
Document the client reporting view
The client may see a dashboard built on a different clock or interval. Publish a short mapping from the site's measure to the client's measure, including exclusions, rounding rules, and the schedule version. If the client's dashboard cannot show the mapping, send a note with the monthly report. A number that cannot be reconciled will be challenged, so keep the mapping next to the dashboard link and update it when the schedule changes. Ask the client to confirm the mapping each quarter.
Test the definition with a dry run
Before using the measure for a decision, run a dry run on a past week with known exceptions. Ask a supervisor to predict the adherence result from the schedule, then compare it with the calculation and investigate every difference. The dry run should include a holiday, an outage, and a schedule change. If the measure cannot reproduce known events, it is not ready. Record the differences and the fix before the first live report, and repeat the dry run after a major system upgrade.
Limits of the evidence
This protocol relies on the accuracy of the schedule, the phone log, and the payroll record. It cannot determine whether an exception was justified without the approval record. Local labor rules and client contracts may add requirements that the measure does not capture. Treat missing approvals as open questions rather than automatic violations, and document each limitation beside the result. The measure should inform a management conversation, not replace it, and keep the missing approvals visible in the review pack.
Manager review questions
Managers should ask which schedule version was used and which time zone served as the reporting clock. They should also ask how breaks and approved offline tasks were mapped and what caused the largest exception group. The remaining questions are which gaps are still unexplained, who owns the correction, and when the fix will be tested. Review these points monthly and after any schedule or telephony change. Record the answers with the published measure so the next review starts from evidence, and send the answers to the client before the monthly call.
Conclusion
Adherence is trustworthy when the clock, the states, and the exclusions are written down before the report is published. Convert every input to one reporting clock, keep the original values, and reconcile the result with payroll. Report causes beside percentages so managers can act on the right problem. A measure that survives a dry run is ready for a client conversation, and it should be reviewed again when the schedule or telephony changes. Review it again when the schedule or telephony changes.
Put this into a support lane
Bring one queue, its reporting extract, and the manager who owns the operating decision.
Review the queueRelated operating guides
FAQs
Should the report use the site clock or the client clock?
Use one documented reporting clock and keep the original values so either side can reconcile the result.
How do we handle daylight saving?
Test the conversion on the transition date and document how the missing or repeated hour is counted.