Security

OpenAI Disbands Its Preparedness Team for "Catastrophic Risk" Evaluation, FT Reports.

The FT reports OpenAI has disbanded Preparedness, the team that evaluated catastrophic risks of frontier models. We cover the redistribution of safety work, staff departures, and what it signals for enterprise adoption.

· Huuush

OpenAI Disbands Its Preparedness Team for "Catastrophic Risk" Evaluation, FT Reports

Key takeaways

  1. 1According to the FT, OpenAI disbanded the Preparedness team, which evaluated catastrophic risks of frontier models, in late July.
  2. 2Biological and cyber risk work was redistributed to existing teams, and OpenAI's official position was unconfirmed at the time of writing.
  3. 3Companies that have adopted OpenAI models should re-check the vendor's safety evaluation owners, standards, and governance documents.
Diagram of an AI safety organization evaluating cyber and biological risks

The Catastrophic-Risk Team Is Gone

One of OpenAI's safety teams is gone. It was the team that evaluated catastrophic risks, named Preparedness. The FT reported its dissolution.

At 6:55 AM (KST) on August 17, 2026, Watcher.Guru posted about it.

The post says "OpenAI disbands its catastrophic risk evaluation team," citing the FT report. It has 212,000 views.

The team was dissolved in late July. Its biological and cyber risk work was redistributed to existing teams.

How the Safety Organization Was Shaken

The Preparedness team evaluated failure modes. Its scope was the cyber, biological, and autonomy risks of frontier models.

Dylan Scandinaro is the former team lead. His role changed to recursive self-improvement AI risk.

Co-founder Greg Brockman offered an explanation: safety work was integrated more tightly with model development.

Safety staff departures also continued. Chief ethics officer Chloe Bakalar left. Joshua Achiam and many others left the company. Unease was reported internally.

The continuity of the evaluation team is in question. That points to a structural change in how safety work is done.

How Should Enterprises Read This Signal?

Companies that use OpenAI models should take note. The evaluation structure has changed. The party doing safety evaluation has moved into the development organization.

The strength of independent verification may weaken. There is a possibility that evaluation gets tied to development schedules. This is an interpretation resting on reporting, though.

What companies should do is clear. Check the vendor's safety evaluation documents yourself. Re-review your standards with your security and governance leads.

Here are the changes in a table.

ChangeSignal for enterprises
Preparedness team disbandedSafety evaluation org structure changed
Bio and cyber work redistributedNeed to confirm who owns evaluation and by what standards
Many safety staff departedCheck for governance gaps
Integrated into model developmentReassess the strength of independent verification

The Internal Story Rests on Reporting

This news is based on press reports. It relies on the original FT report and a summary from the-decoder. OpenAI's official position hasn't been confirmed yet.

The departures and unease are statements based on reporting, not interviews with the people involved. No specific figures have been released either.

The trend is still clear. The center of safety evaluation has moved toward development. Companies should read this as a signal to check their governance.

Sources: Watcher.Guru post (2026-08-17 06:55 KST), original FT report, the-decoder summary (2026-08-16).

Frequently asked questions

What risks did the Preparedness team evaluate?
According to the article, the Preparedness team evaluated failure modes such as the cyber, biological, and autonomy risks of frontier models.
How did safety work change after the Preparedness team was disbanded?
The article, citing the FT, says biological and cyber risk work was redistributed to existing teams, with an explanation that safety work was integrated more tightly with model development.
How should companies check on this change?
The article suggests checking the vendor's safety evaluation documents yourself and re-reviewing evaluation standards with your security and governance leads.

Related articles