ALARA in practice: what “as low as reasonably achievable” actually means for your program

Every radiation safety program has an ALARA policy on file. Far fewer have one that actually changes behavior or would survive close inspector scrutiny. ALARA — As Low As Reasonably Achievable — is both a regulatory requirement (embedded throughout 10 CFR Part 20 and Agreement State equivalents) and a genuinely useful operating philosophy when implemented for real rather than treated as a document to produce once and file away. This guide covers what regulators actually expect an ALARA program to look like in practice.

ALARA is not the same as staying under the dose limit. This is the single most common misunderstanding. The regulatory dose limits in 10 CFR Part 20 (5 rem/year for occupational whole-body exposure, with lower limits for specific organs and for the public) are the legal ceiling, not the target. ALARA requires that exposures be kept as low as reasonably achievable below that ceiling, considering the state of technology, the economics of improvements, and the benefits to public health and safety. A program that stays comfortably under the dose limit but has never actually reviewed whether exposures could reasonably be lowered further is not, technically, an ALARA-compliant program — even though it's compliant with the numeric dose limits.

A real ALARA program has a documented, periodically reviewed dose investigation level. Most functioning programs set an internal action level below the regulatory limit — commonly some fraction of the annual limit, like 10% or 30% — that triggers a documented review when an individual's dose approaches it. The review asks: was this exposure expected given the person's role, or is something happening that could be corrected? A program with no investigation level, where dosimetry reports are filed without anyone looking at trends, is the most common gap inspectors find.

Time, distance, and shielding are the three levers, and a real ALARA review should reference all three explicitly, not just default to shielding. Reducing time in a radiation field, increasing distance from the source, and adding shielding are the three fundamental exposure-reduction tools, and they're not equally available or equally costed in every situation. A genuine ALARA review for a specific task — say, a nuclear medicine technologist drawing and administering doses — should walk through whether procedure time can be shortened, whether remote handling tools could increase effective distance, and whether additional shielding (a syringe shield, an L-block) is practical, rather than reflexively recommending "more lead" without considering the other two levers.

ALARA applies to both occupational and public exposure, and the public-facing side is often the weaker part of a program. Programs tend to focus ALARA attention on their own workers because that's where the dosimetry data lives. But ALARA equally covers exposure to members of the public — patients' family members in a treatment area, visitors near an industrial radiography site, neighbors of a facility with any environmental release pathway. If your ALARA documentation only discusses worker dose, that's a gap; a complete program addresses both.

Training is where ALARA becomes real or stays theoretical. Every worker with radiation exposure potential should receive ALARA training as part of initial and periodic radiation safety training — not generic "radiation is dangerous" messaging, but role-specific guidance on how that person's actual daily tasks connect to the time/distance/shielding levers. A nuclear medicine technologist's ALARA training should look different from an industrial radiographer's, which should look different from a dental assistant's. Generic, one-size-fits-all ALARA training that doesn't connect to actual job tasks is a common inspection finding, even when the training technically happened and was documented.

Design review is an underused ALARA tool. When planning a new facility, room, or procedure, a documented ALARA review at the design stage — before construction or procedure implementation — is one of the highest-leverage places to apply the principle, because changes are cheap before something is built and expensive after. A shielding evaluation is itself a form of ALARA design review. Equipment selection (choosing lower-dose imaging technology where clinically equivalent, for example) is another. Programs that only think about ALARA after something is already operating are missing the cheapest opportunities to apply it.

Documentation is what turns ALARA from philosophy into something an inspector can verify. A regulator cannot inspect your intentions; they can inspect your records. A functioning ALARA program should be able to produce: a written ALARA policy signed by the RSO and reviewed on a documented schedule (typically annually), records of periodic dose trend review, documentation of any investigation triggered by an elevated dose and its resolution, training records showing role-specific ALARA content, and evidence that ALARA was considered in at least the more significant facility or procedure changes made during the review period. A program that can't produce most of these when asked is, in practice, treating ALARA as a document rather than a program.

The ALARA committee, for larger programs. Organizations above a certain size and complexity — hospitals, universities, large industrial operations — often establish a formal ALARA or radiation safety committee that meets on a set cadence, reviews dose trends across the organization, and has actual authority to require changes. This isn't legally mandated by a specific numeric threshold in most jurisdictions, but larger broad-scope licenses are increasingly expected to have some form of institutional oversight beyond a single RSO working alone, and regulators will ask about it during more complex license reviews.

The common failure mode: ALARA as a document written once, at license application, and never revisited. The single most common gap in real-world ALARA programs isn't malice or negligence — it's that the ALARA policy was written to satisfy the license application requirement, filed, and then never actually operated as a living process. Dosimetry reports arrive and get filed without trend review. No investigation level was ever set, or it was set once and never checked against. Training happens on a compliance calendar but doesn't reference actual job-specific exposure scenarios. None of this shows up as a violation until an inspector specifically asks to see evidence of the ALARA program in action — at which point the gap between the policy on paper and the practice on the ground becomes very visible, very quickly.

The procurement and program implication. If you're hiring an outside CHP or radiation safety consultant, ask explicitly whether their engagement includes a functioning ALARA program review, not just a paper policy update. If you're building an ALARA program from scratch, start with a documented investigation level, role-specific training content, and a real annual review cadence — those three elements alone move a program from symbolic to genuinely operative.