GxP Frame Visual Reference · White Paper v4.2 · Overview
Governing AI in Pharmaceutical Operations
The AI-Supported Work Authorization Cycle: six gate decisions for whether a defined AI-supported quality workflow may proceed, be narrowed, or be stopped.
A defensible authorization decision applies to a defined workflow, not AI in the abstract. Passing a model test or completing a course does not establish that the combined workflow will produce acceptable work: testing supplies evidence, but the decision also depends on the system's authority, whether people can perform their assigned role, and whether the organization can find and correct failures.
The Cycle: Six Gates, One Loop
Inventory & ownership
Define work & risk
Set authority & records
Test the workflow
Authorize & monitor
Change, correct, retire
Change or failure: reassess scope and authority
The Question Each Gate Has To Answer
Inventory
What AI is in use, including unapproved use, and who owns it?
Define
What task will AI support, and what could failure affect?
Authority
What may the system read, recommend, change, or approve?
Test
Can the system and people perform representative work reliably, within a reviewer burden they can sustain?
Reviewer-burden limit: pass/fail, not a monitoring nicety
Authorize
Does pilot evidence justify routine use, and does performance hold?
Continue · Expand · Restrict · Investigate · Suspend
Register tracks the burden limit; threshold fires regardless of omission rate
Respond
What changed, what was affected, and did the response work?
Decide Before The Work Proceeds
Before allowing AI to support a consequential quality decision: name the task and accountable owner, examine representative results, and agree on what finding would make the team stop or restrict use.
What evidence would justify authorizing this workflow?
What finding would make us restrict or stop it?
Answer both before authorizing a pilot, and again before authorizing routine use.
Governing AI in Pharmaceutical Operations · Version 4.2 · Brian Drapeau, GxP Frame
Gate-by-gate requirements → page 2 · Toolkit, roles & regulatory basis → page 3
GxP Frame Visual Reference · White Paper v4.2 · Reference Sheet 1 of 2
Gate Requirements: Question, Evidence, Owner, Decision
What each of the six gates in the AI-Supported Work Authorization Cycle requires, and what “tested” has to mean before routine use.
Gate Detail: Question, Evidence, Owner, Decision, Toolkit Record
Inventory & ownership
What AI is in use, including unapproved use, and who owns it?
Use inventory; systems, data, users; named owners.
Define work & risk
What task will AI support, and what could failure affect?
Intended use, source boundary, measured baseline, risk.
Toolkit record: Gate Decision Record (light path)
Set authority & records
What may the system read, recommend, change, or approve?
Permissions, approval design, record/signature rules.
Enforced, not just instructed: the agent's own credentials must technically enforce the envelope, and each approval stays tied to the record state it reviewed. If that state changes before the agent acts, the system determines whether the approval still applies, and another review is required only where the change undermines its original basis.
Toolkit record: Gate Decision Record (Authority Envelope)
Test the complete workflow
Can the system and people perform representative work reliably?
Challenge cases, omissions, false alarms, recovery.
A reviewer's presence is not proof of review: test whether the review design detects seeded and naturally occurring errors under realistic workload. Automation bias is treated as a control failure mode, not assumed away.
Reviewer-burden limit: a pre-set pass/fail condition, not a monitoring nicety. It is set alongside the omission criterion and carried into Stage 4 and the Authorization Register.
Toolkit record: Workflow Evaluation Scoring Sheet + Adjudication Protocol
Authorize routine use & monitor
Does pilot evidence justify routine use, and does performance hold?
Pilot results, incidents, overrides, drift, feedback.
Reviewer burden is monitored against the Stage 3 limit here: the register carries the limit and the current burden against it; the action threshold fires whether or not the omission rate still looks acceptable.
Toolkit record: AI Authorization Register + Independent Effectiveness Review
Change, correct, reauthorize, retire
What changed, what was affected, and did the response work?
Change impact, regression, requalification, CAPA.
Toolkit record: Gate Decision Record + Management actions
What “Tested” Has To Mean
95% one-sided upper confidence bound on the true critical-omission rate
These numbers are the acceptance criterion worked out for one example (a bounded pilot testing an AI-supported deviation chronology), not a fixed pass mark for every workflow. Each workflow sets its own criterion sized to its own risks and failure modes: zero critical omissions in 59 independent holdout cases yields a 95% one-sided upper confidence bound of about 4.95%; if one critical omission occurs, at least 93 total cases with no further failures are required to support the same below-5% rate claim; demonstrating a rate below 1% requires 299 zero-failure cases. Cases must be independent, representative of the authorized scope, and held out from any tuning or rehearsal. These are separate statistical bounds, not alternate ways to pass: one omission may still support the same rate claim with a larger sample, but it fails this example's preset zero-omission acceptance criterion.
Reviewer burden is set in the same acceptance criterion, as a pass/fail condition, not monitored separately. The criterion states the review effort per case a reviewer can sustain and still perform the verification authorization depends on. A result above that limit is a failed condition under the pre-set monitoring rule, not an operational inconvenience. The limit and the current burden against it carry into Stage 4 monitoring and the AI Authorization Register.
Governing AI in Pharmaceutical Operations · Version 4.2 · Brian Drapeau, GxP Frame
Six-gate cycle overview → page 1 · Toolkit, roles & regulatory basis → page 3
GxP Frame Visual Reference · White Paper v4.2 · Reference Sheet 2 of 2
Toolkit, Roles & Regulatory Basis
What runs the cycle, who is accountable at each step, and the regulatory requirements and supporting guidance it sits on.
The Control Basis: Regulatory Requirements And Supporting Guidance, Not A Replacement
21 CFR 211.68 / Part 11 Electronic records & signatures
FDA data integrity / PIC/S PI 041-1 Provenance
What Runs The Cycle: The AI Work Authorization Toolkit (v4.2.1, Eight Operating Artifacts)
AI Use Inventory
Identifies actual use, ownership, status, and disposition. Does not authorize.
Gate Decision Record
Records the decision to authorize a bounded workflow, supported by the required evidence and approvals: Authority Envelope, accepted risk, reconsideration triggers.
Workflow Evaluation Scoring Sheet
Records test evidence, critical-failure handling, holdout integrity, and gate recommendation.
Adjudication Protocol
Freezes the critical-omission classification method, calibrated and blinded, before the holdout is scored.
AI Authorization Register
Aggregates current state, Decision history, and Management actions. Indexes; does not replace GDRs.
Independent Effectiveness Review Record
Tests whether authorization, monitoring, and actions actually work in practice.
User Guide
Explains the connected control sequence, artifact crosswalk, and implementation boundary.
Role Quick-Start Cards
Gives each of the eight role groups an actionable starting point.
No single artifact authorizes a workflow or demonstrates continuing effectiveness. The eight operate as one control system, alongside the companion white paper (v4.2), a Release Notes / Verification Summary, and the v4.2.1 correction notice. gxpframe.com/ai-work-authorization-toolkit
Who Operates It: Eight Role Groups, One Connected Sequence
1. Process owner
Do: Define the bounded task, baseline, downstream decision, and record path.
Never: Authorize through an inventory or register entry alone.
2. Quality owner / unit
Decide whether evidence and controls support the regulated use.
Do: Approve thresholds, critical-failure mapping, and the Adjudication Protocol before results are examined.
3. System / data / security / privacy owners
Define and enforce what the workflow may access and do.
Do: Maintain and technically enforce the approved Authority Envelope.
Never: Rely on a prompt to prohibit an available action.
4. Evaluation owner
Run the scoring sheet and produce Stage 3 evidence.
Do: Freeze the rubric and calibrate on a seeded collection before the protected holdout is scored.
Never: Confirm your own mapping as the only reviewer.
5. Assessor / operational reviewer
Judge the evidence independently and document the basis.
Do: Complete the independent assessment before seeing the AI conclusion, when the protocol requires it.
Never: Score tone or polish instead of evidence.
6. AI governance / portfolio owner
Keep organizational evidence complete, current, and traceable.
Do: Reconcile the Use Inventory, Authorization Register, and Decision history.
Never: Replace local process and quality owners.
7. Independent effectiveness reviewer
Test whether authorization and monitoring controls work in practice.
Do: Test actual use against the Authority Envelope and authorized scope.
Never: Review work you designed or operate without disclosed safeguards.
8. Management review chair
Convert organizational evidence into accountable decisions and resources.
Do: Decide whether to restrict, suspend, requalify, resource, or retire affected workflows.
Never: Accept a portfolio average that hides a failed subgroup.
What This Method Does Not Establish
That every AI-supported workflow is acceptable.
Real-world performance of the Cycle or its worked examples.
A replacement for validation or existing GMP responsibilities.
Authorization without locally approved evidence and an accountable quality decision.
Governing AI in Pharmaceutical Operations · Version 4.2 · Brian Drapeau, GxP Frame
Six-gate cycle overview → page 1 · Gate-by-gate requirements → page 2