IACUC Adverse Event and Unanticipated Outcome Plan

An IACUC adverse event and unanticipated outcome plan is the written contingency component of an approved animal-use protocol that describes what investigators and animal care staff must do if an animal experiences unexpected pain, distress, injury, illness, or death outside the parameters the Institutional Animal Care and Use Committee (IACUC) reviewed and approved. It is distinct from the protocol’s routine, expected procedures: the plan exists specifically for the outcomes a study did not anticipate, and it sets out who must be notified, how quickly, and what actions (treatment, euthanasia, protocol modification) are authorized before or without further IACUC review.

Operational definition

A protocol element counts as an adverse event/unanticipated outcome plan, in the operational sense used here, when it specifies all of the following:

• Trigger criteria. A description of what counts as an “adverse event” or “unanticipated outcome” for that specific study — typically pain, distress, injury, illness, or a clinical sign that exceeds the severity, frequency, or humane endpoints the IACUC approved, or that is unrelated to the study’s approved scientific manipulations.
• Immediate response authority. Who is authorized to act immediately — in practice, this is the Attending Veterinarian (AV) or on-call veterinary staff acting under the AV’s delegated authority, who can order treatment, analgesia, or euthanasia without waiting for investigator consent or a convened IACUC meeting when an animal’s welfare requires it.
• A defined reporting pathway and timeframe. Who must be told, in what order, and how soon — typically veterinary staff first (often within hours, for anything requiring clinical judgment), then the IACUC office, with the expectation of a written incident report within a set number of business days.
• A documented outcome. A record of what happened, what action was taken, and whether the event indicates the protocol itself needs IACUC-reviewed modification — distinguishing a one-off clinical event from a pattern that suggests the approved procedures are no longer appropriate.

What the written plan must address

Institutional IACUC policies vary in format, but a compliant plan generally covers:

• Humane endpoints specific to the study — the clinical or behavioral signs (weight loss thresholds, tumor size, neurological signs, inability to access food/water) that trigger early euthanasia rather than continuing the approved endpoint.
• Pre-authorized veterinary intervention — standing orders for analgesia, supportive care, or euthanasia that the AV or veterinary staff can act on immediately, without a case-by-case investigator sign-off, when an animal’s condition falls outside what the protocol anticipated.
• After-hours and weekend coverage — consistent with the emergency-availability requirement built into the institution’s broader Program of Veterinary Care (PVC), since an unanticipated outcome does not wait for business hours.
• The internal notification chain — investigator/animal care staff to veterinary staff, veterinary staff to the IACUC office, and, for events that suggest a protocol deviation or unrelieved pain/distress inconsistent with the approved study, formal notification to the full IACUC.

The reporting pathway: investigator or animal care staff, to the AV, to the IACUC

The pathway runs in a consistent sequence at most institutions. First, whoever observes the event — an investigator, technician, or animal care staff member — reports it to veterinary staff or the AV, since the immediate priority is the animal’s welfare, not committee process. The AV or delegated veterinary staff then exercise their own, separate intervention authority (documented on CASRAI’s Attending Veterinarian entry) to treat, stabilize, or euthanize as needed. Only after the immediate welfare issue is addressed does the event move to the IACUC as a reportable occurrence, typically via a written incident or adverse-event report submitted by the investigator or veterinary staff within an institution-defined window.

Whether an individual event needs to go before the convened IACUC (rather than being logged and reviewed at the next semiannual program review) generally depends on severity and pattern: an isolated, promptly treated clinical event is usually logged and trended, while an event suggesting the protocol’s approved pain/distress parameters were exceeded, that a procedure was performed outside its approved scope, or that a pattern of similar events is emerging across a protocol typically triggers a full IACUC review and may lead to required protocol modification.

When an event triggers reporting beyond the institution

Some adverse events cross the threshold from an internal welfare/reporting matter into a mandatory external report. Institutions holding a PHS Animal Welfare Assurance must report specific categories of event to the NIH Office of Laboratory Animal Welfare (OLAW) under PHS Policy IV.F.3 — commonly summarized as any serious or continuing noncompliance with PHS Policy, any serious deviation from the provisions of the Guide for the Care and Use of Laboratory Animals, or any suspension of an activity by the IACUC. A related, separate authority — the IACUC’s own power to suspend an ongoing activity under PHS Policy IV.C.6 and 9 CFR 2.31 — can itself be triggered by a serious adverse event, and a suspension of a PHS-supported or USDA-covered activity carries its own notification obligation to OLAW or USDA/APHIS respectively. Institutions accredited by AAALAC International also expect their internal adverse-event mechanism to be functioning in practice, not just documented on paper, since it is reviewed as part of AAALAC’s periodic site visits.

Regulatory and accreditation basis

• 9 CFR 2.31 (AWA regulations). Requires the IACUC to review and approve animal-use protocols before work begins, including criteria for minimizing pain and distress, and gives the IACUC independent authority to suspend an ongoing activity that is not being conducted in accordance with the approved protocol.
• 9 CFR 2.33 (Attending Veterinarian and adequate veterinary care). Establishes the AV’s authority to intervene — order treatment or euthanasia, require analgesia, or halt a procedure — independently of, and often faster than, a full IACUC action.
• PHS Policy IV.C.1 and IV.C.6. Requires IACUC-approved protocols to describe procedures that limit pain and distress to the study’s scientific requirements, and gives the IACUC suspension authority parallel to the AWA’s.
• PHS Policy IV.F.3. The Assured institution’s reporting obligation to OLAW for serious/continuing noncompliance, serious deviations from the Guide, and IACUC-ordered suspensions.

Worked examples

Example 1 — routine adverse-event handling. A mouse on an approved tumor-growth protocol develops ulceration beyond the protocol’s specified humane endpoint over a weekend. On-call veterinary staff, acting under the AV’s standing authority, euthanize the animal immediately per the protocol’s pre-authorized humane endpoint criteria, log the event, and notify the IACUC office the next business day. Because the event fell within an anticipated, pre-authorized contingency, no full-committee review is required — it is logged and included in the next semiannual program review’s trend analysis.

Example 2 — event triggering full IACUC review. Several animals on the same protocol unexpectedly develop signs of pain outside anything the approved procedures or humane endpoints anticipated. Veterinary staff intervene on each animal individually, but the pattern itself is reported to the IACUC as a possible protocol-adequacy issue. The IACUC reviews the report, may require the investigator to amend the protocol’s analgesia plan or humane endpoints, and documents the review — consistent with the institution’s PHS Policy IV.F.3 obligation to evaluate, and where warranted report to OLAW, a serious or continuing pattern rather than treating each incident in isolation.

Counter-example

A lab that handles an animal’s unexpected, severe distress internally — treating or euthanizing the animal without any veterinary involvement, without notifying the IACUC office, and without any written record — does not meet the operational definition of an adverse event/unanticipated outcome plan in practice, even if the institution’s protocol template contains boilerplate contingency language. The regulatory and accreditation expectation is a documented, veterinary-involved, IACUC-visible process, not case-by-case investigator discretion with no record and no committee awareness.

Related terms

• IACUC (Institutional Animal Care and Use Committee) — the committee that reviews adverse events reported at this level and holds independent suspension authority.
• Attending Veterinarian (AV) — holds the immediate intervention authority an adverse-event plan relies on.
• Program of Veterinary Care (PVC) — the broader documented program the emergency/adverse-event response mechanism is part of.
• IACUC Semiannual Program Review and Facility Inspection — where logged, non-urgent adverse events are typically trended and reviewed.
• Office of Laboratory Animal Welfare (OLAW) — the external body Assured institutions must notify for serious/continuing noncompliance or IACUC-ordered suspensions.
• Animal Welfare Act (AWA) — statutory basis for 9 CFR 2.31’s protocol-review and suspension-authority requirements.
• PHS Policy — parallel basis for the IV.C and IV.F reporting requirements.
• AAALAC International — voluntary accreditation that reviews the adverse-event mechanism’s functioning in practice.
• IACUC Training — covers personnel training on recognizing and reporting adverse events.