Written and maintained by CASRAI Editorial Board
Last updated
Every animal procedure authorised under EU Directive 2010/63/EU on the protection of animals used for scientific purposes must be assigned a severity classification — one of four categories that describe the degree of pain, suffering, distress, or lasting harm an animal is expected to experience. This classification is not a formality. It is a load-bearing part of project authorisation: the competent authority’s harm-benefit analysis, the ceiling written into the authorisation itself, and the statistics the European Commission publishes each year all run on this framework. For an ethics review body, an animal welfare body (AWB), or anyone administering an animal-use protocol, getting severity classification right — both at the prospective, protocol-approval stage and in the actual, after-the-fact assessment — is a core compliance obligation, not a box-ticking exercise.
This guide covers the four severity categories defined in Annex VIII of the Directive, how prospective classification at authorisation differs from the actual severity assessment performed after a procedure, why EU institutions are required to report both, and how the framework compares conceptually to the USDA Pain and Distress Category system (Categories B–E) that US IACUCs use — a comparison that matters for anyone administering protocols across both jurisdictions.
The four severity categories under Annex VIII
Directive 2010/63/EU, Article 15, requires Member States to ensure that every procedure is classified, on a case-by-case basis, as non-recovery, mild, moderate, or severe, applying the assignment criteria in Annex VIII. The classification reflects the cumulative effect of the whole procedure on an individual animal — the most severe effect the animal is likely to experience after every appropriate refinement has been applied — not just the impact of a single step within it.
- Non-recovery — the entire procedure is performed under general anaesthesia from which the animal does not regain consciousness. Because the animal never experiences post-procedural pain, suffering, or distress, this is treated as the least severe category regardless of what is done under anaesthesia.
- Mild — procedures where the animal is likely to experience short-term mild pain, suffering, or distress, along with procedures causing no significant impairment of well-being or general condition. A single blood sample taken with minimal restraint is the commonly cited example.
- Moderate — procedures likely to cause short-term moderate pain, suffering, or distress, or long-lasting mild pain, suffering, or distress, as well as procedures causing moderate impairment of well-being. Surgery performed under general anaesthesia with appropriate post-operative analgesia typically falls here.
- Severe — procedures likely to cause severe pain, suffering, or distress, or long-lasting moderate pain, suffering, or distress, as well as procedures causing a severe impairment of well-being or general condition. Annex VIII’s illustrative examples include chronic relapsing disease models and procedures producing sustained severe distress that cannot be adequately alleviated.
Annex VIII is deliberately structured as assignment criteria plus illustrative examples, not a rigid procedure-by-procedure lookup table — the same nominal procedure (surgical implantation, for example) can land in different categories depending on species, technique, and the analgesic/anaesthetic regimen actually used, which is precisely why case-by-case classification, not a fixed list, is the legal requirement.
Prospective classification: severity at protocol authorisation
Prospective severity classification happens before a single procedure is carried out. It is submitted as part of the project application and forms part of the harm-benefit analysis the competent authority performs under Article 38 when deciding whether to authorise the project at all. At this stage, the classification is a prediction — the anticipated cumulative severity an animal will experience, given the procedures as designed and the refinements already built in — and it becomes a binding ceiling once the authorisation is granted. The non-technical project summary required under Article 43 also states the expected severity, so it is visible to the public, not just the reviewing authority.
Because this classification is set before any animal is used, it is inherently an estimate. An ethics review body or animal welfare body specifying a protocol needs to state, per procedure and per animal (or per representative animal in a cohort), the expected severity, the humane endpoints that will end a procedure early if welfare deteriorates beyond what was authorised, and how staff will monitor for signs that the actual experience is tracking above the prospective classification.
Actual severity assessment: what happens after the procedure
The Directive does not stop at the prospective estimate. Institutions are also required to record the actual severity an animal experienced, assessed retrospectively once the procedure — or, for a chronic study, the animal’s full experience — is complete. This is a genuinely separate assessment, not a copy-forward of the prospective figure: it reflects what actually happened, including any unanticipated complications, individual variation in response, or effective early intervention that kept the actual experience below what was authorised.
This matters operationally in two directions. If actual severity comes in at or below the prospective classification, that is the expected, compliant outcome. If actual severity exceeds what was authorised, that is a deviation the institution’s animal welfare body and the competent authority need visibility into — conceptually the same trigger the UK’s implementing framework under the Animals (Scientific Procedures) Act 1986 formalises as a notifiable event when actual suffering runs ahead of the licensed severity limit. A protocol that specifies only the prospective classification and has no defined process for recording and escalating actual severity has not fully implemented Article 15’s intent.
Why both figures get reported to the Commission
Article 54(2) of the Directive requires Member States to collect and make publicly available, on an annual basis, statistical information on animal use in procedures — and that statistical return is built on actual severity, not the prospective classification used at authorisation. This is a deliberate design choice: aggregating what was planned would measure institutional intent, while aggregating what actually happened measures real animal welfare impact across the EU. Reporting both figures within the compliance system — prospective at authorisation, actual at the end of the procedure — lets a competent authority audit the gap between the two: a facility whose actual severity consistently exceeds its prospective classifications is a signal worth investigating, independent of whether any single case crossed the line.
For an oversight body, this means severity classification is not a one-time field filled in on a submission form. It is a data point that has to be captured twice, on a defined timeline, with a process for reconciling the two and escalating a material gap between them.
How this compares to the US IACUC pain/distress category system
A researcher or research-administration professional working across both jurisdictions will run into a structurally different framework in the United States. Under the Animal Welfare Act, USDA’s Animal and Plant Health Inspection Service (APHIS) requires registered research facilities to report animal use annually (APHIS Form 7023) using four categories, commonly referred to as Pain and Distress Categories B–E:
- Category B — animals bred, conditioned, or held for use in research, teaching, or testing, but not yet used in an actual procedure.
- Category C — animals used in procedures involving no pain, distress, or use of pain-relieving drugs.
- Category D — animals used in procedures involving pain or distress, for which appropriate anesthetic, analgesic, or tranquilising drugs were used.
- Category E — animals used in procedures involving pain or distress, for which pain-relieving drugs were withheld because their use would have adversely affected the procedure, results, or interpretation of results.
The conceptual overlap with Annex VIII is real but partial, and the differences matter for anyone assuming a direct crosswalk:
- What is actually being graded differs. Annex VIII grades a continuum of anticipated pain, suffering, distress, and lasting harm across the whole procedure. USDA’s C/D/E split is built around a narrower, more mechanical question: was pain-relieving medication given, and if not, why not. Category E is not “the US equivalent of EU severe” — it is specifically the category for withheld analgesia, which in practice often but not always correlates with higher severity.
- Species scope is different. The Animal Welfare Act’s definition of “animal” excludes purpose-bred rats of the genus Rattus, mice of the genus Mus, and birds bred for research — species that make up the large majority of laboratory animals in practice — so USDA Pain and Distress Category reporting simply does not cover them (those species remain under an institution’s IACUC oversight via PHS Policy where federal funding applies, just not on Form 7023). The EU Directive’s protected-animal definition covers essentially all live vertebrates plus cephalopods, so Annex VIII classification applies to species that never appear in a US facility’s USDA pain/distress statistics at all.
- The reporting structure differs. The Directive builds in two distinct, formally required assessments — prospective at authorisation (Article 15) and actual at completion, feeding annual Commission-published statistics (Article 54). USDA reporting is a single annual retrospective tally per facility; the prospective equivalent exists functionally through IACUC protocol review, which sets an expected category before work begins, but that expectation is not a second, separately reported data point in the way EU actual-severity reporting is.
The practical implication for anyone drafting protocols or writing SOPs meant to satisfy both systems: don’t build a single crosswalk table that maps “EU moderate” to “USDA Category D” and call the mapping complete. Document severity against each framework’s own criteria — anticipated welfare impact for Annex VIII, analgesic use and justification for withholding it for USDA — and expect a procedure to sit in a category under one system that doesn’t obviously correspond to its category under the other.
What an ethics review body needs to specify
For a protocol moving through committee review under either framework, a defensible submission specifies:
- The expected (prospective) severity classification for each procedure, with the reasoning behind it — not just the category label, but why that category applies given the species, technique, and analgesic/anaesthetic plan.
- Humane endpoints that trigger early termination of a procedure if the animal’s condition is tracking beyond what was authorised.
- Who is responsible for the actual/retrospective severity assessment, when it happens relative to the procedure, and how it is recorded.
- The escalation path when actual severity exceeds prospective classification — who is notified, on what timeline, and what review follows.
- How refinement is applied to reduce classification over time, consistent with the 3Rs principle that underlies both the EU Directive and US oversight practice; see the broader compliance guide to IACUC and animal research oversight for how this fits the full protocol lifecycle, and IRB vs. IACUC for how animal-research oversight sits alongside human-subjects review in a research administration office.
Frequently asked questions
What does “non-recovery” mean under EU Directive 2010/63/EU?
A non-recovery procedure is one performed entirely under general anaesthesia from which the animal is not permitted to regain consciousness. Because the animal experiences no post-procedural pain, suffering, or distress, Annex VIII treats it as the least severe of the four categories, independent of how invasive the procedure itself is.
Who assigns the actual severity after a procedure is completed?
The Directive leaves the specific role to Member State implementation, but the assessment is typically performed by veterinary or animal-care staff responsible for post-procedural monitoring, working from the animal’s observed clinical signs, and is reviewed as part of the institution’s animal welfare body function — the same body that oversees compliance with the authorised project.
What happens if actual severity turns out worse than the prospective classification?
That is a deviation from what was authorised and needs to be captured and escalated, not silently absorbed into the record. Depending on Member State implementation, this can trigger a notification to the competent authority and a review of whether the project’s authorisation, humane endpoints, or refinement measures need to change.
Does Annex VIII severity classification apply to fish and other cold-blooded animals?
Yes. Directive 2010/63/EU’s definition of protected animal covers live non-human vertebrates, including fish, amphibians, and reptiles, plus cephalopods — a broader scope than the US Animal Welfare Act, whose “animal” definition excludes purpose-bred mice, rats, and birds outright.
Is USDA Pain and Distress Category E the same as EU “severe”?
Not directly. Category E specifically means pain-relieving drugs were withheld because they would have compromised the study; EU “severe” is a graded judgment about the anticipated pain, suffering, distress, or lasting harm itself. The two frameworks measure different things, and a procedure’s category under one system should not be assumed to translate directly to the other.
How often is actual-severity data reported to the European Commission?
Article 54(2) requires Member States to collect and publish statistical information on animal use, including actual severity, on an annual basis — a running, year-over-year public record rather than a one-time submission at project authorisation.








