No documented obligation
Establish it first. Supervision without a stated regulatory basis is difficult to defend to employees or to a regulator.
Twenty checks before turning on supervision, covering scope, privacy and whether the review queue is workable.
Communication supervision is a legitimate regulatory control and an employee relations risk in equal measure. Scoped badly it produces an unmanageable queue and a workforce that feels surveilled.
The design decisions below are compliance and legal decisions before they are technical ones. Getting the order wrong is the common failure.
Head of Compliance
Legal and privacy counsel
IT administrators and the intended reviewers
Tick only what you can genuinely evidence today. An item you intend to do is not an item you have done, and scoring yourself generously here only produces a comfortable number and an uncomfortable project.
Why you are doing this and to whom.
Whether the configuration will produce useful signal.
The most sensitive access in your tenant.
Whether it will demonstrably have operated.
These bands are deliberately blunt. The middle band is where most organizations honestly sit, and it is a perfectly reasonable place to proceed from — provided the gaps are written down with owners rather than carried as optimism.
Do not proceed yet. More than four in ten items are unaddressed, and the ones that fail here are usually the foundational ones that make everything after them harder.
Proceed on a defined scope, with the outstanding items written into the plan as risks with owners and dates. This is the most common honest position.
The remaining gaps are small enough to handle during delivery rather than before it. Confirm the unticked items are genuinely minor rather than simply unexamined.
Your score highlights automatically as you tick items above. Nothing is saved, sent or tracked — refreshing the page clears it.
The four items below are the ones whose absence causes the most trouble downstream. If your unticked items include any of these, they are worth addressing before the rest.
Establish it first. Supervision without a stated regulatory basis is difficult to defend to employees or to a regulator.
Do this before configuration. Retrofitting consultation after supervision has started is materially worse than doing it first.
Pilot in a limited scope and measure the queue. An unworkable queue is the most common cause of a supervision programme quietly lapsing.
Train before enabling. Untrained reviewers produce inconsistent decisions, which is worse evidence than no supervision.
We will review one control process end to end and show you what supervision scoped to your actual obligation would look like, including the expected queue volume.
Whether your analytics platform would satisfy an examiner, tested against twenty specific capabilities.
Twenty checks on whether your customer data supports the pricing, risk and cross-sell decisions being made from it.
Describe the situation in your own words.