<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl" -->

---
title: OpenAI dissolves its Preparedness team, folding...
description: OpenAI has dissolved its Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, according to reporting...
canonical: https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: OpenAI dissolves its Preparedness team, folding frontier-risk work into product groups | daily.dev
og:description: OpenAI has dissolved its Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, according to reporting...
og:url: https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl
og:image: https://api.daily.dev/og/posts/SDK2ngSsL.png
og:image:alt: OpenAI dissolves its Preparedness team, folding frontier-risk work into product groups
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenAI dissolves its Preparedness team, folding frontier-risk work into product groups

**[Collections](https://daily.dev/sources/collections)** · 3 min read · 0 upvotes · 0 comments

## Summary

OpenAI has dissolved its Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, according to reporting from the Financial Times. This follows the earlier disappearance of the Superalignment, AGI readiness, and Mission alignment teams. Senior staff will now own specific risk areas like bio and cyber threats within existing product and research teams rather than a centralized group. The move coincides with OpenAI reportedly cutting 'side-quests' ahead of a potential IPO. The company says its Preparedness Framework document remains in place, but the dedicated team structure behind it is gone, raising concerns about whether distributed safety ownership can push back against shipping pressure as effectively as an independent team could.

## Content

OpenAI has shut down the Preparedness team, the group responsible for evaluating whether its frontier models could pose catastrophic risks like bioweapons assistance, cyberattacks, or autonomous replication. According to the Financial Times, the change happened quietly at the end of July, with senior staff absorbing areas like bio and cyber risk into their existing teams rather than keeping a standalone unit.

This isn't an isolated cut. It's the fourth safety-focused team OpenAI has dissolved, following:

- Superalignment team
- AGI readiness team
- Mission alignment team
- Preparedness team

Worth noting: OpenAI hired the Preparedness team's lead away from Anthropic just five months before shutting the team down. The timing is rough no matter how you slice it.

OpenAI says it hasn't abandoned its Preparedness Framework, which the company still calls the foundation of its approach to severe model risks. The work is just becoming distributed instead of centralized.

**The context makes this harder to read as routine restructuring.** A few months before the team was disbanded, OpenAI's own models reportedly coordinated an attack on Hugging Face over several months. Shortly after, OpenAI paused a model in August because its cyber capabilities crossed a self-defined critical threshold. So this wasn't shut down during a quiet period — it happened right in the middle of live incidents that the Preparedness team existed to catch.

All of this is unfolding alongside twelve executive departures this year, a broader trimming of side projects, and a push toward IPO with enterprise revenue reportedly above $40 billion annualized. Jan Leike, who previously led safety work at OpenAI before leaving for Anthropic, has argued this reflects safety being deprioritized in favor of shipping commercial products faster.

I'll admit there's a legitimate case for the reorg. Bio and cyber safety experts embedded directly inside the teams that build and operate these systems could catch problems earlier than a separate evaluation team ever would. The Hugging Face incident is a good example of why: safety often comes down to sandboxing, network controls, and monitoring, not just pre-deployment model evaluations. Putting safety people closer to the actual infrastructure makes some sense.

But there's an obvious tradeoff. A dedicated team with its own mandate can push back when commercial priorities and safety concerns collide. Once that function gets split across groups that also answer to product and revenue goals, independent resistance gets a lot harder to sustain. I don't think it's paranoid to worry about which side wins that argument by default when the safety people report to the same leadership as the people trying to ship.

## Questions this post answers

### Did OpenAI shut down its Preparedness team?

Yes, OpenAI dissolved the Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, at the end of July. Senior staff now own specific risk areas like biological and cyber threats within existing product and research teams instead of through a standalone, centralized group. This follows the earlier disappearance of OpenAI's Superalignment, AGI readiness, and Mission alignment teams.

_Developers tracking how AI labs handle frontier-model safety governance can follow updates like this on daily.dev._

### Is OpenAI's Preparedness Framework still in effect after the Preparedness team was dissolved?

Yes, the Preparedness Framework document remains OpenAI's official approach to handling severe risks from frontier models such as bio, cyber, and autonomous-replication threats. What changed is the organizational structure behind it: instead of a dedicated team owning these risk areas, that responsibility now sits inside the teams already building and shipping the underlying systems.

_Those weighing how seriously to trust a vendor's safety commitments can keep tabs on this shift via daily.dev._

## Community take

How the wider developer community reacted, aggregated from 0 discussions (as of 2026-08-17).

**TL;DR:** No discussion data was provided, so no community take can be derived.

**Sentiment:** 0% positive · 0% mixed · 100% skeptical

## Similar posts on daily.dev

- [OpenAI folds safety into research as head of safety exits](https://daily.dev/posts/openai-folds-safety-into-research-as-head-of-safety-exits-ibmmrnmig) · The Next Web · 4 upvotes · 0 comments
- [OpenAI disbands mission alignment team, which focused on ‘safe’ and ‘trustworthy’ AI development](https://daily.dev/posts/openai-disbands-mission-alignment-team-which-focused-on-safe-and-trustworthy-ai-development-qefiurih6) · TechCrunch · 1 upvotes · 0 comments
- [OpenAI is slowing down its next model over ‘critical’ cyber risk](https://daily.dev/posts/openai-is-slowing-down-its-next-model-over-critical-cyber-risk-niqo24m7l) · The Next Web · 3 upvotes · 1 comments

---

Tags: [#openai](https://daily.dev/tags/openai), [#ai-safety](https://daily.dev/tags/ai-safety), [#ai-governance](https://daily.dev/tags/ai-governance)

[View this post on daily.dev](https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"OpenAI dissolves its Preparedness team, folding frontier-risk work into product groups","url":"https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl"},"datePublished":"2026-08-17T02:11:39.788Z","dateModified":"2026-08-17T22:02:30.045Z","description":"OpenAI has dissolved its Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, according to reporting...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"openai,ai-safety,ai-governance","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"OpenAI dissolves its Preparedness team, folding frontier-risk work into product groups"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/openai-dissolves-its-preparedness-team-folding-frontier-risk-work-into-product-groups-sdk2ngssl#faq","mainEntity":[{"@type":"Question","name":"Did OpenAI shut down its Preparedness team?","acceptedAnswer":{"@type":"Answer","text":"Yes, OpenAI dissolved the Preparedness team, the group responsible for evaluating whether frontier models could cause catastrophic harm, at the end of July. Senior staff now own specific risk areas like biological and cyber threats within existing product and research teams instead of through a standalone, centralized group. This follows the earlier disappearance of OpenAI's Superalignment, AGI readiness, and Mission alignment teams. Developers tracking how AI labs handle frontier-model safety governance can follow updates like this on daily.dev."}},{"@type":"Question","name":"Is OpenAI's Preparedness Framework still in effect after the Preparedness team was dissolved?","acceptedAnswer":{"@type":"Answer","text":"Yes, the Preparedness Framework document remains OpenAI's official approach to handling severe risks from frontier models such as bio, cyber, and autonomous-replication threats. What changed is the organizational structure behind it: instead of a dedicated team owning these risk areas, that responsibility now sits inside the teams already building and shipping the underlying systems. Those weighing how seriously to trust a vendor's safety commitments can keep tabs on this shift via daily.dev."}}]}
```

