Netizen9 — Compliance Duty Platform

Recognise the pattern before you're the next case study.

A duty and training platform for the people who personally carry the risk — MLROs, Section 151 Officers, and the teams around them. Built on real enforcement failures, not generic theory, and given to each organisation as its own sealed instance.

Find your duty See Reeve live

PERSONAL DUTY
ON RECORD

Two duties. One underlying playbook.

Different statute, same exposure — an individual, named in law, personally on the hook if the wrong thing goes unchallenged. Each entry below opens the same engine, trained on the specific law and real case failures for that role.

Financial services

§ 330 POCA 2002 · SMF17

Money Laundering Reporting Officers

You are the person a firm's suspicions flow through, and the one exposed if they don't flow through properly. ECCTA 2023 sharpened that further — a senior manager's actions can now sink the firm without board-level knowledge.

Reeve works through the SAR/DAML chain, personal liability under POCA and ECCTA, and real cases — Wirecard, Greensill, Binance — as scenarios your team can actually be tested on.

Open Reeve for MLROs →

Local government

§ 114 LGFA 1988

Section 151 Officers

A personal, non-delegable statutory duty to report unlawful spending — the mechanism that exists precisely so no leader or cabinet can pressure you into silence. Thurrock and Woking show what happens when it isn't used in time.

Reeve includes a Treasury "Trust But Verify" calculator for checking a broker's quote against central government borrowing, alongside procurement red flags and the statutory duty itself, worked through as real scenarios.

Open Reeve for S151 Officers →

New entries are added as they're properly researched — NHS counter-fraud, large public-sector contractors and others are being considered, not shipped until the underlying law and case material earns a place here.

Case pending

How an organisation actually gets one

Not a shared chatbot with your logo on it. A sealed instance built around the same engine.

Shared core

One knowledge base, maintained once

Real, sourced enforcement failures and the statute behind them — maintained centrally so every organisation benefits when it grows, without waiting on a vendor release cycle.

Sealed per organisation

Your own instance, your own data

Your in-house policies, your team's sessions — held in infrastructure that belongs to your instance alone, never pooled with another organisation's.

Evidence, not a certificate

Training you can actually point to

Real scenario sessions your team can be shown working through — the kind of engagement a "reasonable procedures" defence is supposed to be built on.