Why this hour is worth your calendar
Three things changed at once. AI is now making or shaping real decisions - who gets hired, who gets credit - at a scale and opacity that outruns old controls. Regulators responded: the EU AI Act is the first comprehensive, binding AI law, and it is written to follow AI wherever its effects land. And a set of frameworks - NIST AI RMF, ISO/IEC 42001, Singapore's Model AI Governance Framework - grew up to turn "govern your AI" from a slogan into a runnable program. This hour puts the three together and answers the first question a Singapore leader must ask: does the EU AI Act apply to us?
Law, method, proof 9 min live
The confusing part of AI governance is that several big things share the name. They are not competitors - they are three layers. One is the law you must obey; one is how to think about risk; one is how to run and prove your governance.
LiveThe one line that untangles it3 min▶
Say it this way: "NIST shows what good looks like, ISO 42001 lets you prove it, and the EU AI Act makes parts of it mandatory."
- EU AI Act: binding law. Risk-tiered obligations, prohibited uses, provider/deployer duties, real fines. If you are in scope, this is the floor - not optional.
- NIST AI RMF: a voluntary, US-origin risk method (Govern, Map, Measure, Manage). It gives your teams a common language for AI risk and maps neatly onto the Act and ISO.
- ISO/IEC 42001: the first certifiable AI management-system standard. It is how you run governance operationally and show an auditor or a customer third-party-verified proof.
- Singapore's Model AI Governance Framework: voluntary, principles-based, the responsible-AI reference for the region - useful even where the Act does not reach.
LiveWhy governance became a board topic3 min▶
- The decisions got consequential. AI now screens job applicants, scores credit, triages services. When it is wrong or biased, the harm is real and the liability is yours.
- The law got teeth. The EU AI Act's top fine tier is EUR 35 million or 7% of global turnover - a board-level number, larger than the GDPR's.
- The scrutiny got public. Customers, employees, and regulators now ask "how is this AI governed?" - and "we're careful" is not an answer you can evidence.
Vantage's board question. Our running-case Singapore firm, Vantage, sells an AI hiring tool. Its board assumed AI regulation was a European problem for European companies - until a customer in Germany asked for its EU AI Act conformity documentation. That single request turned governance from a someday-item into a this-quarter one. The rest of the course is Vantage answering it.
When the Act reaches Singapore 8 min live
The EU AI Act uses a market-and-output model, not a where-are-you model. Like the GDPR, it follows the effect. For a Singapore company the trigger is simple, and it catches more firms than they expect.
LiveThe output-in-the-Union trigger3 min▶
Article 2 puts you in scope if any of these is true, regardless of where your company sits:
- You place an AI system (or a GPAI model) on the EU market or put it into service there - even through an EU reseller.
- You are a deployer located in the EU.
- You are a provider or deployer in a third country and the output of your AI system is used in the Union.
That third limb is the one that surprises Singapore firms. A model run entirely in Singapore, whose results are used to make decisions about people in the EU - screening EU job applicants, scoring EU loan seekers - is in scope. A purely Singapore-internal system whose output never touches the EU is not.
Self-studyGovernance is bigger than the Act2 min read▶
It would be a mistake to reduce AI governance to "comply with the EU AI Act". The Act is the sharpest legal edge, but governance is the broader discipline of making sure your AI is trustworthy, accountable, and defensible - whether or not a specific law compels it. Even a Singapore company entirely outside the Act's reach has customers, employees, and a reputation that depend on its AI behaving well, and Singapore's own Model AI Governance Framework exists precisely to guide that. So treat the Act as the forcing function that makes governance concrete and urgent, but build the program for the wider goal: an AI operation you can explain, evidence, and stand behind. That framing also future-proofs you - more AI laws are coming, and a real governance program adapts to the next one far more cheaply than a bare EU-AI-Act checklist does.
Does the Act reach you? ★ 12 min · pen and paper
Run the Article 2 test on your own AI systems.
List the AI systems your company builds or uses - the CV screener, the recommender, the chatbot, the credit model.
For each, ask: do we place it on the EU market, or is its output used in the EU (about EU people)? Mark in scope / out of scope.
For the in-scope ones, note your likely role - are you the provider (you built it) or a deployer (you use someone else's)? This decides who carries the obligations.
Circle the highest-stakes in-scope system. That is where the rest of this course pays off first.
Map your frameworks ★ 8 min · your next AI review
Four questions that reveal whether your governance is a program or a slide.
"Which of our AI systems are in scope of the EU AI Act, and what tier are they?" If nobody can answer, governance has not started.
"Do we use a risk method like the NIST AI RMF, or do we assess AI risk ad hoc?" A common method beats hero effort.
"Could we show a customer or regulator evidence of our governance - or just describe it?" This is the ISO 42001 question: proof vs assertion.
"Who owns AI governance, and does it connect to our data governance and our model evaluations?" Three disconnected efforts is the common failure.
Before session a2 ◐ 30 min total
- Finish the Article 2 scope test for your AI systems and keep it - a2 classifies the in-scope ones by risk tier.
- Find out whether your company already uses any AI risk framework (NIST, ISO, the SG model) - or assesses risk ad hoc.
- Ask: who, if anyone, owns AI governance, and does it talk to data governance and model evaluation?
- Optional: skim the EU AI Act's Article 2 - it is short, and it is the whole applicability question.
- Which of our AI systems have output used in the EU, and are therefore in scope of the EU AI Act?
- For each, are we the provider or the deployer - who carries the obligations?
- Do we use a common AI risk method (like the NIST AI RMF), or is risk assessed ad hoc?
- Could we evidence our AI governance to a customer or regulator, or only describe it?
- Who owns AI governance, and does it connect to our data governance and our evals?
Official sources covered
Taught from the primary texts and framework docs. This page covers:
Three questions before you go 🎯 ◐ 90 seconds
1 · A Singapore firm runs an AI hiring model in Singapore, but its decisions are used to screen candidates in Germany. Under the EU AI Act it is...
Article 2 catches providers/deployers in a third country when the AI system's output is used in the EU. The law follows the effect, not the company's location.
2 · "NIST shows what good looks like, ISO 42001 lets you prove it, the EU AI Act makes parts mandatory." This means...
They are three layers, not competitors: the law you must obey, the method for reasoning about risk, and the certifiable system that evidences governance.
3 · The EU AI Act's top fine tier is...
Prohibited-practice breaches carry up to EUR 35M or 7% of global turnover (Art 99) - larger than the GDPR's top tier, and a board-level number.