Adherence and Conformance Monitoring (generic process)

Adherence and Conformance Monitoring (generic process) is the generic process card, GP-303, for the operating process by which the real-time function of a workforce operation compares each agent's actual state with the scheduled one, separates legitimate deviation from exception, corrects the schedule of record where the schedule was wrong, hands individual patterns to the supervisor and systemic patterns to the scheduler, and keeps an audit view that survives the retirement of the scored metric. The card owns its method. The two metrics, their formulas, grace periods and tolerances are defined on Adherence and Conformance and are not restated; the activity codes the comparison depends on are governed by Activity-Code Consistency. What this card adds is the process: who looks at what, on what cadence, what happens when a deviation is found, and the point at which the ticket-based exception apparatus is replaced by a rule log. It is part of Process Standardization and sits under the real-time section of the function catalog in Anatomy of a ROC Standard. The process is drawn so that the metric is read as a signal before it is read as a verdict: the metric page records that low adherence often means the schedule is wrong rather than that the agent is non-compliant, which is why the legitimacy check and the schedule correction sit ahead of the exception path.

Process profile

Field	Generic value
Card	GP-303 · local card id assigned by the standards committee at deployment
Class	real-time, with a supporting tail: the period aggregate feeds the scheduling cycle and the weekly review
Trigger	continuous during staffed hours; the exception path triggers when a deviation exceeds the tolerance for longer than the grace period (both SET LOCALLY)
Cadence	refresh at the surface's interval (SET LOCALLY); an interval read inside the rotation of GP-301; a daily close; a period roll-up
Scope in	the comparison per agent and team; the legitimacy check; the schedule correction; the exception path in its ticket form and its rule-log form; the coaching hand-off; the audit view; the systemic read-back to scheduling
Scope out	the metric definitions, tolerances and targets (Adherence and Conformance); the lever (GP-302); the content of the coaching conversation and any disciplinary step (Performance Management); the activity-code set itself
Inputs	the schedule of record as written back by GP-302; the agent state feed; the activity-code map; tolerances, grace and targets (SET LOCALLY); the rule registry
Outputs	the live exception list; the rule log (or, before it, exception tickets); the corrected schedule; the daily summary by agent, team and interval; the coaching hand-off record; the audit extract; the systemic-signal note to scheduling
Upstream	GP-201 and GP-202; GP-302 (the write-back); Activity-Code Consistency; the adherence row of The Definitions Register
Downstream	supervisors (coaching); GP-602; Shift Design and GP-201 (systemic signals); GP-603; the variance-capture measure of Variance Harvesting
Resources	a real-time adherence surface; the schedule system of record; a rule log or a ticket system; an audit extract. Platforms are named at L3, never here
Decision points	is the deviation legitimate or an exception? does it persist past grace? does it move the interval's staffing position? is the pattern individual, team or schedule-design? does a coaching hand-off follow?
Authority tier	tier 1, the real-time analyst inside guardrails, for monitoring, the legitimacy check and the schedule correction; tier 2, the supervisor or team lead, for every conversation with an agent; tier 3, the operations manager or ROC duty lead, for a change to tolerances; tier 4, the function head, through GP-601, to retire adherence as a scored metric
Risk and compliance flags	agent-state data is employment data. In the European Union, Article 88 of the General Data Protection Regulation lets Member States and collective agreements set more specific rules for processing in the employment context, and Article 88(2) names monitoring systems at the workplace among the matters those rules address; in Germany, for example, the works council has co-determination over technical devices designed to monitor employee behaviour or performance. Adherence used as a discipline tool, and targets set high enough to be gamed, are the two failure modes the metric page documents
Variant-prone steps	who may see agent-level data; the tolerance and grace values; the hand-off path at partner supply nodes; the exception path during a platform transition
Automation candidates	13 L2 rows marked Y, every one ranked below

L1 flow

1. Load the day's schedule of record and the activity-code map; confirm the state feed is live. Owner: real-time analyst.
2. Compare actual state with scheduled state per agent and team at each refresh. Real-time analyst.
3. Raise the deviations that exceed tolerance and persist past the grace period. Real-time analyst.
4. Is the deviation legitimate: a GP-302 move not yet written back, a system fault, an approved swap? If so, go to step 5; if not, to step 6. Real-time analyst.
5. Correct the schedule of record so the metric measures the schedule the agent was actually given. Real-time analyst.
6. Act on the exception: in the ticket form, notify the supervisor and file an exception for review; in the rule-log form, record the deviation, move the break or activity inside guardrails, update the schedule and tell the agent why. Where the rule class has been released, the analyst owns the step and the rule performs it. Real-time analyst.
7. Does the deviation move the interval's staffing position? If so, hand it to GP-302. Real-time analyst.
8. Aggregate at the daily close by agent, team and interval. Reporting analyst.
9. Classify each pattern: individual, team, or schedule-design (one interval, many agents). Real-time analyst.
10. Hand off: individual patterns to the supervisor as a coaching record with its evidence and no verdict; schedule-design patterns to the scheduler. Real-time analyst.
11. Hold the coaching conversation and record its outcome; any step beyond coaching leaves this process. Supervisor or team lead.
12. Produce the audit view: the compliance extract, separable from the scored metric, retained per policy. Reporting analyst.
13. Roll up for the period and read back to scheduling and the weekly review. Reporting analyst.

L2 step table

Tolerances, grace values and platform names 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	Confirm the schedule version is the one agents received, the activity-code map matches the register, and the state feed is live	real-time analyst	schedule, version log, map, feed status	three confirmations	—	Y	GP-303.1.1
2	Compare scheduled with actual state per agent at each refresh; roll to team and interval	real-time analyst	schedule, states	deviation list, team and interval view	continuous	Y (trigger)	GP-303.2.1
3	Apply tolerance and grace (SET LOCALLY); raise only persisting deviations	real-time analyst	2.1	exception candidates	continuous	Y (trigger)	GP-303.3.1
3	Suppress deviations already explained by a written-back move	real-time analyst	GP-302 log	net list	continuous	Y	GP-303.3.2
4	Check each net deviation against moves, faults and approved swaps	real-time analyst	3.2, swap log, fault log	legitimate or exception	—	Y (offer)	GP-303.4.1
5	Write the correction to the schedule of record with a reason code	real-time analyst	4.1	corrected schedule	—	Y	GP-303.5.1
6	Ticket form: notify the supervisor, file the exception, review at the daily close	real-time analyst	4.1	ticket	SET LOCALLY	N (retired by 6.2)	GP-303.6.1
6	Rule-log form: record, act inside guardrails, update the schedule, tell the agent why	real-time analyst	4.1, guardrails	log row	—	Y (action, per class)	GP-303.6.2
7	Test the deviation's effect on the interval staffing position	real-time analyst	position	hand-off to GP-302, or none	—	Y	GP-303.7.1
8	Aggregate the day by agent, team and interval	reporting analyst	2.x to 6.x	daily summary	at close	Y	GP-303.8.1
9	Test each pattern: individual, team, or interval-wide	real-time analyst	8.1	classification	at close	Y (offer)	GP-303.9.1
10	Draft the coaching record (agent, pattern, intervals, evidence) and the scheduling note (interval, teams, suspected design cause)	real-time analyst	9.1	hand-off record, note	at close	Y (draft)	GP-303.10.1
11	Hold the conversation and record the outcome	supervisor or team lead	10.1	outcome record	SET LOCALLY	N	GP-303.11.1
12	Produce the audit extract: states, times, corrections, who saw what	reporting analyst	all	extract	at close	Y	GP-303.12.1
12	Apply retention and access per the data policy (SET LOCALLY)	reporting analyst	12.1, policy	retained extract	—	N	GP-303.12.2
13	Roll up the period and read back to scheduling and the weekly review	reporting analyst	8.1 series	period summary, read-back	per period	Y	GP-303.13.1

Variants

Recorded per Standard and Variant in Process Documentation:

• Statutory. Where a works-council agreement limits which fields the comparison may hold or who may see them, the field list is a parameter, SET LOCALLY. Where it removes the center's agent-level view entirely, steps 2 to 4 change owner at that supply node (the supply node's supervisors see the agent, the center sees the team) and take a variant row, approved by the function head on legal advice.
• Contractual. A partner contract under which only the partner's supervisors see agent-level data routes step 10 to the partner's named seat and takes a variant row, reviewed at renewal. A client contract that sets an adherence target is a parameter.
• Structural. A channel with no observable in-contact state cannot be measured as state-at-time; a conformance or output measure substitutes at steps 2 and 3 under a variant row until a time-accounting ledger exists for the channel. A self-scheduled pool where conformance is primary (Self-Scheduling and Flexible Workforce Models) changes only which metric is primary, a parameter.
• Transitional. A supply node from a predecessor organization that keeps its ticket path (6.1) until the rule log is live there holds a variant row with an expiry at that date; its automation effect reads blocks against candidate 8 below.

L3 register

Job aid	Anchored to	Form
The tolerance, grace and target values, by activity (SET LOCALLY)	steps 2 and 3	work instruction
The activity-code map and its register row	step 1	work instruction; method on Activity-Code Consistency
The legitimacy checklist (moves, faults, swaps) and the reason codes	steps 4 and 5	work instruction
The rule log layout and the guardrails per rule	step 6	playbook
The retired ticket path, with a record of what retirement removed	step 6	playbook
The coaching hand-off record and the scheduling note	step 10	work instruction
The audit extract, its access list and retention	step 12	work instruction
The watch when the state feed is down	steps 1 and 2	runbook

Automation candidates

Flagged at L2 per Process Decomposition (L0–L3); released per class of action on a published catch rate per Human Gates and Number Grades. The classes are those of Expanding Intraday Automation: trigger, notify, offer, action. The list is ordered by how easy that catch rate is to publish.

1. The comparison and the tolerance filter (2.1, 3.1): trigger class; first, since a seeded deviation is either raised or missed.
2. The day-start confirmations (1.1): deterministic; ranks after 1 because each of the three confirmations reads a different system of record and must be seeded separately.
3. Suppression of explained deviations (3.2): ranks after 2 because it depends on GP-302's write-back being complete, so a miss may belong to the other process and must be attributed before it counts.
4. The daily aggregate, the audit extract and the period roll-up (8.1, 12.1, 13.1): assembled, not decided; ranks after 3 because each is computed from the net list and inherits any miss upstream, so its own catch rate is meaningful only once 1 to 3 are published.
5. The staffing-position test (7.1): computed; ranks after 4 because it reads the position from GP-302, so a seeded error may belong to either process.
6. The legitimacy check and schedule correction (4.1, 5.1): offer class, the rule proposes and the analyst accepts; ranks after 5 because its verifier is the analyst's decision, so the catch rate needs an outcome record rather than a seeded input; action class once that rate is published.
7. Pattern classification and the hand-off drafts (9.1, 10.1): offer and draft; ranks after 6 because its verifiers, the supervisor and the scheduler, sit in other processes, so the outcome record is written there.
8. The rule-log action (6.2): action class per rule, and the rule-log form of the exception path; ranks last because it changes the floor and must pass the overseen pilot. Until a rule's catch rate is published, the same move is proposed by the rule and approved by the analyst; after it, the ticket path (6.1) is retired, and the function keeps a written record of what was retired and the risk its retirement removed, as Level 3: The Automation Layer requires.

Three rows are never candidates: the ticket path (6.1), which is retired rather than automated; the coaching conversation (11.1), a human act between a supervisor and an agent; and retention and access (12.2), which is policy. The decision to retire adherence as a scored metric is a change to the standard at tier 4. A caution attaches to candidate 8: supervisors of a reliable automation drift toward assent, so the overseer's error-injection program is what keeps the analyst's approval at step 6 a decision rather than a click.

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 ticket path with published tolerances and a coaching hand-off is at Level 2; one that has released candidates 1 to 4, runs the rule log for at least one rule class on a published catch rate, has retired the corresponding tickets and, where it chooses, has retired adherence as a scored metric in favour of outcome measures and the audit view is at Level 3, which that page names as its clearest sign; one that runs the rule-log action at every supply node, with the catch rate published per variant as Standard and Variant in Process Documentation requires, is at Level 4.

See Also

• Process Standardization — the hub and the inventory this card belongs to
• Adherence and Conformance — the two metrics, their formulas, grace periods and pitfalls
• Activity-Code Consistency — the code set the comparison depends on
• Real Time Analyst Role and Responsibilities — the seat that owns most steps
• Level 3: The Automation Layer — the rule log that replaces the exception apparatus
• Labor Law and Scheduling Compliance and Union Environments and WFM — the statutory variant in depth
• Decision Authority Tiers in Workforce Operations — the tiers in the profile
• 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)