FROM THE EDITOR
Over the previous additions of The GC Playbook I have written about FDA enforcement as something the company manages: the 483 response, the warning letter reply, the quality agreement with the contractor. In each, the working assumption was that the company controls the story. It decides what to disclose, when, and how to describe it.
On August 31, 2026, that assumption got weaker. The SEC and FDA signed a Memorandum of Understanding that sets up a formal channel for sharing nonpublic information about FDA-regulated products and the companies behind them. On October 2, FDA’s Transparency Roadmap added a second change: a plan to publish redacted Forms 483, inspection observation lists and establishment inspection reports, and clinical study reports for approved applications.
Put the two together and the regulator’s version of events can reach your investors, and your securities regulator, without passing through you. This issue is about what that does to the work of the legal department.
John LaRocca
WHAT THE MOU SAYS
The SEC announced the MOU on August 31, 2026. SEC Chairman Paul Atkins and Acting FDA Commissioner Kyle Diamantas signed it. It took effect immediately and runs three years; either agency may end it on 30 days’ notice. Four features matter to a general counsel.
Scope. It covers nonpublic information about FDA-regulated products and the firms and individuals who make, distribute or sell them. Sharing can be proactive or on request. Its stated concern is representations to investors about the status of FDA review, product approvals, clinical results, manufacturing compliance, and marketing activity.
Direction. The main flow is FDA to SEC. The MOU’s own examples, as described in law firm alerts, include FDA meeting minutes, Complete Response Letters, and correspondence with review divisions. The standard categories of FDA material are the obvious candidates for sharing and for SEC inquiry: warning letters, Form 483 observations, import alerts, and clinical hold letters. I have not seen the MOU list each of those by name, so treat that list as the practical reading of “nonpublic information about regulated firms,” not a quotation.
Plumbing. Each agency names points of contact. On the SEC side they sit in the Division of Enforcement and the Division of Corporation Finance’s disclosure review program. On the FDA side they sit in the Office of the Chief Counsel and the Office of Inspections and Investigations. The agencies plan standardized request and transmittal templates. That is the difference between a favor between colleagues and a process.
Limits. FDA’s sharing rests on 21 C.F.R. § 20.85, which carves out trade secrets and confidential commercial information. SEC sharing back to FDA rests on 17 C.F.R. § 240.24c-1 and needs confidentiality assurances. The SEC may not pass FDA-sourced information beyond its own staff without FDA’s written permission. Shared information is not treated as public, and the MOU says sharing does not waive privilege. If a FOIA request, subpoena or congressional inquiry seeks the shared material, each agency must promptly notify the other.
What the MOU does not do, as far as the summaries show, is create rights for companies. It is an operating agreement between two agencies. I found no language giving a company notice that its information was shared.
WHAT THE TRANSPARENCY ROADMAP ADDS
The October 2 roadmap is the public half of the same shift. FDA says it will build on existing datasets by proactively publishing redacted Form 483s, lists of inspection observations and establishment inspection reports where appropriate, with trade secrets and confidential commercial information redacted. It plans to publish clinical study reports for approved applications. Through rulemaking, it aims to disclose the fact that major applications (NDAs, BLAs, ANDAs) were submitted, and says it will consider company disclosure timing when releasing redacted documents.
Two cautions. First, the roadmap gives no dates for the 483, study report, or submission-disclosure commitments, and to my knowledge the submission rule has not been proposed. Second, FDA already publishes redacted Complete Response Letters (since July 2025) and said in September 2025 that it would publish future ones in real time. The direction of travel is established; the pace is not.
THE SHIFT FOR THE GC: THREE VERSIONS OF THE SAME EVENT
Take a routine event, a Form 483 after a plant inspection. Before these changes there were two versions: the one in FDA’s file and the one in the company’s 10-Q, earnings script and press release. The gap between them was rarely tested, because only the company held both.
Now there can be three: FDA’s file, the company’s public description, and what the SEC’s disclosure reviewers and enforcement staff can see side by side. A statement that the company “continues to believe its manufacturing operations are in compliance” reads differently when the reviewer holds the observation list.
That is the exposure. The company’s lawyers did not become less careful. The cost of checking them went down.
A WORKED EXAMPLE: THE REPEAT-ISSUE LETTER
The Baxter warning letter of September 29 shows the pattern. The letter on the Round Lake, Illinois sterile plant cites segregation failures, microbial control, laboratory controls and weak investigations. It says management oversight is inadequate across sites and told Baxter to assess its global operations. It also alleges that a summer cefazolin recall happened only after FDA made contact. It flags consequences including federal contract eligibility, export certification and a hold on new applications.
Nothing in this article asserts that Baxter’s disclosures were inadequate. I have not compared them to the letter. The point is structural. A letter that says “inadequate management oversight across sites” and links the recall to FDA contact is a document a disclosure reviewer would want to line up against risk-factor language, the description of quality systems in the 10-K, and any statements about the timing of the recall decision. Under the MOU, that comparison is something the SEC can request from FDA, not only something the company chooses to hand over.
FIVE QUESTIONS FOR YOUR OWN DEPARTMENT
1. Who sees every piece of FDA correspondence, and who decides whether it is disclosure-relevant?
In many companies regulatory affairs receives the 483, warning letter, CRL, or meeting minutes and quality owns the response. Securities counsel sees it only if someone forwards it. The MOU makes that gap a control weakness. Name the owner and the timeline, in writing.
2. Can you tie every public regulatory statement to a document?
Pull the last four quarters of earnings scripts and filings and for each statement about FDA status, timelines, inspection outcomes, or recall decisions, identify the source document in your files. If you cannot, assume a reviewer will ask.
3. What does your 483 response now say to a second audience?
Responses already go to FDA. If 483s and observation lists become public, the response commitments are read by investors too. Draft with that audience in mind, without softening what the quality team must say to FDA.
4. How do trading windows and 10b5-1 plans connect to the regulatory calendar?
FDA-held information about a pending CRL or inspection outcome is the kind of thing insiders may know before the market. Confirm the insider list includes regulatory affairs and quality staff who receive such correspondence, and that blackout triggers include regulatory events, not only earnings.
5. What is your protocol when a subpoena, FOIA request, or SEC inquiry arrives?
The agencies must notify each other of third-party demands for shared information. A company facing parallel FDA and SEC contact should assume each agency may learn what the other has. Decide in advance who coordinates privilege and who speaks to each agency.
WORKSTREAM 1 — IMMEDIATE: Build the Correspondence-to-Disclosure Pipeline
Create one intake point for every nonpublic FDA communication (483s, warning letters, untitled letters, CRLs, clinical hold letters, import alerts, meeting minutes) with a same-week review by securities counsel and a written disclosure-relevance call. Keep the call and the reasoning in the file.
BUSINESS IMPACT: If an SEC reviewer asks why a 483 was not discussed in a filing, the answer should be a dated memo showing a considered judgment, not a search for who knew.
WORKSTREAM 2 — NEAR-TERM: Reconcile Filings Against the Regulatory Record
Run the four-quarter statement-to-document tie-out described above, starting with manufacturing compliance and approval-timeline language. Fix risk factors that describe FDA risks as hypothetical when an observation or letter already exists.
BUSINESS IMPACT: A hypothetical risk factor for a risk that has already occurred is the form of disclosure problem that cross-checking against FDA files exposes quickly.
WORKSTREAM 3 — STRATEGIC: Prepare for Publication of Your Own 483s
Assume that redacted 483s and inspection reports will eventually be public. Decide your redaction requests in advance: which content is a trade secret or confidential commercial information, who marks it, and how you will tell FDA. Draft the next 483 response knowing investors, competitors and plaintiffs may read it.
BUSINESS IMPACT: Companies that have already sorted their confidential material can respond to a publication notice in days. Companies that have not will argue about it under deadline.
“The company’s lawyers did not become less careful. The cost of checking them went down.”
For interested readers I have created an FDA Disclosure Readiness Toolkit. You can find it at https://laroccaadvisory.gumroad.com/l/mfsust
ABOUT THE AUTHOR
John LaRocca is the founder of LaRocca Advisory Services and the author of The GC Playbook. He served as CLO at Aerie Pharmaceuticals (Aerie/Alcon, ~$930M), Y-mAbs Therapeutics (SERB, $412M), and Eagle Pharmaceuticals, with 37 years of legal experience and 26 years at the GC/CLO level in specialty pharma and biotech. The GC Playbook is published on Substack at laroccaj.substack.com.
© 2026 LaRocca Advisory Services | laroccaj.substack.com



John, "the cost of checking them went down" is the line that sums up the whole issue. Your first question, who sees every piece of FDA correspondence and who decides whether it's disclosure-relevant, is a decision-rights question before it's a legal one. In a lot of companies, regulatory affairs and securities counsel probably each assume the other owns that judgment. How are boards reacting so far? Are audit committees asking to see the intake process itself, or still waiting for the first SEC letter?