Legal and Regulatory Requirements for AI: Classifying an AI tool before deployment

NIST AI RMF GOVERN 1.1 is the outcome on legal and regulatory requirements for AI. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the framework says

Legal and regulatory requirements involving AI are understood, managed, and documented.

That is the text of NIST AI RMF GOVERN 1.1. Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

What this looks like in practice

In an assessment, NIST AI RMF GOVERN 1.1 is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Has the organization identified the laws, regulations and binding obligations that apply to its development and use of AI, and does it maintain that register and track changes to it?
• Has legal review set the terms on which this generative AI system may be used under intellectual property law, what may be done with its generated outputs, and what third-party material users may submit to it, with the resulting controls recorded?

Ownership usually sits with legal or compliance, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

NIST AI RMF is voluntary rather than binding, and that changes how it should be used. Adopting it does not create a legal obligation, and declining it is not a violation. It earns its place when a customer contract names it, when it gives structure to AI governance work you already owe under a law or a contract, or when a recognized practice is worth having on record. Treat it as a way of organizing that work, not as a second regime.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Inventory the jurisdictions, sectors and contracts in which the organization builds, buys or deploys AI.
2. Record each applicable law, regulation, regulator expectation and contractual obligation with an accountable owner.
3. Review the register on a set cadence and whenever the organization enters a new market or use case.
4. Identify how the system's outputs are used, internal drafts, customer-facing content, published or commercial material, and what users can submit to it, such as documents, images or code owned by others.
5. Obtain legal review of the permitted uses of generated outputs under applicable law and the model provider's terms, ownership, attribution, and when an output needs human authorship or checking before public or commercial use.
6. Record the conclusions, the controls required, such as user guidance, limits on output use or input restrictions, and the residual risk accepted, and repeat the review when the system's uses, the provider's terms or the law change materially.

Where else this maps

The questions behind NIST AI RMF GOVERN 1.1 also map to NIST AI 600-1 2.10 and ISO/IEC 42001 4.1, which are voluntary guidance and standards rather than law; following them does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this outcome the evidence type that satisfies it is a record. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. The framework sets no retention period, so this is our recommendation rather than a requirement: keep each version for as long as the system it describes is in use and for a period after it is retired, because a question about a past decision is answered from the version that was in force when it was made.

Where this usually goes wrong

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the evidence, not the intention. For NIST AI RMF GOVERN 1.1 that means dated records of each occurrence, not a description of the process. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Legal or compliance should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract or a regulator's guidance names it, or where it gives structure to AI governance work you owe for other reasons, and say in your own documentation which of those reasons applies.

Work backward from the evidence. Decide what evidence would prove legal and regulatory requirements for AI to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the evidence goes stale visibly.

Related outcomes

• Trustworthy AI Characteristics: Defining what trustworthy means for clinical AI
• Risk Management Processes for AI: Sizing AI risk management to the use case
• Ongoing AI Monitoring: Monitoring a model after it goes live

References

• GOVERN 1.1, in NIST AI Risk Management Framework 1.0 (NIST AI 100-1). This is a voluntary framework, not a legal requirement. The quoted statement is NIST's own, from the Core tables of NIST AI 100-1.
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a framework outcome asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations of its own.