All terms

Regulation & Policy

Preparedness Framework

Also known as: OpenAI Preparedness Framework

The Preparedness Framework is OpenAI's published approach to identifying, measuring and mitigating severe risks from its frontier models. It sets out tracked risk categories, capability thresholds that trigger safeguards, and the internal governance process for deciding whether a model can be developed or deployed. It is a voluntary company policy rather than a legal requirement.

What it is

The framework describes how OpenAI evaluates models for dangerous capabilities in areas such as biological and chemical uplift, cybersecurity and self improvement or autonomy. Models are assessed against defined capability levels, and reaching a level obliges the company to have specific safeguards in place before further development or release. Decision rights sit with internal safety bodies and leadership, with oversight by the board.

Why it matters

Frontier safety policies shape what models can do in public, which features are gated, and how quickly capabilities reach customers. If you build products on a provider's API, these policies help explain refusals, usage restrictions, staged rollouts and regional differences. They also feed into enterprise procurement, because buyers increasingly ask suppliers to show how model risks are assessed.

How it works

Teams run evaluations and red teaming against the tracked categories, document findings in system or model cards, and compare results with the thresholds in the framework. Where a threshold is met, safeguards such as refusal training, monitoring, access controls or deployment limits are required before proceeding. External readers use the published framework and accompanying system cards to compare providers and to inform their own risk registers.

When it applies

It applies when you are assessing or procuring frontier models, writing internal AI risk documentation, or explaining why a model's behaviour and availability are constrained in certain domains.

Examples

  • A procurement team maps a supplier's system card against its own risk register before approving an AI feature for launch.
  • A product manager traces a persistent refusal in a chemistry use case back to a documented high risk category and designs a human review step instead.
  • A policy analyst compares several frontier safety policies to see which risk categories each provider tracks.

How it is measured

  • Coverage of tracked risk categories evaluated before each model release
  • Presence and completeness of published system or model cards for models you depend on
  • Time between an internal capability finding and the corresponding safeguard being live
  • Number of deployment restrictions or feature gates affecting your own use cases

Related terms in Regulation & Policy

Primary research · August 2026

How ChatGPT Shortlists Software Brands

An audit across 10 categories and 60 buying questions. I recorded what ChatGPT reads, throws away and links to when a buyer asks it which software to buy, and what that decides.

60
Questions asked
10
Software markets
2,680
Results read
367
Links shown
Free35 pages · PDF · 536 KBDiscovery Digest every Friday

Free download

Get the full report

35 pages · PDF · 536 KB. Enter your details and it downloads straight away.

How ChatGPT Shortlists Software Brands downloads straight away. No spam, unsubscribe anytime.