Writing Policies That Protect Both Patients and Rad Techs

I've written policies that techs actually followed and policies that went straight into a binder nobody touched again. The difference isn't in the legal language or comprehensiveness. It's in whether you involve your staff and whether you write for clarity instead of liability coverage.

When I moved from my first facility to a new hospital system, I inherited a policy manual that was 2 inches thick. Radiation safety protocols, patient handling procedures, infection control, emergency procedures—all of it buried in dense corporate language. I asked my tech staff if they actually used the manual. One tech told me he'd read the first page once and never opened it again.

That's when I realized: policies aren't actually about the policy document. They're about whether your staff understands the procedure and believes it's reasonable.

Let me walk you through how to write policies that actually protect your patients and your techs—not just policies that protect you legally.

Start With Why, Not What

Here's where most department policies fail: they dive straight into the procedure without explaining the reason behind it.

A policy that says "All patients must have current identification before imaging" tells you what to do. But "Current identification prevents wrong-patient errors, which can result in serious harm to patients and significant legal liability. Verify identification before every exam" tells you why it matters.

The first version feels like bureaucratic compliance. The second version makes it clear that this isn't pointless busywork—it's protecting someone's health.

When I started rewriting our radiation safety policies, I began every section with a brief explanation of the clinical or safety reason. "Radiation safety is important because we use ionizing radiation, which carries risks. Our goal is to ensure diagnostic quality while minimizing unnecessary exposure." Not revolutionary stuff, but when your staff understands that a policy exists to protect patients and themselves, not to create paperwork, compliance improves.

This is especially important for policies that feel restrictive or inconvenient to your staff. If you're implementing a new equipment usage protocol that takes 30 seconds longer, explain why it prevents expensive equipment damage or ensures image quality. Your techs will grumble less about procedures that feel purposeful rather than punitive.

Write for People Who Don't Want to Read It

I'm not being sarcastic. Your techs are busy. They don't want to read your 4-page policy on patient positioning. They want to know the key points and when to deviate from standard procedure.

Effective policies are concise. Get to the point. Use bullet points and numbered steps instead of paragraphs. Break it into sections: Purpose, Procedure, Exceptions. Make it skimmable.

Here's an example. This is the cramped, dense version:

"In order to maintain proper infection control and prevent the spread of bloodborne pathogens and other infectious agents, all imaging equipment must be cleaned and disinfected according to manufacturer specifications. High-touch surfaces including the control room workstations, patient positioning aids, handles, and any surfaces contacted by patients with known communicable infections must be cleaned with appropriate disinfectant immediately following patient removal from the room. Proper documentation of cleaning procedures is maintained in the equipment log for regulatory compliance and incident investigation purposes."

That's one sentence and it puts you to sleep. Here's the same information, written clearly:

Equipment Cleaning and Disinfection

Clean high-touch surfaces (table, handles, positioning aids) after every patient
Use approved disinfectant [see product list in appendix]
For patients with known infections: clean immediately after they leave the room
For blood/bodily fluid exposure: use biohazard disinfectant protocol [see attached]
Log cleaning in equipment log: date, time, tech name, disinfectant used

This is faster to read, easier to reference, and more actually useful when you're in the middle of a busy shift.

Involve Your Staff in Policy Creation

Here's the insight I wish I'd had earlier in my management career: policies your staff helped create get followed better than policies handed down from above.

When I needed to revise our patient handling and positioning policies, instead of writing them myself and distributing them, I brought together three of my most experienced techs. I said: "Here's what we need to address. What are the challenges? What causes injuries? What are best practices?" They gave me real, tactical feedback. They caught things I would've missed. And when those policies rolled out, the techs bought in because they'd shaped them.

This doesn't mean policies become a committee vote where everyone gets their way. You still make final calls. But involving staff in the discussion phase reduces pushback and produces better policies.

For safety-critical policies (radiation safety, patient handling), involve your clinical staff. For administrative policies (call scheduling, attendance), involve your schedulers and supervisors. For IT policies, ask the people actually using the systems daily.

You'll discover that your staff often has legitimate concerns about proposed policies that you hadn't considered. A policy that makes sense to management might be operationally difficult. Your staff knows. Ask them.

Make Policies Specific to Your Environment

Generic policies from corporate or from templates don't account for your specific facility, equipment, or patient population.

I've seen departments use infection control policies designed for general hospitals applied to outpatient imaging centers, or radiation safety protocols for large academic centers applied to small rural facilities. The policies were technically correct but didn't fit the actual operational context.

Your policies should reference:

Your specific equipment (Siemens CT vs. GE CT have different protocols)
Your staffing model (a 24-hour facility needs different call policies than a daytime clinic)
Your patient population (pediatric imaging departments need different patient handling policies than geriatric-focused facilities)
Your resources (a well-staffed department can have different protocols than a lean operation)

When I moved to a new facility with different equipment, I adapted our radiation safety and positioning policies to match the actual scanners and equipment we were using. The core principles stayed the same, but the specific procedures reflected our reality.

Separate Critical Policies From Operating Procedures

Not all policies are equally important. Conflating critical safety policies with routine procedures dilutes both.

Your truly critical policies—the ones you need everyone to follow, every time, with no deviation—should be separated and clearly marked. Radiation safety, patient identification, emergency procedures, bloodborne pathogen protocols: these are non-negotiable. Make them distinct and make the non-negotiable nature clear.

Operating procedures—how to schedule a specific type of exam, documentation standards, quality control checks—are important but have more room for reasonable variation and judgment. Separate them.

When I restructured our policy manual, I created a "Critical Safety Policies" section and an "Operating Procedures" section. The critical policies were concise, mandatory, and reviewed annually with certification. Operating procedures were more detailed because they could be more detailed—they included context and reasoning and problem-solving guidance.

This structure made clear what was fundamental and what was operational guidance.

Document the Discipline Process

Policies should clearly outline what happens when someone doesn't follow them.

I've seen departments with excellent policies that fell apart because enforcement was inconsistent. One tech gets a verbal warning for a violation, another gets written up, another faces termination. Your staff notices. They lose faith in the policy system if they perceive inconsistent enforcement.

Your policy should include:

What constitutes violation of the policy
What the disciplinary progression is (verbal warning → written warning → final warning → termination, or whatever your model is)
Who makes discipline decisions
How to appeal or request review

Be specific. For a radiation safety violation, is a single incident grounds for written warning? What if it's a pattern? What mitigating factors matter?

I've also learned: involve your HR department in policy discipline sections. They know the legal requirements and what creates liability. Work together so your policies are both clinically sound and legally defensible.

Schedule Policy Review and Update

Policies aren't write-it-and-forget-it documents. They need regular review.

I recommend reviewing critical policies annually, at minimum. Operating procedures can be less frequent, but they should still be reviewed every 18-24 months. Equipment changes, regulations change, your staff learns better ways to do things.

Build policy review into your annual calendar. Set aside time to ask: Does this policy still reflect our reality? Are there new regulations or clinical evidence that should change this procedure? Are there unintended consequences we've discovered?

Also, when you revise policies, notify your staff clearly. Don't just distribute updated versions without explanation. Say: "We've revised our patient positioning policy based on feedback and new equipment capabilities. Here's what changed and why." This prevents confusion and helps people understand that policies evolve.

Get Real About Enforcement

Here's something nobody says out loud: you can't enforce every policy perfectly every time.

If you have 30 techs and they're all busy, someone's going to occasionally skip a non-critical step. Rather than pretending you'll catch every violation, focus enforcement on what actually matters most.

I prioritized:

Patient safety procedures (identification, positioning)
Radiation safety protocols (proper shielding, exposure documentation)
Equipment care (proper cleaning, handling)
Communication with radiologists and physicians
Everything else

When I saw a violation of the first two categories, I addressed it directly. The others, I used judgment. If a tech slightly modified a non-critical workflow step to improve efficiency and it wasn't unsafe, I let it go. If they were cutting corners on documentation or patient care, I addressed it.

Your staff is more likely to follow your policies if they believe you're enforcing fairly based on what actually matters, not creating busywork.

The Ultimate Test

The best test for a policy is whether your experienced staff would write it similarly.

Before finalizing any new policy, ask one of your most experienced, respected techs to read it and tell you honestly: would you actually follow this? Would you recommend a new hire to follow this? Does this make sense clinically and operationally?

If the answer is no, revise it. Your most experienced staff are your quality control for whether policies are actually usable.

The Real Purpose of Policies

At their core, policies exist to protect patients from harm and to create consistency in how your department operates. They're not primarily CYA documents or bureaucratic exercises, even though they serve that function too.

When you write policies with the actual goal of protecting patients and creating reasonable procedures for your staff, when you involve your team, when you enforce fairly and review regularly, they work. People follow them. They become part of your department's culture instead of being rules everyone resents.

That's the difference between a policy manual that sits on a shelf and policies that actually guide how your department operates safely and effectively.