Compliance Review for Workforce Operations (generic process)

Compliance Review for Workforce Operations (generic process) is the generic process card, GP-603, for the periodic review by which a workforce function tests its published schedules, its time records and its placement decisions against four sources of obligation: labour law, collective agreements and works-council rulings, client contractual terms, and the requirements of the audits it is subject to. The review produces findings, each with an owner and a remediation date, and an evidence trail that shows what was tested and how; and it is the process by which a local difference discovered in operation becomes either a variant row or a preference finding under Standard and Variant in Process Documentation. The obligations themselves are not restated here: the statutes are on Labor Law and Scheduling Compliance, the bargaining provisions on Union Environments and WFM, the certification requirements on COPC Standard and operational implementation on Labor Compliance Scheduling. It is part of Process Standardization and sits among the cross-cutting sections of the function catalog in Anatomy of a ROC Standard.

The card has the shape of a management-system audit: a programme with a scope and a sampling rule, evidence gathered against criteria, findings classified, corrective action owned and verified, and a record kept. What is specific to a workforce function is the object under test: a schedule is a promise made to an employee under rules that differ by jurisdiction and contract, and a time record is the record the statute requires and the evidence a regulator or an arbitrator asks for first.

Process profile

The profile extends the L0 identity fields of Process Decomposition (L0–L3). Local values are held by the deploying function and marked SET LOCALLY. Authority tiers follow the cross-cutting row of Decision Authority Tiers in Workforce Operations.

Field	Generic value
Card	GP-603 · local card id assigned by the standards committee at deployment
Class	supporting, in the catalog's four-class vocabulary (strategic · real-time · both · supporting)
Trigger	the review calendar; by event, a change to a statute, agreement or contract, a new supply node (a site, centre or partner) or client, a grievance, an audit notice
Cadence	a sample review monthly and a full review quarterly is typical [A] (SET LOCALLY); the external audit cycle as the certification body or the client contract sets it
Scope in	published schedules and their change logs; time records (hours, rest intervals, breaks, overtime); the distribution of overtime and voluntary time off; placements of work at supply nodes; the predictability-pay and premium-pay record; findings, remediation and evidence
Scope out	legal interpretation (the legal partner); building a compliant schedule (GP-201, which encodes the rules as hard constraints); payroll computation; the external audit itself; any disciplinary matter
Inputs	the obligation register (every statute, agreement clause, contract term and audit item that touches scheduling, time or placement, with jurisdiction and effective date); the schedule as published and every change with timestamp and reason; time records; the variant register; the placement gate record; prior findings
Outputs	the findings register (class, severity, owner, date); the remediation plan; the evidence pack; variant requests and preference findings routed to GP-601; the attestation
Upstream	the legal and HR partners (obligation changes); the works-council liaison (rulings); the placement function (new contracts and supply nodes); the certification body's calendar
Downstream	GP-201 and GP-202 (constraint changes); GP-302 (lever-policy limits); GP-601 (variant rows and preference findings); payroll (liabilities found); the executive issue register for a finding with statutory exposure
Resources	the obligation register; the schedule change log; a time-record extract; the sampling rule; the findings register; an evidence repository with a retention rule. Platforms are named at L3, never here
Decision points	in scope of an obligation; deviation or documented exception; severity; breach, missing variant or preference; escalation or disclosure
Authority tier	the review at tier 3 (the function's compliance lead); closure of a compliance finding, and severity confirmation, at tier 4 (the function head); a finding with statutory exposure to the executive sponsor, by exception; interpretation of an obligation always with the legal partner, never decided in the review
Risk and compliance flags	the review is itself evidence, and one without a sampling rule proves nothing; a finding with no owner recurs; time records are personal data, accessed on need; back-pay and premium-pay liabilities; grievance and unfair-practice exposure where scheduling is a mandatory subject of bargaining
Variant-prone steps	the sampling rule by jurisdiction; works-council access to findings; a client's audit rights over the sample and the evidence format; the retention period
Automation candidates	seven L2 sub-steps (listed below)

L1 flow

Owner seats in parentheses, one per step. Decisions are questions.

1. Has any statute, agreement, contract or audit item changed since the last review? Refresh the obligation register on the legal partner's notices (compliance lead).
2. Which sites, supply nodes, periods and rules are in this review's sample? (compliance lead)
3. Extract the schedule as published, its change log and the time records for the sample (reporting analyst).
4. Do the schedules meet the working-time rules: daily and weekly rest, maximum average hours over the reference period, consecutive days, breaks? (compliance analyst)
5. Were changes made inside a notice window, and where they were, was the predictability or premium pay generated and paid? (compliance analyst)
6. Were overtime and voluntary time off offered in the order the agreement requires? (compliance analyst)
7. Is work placed only at supply nodes where statute and contract permit the construct? (placement and vendor lead)
8. Is each deviation a finding, or a documented exception already on the variant register? (compliance lead)
9. What is the finding's severity, and is its cause a breach, a missing variant, or a local preference? The legal partner advises on the obligation's meaning (compliance lead).
10. Route each finding: a breach to a remediation owner and date; a missing variant to GP-601 as a variant request; a preference to the process owner as a preference finding (compliance lead).
11. Assemble the evidence pack: what was tested, the sample, the results, the sign-offs (compliance analyst).
12. Does any finding carry statutory exposure, which goes to the executive sponsor by exception, or require disclosure to a works council or a client? (function head)
13. Attest the review; close remediated findings from prior reviews; carry open ones with their age (function head).

L2 step table

The documentation join key is the key an L3 job aid, a ticket and a variant row cite. Jurisdictions' values, thresholds and system names are L3 values.

Step	Sub-step	Owner (seat)	Inputs	Outputs	Duration	Automation candidate	Documentation join key
1	Collect obligation changes from the legal partner, the HR partner and the works-council liaison; update the register row (source, jurisdiction, effective date, steps constrained)	compliance lead	their notices	the current register	one sitting	N	GP-603/1.1
2	Apply the sampling rule (SET LOCALLY) to sites, supply nodes, periods and rules; include every open finding's area	compliance lead	the register; the rule	the sample	one sitting	N	GP-603/2.1
3	Extract the schedule as published with its timestamp, every change with timestamp, reason code and approver, and the time records; restrict access to the review seats	reporting analyst	the systems of record	the schedule, change and time sets	minutes [A]	Y	GP-603/3.1
4	Test each shift pair for the daily rest interval and each seven-day period for the weekly rest; test maximum average hours over the reference period and consecutive days (SET LOCALLY)	compliance analyst	the schedule set; the rules	deviations	hours [E]	Y	GP-603/4.1
4	Test break placement and duration against the rule for the shift length (SET LOCALLY)	compliance analyst	the schedule set	deviations	hours [E]	Y	GP-603/4.2
5	Compare each change's timestamp with the notice window for its jurisdiction	compliance analyst	the change set	in-window changes	hours [E]	Y	GP-603/5.1
5	Confirm the pay obligation was generated and reached payroll	compliance analyst	in-window changes; the payroll extract	deviations	hours [E]	N	GP-603/5.2
6	Reconstruct the offer order for overtime and voluntary time off from the offer log	compliance analyst	the offer log; the agreement's order rule	deviations	hours [E]	Y	GP-603/6.1
7	Compare each placement in the sample with the gate record and the contract's permitted constructs	placement and vendor lead	the gate record; the register	deviations	one sitting	N	GP-603/7.1
8	Match each deviation against the variant register; close a documented exception with its variant ID	compliance lead	deviations; the variant register	findings	one sitting	Y	GP-603/8.1
9	Grade severity on the function's scale (SET LOCALLY) and class the cause on the legal partner's advice	compliance lead	findings	classed findings	one sitting	N	GP-603/9.1
10	Open a remediation row with owner, date and the verification evidence required, or raise a variant request or preference finding to GP-601 with the finding ID	compliance lead	a classed finding	a remediation row or a routed item	minutes [A]	N	GP-603/10.1
11	Assemble the pack: scope, sample, tests, results, findings, sign-offs; file under the retention rule	compliance analyst	all of the above	the evidence pack	hours [E]	Y	GP-603/11.1
12	Test each finding for statutory exposure and against the disclosure thresholds (SET LOCALLY)	function head	classed findings	exceptions and disclosures	one sitting	N	GP-603/12.1
13	Verify evidence for each closed remediation; attest; age the rest	function head	remediation rows; evidence	the attestation	one sitting	N	GP-603/13.1

Variants

Recorded per Standard and Variant in Process Documentation:

• Statutory. Where a works council holds the right to be informed and to monitor compliance with the statutes and agreements in force for its employees, a disclosure step owned by the works-council liaison is inserted after step 12: a variant row. A change to working time itself, which the council co-determines under §87(1) Nos. 2 and 3, is GP-201's variant, not this card's.
• Contractual. A client contract's audit right fixes the sample and the evidence format for that client's work: parameters of steps 2 and 11, SET LOCALLY, no variant row.
• Structural. A supply node whose time records live in a partner's system varies step 3 (a partner-supplied extract with its own lineage) under a variant row reviewed each quarter.
• Transitional. A predecessor organization's compliance calendar and findings register continue until a dated cut-over, when open findings transfer to this register and the variant row expires.

L3 register

Job aid	Anchored to	Form
The obligation register layout and its sources	step 1	work instruction
The sampling rule and how it is drawn	step 2	work instruction
The extraction queries and the access restriction on time records	step 3	work instruction
The working-time test checklist per jurisdiction (rest, average hours and reference period, days, breaks)	step 4	work instruction
The notice-window and pay-obligation test	step 5	work instruction
The offer-order test for overtime and voluntary time off	step 6	work instruction
The severity scale and the breach · variant · preference decision tree	step 9	playbook
The evidence pack template and the retention rule	step 11	work instruction
The audit-notice runbook: what the function does when an external audit is announced	steps 2 to 11	runbook
The statutory-exposure escalation path	step 12	runbook

Automation candidates

Flagged at L2 and released per class of action on a published catch rate per Human Gates and Number Grades. The list is ranked by how easy a catch rate is to publish for the sub-step; each item after the first says why it ranks after the one before.

1. The rest-interval test (4.1): first because the daily and weekly rest minima are explicit in the statute (Articles 3 and 5 of the working-time directive) and a miss is checkable by hand; the weekly maximum is an average over a reference period and is SET LOCALLY, so that part of the row is released separately.
2. The notice-window test (5.1): a timestamp comparison per change; ranks after the rest test because the window differs by jurisdiction and a wrong window is found only when pay is disputed.
3. The break test (4.2): ranks after the notice test because break length is left to national law or agreement, so the rule is parameterized per site before a catch rate means anything.
4. The extraction (3.1): queries against systems of record; ranks lower because an incomplete extract hides, rather than produces, deviations.
5. The variant match (8.1): a lookup by step and scope; ranks after the extraction because a stale variant register makes a correct match wrong.
6. The offer-order test (6.1): encodable where the agreement's order is a rule; ranks lower because an agreement that counts refusals differently per classification may block the candidate under its variant row.
7. The evidence pack assembly (11.1): last because its error, an omission, is found only by the auditor.

Finding classification (9.1) and attestation (13.1) are never candidates. The first is interpretation: whether a deviation is a breach, an unrecorded exception or a preference turns on the obligation's meaning, which the legal partner holds. The second is a signature, and a certification standard assumes a person accountable for the operation it certifies.

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 reviews on a calendar with a sampling rule and a findings register is at Level 2, where Union Environments and WFM places agreement rules enforced by hand; one whose rest, notice and offer-order tests run on a published catch rate and whose rules are encoded as hard constraints in schedule build is at Level 3; one whose placement engine reads the obligation register as a constraint class, so that a construct a jurisdiction forbids cannot be placed there, is at Level 4.

See Also

• Process Standardization — the hub and the inventory this card belongs to
• Labor Law and Scheduling Compliance — predictive scheduling, rest periods and overtime by jurisdiction
• Labor Compliance Scheduling — operational implementation of the rules
• Union Environments and WFM — seniority, equalization and bargaining obligations
• COPC Standard — the certification audit
• Predictive Scheduling Laws — the notice-window obligations step 5 tests
• Decision Authority Tiers in Workforce Operations — the cross-cutting tiers this card's profile uses
• Standard and Variant in Process Documentation — where a finding becomes a variant row or a preference finding
• Post-Mortem and RCA for Workforce Operations — the learning loop for a material finding
• Wiki:Packs/Process Decomposition — the pack that localizes this card (CP-OPS-001)