Updated October 17, 2026.
Take this to the job site.
This article as a one-page field sheet – the direct answer, the role-consolidation map, and the four second-eyes checkpoints. Free PDF, prints clean, works offline.
The direct answer: ICRA does not scale down for small teams — the same assessment, the same precautions class, the same permit discipline apply whether the team is thirty people or three. What changes is how the roles are staffed. The infection control risk assessment names functions, not headcount: somebody assesses the risk, somebody sets the precautions, somebody builds the containment, and somebody other than the builder verifies it. In a small facility those are four hats on two or three heads. The process survives that. What it does not survive is one person wearing all four hats with no checkpoint where a second pair of eyes looks at the work.
Books for Bots: take this to your assistant.
This page as a book for your AI – the role-consolidation map, the checkpoint discipline, the call-for-help triggers, and instructions your bot can run with, including what it should ask you first. Upload it to your assistant and plan the job together.
The ASHE ICRA 2.0 framework was written by people imagining a hospital with an infection prevention department, a facilities department, a safety officer, and a design team. A community hospital may have one facilities manager, a maintenance tech or two, and an infection preventionist who is shared across a system, contracted by the hour, or carrying three other jobs. This page is for that team. The standard is the standard; the staffing plan is yours to build honestly.
What doesn’t shrink
Four things are the same size in every facility. The assessment itself: the activity type and the patient risk group still get matched through the ICRA matrix, and the precautions class still comes out of that match, not out of how busy the team is. The precautions for the class: a Class III job in a small hospital needs the same sealed barrier, negative air, and debris control as the identical job in a medical center. The permit: Class III and above, and every Class IV and V job, runs on a permit that somebody issues and somebody signs. And the daily check: containment gets inspected and the inspection gets written down for as long as the barrier stands.
Notice what is not on that list: a committee. Nothing in the process requires the assessment to happen in a meeting of eight people. It requires that the functions happen and leave evidence. A two-person assessment done carefully and documented beats an eight-person meeting that produced no paper.
Who can double up — and who can’t
Role consolidation works when the combined roles do not check their own work. The pairings that hold up:
| Combination | Verdict | Why |
|---|---|---|
| Facilities manager + safety officer | Works | Overlapping knowledge, and neither role verifies the other’s physical work |
| Project lead + permit issuer | Works, with a checkpoint | Fine for issuing; the daily containment check still needs a second person at least at start and teardown |
| Infection prevention + employee health | Works | A common small-facility pairing already; the clinical risk judgment is the same seat of expertise |
| The person who built the barrier + the only person who checks it | Does not work | Self-verification is where containment failures hide — the builder stops seeing the gap they left |
| Contractor’s superintendent + permit issuer | Does not work | The facility issues permits for work in its own building; that authority is never the vendor’s |
The pattern underneath the table: hats can stack on one head as long as the verification moments still involve a second head. Plan the stack around the checkpoints, not around the org chart.
The infection prevention seat
The seat small facilities struggle to fill is infection prevention. The ICRA needs a clinical risk judgment — which patients are in the risk group, how immunocompromised the unit next door really is — and that judgment should not default to whoever is standing closest. The arrangements that work in practice: a system-level infection preventionist who covers several facilities and joins the assessment by phone or video for higher-class work; a contracted IP consultant retained for project review rather than full-time coverage; a shared-services arrangement with a neighboring facility; or the facility’s own IP wearing the hat part-time with project work scheduled around their availability.
What matters is that the arrangement is named before the project starts, with a response time the project schedule can live with. “We’ll find someone when we get there” is how Class IV work ends up assessed by the construction schedule instead of by risk.
Checkpoint discipline: the four second-eyes moments
A lean team cannot watch a barrier all day. It does not have to. Containment fails at transitions, so verify at transitions:
- Before work starts: barrier sealed, negative air running and verified, walk-off and debris route set. Second person walks it before the first tool turns on.
- First day, mid-shift: the plan meets the building — the penetration nobody drew, the dust path nobody predicted. One walk, early, while changing course is cheap.
- Any change of scope: the job that grows from a ceiling tile to a pipe chase is a new assessment, not a longer old one. Growth past the permitted class stops and re-permits.
- Teardown: cleaning verified before the barrier comes down, not after. The most common small-team failure is an eager teardown by the same person who has been staring at the plastic for a week.
Four walks, each a few minutes, each signed on the permit. That is the whole verification system, and it fits a team of three.
The minimum kit
Small teams run ICRA well when the paperwork and materials are pre-built instead of improvised per project. The kit is short: the ICRA Class Finder for the assessment itself, with its printable worksheet carrying the class precautions for the job; a one-page permit form the facility uses every time; pre-written precautions by class so nobody drafts barrier language at midnight; negative-air machines and HEPA capacity sufficient for the largest single zone the facility would ever seal — rented for big jobs, owned for the common ones; and a stocked barrier cart (poly, tape, zipper doors, walk-off mats) that does not get raided for other work. The ICRA Readiness Check will show you which of these your program is missing.
When to call for help
Lean is a staffing model, not a virtue. Bring in outside capacity — a healthcare-experienced contractor, an IP consultant for the project, or the system office — when the work is Class IV or V; when it touches or overlooks the highest-risk areas (operating rooms, sterile processing, protective environments); when it involves a water event in an occupied patient area; or when the honest answer to “who checks this while I’m on vacation” is nobody. The trigger list belongs in writing, agreed in a calm week, because no team in the middle of a flood has ever concluded it was the day to hire help.
Documentation that survives a survey
Surveyors do not count your staff. They read your evidence. The file that answers them is thin and complete: the completed assessment for each project, the issued permits, the daily check entries for the days the barrier stood, and the sign-offs at the checkpoints. Kept in one place, in one format, for every job above Class II — that file is the program, and a three-person team produces exactly as convincing a file as a thirty-person department. The gap surveyors find in small facilities is rarely effort; it is the job that ran on a verbal okay because everyone involved already knew. Everyone knowing is not evidence. Write it down anyway — especially when everyone knows.
Frequently asked questions
Can one person run an ICRA alone?
One person can perform most of the functions, but the verification steps need a second person at the checkpoints — before work starts and at teardown at minimum. A facility with literally one facilities employee should formalize the second-eyes role with a named partner: a clinical manager, a system colleague, or a contracted reviewer.
Does a small hospital have to follow the same ICRA classes?
Yes. The precautions class comes from the construction activity type and the patient risk group, and neither of those depends on facility size. A small hospital’s highest-risk unit carries the same risk as a large one’s.
What if we have no infection preventionist on staff?
Use a system-level IP, a contracted consultant, or a shared arrangement, named in advance with an agreed response time. The clinical risk judgment in the assessment should come from that seat, not from the project schedule.
How much documentation is enough?
The assessment, the permit, the daily checks, and the checkpoint sign-offs for every job that requires a permit — one consistent format, filed in one place. Thin and complete beats thick and occasional.
Go deeper: the ICRA pillar guide walks the full process step by step; ICRA in Older Hospital Buildings covers the investigation side when the building itself is the surprise; and the Books for Bots shelf holds the companion books for the Hub’s core guides.
Run a lean team with a process that works — or a workaround you’re prouder of than this one? Tell the Hub. Practitioner corrections and field methods make these pages better, and we credit contributors the way they ask to be credited.