May 15, 2026
It’s that time of year! Out with the old and in with the new as we begin to clean up our act and think how research teams can put their best foot forward for the rest of the year and that includes remaining in compliance with federal, state, and local rules, laws, and guidelines.
You know what AAALAC looks for. Your IACUC coordinator has a binder for everything. And yet, many programs that look rock-solid on paper still get hit with significant findings or issues that can threaten the progress your teams are working so hard to support.
After working for decades inside research facilities ranging from NIH-supported federal programs to lean academic vivaria, all of us at SoBran have noticed the same pattern that keeps showing up. Audit failures aren’t usually knowledge failures, but rather system failures. The gap between what your program intends to do and what it actually does on a Tuesday afternoon in February is usually the thing that can put a wrench in your program and in the end, slow your progress down.
Here’s where experienced programs still get caught:
The SOP Drift Problem
There’s no doubt your original SOPs were excellent when they were written, probably very carefully researched and properly outlined with your goals clearly in mind. But, of course, facilities evolve. Staff turns over. Workarounds for minor disruptions can become habits. And somewhere along the way, we’ve found the written procedure and the live procedure can quietly diverge into two separate tracks.
The issue is, auditors who know what they’re doing won’t just read your SOPs and call it done. They’ll watch your staff work, then compare the two. That gap is one of the most common findings in programs that consider themselves compliant.
How to fix: It’s building a regular cadence of internal walkthroughs where someone asks: Is this actually how we do it? Sometimes the SOP is outdated and the staff found a better way. Sometimes the staff have unintentionally drifted and the original SOP is still correct. Either way, you need to know where the two paths potentially deviate and you need to reconcile them before someone else does it for you.
Build this into a regular rhythm, quarterly at minimum, and any time you onboard new staff or change a procedure. The walkthrough doesn’t need to be a formal event. It can be a senior tech shadowing a newer one with a copy of the relevant SOP in hand. What matters is that it happens on a schedule, gets documented, and that discrepancies result in an actual update, making sure everyone is on the same page.
Staying On Top Of Post-Approval Monitoring
IACUC approval is table stakes, PAM is where the real compliance conversation has shifted.
Regulatory bodies have spent years refining their expectations around active protocol oversight not just approving studies, but verifying they’re running as approved. Many programs still treat PAM as a checkbox rather than a living feedback loop between the research team, the IACUC, and animal care staff. If your PAM process only activates when something goes wrong, that’s a finding waiting to happen.
How to fix: Start by pulling your current PAM records and asking a simple question: do these show a process, or just an outcome? A PAM file that only contains the annual review and an adverse event report or two isn’t evidence of active oversight, it’s merely showing that your program reacts but doesn’t monitor. Auditors know the difference.
What that looks like in practice varies by program size, but the principle is consistent. The IACUC, the research team, and animal care staff need a shared, documented line of communication that runs throughout the life of a study. If the only time those three groups are talking is during an adverse event, your PAM program is reactive by design.
Now, if your program is resource-constrained or time-constrained, this doesn’t have to mean more meetings or more paperwork but rather, the emphasis should be on smarter integration like checkpoints that align with existing study milestones or a clear protocol for who flags what and when. This demonstrates oversight at its finest, what it is supposed to look like, and auditors recognize that.
Your Training Records Are Older Than You Think
Facilities with high staff turnover know this pain….and even the most stable programs run the risk of underestimating how quickly training documentation ages out of relevance or is glossed over during that critical onboarding period.
The question auditors increasingly ask isn’t just was this person trained, but it’s can this person demonstrate competency, and is that documented? There’s a meaningful difference between a completed sign-off sheet and evidence of assessed proficiency.
Much like the SOP drift problem discussed above, all it takes is one staffing gap, one departure without proper knowledge transfer documentation, and a program can go from compliant to deficient overnight as people develop their own workarounds to address problems they aren’t sure how to solve correctly.
How to fix: Attendance records and signed acknowledgements don’t demonstrate that someone can actually perform a procedure correctly but they demonstrate that they were present during whatever the training or onboarding meetings were. We can circumvent this by building a competency verification step into onboarding that is procedure-specific and assessed by someone with appropriate authority. If a person were the only one in the room performing a task, would you have documented evidence they’ve been evaluated doing it correctly? That’s the bar.
For existing staff, run a currency audit. Pull every active employee’s training file and check not just whether records exist, but whether they reflect what that person is actually doing today. Roles drift over time, and someone performing tasks that were never formally added to their training record is a finding, even if they’re doing the work correctly.
The Environmental Monitoring Blind Spot
Temperature and humidity logs exist in almost every facility. What’s often missing is evidence that someone acted on anomalies when they occurred.
Auditors look for the full picture: the data, the deviation, and the response. A log full of out-of-range readings with no corresponding incident reports or corrective actions is worse than a clean log, but suggests a program that’s monitoring without actually managing.
If your environmental data lives in a system that nobody reviews in real time, that’s a structural gap worth closing before it becomes a finding.
How to fix: Start by auditing your last 90 days of environmental data and asking whether every out-of-range reading has a corresponding documented response. Not a mental note, not a verbal exchange between technicians, but a written record showing what happened, who was notified, and what corrective action was taken. If that trail doesn’t exist, you’re already missing some vital information.
From there, the fix is structural. Someone needs to own real-time review of environmental data: What triggers an incident report? What triggers an escalation? What’s the acceptable window between an anomaly being detected and a corrective action being logged? If those answers live only in someone’s head and not on paper, they don’t exist as far as an auditor is concerned. Write the protocol, assign the responsibility, and document that it’s being followed. For facilities running older monitoring systems that don’t support real-time alerts, this is worth a hard look at infrastructure. The technology exists to flag deviations the moment they occur.
Compliance theater is easy to spot. Auditors have seen the freshly printed logs, the SOPs dated two weeks before the visit, the staff who’ve clearly just been briefed on what to say. It doesn’t hold up.
What does hold up is a program where the animal care technician on the floor can tell you exactly why a procedure is done a certain way, not because they were coached, but because they’ve always understood the reasoning behind it. Where a PAM finding gets addressed the same week it’s identified, not filed away for the next renewal cycle. Where the facility manager isn’t dreading the visit because the day-to-day already reflects what’s on paper.
That’s not achieved through a compliance sprint. It’s the result of programs that have invested in the unglamorous work: regular internal walkthroughs, honest gap assessments, training that actually builds understanding instead of just generating signatures, and leadership that treats a near-miss as useful information rather than something to bury. At SoBran, we have done this kind of work for more than 20 years because we’ve been inside them for over two decades, across federal agencies, academic institutions, and private research organizations of every size and complexity. We’ve seen what breaks under audit pressure and if your program has an audit on the horizon, or if it’s been a while since someone asked hard questions about these procedures, this is the ideal place to start.