Daily ROC Routine

The Daily ROC Routine is the structured set of daily activities that govern how a Resource Optimization Center (ROC) operates in production. It defines what a ROC analyst does at each phase of the operating day, how shifts hand off, what is measured, and how the ROC interfaces with the contact centers it monitors. The routine is the procedural backbone that turns the ROC concept from an organizational chart into reliable real-time operations.

This page is the practitioner reference for that routine. It documents the activities a ROC analyst performs across a 24-hour operating cycle and the rhythms that frame those activities — pre-shift preparation, shift opening, intraday monitoring, shift handoff, and end-of-day reconciliation.

Operating Rhythm

The ROC operates on a continuous monitoring cycle, but the cycle is divided into recognizable phases that align with shift structure and contact center business hours:

Pre-Shift (60 minutes before shift start) — preparation, intelligence gathering, planning
Shift Open (first 30 minutes) — handover, system validation, alignment with operations
Active Monitoring (bulk of shift) — continuous monitoring and intervention
Shift Close (last 30 minutes) — wrap-up, handoff preparation, summary documentation
Post-Shift (after shift end) — incident reconciliation, daily reporting, trend capture

The exact clock times depend on the operation. A 21x5 / 18x2 ROC (the typical first-generation implementation) has different phase timing than a 24x7 follow-the-sun ROC, but the structural phases are the same.

Pre-Shift: 60 Minutes Before Shift Start

The hour before a shift starts is dedicated to building situational awareness so the analyst opens the shift informed rather than reactive.

Intelligence Review

Read the previous shift's handoff log — open incidents, ongoing monitoring, watch items
Review the operations calendar — marketing campaigns launching, product releases, billing cycle peaks, weather events
Check the forecast for the shift period — expected volume, AHT, scheduled staff, planned shrinkage
Review the previous day's variance pattern — did the forecast hold, where did it diverge, was the divergence understood

System Health Validation

Verify all monitoring dashboards are live and refreshing
Confirm telephony and ACD platform status (no overnight incidents lingering)
Confirm WFM platform connectivity and data freshness
Validate that automation platforms (intelligent automation, routing engines) are operating normally

Plan-of-the-Day

Identify the highest-risk intervals in the day — typically open of business, post-lunch return, or known marketing-driven spikes
Identify any planned operational changes — schedule republish, training events, system maintenance
Confirm staffing for the ROC itself — primary, secondary, escalation contacts

Shift Open: First 30 Minutes

The shift transition is the highest-risk window in ROC operations. Issues that the previous shift was managing must transfer cleanly, and the incoming analyst must validate that monitoring is live.

Verbal Handover

A face-to-face or recorded verbal handover covering:

Active incidents and their current state
Items being watched but not yet escalated
Schedule republishes, automation rule changes, or routing changes made during the prior shift
Open items requiring follow-up during the new shift

Documentation Handover

Review the shift log written by the outgoing analyst
Confirm any incident tickets are correctly stated and acknowledged
Sign in to incident management and ticket systems

Operations Touchpoint

Acknowledge the morning operations stand-up or its equivalent — site managers, real-time supervisors, escalation contacts know the ROC is on shift and reachable
Confirm shift coverage and contact methods at each contact center site

Active Monitoring: Continuous

The bulk of the shift is structured continuous monitoring. The analyst rotates through a small number of recurring observation cycles rather than staring at a single dashboard.

Service Level Monitoring

Real-time service level versus threshold across all queues and channels
Trend direction — is the queue stabilizing, deteriorating, or recovering autonomously?
Cross-site comparison — when one site struggles and another is stable, that is a routing-rebalance opportunity, not just a queue alarm

Queue Performance Analytics

Calls in queue and longest call waiting
Queue depth trends over the trailing 15-30 minutes
Predictive queue performance projections (where the analytics support them)

Workforce Adherence

Forecasted vs. actual volume at the current interval
Scheduled vs. on-phone agent count
Adherence pattern across teams and channels — sustained dips signal break or training overrun, not random variation

External Signal Monitoring

Weather and emergency conditions in operating regions
Business event triggers (marketing campaign go-live, product release, billing cycle)
Infrastructure status — telephony, network, internal systems

Variance Response

When monitoring identifies a variance event, the response follows a structured incident pattern documented under Event Management. The ROC analyst:

Classifies the severity and event type
Opens an incident ticket if the severity warrants
Diagnoses cause using the Real-Time Cause and Effect Fishbone
Coordinates response — break adjustment, schedule shift, automation rule activation, escalation to operations
Communicates status to affected sites and management
Logs the resolution and learnings

The analyst's job is not to manually fix every variance — modern operations rely on Intelligent Automation for the routine variance signatures. The ROC's role is to monitor that the automation is operating correctly and to take over the cases automation cannot resolve.

Variance Harvesting Coordination

In a Variance Harvesting operating model, the ROC's role expands from variance suppression to variance capture. When forecasted variance windows arrive, the ROC coordinates the harvesting moves — coaching pushed to free agents, micro-learning delivered during dips, protected breaks during sustained surges. The ROC tracks Variance Capture Efficiency (VCE) as a core operational metric.

Shift Close: Last 30 Minutes

The shift close mirrors the shift open in importance. The transition out must leave the next shift positioned to succeed.

Wrap-Up

Resolve incidents that can be closed during the shift
Update incident state for incidents that will continue
Reconcile shift activity log — events, decisions, escalations, communications

Handover Preparation

Write the handover log for the incoming analyst
Identify watch items the next shift should monitor closely
Surface any unresolved questions that need next-shift attention

Operational Communication

Confirm any outstanding commitments to operations sites
Communicate end-of-shift status to escalation contacts
If a critical incident is mid-flight, ensure the verbal handoff covers full context

Post-Shift: Reconciliation and Reporting

After the shift closes, the analyst (or a designated end-of-day analyst) handles the reconciliation and reporting work that does not fit inside the active monitoring window.

Incident Reconciliation

Confirm all incident tickets are correctly stated and assigned
Validate root-cause classifications
Surface incidents that suggest a systemic issue rather than a one-off

Daily Summary

A daily summary report capturing:

Service level performance vs. plan, by site and queue
Major incidents — count, severity, root cause classification
Variance pattern — where the day diverged from forecast and why
Automation health — were the rules effective, were there false-positive alerts, were there events automation should have caught and did not
Items requiring follow-up

Trend Capture

Update trend logs for slow-developing issues (multi-day attrition spikes, recurring queue patterns, automation degradation)
Surface trend data for the weekly ROC review

Tools and Systems

The ROC operates with a small, well-defined toolkit:

Event management system — incident classification, tracking, and reporting (OpsCenter or equivalent)
Ticketing system — Severity 4 standard requests, change requests, enhancement requests
Real-time monitoring dashboards — service level, queue depth, adherence, agent state
WFM platform — scheduled vs. actual workforce data
CCaaS or ACD platform — real-time and historical interaction data
Real-time automation platform — automation rules and intervention logs
Communication platforms — voice contact to sites, chat for asynchronous coordination, email for documentation

Severity Framework

The ROC operates against a standard severity framework that determines response speed and escalation:

Severity 1 — Critical customer impact, multi-site or platform-level. Immediate response, leadership notification, executive communication.
Severity 2 — Significant customer impact at a single site or queue. Rapid response, site management notification, hourly status updates.
Severity 3 — Moderate impact, contained to a single team or shift. Active management, status updates as warranted.
Severity 4 — Standard requests, no customer impact. Ticket-managed, queue-prioritized.

The severity classification drives whether the response is voice (Severity 1-3 — telephone contact required) or ticket-based (Severity 4 — standard ticketing system).

Maturity Model Position

The Daily ROC Routine evolves with organizational maturity in the WFM Labs Maturity Model™:

Level 2 — Foundational (Traditional WFM Excellence) — The routine exists but is heavily reactive. Real-time analysts respond to alerts and exception conditions; the variance response is largely manual.
Level 3 — Progressive (Breaking the Monolith) — Automation handles routine variance signatures. The ROC analyst's role shifts toward monitoring automation health, intervention on cases automation cannot handle, and variance harvesting coordination.
Level 4 — Advanced (The Ecosystem Emerges) — The ROC operates by exception. Most of the day is automation-managed; the analyst's attention focuses on novel patterns, automation tuning, and cross-system orchestration.
Level 5 — Pioneering (Enterprise-Wide Intelligence) — The routine extends to enterprise-wide signal monitoring (HR, CRM, finance) and the ROC contributes operational truth back to enterprise decision-making.

The structure of the routine — pre-shift, open, monitor, close, post-shift — remains stable across maturity levels. What changes is the analyst's relationship to automation: from manual operator at Level 2 to exception manager at Level 4-5.

Anonymous

Search