Description

A focused course, tailored for you

The Global Risk Operations Run-Book for Platform Companies

Twelve modules that turn an integrity-and-policy risk inbox into a documented operating system the second line trusts.

Risk Operations in a global platform company sits between Policy, Legal, Trust and Safety, and the second line of defence. Every escalation arrives with a deadline and almost none of them arrive with a documented operating model attached. This course gives you the run-book.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Global Risk Operations at a platform company is a hybrid role. Half of it is policy-implementation operations: standing up review queues, calibrating reviewers, sampling outputs, documenting override rates, writing the evidence packs that Legal and the second line will sign off. The other half is regulator-facing: explaining how a content or marketplace enforcement action was applied consistently across regions, on what timeline, with what reviewer training, with what appeals workflow. The friction shows up on the days the second line of defence asks for the artefact behind a decision and the artefact is a thread, not a document. The run-book this course delivers is the operating spine that makes the artefact the default output of every workflow, not a reconstruction after the fact.

What you walk away with

A documented queue design with reviewer-load, override-rate, and regional consistency baselines.
A reviewer calibration loop you can run quarterly with documented inter-rater agreement.
An evidence pack template the second line of defence accepts without rework.
An escalation rail into Legal, Policy, and executive risk that has named owners and SLAs.
A quarterly readout deck the executive team actually reads.

The 12 modules

Module 1. The operating model on one page

Risk Operations sits between Policy, Legal, Trust and Safety, vendor reviewers, and the second line of defence. This module gives you the one-page operating model that names every interface, every owner, every quarterly artefact the role is on the hook for. The output is a single document you can put in front of a new General Counsel or a new Chief Risk Officer and have them understand the function in ten minutes.

Module 2. Queue design for global platform enforcement

Reviewer queues at platform scale fail in a specific way. Routing rules drift, reviewer load goes uneven across regions, edge-case queues accumulate, and the SLA dashboard turns green while the underlying quality decays. This module walks the queue design choices that hold up under audit. Routing taxonomy, priority tiers, escalation gates, the sampling rate per queue, and the reviewer-load curve the operations team should be calibrating to.

Module 3. Reviewer calibration and inter-rater agreement

Policy decisions get applied through human reviewers, and the question the second line will ask is whether two reviewers looking at the same borderline case land in the same place. This module is the calibration loop. Gold sets, inter-rater agreement targets, the quarterly recalibration ritual, the documented coaching path for reviewers below threshold, and the artefact you hand to the second line that proves the loop is running.

Module 4. Override rate as a control signal

Override rate is the metric most platform risk operations functions track and the one most often misread. This module separates legitimate override patterns from drift signals, sets the override-rate thresholds that should trigger a policy clarification versus a reviewer-coaching cycle, and gives you the dashboard schema that lets you act on overrides instead of just counting them.

Module 5. Regional consistency checks

A platform that enforces the same policy differently in two regions has a regulatory exposure and a reputational exposure at the same time. This module gives you the regional consistency check you can run quarterly. The sampling design, the cross-region case comparison ritual, the documented variance thresholds, the documented exceptions process when local law genuinely diverges, and the cross-region calibration session that closes the loop.

Module 6. Vendor of record and BPO reviewer governance

Most platform review work runs through vendor-of-record BPOs in multiple geographies. This module is the governance layer. Contractual SLA structure, the reviewer training documentation the vendor owes you, the audit-rights clauses that hold up under a regulator visit, the joint calibration ritual with the BPO, and the offboarding playbook for when a vendor relationship has to be wound down without dropping a queue.

Module 7. Escalation rails into Legal and Policy

Operational decisions and policy decisions look identical on a Tuesday and become very different on a Friday when a journalist calls. This module is the escalation rail. The named triggers that send an open queue item to Legal review, the named triggers that send it to Policy, the SLA each owner commits to, and the documented record the escalation produces so the audit trail is complete by the time the matter lands on a Vice President's desk.

Module 8. The evidence pack the second line accepts

Second line of defence reviews fail when the first line cannot produce the artefact behind a decision in under fifteen minutes. This module gives you the evidence pack template. Queue identifier, reviewer identifier, decision rationale, policy clause referenced, override history, calibration session reference, regional consistency check reference, and the audit-trail signature chain. One template, one place, fifteen-minute retrieval.

Module 9. Regulator-facing readouts

Regulators in the EU, the UK, India, Brazil, and Australia are asking platforms how integrity enforcement actions are applied consistently. This module is the readout. The reporting structure that satisfies the DSA risk assessment cadence, the equivalent structures emerging in the UK Online Safety Act, India IT Rules, Brazil's marketplace rules, and Australia's Online Safety Act. Not legal advice. The operations data each readout needs and where it lives.

Module 10. Incident response for enforcement breakdowns

Sometimes a queue mis-fires. A category gets enforced incorrectly for forty-eight hours before anyone notices. This module is the incident response playbook. The detection ritual that surfaces breakdowns before a Vice President's inbox does, the rollback procedure, the customer communication template, the remediation timeline, the post-incident review structure, and the documented learnings that feed back into queue design and reviewer calibration.

Module 11. Quarterly readout to the executive team

The executive team wants four things from Risk Operations every quarter. What went wrong, what was changed because of it, what the second line and regulators are likely to ask next, and what trade-offs the executive team needs to weigh in. This module is the quarterly readout structure. The deck shape, the metric set, the narrative arc, and the documented decisions the executive team makes off the back of it.

Module 12. The first ninety days using this run-book

The final module is the implementation plan. Week-by-week, which artefact you are documenting, which calibration ritual you are running first, which queue you are baselining, which evidence-pack template you are rolling out, and which conversation you are having with the second line of defence by the end of the first quarter. Paired with the implementation playbook delivered alongside course access so the run-book lands in your actual operating environment.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Second-line review is asking for the artefact behind a borderline enforcement decision and the artefact is a thread.

Override rate is trending upward in one region and nobody has agreed whether that is a policy issue or a reviewer issue.

A regulator request asking for evidence of consistent enforcement across regions has landed and the data lives in five systems.

A queue mis-fired for forty-eight hours and the executive team wants to know what changes to prevent the next one.

What you get with this course

Twelve written modules with downloadable templates and worked examples for every module.
The hand-built implementation playbook tailored to your operating environment, delivered alongside course access.
Queue design template, reviewer calibration template, override-rate dashboard schema, evidence pack template, quarterly readout deck shape.
30-day money-back guarantee.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours: course access provisioned in the Art of Service learning environment.

Within 24 hours: hand-built implementation playbook delivered alongside course access.

Weeks 1 to 4: work through modules 1 to 6, queue design and reviewer calibration first.

Weeks 5 to 8: work through modules 7 to 12, evidence pack and quarterly readout.

Quarter end: run the first full calibration plus regional consistency check using the templates.

Before and after

Before

Risk Operations runs on tribal knowledge. The artefact behind any given decision is a thread, the override rate is a number nobody acts on, regional consistency is asserted not documented, and the second line of defence has standing rework requests against the function.

After

Risk Operations runs on a documented operating model. Every decision has a fifteen-minute-retrieval evidence pack, override rate is a control signal with thresholds and owners, regional consistency is documented quarterly, and the second line of defence signs off on the evidence pack on first review.

What happens if you do not address this

The risk is not a single dramatic failure. The risk is that the second line of defence keeps escalating documentation gaps quarter after quarter, the executive team's confidence in the operating model erodes, and the function becomes reactive rather than the trusted operator the platform needs when the next regulatory readout lands.

Who it is for

Operations leaders inside global platform companies who carry an integrity, trust-and-safety, marketplace, or platform-risk operations remit. The person who owns reviewer queues, vendor-of-record relationships with content review BPOs, the calibration loop between Policy and execution, the regional consistency checks, and the readout to the second line. Practical mid-career to senior operators, not policy authors and not investigators.

Who this is NOT for. Policy authors who write the enforcement standards, regulators looking for a policy primer, or pure trust-and-safety investigators working individual cases. This course is the operating-model and evidence layer that sits between policy and case work.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly six to eight hours over the first two weeks for the modules, plus the calibration and consistency rituals once they are running in your operating environment.

Why $199 is the right number

Big consultancy operating-model engagements deliver a similar artefact for six figures and a three-month timeline, then leave it on a shelf. Internal authoring takes one to two quarters of a senior operator's time and produces something that has never been pressure-tested outside the company. This course gives you the operating model and the templates this week, plus a hand-built implementation playbook tailored to your actual operating environment.

FAQ

Is this policy or operations?

Operations. The course assumes the policy is set elsewhere. The run-book is how the operations function executes against policy in a way the second line and regulators accept.

Is this only for content moderation?

No. The same operating model applies across content integrity, marketplace integrity, ads integrity, and platform safety. The templates are written to be reused across queue types.

What does the implementation playbook cover?

It is hand-built per buyer to your specific operating environment. Queue mix, regions you cover, vendor-of-record arrangements, the second-line owners you report to, the regulators you face.

Refund policy?

30-day money-back guarantee.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.