Skip to main content

Standards versus law: what certification buys you and what it never will

The short answer

The test is "who can punish me for ignoring it."

A law is mandatory and enforceable by the state or private plaintiffs; a standard, a framework, and a pledge are voluntary, adopted by choice, and enforced by no one. Sort every instrument into the right pile first, because moving something from the voluntary pile to the mandatory pile in your head is the root error of this topic.

What you will be able to do

  • Distinguish a law (mandatory, enacted, enforceable by the state or private plaintiffs) from a standard, a certification, and a voluntary commitment (adopted by choice, enforced by no one), using the exact test of "who can punish me for ignoring this."
  • Analyze what a certification actually buys an organization: a trust and procurement signal, forced internal discipline, evidence of due diligence, a common language across jurisdictions, and, in one specific legal setting, a presumption of conformity.
  • Analyze what a certification never buys: legal compliance itself, immunity from liability, discharge of an obligation the law imposes directly, coverage beyond its defined scope and audit date, or a safe harbor for over-claiming it in marketing.
  • Explain the Bletchley Declaration (2023) as the purest case of a voluntary commitment: what it bought (global coordination, shared risk understanding, a chain of follow-on institutions) and what it never bought (any enforceable obligation on any company or government).
  • Identify the one bridge where a voluntary standard gains borrowed legal force: when a law points to it, as the European Union AI Act does through the presumption of conformity for harmonised standards (Article 40).
  • Distinguish the three kinds of certification (management-system, product or conformity, and personal or professional) and say what each one actually certifies and does not.
  • Place any instrument on the soft-to-hard spectrum (declaration, framework, certifiable standard, law, treaty) and sort it into the voluntary or mandatory pile with the "who can punish me" test.
  • Defend a certification decision against the challenge that "we are certified, so we are compliant," and against the opposite challenge that "voluntary standards are meaningless, so skip them."
  • Produce a one-page certification decision for your own organization that names, in plain words, what a specific certification or commitment will buy you and which legal obligations it leaves untouched.

The ideas, one by one

Certification buys six real things

A trust and procurement signal, forced internal discipline (often the real prize), due-diligence evidence, a common cross-jurisdiction language, market access where a buyer requires it, and, only where a law points to the standard, a presumption of conformity. None of the first five is legal compliance, and all of them are worth real money.

Certification never buys five things

Legal compliance itself, immunity from liability, discharge of an obligation the law imposes directly, coverage beyond its defined scope and audit date, or a safe harbor for over-claiming it in marketing. A professional can recite this list from memory.

The Bletchley Declaration is the purest case

Twenty-eight countries and the European Union signed it in 2023; it bought global coordination, shared risk understanding, and a chain of follow-on institutions, and it never bound a single company or government to anything, which is why signatories could freely decline the next declaration at Paris in 2025.

A standard gains legal force only when a law points to it

The EU AI Act Article 40 presumption of conformity gives harmonised standards real legal effect, but only for a specific requirement, in one jurisdiction, and rebuttably. As of 2026, ISO/IEC 42001 is not such a harmonised standard, so certifying to it does not grant that presumption. The bridge is not a European invention: Tennessee's Information Protection Act points at the NIST Privacy Framework and hands a conforming written privacy program an affirmative defense to a TIPA claim, which is the same mechanism buying a narrower prize. The decisive question is always "does a law that applies to me point to this standard, and what exactly does it grant?", asked of every jurisdiction on your list rather than of Europe alone.

Read the scope and the date

A certificate covers only the systems, products, and sites in its audited scope, as of the audit, maintained through surveillance audits. The AWS ISO/IEC 42001 certificate covered specific named services, not the whole company. Confirm your highest-stakes system is inside the scope, or you are citing a certificate that does not cover the product.

Both traps are fatal

"Certified, so compliant" launches you non-compliant; "voluntary, so worthless" forfeits procurement gates, internal discipline, due-diligence evidence, and any presumption of conformity. The professional posture holds both halves: voluntary instruments buy real, specific things and never buy legal compliance by themselves.

A voluntary instrument can hurt you

Over-claiming a certificate is a deception risk; a public pledge you break becomes evidence against you; an audit trail documents a risk you left open. Certify honestly, claim only what the certificate says, honor what you sign, and close what your audits find.

The spectrum runs soft to hard, and even a treaty is not a direct company duty

From a non-binding declaration, through voluntary frameworks and certifiable standards, to laws and international treaties, only the mandatory side can penalize you, and a treaty like the Council of Europe Framework Convention binds ratifying states, reaching your organization only through the domestic law it produces. The operative question is always which law actually reaches you and what it requires.

"Certification" hides three different instruments

Management-system certification (ISO/IEC 42001) certifies a process; product or conformity certification (the EU AI Act conformity assessment and CE marking) is a legal market-access step; personal certification (the AIGP) certifies an individual. None of the three, by itself, certifies that a specific system is legally compliant, and treating one kind as another is a category error.

Certifying is a business decision, not a compliance decision

Weigh it on four questions: do buyers require or reward it, is the internal discipline worth it anyway, does a law in your markets point to the standard, and can you honor it without over-claiming. The compliance obligations are satisfied separately, on the law's terms, regardless of how the certification call comes out.

The artifact is a two-part decision

The certification decision you built says, in one page: yes, adopt this voluntary instrument for these real benefits, and separately, here is the legal obligation that still must be satisfied by other means. That two-part answer is the whole lesson made actionable, and it feeds the cross-border shipping decision and the board audit. (see Topic 6.6) (see Topic 13.1)

Listen to it

The same lesson, talked through by two hosts as episode 45 of the podcast.

Real cases

These examples show the standard-versus-law distinction in real instruments, with the legal status of each stated plainly.

Example 1: The Bletchley Declaration, a pledge that bound no one (your anchor). In November 2023, twenty-eight countries and the European Union signed the Bletchley Declaration on frontier AI safety at the United Kingdom's AI Safety Summit (UK Government, 2023). It bought a genuine first: rivals including the United States and China jointly acknowledging shared frontier risk, seeding the AI Safety Institute network and a chain of follow-on summits and reports. (see Topic 7.5) (see Topic 12.1) It never bound a single company or government to do anything, which is why, at the Paris summit in February 2025, two original signatories (the United States and the United Kingdom) could simply decline to sign the next declaration with no legal consequence (TechCrunch; Al Jazeera, 2025). The purest illustration that a voluntary commitment buys coordination and momentum, never obligation.

Example 2: An ISO/IEC 42001 certificate as a procurement signal. In late 2024, Amazon Web Services announced ISO/IEC 42001 certification for a defined scope of named AI services, and KPMG's Australian firm became, via the certification body BSI, among the first organizations certified to the standard (AWS; BSI, 2024). The benefit was real and non-legal: a credential enterprise buyers could rely on instead of running their own deep audit of the vendor. It did not make either organization "compliant" with any AI law; it attested that a bounded set of systems conformed to a voluntary management standard as of the audit. The certificate is a trust signal and a procurement ticket, exactly the 3D value, not a legal safe harbor.

Example 3: The scope boundary in a real certificate. The AWS ISO/IEC 42001 certification covered specific named services (its public scope statement lists particular products), not the entire company (AWS, 2024). This is the scope lesson from 3E in a real document: a certificate covers what its scope names and nothing more. A buyer who read "AWS is ISO 42001 certified" as "every AWS service is covered" would have over-read the certificate. Always read the scope statement, not the headline.

Example 4: The presumption of conformity that only the law can grant. Under Article 40 of the European Union AI Act, a high-risk system that conforms to a harmonised standard (once such standards are published in the Official Journal) is presumed to comply with the corresponding legal requirement, though the presumption is rebuttable and the standard remains a voluntary route (EU AI Act, Article 40). As of 2026 the European standardization bodies were still finalizing the first such standards. This is the one bridge from 3F in the live law: a standard gains legal force only because a statute chose to point at it, for a specific requirement, in one jurisdiction.

Example 5: The standard that does not (yet) unlock the presumption. An organization certified to ISO/IEC 42001 sometimes assumes the certificate satisfies the EU AI Act. It does not: ISO/IEC 42001 is not, as of 2026, a harmonised standard under the Act, so the certificate does not grant an Article 40 presumption of conformity with the high-risk requirements. (see Topic 5.6) The certificate still buys the 3D benefits; it simply does not do the one legal thing a harmonised standard does. This is the most common sophisticated error in the field, and spotting it is a mark of expertise.

Example 6: The voluntary framework that a deregulatory government cannot repeal but also does not mandate. The NIST AI Risk Management Framework is a voluntary United States framework; the United States has no law requiring private companies to use it. (see Topic 6.2) Its voluntariness is a feature in a volatile political environment: it does not flip with an administration the way an executive order does (see Topic 6.1), but it also imposes no legal obligation. Adopting it buys a recognized operating structure and a common language with regulators and partners; it does not, by itself, satisfy any legal requirement. A framework in the voluntary pile, useful and non-binding at once.

Example 7: Over-claiming a credential into an enforcement hook. Regulators have repeatedly treated overstated AI and security claims as deception. (see Topic 6.1) A company that turns a narrow certificate ("our management system conforms to ISO/IEC 42001 for these services") into a broad public promise ("our AI is certified safe and compliant") has made a claim that must be true and has manufactured its own exposure if it is not. The instrument was an asset; the over-claim made it a liability. The 3I edge case, in the wild.

Example 8: A signed commitment used as the yardstick. When frontier labs sign public safety commitments (see Topic 7.5), those pledges are voluntary and unenforceable as law, yet they create a documented standard the public and regulators can measure the company against. A lab that signs a commitment and then visibly departs from it invites the charge that it broke its own public word, which can feed a deception or reputational case even though the pledge itself imposed no legal duty. The signaling value and the accountability risk are the same coin: 3I in the frontier-safety context.

Example 9: The personal credential that does not compliance-certify the company. An organization hires a team of professionals holding the Artificial Intelligence Governance Professional (AIGP) credential. The individual certifications are real and valuable: they signal that these people passed an exam covering a recognized body of AI-governance knowledge, and they buy hiring confidence and a shared vocabulary. But no combination of certified people makes the organization's AI systems legally compliant; compliance is still measured system by system against the law. Reading "our team is AIGP-certified" as "our AI is compliant" is the personal-versus-organizational category error from 3J. The credential certifies people, not products or lawfulness.

Example 10: The mandatory conformity step that is not a voluntary badge. A high-risk AI system entering the European Union market undergoes a conformity assessment under the EU AI Act and, where applicable, bears the CE marking; without that step the regulated product cannot be lawfully placed on the market. (see Topic 5.6) This looks like "certification" but sits in the mandatory pile: it is a legal precondition to market, enforced by the state, not a voluntary credential you adopt for a trust signal. The contrast with a voluntary ISO/IEC 42001 certificate is the whole point of 3J: same word, "certification," two different piles. One is a legal gate; the other is a business signal.

Example 11: Singapore's AI Verify, a voluntary testing framework that buys procurement standing. Singapore's Infocomm Media Development Authority launched AI Verify, a voluntary AI governance testing framework and toolkit, first released in 2022, that lets organizations run standardized technical tests and process checks against recognized AI-ethics principles (Infocomm Media Development Authority; Future of Privacy Forum). It is explicitly voluntary and carries no enforcement consequences, yet it is increasingly referenced in Singapore public-sector procurement and sector guidance. This is the 3D benefit set in a non-Western jurisdiction: a voluntary instrument that buys a trust signal, internal testing discipline, and procurement standing, and that makes no organization legally compliant by itself.

Example 12: A binding treaty that still is not a direct company obligation. The Council of Europe opened its Framework Convention on Artificial Intelligence for signature on 5 September 2024, described as the first international legally binding treaty on AI; states including the United States, the United Kingdom, and the European Union signed, and it enters into force after five ratifications, a threshold not yet reached as of mid-2026, so it is not yet in force (Council of Europe; Inside Privacy, 2024). Here is the nuance that sharpens the whole topic: the treaty is legally binding on the states that ratify it, obliging them to adopt domestic measures, but it is not a direct, enforceable obligation on any private company until a state turns it into national law. So even a genuine treaty, the hardest end of the international spectrum, reaches your organization only through the domestic law it produces, which is one more reason the operative question is always "what law actually reaches me, and what does it require."

Example 13: A United States statute that points at a voluntary framework (Tennessee TIPA). The Tennessee Information Protection Act, in effect in its entirety from 1 July 2025, gives a controller or processor an affirmative defense to a cause of action for a TIPA violation where it voluntarily creates, maintains, and complies with a written privacy program that reasonably conforms to the NIST Privacy Framework Version 1.0 (or other documented policies and standards designed to safeguard consumer privacy), provides individuals the substantive rights the statute requires, and keeps the program updated as the framework is revised (Tennessee Information Protection Act; Tennessee Attorney General guidance, 30 April 2025). This is Example 4's bridge built by an American legislature rather than a European one, and it is the row a United States operator would otherwise leave blank. Note what it buys and what it does not: not permission to operate and not proof of compliance, but a defense you may plead and must prove, bounded to this one statute in this one state. The mechanism travels; the European address does not.

Where people go wrong

  • "We are certified, so we are compliant." The single most expensive belief in this topic. A certificate against a voluntary standard attests that your management system conforms to the standard, within a scope, as of an audit. It is not a determination that you comply with any law, and no regulator is bound by your certifier's opinion. Compliance is measured against the law's own requirements by the law's own enforcer. The fix is to write, after every certification, which legal obligations it did and did not discharge.
  • "Voluntary standards are meaningless, so we will skip them." The mirror-image error. Certification buys a procurement signal, forced internal discipline, due-diligence evidence, a common cross-jurisdiction language, market access where buyers require it, and, where a law points to the standard, a presumption of conformity. Skipping it forfeits all of that. The fix is to name the specific benefits and decide against them, not against a caricature.
  • "Our certificate covers the whole company forever." Every certificate has a scope and a date. It covers only the systems, products, and sites named in the audited scope, as of the audit, maintained through surveillance audits. Anything outside the scope or drifting after the audit is uncovered. The fix is to read the scope statement and confirm your highest-stakes system is actually inside it.
  • "ISO 42001 certification satisfies the EU AI Act." As of 2026, ISO/IEC 42001 is not a harmonised standard under the AI Act, so the certificate does not grant an Article 40 presumption of conformity with the high-risk requirements, and it is not the required conformity assessment. It buys the real non-legal benefits; it does not do the one legal thing a harmonised standard does. The fix is to check, per requirement and per jurisdiction, whether the law actually points to the standard you hold.
  • "A standard can never have legal force." Also wrong, in the other direction. A standard gains legal force exactly when a law chooses to point at it, as the EU AI Act does through the Article 40 presumption of conformity for harmonised standards. The force is real but bounded: to the specific requirement, in the specific jurisdiction, and rebuttable. The fix is to look for the bridge (does a law point to this standard?) rather than assuming it is present or absent.
  • "Our government signed the declaration, so frontier risk is handled." The Bletchley Declaration and its successors are voluntary commitments by governments; they impose no enforceable obligation on any company, and a signatory can decline the next one freely, as the United States and United Kingdom did at Paris in 2025. A signed declaration buys coordination and momentum, never a duty. The fix is to treat pledges as signals of intent, not as controls.
  • "Signing a safety pledge is all upside." A public commitment you then depart from becomes evidence of a broken promise that regulators and plaintiffs can use against you. The signaling value and the accountability risk are the same coin. The fix is to sign only what you will honor, and to treat a public pledge as a standard you will be measured against.
  • "Marketing can say we are 'certified safe and compliant.'" Overstating a narrow certificate is itself a deceptive-practice risk; a regulator can build a deception case from your own words. The certificate does not license the claim; the facts do. The fix is to state exactly what the certificate attests (conformance to the named standard, for the named scope, as of the audit) and nothing broader.
  • "A certificate is always at worst neutral." It can hurt you: through over-claiming, through a signed commitment you then break, and through an audit trail that documents a risk you identified and did not fix. The fix is to certify honestly, claim only what the certificate says, honor what you sign, and close what your audits find, so the instrument stays an asset and never becomes the exhibit against you.
  • "Getting the framework or certificate is the goal." The badge is the receipt; the management system is the value. The internal discipline you build on the way to certification is often worth more than the certificate. The fix is to treat the audited management system, not the certificate, as the thing you are actually buying. (see Topic 6.3)
  • "Any certificate satisfies any buyer or regulator that mentions 'certification.'" Certifications are specific: a buyer requiring SOC 2 is not satisfied by ISO/IEC 42001, and a law requiring a named conformity assessment is not satisfied by a general management certificate. The fix is to match the exact instrument to the exact requirement, per buyer and per law, never treating "certified" as a generic status.
  • "Our people are AIGP-certified, so our AI is compliant." A personal certification attests that individuals passed a knowledge exam; it says nothing about whether any specific system complies with any law, which is measured system by system. A credentialed team is genuinely valuable, but organizational compliance and personal certification are different kinds of achievement. The fix is to keep the three kinds of certification (management-system, product-conformity, personal) distinct and never let one stand in for another.
  • "Certification is a compliance decision, so we must get it." Certification buys business benefits, not legal compliance, so whether to pursue it is a business decision weighed on buyer demand, internal-discipline value, whether a law points to the standard, and over-claim risk. The fix is to make the certify-or-not call on those four questions and to handle the legal obligations separately, since the certificate never substitutes for them.

Questions people ask

What is law (mandatory instrument)?
A rule enacted by a body with authority (a legislature or a regulator acting under a statute) that applies to you whether or not you agree with it, signed it, or ever heard of it, and that a regulator, a court, or a private plaintiff can enforce with a consequence such as a fine, an injunction, damages, a ban, or a model deletion. The EU AI Act and Illinois BIPA are laws.
What is standard (voluntary instrument)?
A consensus specification, usually written by an expert body such as ISO and IEC or a national body such as NIST, describing a good way to do something. No one is legally required to follow it; you conform by choice for the benefits it buys. ISO/IEC 42001 is a standard.
What is framework (voluntary instrument)?
A standard-like voluntary instrument, often broader and less prescriptive than a certifiable standard, that structures how you approach a problem. The NIST AI Risk Management Framework is a framework; the United States has no law requiring private companies to use it.
What is voluntary commitment (or declaration or pledge)?
A public statement of intent, by governments or companies, with no specification to conform to and usually only a signature, enforceable by no one. The Bletchley Declaration is a voluntary commitment by governments.
What is certification?
A written attestation by an accredited outside body that your organization's management system (or product) conforms to a published standard, within a defined scope, at a point in time, maintained through periodic surveillance audits. A certification is not a determination of legal compliance and does not bind any regulator. More on Certification

Keep going

Watch the lesson and prove it

Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.

Watch the lesson and prove it →