Real-Time Lever Deployment (generic process)

Real-Time Lever Deployment (generic process) is the generic process card, GP-302, for the process by which the real-time function of a workforce operation closes a confirmed intraday variance: it selects the cheapest lever that will close the projected gap, obtains the authority the lever needs, executes it, writes the move back to the schedule of record, validates the result at the next interval and records what was done. The card owns its method. The taxonomy of levers by deployment speed is on Real-Time Schedule Adjustment, the economics and fairness of overtime and voluntary time off on Overtime and Voluntary Time Off (VTO) Management, the principle that a surplus is a window to use on Variance Harvesting, and the order in which automation is extended across the levers on Expanding Intraday Automation; none is restated. What this card adds is the ladder ordered by cost and reversibility rather than by speed, with the direction each rung applies to, the step sequence with one owning seat per step, the exit from the ladder to placement, and, for each lever, the class of automated action it is. It is part of Process Standardization and sits under the real-time section of the function catalog in Anatomy of a ROC Standard. The operations-research literature framed the problem two decades ago: a planned schedule must be modified during the day when capacity diverges from demand, and the quality of those modifications materially affects the day's service outcome.

Process profile

Field	Generic value
Card	GP-302 · local card id assigned by the standards committee at deployment
Class	real-time
Trigger	a confirmed variance from GP-304, or a projected gap from the intraday reforecast (GP-104); deficit or surplus
Cadence	event-driven, many times per operating day; each deployment is bounded by a checkpoint at the next interval
Scope in	the ladder inside one supply node: selection, authorization, execution, notification, write-back, validation, capture; both directions
Scope out	detection (GP-304); the reforecast (GP-104); reallocation across supply nodes, which is placement at the intraday horizon (Placement Engine Architecture) governed as a routing change (Vendor Change Control for Routing); queue priority adjustment, which shapes demand through routing and is excluded as a routing change for the same reason; a declared incident (Incident Management for Contact Centers); a change that outlives the day (Schedule Maintenance)
Inputs	the variance record (direction, magnitude, persistence, projected window); the staffing position by interval; lever availability; the guardrails and budgets (SET LOCALLY); the constraint register
Outputs	the deployment record (lever, scope, time, authorizer, cost, outcome); the updated schedule of record; notifications; the validation result; the capture row for the forecaster and for the variance-capture measure of Variance Harvesting
Upstream	GP-304; GP-104; the published schedule with its pooled off-phone budget (GP-201); the rule registry of Level 3: The Automation Layer
Downstream	GP-303, which measures against the written-back schedule; GP-602; the forecaster; overtime and time-off cost reporting; the catch-rate program of The Agent Overseer; placement, which receives the case when the ladder is exhausted
Resources	a schedule system of record with intraday write access; a notification channel to agents; the routing administration surface; an offer mechanism; the rule registry. Platforms are named at L3, never here
Decision points	will the variance outlast the cheapest lever's window? is the lever available? is it inside tier-1 guardrails? did it close the gap at the checkpoint? is the remaining gap a supply-node gap?
Authority tier	tier 1, the real-time analyst inside guardrails, for rungs 1 to 3 and for rungs 4 and 5 inside the pre-authorized budget; tier 2, the supervisor or team lead, for offers beyond the budget, mandatory overtime and off-phone deferral beyond the budget; tier 3, the operations manager or ROC duty lead, for the incident declaration; tier 4 by exception when the day's cost line is exceeded
Risk and compliance flags	overtime premiums and hour thresholds; rest-break statutes bounding a break move; co-determination over changes to working time; fairness and income stability in time-off offers; an off-phone budget raided rather than delivered; a write-back failure, after which adherence measures a schedule nobody is running
Variant-prone steps	the break-move window; the overtime solicitation order; time-off caps; the exit to placement; the notification channel
Automation candidates	13 L2 rows marked Y, every one ranked below

L1 flow

The flow walks a ladder. Each rung is cheaper and more reversible than the one above, and the rule is to deploy the lowest rung that closes the projected gap, stepping up only when the checkpoint shows it did not; the formal procedures for intraday updating formalize lever selection on cost. Mandatory overtime and training recall sit above the ladder at tier 2 and are not generic rungs.

Rung	Lever	Direction	Cost	Reversible
1	break and lunch resequencing	deficit and surplus	none	within the day
2	off-phone activity move	deficit (defer), surplus (accelerate)	none in cash; opportunity cost against the off-phone budget	if re-placed the same week
3	skill rebalancing inside the supply node	deficit	none in cash; occupancy and quality effect on the receiving queue	at the next interval
4	voluntary time off offer	surplus	negative (saves hours)	not once the agent has left
5	voluntary overtime or shift extension offer	deficit	premium hours	not once worked

The ladder ends at the supply-node boundary. When it is exhausted and a gap remains, the case leaves this process: moving work or supply between supply nodes is placement at the intraday horizon, decided by the supply-node owner through the placement engine, as Expanding Intraday Automation draws the line, and it is not a rung.

1. Receive the confirmed variance with its direction, magnitude, persistence and projected window. Owner: real-time analyst.
2. Project the staffing position for the remaining intervals from the reforecast. Real-time analyst.
3. Will the variance outlast the effective window of rung 1? If not, rung 1 only; if so, open the ladder. Real-time analyst.
4. Check availability at each rung from the bottom up. Real-time analyst.
5. Select the lowest rung that closes the projected gap; record why the rungs above were not taken. Real-time analyst.
6. Is the selected rung inside tier-1 guardrails? If not, escalate with a one-line case. Real-time analyst.
7. Authorize a lever outside the guardrails, producing a decision per lever rather than a click. Supervisor or team lead.
8. Execute the move and notify each affected agent and supervisor with the reason; where a rule class has been released, the analyst owns the step and the rule performs it. Real-time analyst.
9. Write the move back to the schedule of record so that adherence, payroll and the next reforecast read it. Real-time analyst.
10. Validate at the next interval checkpoint: has the position closed? Real-time analyst.
11. Did it close? If so, stand down and log; if not, return to step 5 one rung up; if the ladder is exhausted or the cause is external, go to step 12. Real-time analyst.
12. Declare an incident where the cause is external or the breach is wide, or hand the remaining gap to placement as a supply-node case. ROC duty lead.
13. Capture: write the deployment row to the day log and the capture record; propose any event the day revealed to the forecaster. Real-time analyst.

L2 step table

Thresholds, budgets and platform names never appear here; they are L3 values marked SET LOCALLY. Sub-steps without a duration take minutes.

Step	Sub-step	Owner (seat)	Inputs	Outputs	Duration	Automation candidate	Documentation join key
1	Accept the variance record; confirm direction, magnitude and persistence are present	real-time analyst	GP-304 record	accepted variance, branch by direction	—	Y (trigger)	GP-302.1.1
2	Extend the reforecast to end of day; compute the gap per interval against the net requirement	real-time analyst	actuals, reforecast, requirement	gap table	one interval	Y (computed)	GP-302.2.1
3	Estimate the persistence window from pattern and matched events	real-time analyst	collision calendar, pattern library	window	—	N	GP-302.3.1
4	List breaks and lunches not yet taken inside the movable window, and off-phone activities in the window with their move cost	real-time analyst	schedule of record, activity calendar, budget	rung 1 and 2 candidates	—	Y	GP-302.4.1
4	List cross-trained agents whose home queue is at or above requirement	real-time analyst	skill matrix, positions	rung 3 candidates	—	Y	GP-302.4.2
4	List agents eligible for time off or overtime within caps and hour thresholds (SET LOCALLY)	real-time analyst	eligibility rules	offer list	—	Y	GP-302.4.3
4	Where the gap exceeds what rungs 1 to 5 can close, write the supply-node case for placement	real-time analyst	gap table, constraint register	placement case	—	N	GP-302.4.4
5	Select the lowest rung that closes the gap; record the rungs passed over	real-time analyst	2.1, 4.x	selection	—	Y (offer)	GP-302.5.1
6	Test the selection against the guardrails (SET LOCALLY); if outside, draft the case: what, by how much, how long, what was tried	real-time analyst	guardrails, 5.1	inside, or a case	—	Y (draft)	GP-302.6.1
7	Authorize with the decision recorded per lever	supervisor or team lead	case	signed authorization	window SET LOCALLY	N	GP-302.7.1
8	Issue the move: break move, activity move, skill change or offer broadcast	real-time analyst	authorization	executed move	—	Y (action, per class)	GP-302.8.1
8	Notify each affected agent and supervisor with the reason	real-time analyst	8.1	notification record	—	Y (notify)	GP-302.8.2
8	Run the offer acceptance queue in the published order (SET LOCALLY)	real-time analyst	offer list	accepted list	—	Y (action, within budget)	GP-302.8.3
9	Write the move to the schedule of record with its reason code; confirm the adherence, payroll and reforecast feeds received it	real-time analyst	8.x	updated schedule, confirmation	—	Y	GP-302.9.1
10	Compare the position at the checkpoint with the projected close	real-time analyst	actuals	validation result	one interval	Y (computed)	GP-302.10.1
11	Stand down, step up one rung, or pass to step 12	real-time analyst	10.1	branch	—	N	GP-302.11.1
12	Declare the incident, or hand the supply-node case to placement	ROC duty lead	4.4, 11.1	severity row, or placement hand-off	—	N	GP-302.12.1
13	Write the deployment row (lever, scope, cost, authorizer, outcome); propose events the day revealed	real-time analyst	all	log row, event proposal	—	Y (offer for the event)	GP-302.13.1

Variants

Recorded per Standard and Variant in Process Documentation:

• Statutory. Rest-break law fixes how far a break may move and the latest point it may be taken: a parameter of rung 1, SET LOCALLY. Where a works council's co-determination over temporary changes to working hours requires its consent to an overtime offer, step 7 gains a consent sub-step at that supply node and takes a variant row, approved by the function head on legal advice.
• Contractual. A collective agreement or partner contract that fixes the overtime solicitation order, or forbids time-off offers to a cohort, parameterizes 4.3 and 8.3. Supply a client contract dedicates is already excluded from rung 3 by the constraint register. A partner supply node where the center may not instruct agents directly routes step 8 through the partner's seat and takes a variant row, reviewed at renewal.
• Structural. A single-skill supply node has no rung 3; one with no pooled off-phone budget has no rung 2 in the surplus direction. Both are shell marks (NOT INVENTORIED at that supply node), not variants. A channel without an observable in-contact state runs the ladder on backlog and elapsed time; the gap computation at step 2 changes and takes a row.
• Transitional. A unit whose predecessor platform cannot accept an intraday write keeps a manual write-back under a row with an expiry at the platform cut-over; its automation effect reads blocks against candidates 2 and 7 to 10 below until then.

L3 register

Job aid	Anchored to	Form
The guardrails per rung: scope, cost, hours, the movable window, the pre-authorized offer budget	steps 4 to 6	work instruction
The ladder as the function runs it, with the rungs it does not have	step 5	playbook
The escalation case format and the response windows per tier	steps 6 and 7	work instruction
The offer broadcast: eligibility, order, caps, the agent-facing wording	steps 4.3 and 8.3	work instruction
The write-back: reason codes and the feeds that must confirm	step 9	work instruction
The checkpoint, the step-up rule and the exit to placement	steps 10 to 12	playbook
The ladder when the schedule system cannot accept a write	step 9	runbook

Automation candidates

These are the heart of the card. Each lever is a class of automated action in the vocabulary of Expanding Intraday Automation: trigger (the rule detects and writes), notify (the rule tells a person), offer (the rule proposes and a person decides at the action gate of Real-Time Agents), action (the rule executes inside guardrails). Release is per class on a published catch rate, as Human Gates and Number Grades states for the whole wiki; the overseer who publishes it is defined on The Agent Overseer. The list is ordered by how easy that catch rate is to publish, which runs with the human-factors ladder of automation levels from information to execution. The three tiers Real-Time Schedule Adjustment uses for automated levers are tiers of automation (fully automated, recommended and approved, human only), not the seat tiers of this card's profile.

1. Variance intake and position projection (1.1, 2.1): trigger and computed; a seeded variance either produces a record or does not, so the catch rate is the easiest to publish.
2. Notification and write-back (8.2, 9.1): deterministic; ranks after 1 because its errors, a notification not delivered or a feed not confirmed, are observable only after a lever has run, so the seeded test needs a lever in flight.
3. The checkpoint comparison (10.1): computed; ranks after 2 because it reads the projected close from 2.1 and inherits that projection's error.
4. The availability lists (4.1, 4.2, 4.3): ranks after 3 because they read three systems of record whose definitions must agree before a seeded miss can be attributed to the rule.
5. The ladder proposal and the guardrail test with its case draft (5.1, 6.1): offer class; ranks after 4 because a proposal is judged against the analyst's decision, so the catch rate needs an outcome record at the action gate rather than a seeded input.
6. Event proposals to the forecaster (13.1): offer class; ranks after 5 because its verifier is the forecaster, outside the real-time function, so the outcome record is written in another process.
7. Break and lunch resequencing (8.1, rung 1): the first lever to reach the action class, because it is cost-free and reversible within the day; ranks after 6 because an executed move changes the floor, so its catch rate is measured on the overseen pilot and not on seeded records alone.
8. Off-phone activity move (8.1, rung 2): action class in both directions, with the off-phone budget as its guardrail; ranks after 7 because two directions must be seeded and a miss costs a budget rather than a break.
9. Offer broadcast and acceptance queue for time off and overtime (8.1 and 8.3, rungs 4 and 5): action class inside the pre-authorized budget, offer class to tier 2 outside it; ranks after 8 because an accepted offer is irreversible, so the pilot must run long enough to seed acceptance errors. Only the broadcast and the queue are automated.
10. Skill rebalancing (8.1, rung 3): offer class until the routing change it implies has its own catch rate; ranks last because the workforce rule and the routing rule become one here and must be measured together.

Five rows are never candidates. The persistence estimate (3.1) is judgment against matched events. Authorization (7.1) is a gate, and a gate at which the holder must produce a decision is a human act by definition. The stand-down or step-up (11.1) is the analyst's reading of the checkpoint. The declaration and the hand-off to placement (4.4, 12.1) belong to the severity matrix, to tier 3 and to the supply-node owner.

Maturity Model Position

Four scales on this wiki use the word level; the launch page states which is which. On the WFM Labs Maturity Model™ a function that runs the ladder from a written playbook with a checkpoint and a write-back is at Level 2; one that has released candidates 1 to 3 and candidate 7 on a published catch rate, with the larger rungs behind approval, is at Level 3; one that extends the action class rung by rung under a standing catch-rate program is at Level 4.

See Also

• Process Standardization — the hub and the inventory this card belongs to
• Real-Time Schedule Adjustment — the lever taxonomy by speed and the automation tiers of automated levers
• Overtime and Voluntary Time Off (VTO) Management — rungs 4 and 5 in depth
• Variance Harvesting — the surplus direction, the response library and the variance-capture measure
• Intraday Management — the cycle this process is the actuator of
• Expanding Intraday Automation — the expansion order, the supply-node boundary and the catch rate before any action class
• Decision Authority Tiers in Workforce Operations — the tiers in the profile and at step 7
• Standard and Variant in Process Documentation — how the variants above are recorded
• Wiki:Packs/Process Decomposition — the pack that localizes this card (CP-OPS-001)