Real-Time Adherence: Control room
Objective. Open the live Control Room, read it as the floor-wide health view for the current moment, and name which of the three adherence layers a given signal belongs to.
The Control Room answers 'right now, is my floor on plan and is that plan producing work?' - the single live view a supervisor keeps open during a shift so drift is caught while the day is still fixable.
See it in the demo
What this screen answers
The customer question is: at this moment, is the floor doing the planned activity, and is that activity delivering the work we need? A Sales person opens it to show that one live board carries schedule, work and output adherence together, not just presence. A CSM opens it at shift start to establish the day's baseline and to confirm a named owner is actually watching the room live - the whole value of RTA is intraday, so a Control Room nobody looks at during the shift delivers nothing.
The task
Scope the room to the team, site or queue you care about and to the current interval, then read it top-down: overall health first, then where it is thin, then who is driving it. From here you move outward to Coverage and intraday for the interval picture and inward to Live adherence for the individual. Treat the Control Room as the entry point, not the place you resolve a case. Exact filter controls and panel labels are SME-validation-pending - drive at the level of 'scope to team and current interval', not invented buttons.
How to read it
The classic misread is treating a green board as proof the work is getting done. Green on schedule adherence means people are logged in and in the planned state - it says nothing about whether that time became work or met standard. Always ask which layer a number is reporting before you react to it. A red state is also not automatically a problem: an agent can be legitimately reassigned to an off-schedule task to protect a hotter queue, which shows as non-adherent while being exactly the right call. The room flags where to look; it does not pass judgement.
Honest limits
The Control Room proves the model is live on seeded demo data; it does not prove a specific customer's real-time latency or that their schedule and activity feeds are wired. Freshness and which schedule/activity sources are supported are production-dependent - confirm with product. The output layer visible here is only as trustworthy as the underlying output standard and capture coverage, so in an unvalidated account read it as directional. Do not quote a refresh interval or integration as fact.
Interpretation check
A green Control Room means people are present and on-state - not that the work is getting done. Never let a customer read overall schedule adherence as proof of productivity; that is what the work and output layers are for.
In the field
KnackGlobal (RCM, ~6,000 seats): a live floor view on time-sensitive claim queues is where same-day drift turns into missed filing or appeal windows, so a watched Control Room has a direct revenue-cycle cost attached.
Practical task
Open the Control Room, scope it to one team and the current interval, and write a 3-line shift-start reading: overall state, the one layer you would watch most closely today and why, and the named owner plus response-time target you would hold them to.
Self-check
A supervisor glances at a mostly-green Control Room and says 'we're fine today.' What do you check before agreeing?
Which layer is green. Schedule adherence green only confirms presence and state. Check work and output adherence for the same scope before concluding the plan is actually producing work.
You see a red (non-adherent) agent. Why is that not automatically a problem to fix?
The agent may have been deliberately reassigned to protect a hotter queue, which shows as off-schedule while being the correct call. A red state is a prompt to look, not a verdict.
Why does a CSM care whether anyone is watching the Control Room live, not just that it exists?
RTA's value is intraday intervention. A room nobody watches during the shift turns into an after-the-fact report, which can only apologise for drift, not fix it. Adoption requires a named live owner and a response-time target.
Verified vs demo. The Control Room is live in the demo at /#/control on seeded data. Exact filter controls, panel labels, figures, refresh latency and which schedule/activity integrations feed it are SME-validation-pending; confirm with product.