21 CFR Part 11 for AI agents
Part 11 governs electronic records and signatures. When an AI agent makes the record, here is what a control plane must provide to keep it defensible.
Read →Insights
Plain-language writing on segregation of duties, sign-off, and the audit evidence a regulator can verify for themselves — for the people who have to answer for what a machine decided.
Part 11 governs electronic records and signatures. When an AI agent makes the record, here is what a control plane must provide to keep it defensible.
Read →AI agents can draft queries, propose medical coding, and reconcile clinical trial data — but decisions that change the trial record stay a signed human call.
Read →An AI agent can triage a vaccine temperature excursion and run the stability assessment. It cannot release the stock. That line is the control.
Read →An AI agent can triage complaints for FDA medical device reporting. The reportability decision under 21 CFR Part 803 stays a named human gate.
Read →AI agents can assemble the batch-disposition case — deviations, results, reconciliation. The Qualified Person still signs the release. Here is the line.
Read →AI agents can draft rebate, chargeback and gross-to-net accruals from the ERP. A controller still signs the number that hits the financials. Here is the line.
Read →AI agents can intake, deduplicate and triage device complaints and route the reportable ones — while reportability and closure stay named human gates.
Read →AI agents can structure adverse-event cases to ICH E2B and triage volume — but seriousness and causality must stay a qualified human gate, on record.
Read →An AI agent can assemble and quality-check an eCTD dossier. A regulatory-affairs lead still signs the release. Versioned and Part 11-defensible.
Read →Reconciliation, AML triage, and sanctions screening are the wedge for AI agents — if they carry roles, limits, and a maker-checker split examiners recognise.
Read →An AI agent can match statement to ledger and surface breaks at machine speed. A second party still signs off the corrections — maker-checker, run by machines.
Read →AI agents can clear the AML alert backlog at machine speed. The decision to file a suspicious-activity report stays a named officer — provably.
Read →AI agents can assemble and screen an onboarding file in minutes. Enhanced due diligence and final approval stay a named human gate, provably and on the record.
Read →SR 26-2 scoped agentic AI out of model-risk guidance. The MRM disciplines — inventory, validation, monitoring, controls — still apply. Here is how.
Read →A senior officer must personally certify the transaction-monitoring program every year. When agents triage alerts, what is that certification standing on?
Read →AI agents can clear the sanctions false-positive backlog at speed. Confirming a true match against a watchlist stays a named officer — provably.
Read →SR 26-2 scoped agentic AI out of model-risk guidance. No template means no safe harbor — the predicate rules and discovery never went away.
Read →AI agents can clear the market-abuse alert queue at speed. The call to escalate toward a regulatory filing stays a named supervisor — provably.
Read →Before shipping an AI agent into regulated work, verify six things: identity, deny-by-default grants, segregation of duties, human gates, limits, and audit.
Read →Guardrails ask if content is dangerous. Governance asks if the actor is authorized. An agent can pass every check and still move money it should never touch.
Read →Least privilege for agents means versioned grants held by a role — so you can reconstruct exactly what an agent could do on any past date, and who signed off.
Read →Agent pilots stall because nobody can answer for what the agent did. Accountability, not speed, is the blocker — and it is fixable.
Read →An examiner asks four things of an agent: what was it permitted to do, who granted that, who approved each decision, is the record intact. How to answer.
Read →Approval gates as first-class workflow steps: the run parks at the one-way door until a named human signs — quorums, requester exclusion, captured reason.
Read →The oldest control in finance and pharma, applied to machines: enforce maker-checker structurally at runtime, so the same agent cannot prepare and approve.
Read →Why regulated teams run agent governance in their own environment: data never leaves, it works air-gapped, nothing phones home, the audit evidence is yours.
Read →A SIEM log or trace shows what happened. It does not prove the record was not altered. The difference is what an auditor and a court accept as evidence.
Read →Four-eyes means a second named person — not a second model — signs the work. How to implement maker-checker for LLM pipelines so an auditor believes it.
Read →A control plane governs what AI agents are allowed to do — identity, grants, segregation of duties, approval gates, and audit — separate from the agent itself.
Read →Maker-checker is the control where one party prepares work and another approves it. Banks and manufacturers ran it for decades. Now it governs AI agents.
Read →Accountability does not transfer to a model. Named principals, human gates on the decisions that matter, and a record tying every action to who authorized it.
Read →A proxy session makes MakerChecker the authorization point and the evidentiary record while the Claude Agent SDK keeps executing the tools.
Read →Wrap the tools your CrewAI crew already uses so every call gets a grant check, segregation of duties, and an audit entry — no re-platforming.
Read →Wrap your LangChain and LangGraph tools in a governed adapter — same name, same schema, plus a grant check, segregation of duties, and an audit entry per call.
Read →MCP lets an agent call any tool a server exposes. Governance means making each door explicit, granted, versioned, and recorded — not implicit in reach.
Read →Governing AI agents should not mean rebuilding them. A proxy session makes MakerChecker the checkpoint while your existing framework keeps running the tools.
Read →See it for yourself
One command starts the demo: an agent stopped from signing off its own work, and the signed evidence file an inspector can check for themselves.
Designed against the rules your auditors already enforce.