Regulation is rewriting what staffing operations must be able to prove
Each of these obligations has the same shape: a regulator asks what actually happened to a worker, a shift or a payment — and the answer has to come from your systems, not from someone's recollection.
Compliance guides are usually written for lawyers. These are written for the person who has to change how a workflow runs on Monday. Each page states the obligation, then covers the operational records it implies and where automation genuinely helps.
Live and dated obligations
| Change | Where | Status | What it demands operationally |
|---|---|---|---|
| Joint and several PAYE liability | United Kingdom | In force 6 April 2026 | Continuous supply-chain reconciliation and per-worker payment evidence |
| Platform Work Directive 2024/2831 | European Union | Transposition by 2 December 2026 | Decision logs, human review gates, worker-facing disclosure of automated decisions |
| Wet DBA enforcement | Netherlands | Active; vergrijpboetes possible from 1 January 2026 | Structured assignment records showing how work was actually performed |
Also on operators' desks
- German AÜG — the 18-month assignment cap and equal-pay parity make premium calculation an audit surface, which is an argument for encoding the rule once rather than recalculating it monthly.
- EU AI Act — AI used in employment is Annex III high-risk, with transparency duties preceding the main obligations in 2027. Audit logs and human oversight cover the shared core with the Platform Work Directive.
- South Africa, Section 198A deeming — after three months, deemed-employment rules make assignment duration tracking a commercial control, not an HR nicety.
- Nigeria, payroll and ghost-worker audits — enforcement has recovered sums in the tens of billions of naira, which puts verified attendance ahead of most other automation candidates.
- Gulf wage protection and Emiratisation — WPS filing and nationalisation quotas both require payroll data that reconciles the first time it is submitted.
- US TCPA — the FCC treats AI-generated voices as robocalls, so consent capture has to be designed into candidate contact rather than added later.
The pattern worth noticing: every item above is satisfied by records that a well-built operation produces anyway — verified attendance, structured intake, reconciled payments, logged decisions. That is why we treat compliance posture as a by-product of cost-to-serve work rather than a separate product to sell you.
ShiftMargin builds operations software. None of these pages is legal, tax or employment advice, and several of these regimes are still moving. Confirm your position with local advisers.
Questions operators ask
Is ShiftMargin a compliance vendor?
No. We automate staffing operations to reduce cost per filled shift. The audit trail, decision logs and payment evidence that regulators ask for are by-products of building those workflows properly.
Which of these should an operator address first?
Whichever one your business already has a dated exposure to, and where the same build also reduces cost. In practice that is usually the attendance-to-payroll loop, because it produces payment evidence for the UK regime, verified attendance for ghost-worker audits, and a measurable saving in one pay cycle.
Do you provide legal advice on these regimes?
No. We build the operational records and controls, and we work alongside your advisers rather than in place of them.
Turn a compliance deadline into a margin project.
A two-week Ops Audit identifies where your records break, which workflow closes the most exposure, and what that same automation saves per filled shift.
Request a free 30-minute teardown →