The real-time workflow
The planning workflow builds the plan; this is what you do on the day the plan meets reality. Real-time management is its own cycle — watch, diagnose, decide, act, recover, communicate, review — and the hardest skill in it is knowing when not to act. This page lays the cycle out step by step, with the article, lesson and tool for each one.
1Watch the day
Is the day tracking the plan — on volume, AHT, adherence and service?
Real-time starts with seeing clearly: actuals against the plan, not just a wall of red and green. The skill is reading the floor, not just the dashboard.
2Signal or noise?
Is this a real deviation, or just the random scatter of a normal day?
Half of real-time mistakes are reactions to noise. Contacts arrive randomly, so service wobbles even when nothing is wrong — learn the size of normal before you chase a blip.
3Decide if action is needed
Does this deviation cross the line where acting beats leaving it alone?
Doing nothing is a legitimate, often correct, decision. A tolerance grid tells you when a gap is big and durable enough to be worth a lever — and when intervening would only add churn.
4Pick the lever
Which action gives the most coverage for the least disruption?
When you do act, choose deliberately from the menu — move off-phone work, shift breaks, flex overtime, re-skill, throttle outbound. The sensitivity tool shows which input is moving service, so you pull the lever that matches the cause.
5Work the backlog
For deferred work, are you clearing it fast enough to hit the promise?
Email and case work give you a backlog to manage, not a queue to answer instantly. Re-shape the day’s effort to clear the oldest items inside their deadline, using the troughs the plan gave you.
6Protect adherence — don’t weaponise it
Is the schedule being followed — and are you using adherence to help, not punish?
Adherence is how the plan’s coverage actually shows up on the floor. Used as a diagnostic it protects service; used as a stick it breeds gaming and resentment and quietly damages the coverage you were trying to defend.
7Communicate on the day
Do operations know what’s happening, what you’re doing, and what you need?
A good intervention nobody knows about still causes friction. Clear, calm, timely updates to team leaders and ops — what’s happening, the action, the ask — turn real-time from a backroom into a partnership.
8Review after the event
What did the day teach the forecast, the schedule and the playbook?
The loop closes by feeding back: a short post-event review turns today’s surprise into tomorrow’s better plan, and sends the lessons upstream to the planning workflow.
The rest of the operating cycle: planning, scheduling and quality assurance workflows. See all the tools on the calculators page, or learn it end-to-end in the real-time Academy track.