SOP: Emergency Unblinding Procedure

This is a ready-to-use SOP for the clinical-conduct side of emergency unblinding: the decision to reveal one subject’s treatment assignment for their immediate clinical management, and how that break is documented and contained. It is distinct in scope from the manufacturing and supply-side controls (randomization code security, product indistinguishability, comparability data) covered separately; if you need that SOP, see SOP: Randomisation, Blinding, and Emergency Code-Break Control. Replace every <<FILL: ...>> placeholder and route this through your document control. A filled specimen follows. Verify each cited regulation against the current source before you rely on it.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> and its investigator sites reveal, document, and contain the treatment assignment of a single trial subject when knowledge of that assignment is necessary for the subject’s clinical management, without compromising the blind for any other subject or for the trial as a whole.

2. Scope

This procedure applies to all blinded (single- or double-blind) protocols listed in the header, at all participating sites, twenty-four hours a day. It covers the decision to break the blind for an individual subject, the primary (IRT) and backup (manual) mechanisms, documentation, notification, and reconciliation. It does not cover the manufacturing and packaging-side controls that protect the blind before dispensing (see the SOP referenced above), and it does not cover the deliberate, planned unblinding of the study team for analysis, which follows <<FILL: SOP-ID / plan for planned unblinding and database lock>>.

3. Responsibilities

4. Definitions

• Emergency unblinding: a controlled, logged reveal of a single subject’s treatment assignment, performed because knowing the assignment is necessary for that subject’s clinical management.
• Primary channel: the IRT/RTSM emergency-unblinding function, available continuously and self-logging.
• Backup channel: a manual method (sealed per-subject envelope or a scratch-off panel on the kit or label) used only when the primary channel is unavailable.
• Containment: keeping the revealed assignment restricted to pharmacovigilance and the individuals who needed it for the subject’s care, while the sponsor conduct team learns only that a break occurred.

5. Procedure

5.1 Trigger and authorization

1. The standard for a break is narrow: knowledge of the treatment assignment must be necessary for the clinical management of the subject. If the situation can be managed without that knowledge, do not break the blind.
2. The treating investigator, or a qualified delegate at the site, makes the decision. This decision is not delegated to the sponsor and does not require sponsor pre-approval; requiring sponsor sign-off before an emergency break is a procedural failure, not a control.
3. Document the medical reason for the break at the time of the decision, in the subject’s source documentation, before or immediately after using the IRT.

5.2 Primary channel: IRT emergency unblinding

1. Log in to the IRT and select the subject.
2. Use the emergency-unblinding function. The IRT reveals the assignment to the requester only, records the event with a system time stamp, and generates the log entry described in section 5.4.
3. Confirm the notification described in section 5.5 was triggered.

5.3 Backup channel: manual code-break

1. Use the manual backup (sealed envelope or scratch-off panel) only when the IRT is confirmed unavailable.
2. Open the sealed envelope or scratch-off panel for the specific subject only; do not open envelopes for other subjects.
3. Record the same fields required in section 5.4 by hand, including the reason the IRT was unavailable.
4. Reconcile the manual break against the IRT as soon as the IRT is available again (see section 5.6).

5.4 Documentation requirements

Every break, primary or backup, is documented with all of the following, captured on the Unblinding Event Log:

1. Subject identifier and randomization number.
2. Date and exact time of the break, with time zone.
3. Who broke the blind and, where different, who authorized it.
4. The medical reason that made the break necessary.
5. The method used (IRT or the named manual mechanism).
6. The treatment revealed, recorded in a controlled, access-restricted field.
7. Confirmation that pharmacovigilance was notified and when.
8. Confirmation of what the sponsor conduct team was told (that a break occurred, not the assignment).
9. Subject outcome and whether the subject continued or discontinued.

5.5 Notification and containment

1. The IRT (or the site, for a manual break) notifies the sponsor pharmacovigilance/safety function that a break occurred, within <<FILL: e.g. 24 hours>>, so the case can be assessed and any expedited report prepared within the applicable regulatory clock.
2. Pharmacovigilance may see the assignment for case assessment. The sponsor clinical operations, medical monitor (for routine conduct), and study team are informed only that a break occurred at a named site for a named subject, never the treatment revealed.
3. Any request from the conduct team for the actual assignment is declined and escalated to <<FILL: role, e.g. Head of Clinical Operations>>.

5.6 Reconciliation

1. At the next monitoring visit, or within <<FILL: e.g. 10 business days>> for a remote review, the CRA confirms the IRT log entry matches the site’s source documentation and any manual envelope used.
2. Unreconciled breaks, or manual breaks never reconciled against the IRT, are raised as a finding to Quality Assurance.
3. At the end of the study, all breaks (IRT, manual, and any others) are reconciled in a single summary per the Blinding and Unblinding Plan.

6. Acceptance criteria

• The break was authorized under the narrow “necessary for clinical management” standard, with the reason documented.
• The break was executed and logged within minutes via the IRT, or via a documented, reconciled manual backup if the IRT was unavailable.
• All fields in section 5.4 are complete.
• Pharmacovigilance was notified within the defined window; the conduct team was informed only that a break occurred.
• The break reconciles against source documentation at the next review.

7. Records generated

Unblinding Event Log entry (see Log: Unblinding Event Log / Record); source documentation of the medical justification; pharmacovigilance case reference, where applicable; reconciliation record.

8. References

ICH E6(R2) Good Clinical Practice and ICH E6(R3) Principles and Annex 1, integrity of randomization and blinding, and investigator responsibility for subject safety. ICH E2A, clinical safety data management, definitions and standards for expedited reporting. 21 CFR 312.64 and 21 CFR 812.150, investigator reporting responsibilities (adapt citation to the applicable regulatory framework for the product type).

Confirm the current version and clause numbers of each reference before issue.

9. Revision history

10. Approvals

Filled specimen

The following shows a completed emergency-unblinding log entry for an example scenario, distinct from any example elsewhere, so you can see the level of detail expected. The company, protocol, and numbers are illustrative.

A subject enrolled in a blinded Phase 3 anticoagulant trial requires emergency surgery following a traffic accident. The surgical team needs to know whether the subject is on the active anticoagulant or placebo to plan intraoperative bleeding management and reversal strategy. The on-call investigator judges that surgery cannot be planned safely without this information and breaks the blind through the IRT.

Common inspection findings this SOP prevents

• Emergency unblinding requiring sponsor pre-approval, delaying subject care.
• Breaks with no documented medical justification, or a justification that does not support the necessity standard.
• Manual backup breaks never reconciled against the IRT.
• The sponsor conduct team learning the actual assignment through an informal notification instead of a contained one.
• Incomplete log entries missing time zone, authorizer, or method.

How to adapt this SOP

1. Set your document number, owner, and protocols in scope in the header.
2. Confirm your IRT vendor’s emergency-unblinding function meets the speed requirement in section 5.2 and test it as part of computer system validation.
3. Point section 5.5’s notification window and section 5.6’s reconciliation window to your actual pharmacovigilance and monitoring cadence.
4. Confirm every regulation in section 8 against the current published version, and against the applicable regulatory framework for your product type, before issue.