Why 'We’ve Always Done It This Way' Fails Under Audit Pressure

Every facility has at least one process that nobody can fully explain, except to say it's how things have always been done. The barrier gets set up a certain way because that's how the last three crews did it. The negative air machine gets placed in the same corner every time because that's where it goes. The documentation gets filled out after the fact because that's always been fast enough.

None of that is malicious, and none of it is lazy. It's just what happens when a process survives long enough without being tested. Habits calcify into standards, and standards that were never actually validated start getting treated as if they were.

The trouble is that a legacy process only looks solid because it hasn't been challenged yet. An assumption that has never been tested is not the same thing as a process that has been proven. Those two things feel identical right up until an auditor, a surveyor, or a new infection prevention lead asks the one question legacy habits are rarely built to answer: why do we do it this way, and can you show me it works.

What Is Infection Control, and Why "Always Done It This Way" Doesn't Answer It

Infection control is the set of practices, protocols, and physical controls used to prevent the transmission of pathogens between patients, staff, and the surrounding environment, particularly during construction, renovation, or maintenance activity in active healthcare facilities. In practice, that means containment barriers that hold their seal, negative air machines sized and verified for the space they're protecting, HEPA filtration that actually meets 99.97 percent efficiency at 0.3 microns, and a documented infection control risk assessment (ICRA) that connects the level of risk to the level of control being used.

That definition is deliberately specific, because infection control is not a feeling of caution. It's a set of controls that either meet a defined standard or don't. "We've always done it this way" is not a control. It's an explanation for why a control exists, and explanations are not what an auditor is asking for. An auditor is asking whether the control, right now, on this job, meets the standard it's supposed to meet.

That distinction is where legacy processes get exposed. A team can genuinely believe its infection control program is solid because nothing has gone wrong yet, while at the same time having no real answer for why the process works, only that it's what they've always done. Those are two different claims, and only one of them holds up when someone actually checks.

The Assumption: If It Hasn't Failed, It Must Be Working

Most legacy processes carry the same unspoken logic. If a barrier configuration has been used on forty jobs without an incident, the assumption is that the configuration works. If a negative air machine has always been placed in the same spot regardless of room size, the assumption is that placement doesn't matter much. If documentation has always been completed the day after setup instead of during it, the assumption is that timing is a formality.

The problem with that logic is that the absence of a failure is not evidence of a working system. It's evidence that a failure hasn't happened yet, which is a much weaker claim. The true cost of construction dust control gaps rarely comes from one dramatic collapse. It comes from a process that was quietly under-built for years, running fine until the one job where conditions were slightly different, the crew was less experienced, or the room was larger than the ones the habit was originally built around.

Legacy processes survive because they're rarely tested against the actual standard they're supposed to meet. They're tested against experience, which is a different and much softer bar. A barrier configuration that has never been checked for seal integrity has not been proven to work. It has simply not yet been asked to prove it.

Why Legacy Habits Feel Safer Than They Are

There's a real reason "we've always done it this way" feels like a defensible answer, and it's not because the people saying it are careless. It's because familiarity is genuinely reassuring, and reassurance is easy to mistake for validation.

The process has survived every job so far. A track record feels like proof, even when the track record was never measured against the actual requirement. Running the same setup forty times without a flagged incident feels like forty data points in favor of the process. It's actually forty jobs where nobody happened to check closely enough to find the gap.

Nobody wants to be the one who slows the job down to ask. Questioning a familiar process, even briefly, can feel like friction on a job that's already moving. Don't slow the room down is a real and understandable instinct, but it's also exactly the instinct that keeps unverified habits in place long after they should have been checked.

Training gets passed down instead of built in. When the correct process lives in one experienced foreman's head instead of in the equipment and workflow itself, "how we've always done it" is really shorthand for "how the last person who trained me did it," which may or may not reflect the current standard. Standardizing infection control risk assessment across teams exists specifically to close that gap, because verbal tradition is not a system.

Growth outpaces the habit that used to be good enough. A process built for a single facility with one regular crew can look completely different once a health system adds locations, contractors, and shift turnover. What was reliable at a smaller scale becomes a liability once variability increases, and legacy habits rarely get re-evaluated just because the environment around them changed.

Where Legacy Process Actually Breaks Down

A few patterns show up repeatedly when a long-standing habit finally gets tested for the first time, and none of them are about anyone acting in bad faith.

The first is a containment configuration that was never validated against the room it's currently being used in. A barrier setup that worked for a small spot repair gets reused, unmodified, on a larger renovation, because that's the configuration everyone already knows. Choosing the right containment system for healthcare facilities means matching the system to the job in front of you, not defaulting to whatever configuration is most familiar.

The second is a negative air machine placed by habit rather than by calculation. How negative air pressure works in healthcare construction depends on unit sizing, exhaust path, and a sealed barrier working together, not on placing the machine wherever it has always gone. A habit that has never accounted for room volume is a guess that hasn't been caught yet.

The third is documentation completed after the fact instead of verified during setup. A signed form proves someone remembered to fill it out. It doesn't prove pressure differentials were actually achieved and held. What happens when dust escapes containment in a hospital is rarely traced back to a form that was missing. It's traced back to a step that was documented but never actually verified.

The fourth is treating one piece of equipment as the whole system. A running negative air machine looks like compliance to a crew under schedule pressure, but most teams get the role of a negative air machine wrong precisely because habit substitutes a single visible signal for the full set of controls an ICRA actually requires.

Legacy Habit vs. Tested Process

This comparison isn't a claim that every legacy habit is wrong. Some familiar processes hold up perfectly well under scrutiny. The problem is not knowing which ones do until they've actually been tested, and an audit is a poor time to find out for the first time.

What Actually Holds Up When Someone Asks Why

Replacing "we've always done it this way" doesn't mean discarding institutional knowledge. Experienced crews know things that matter. It means separating the habits that happen to be correct from the ones that were simply never checked, and building a process where the difference doesn't depend on memory.

Validate the configuration against the room, not the last job. Room volume, containment barrier type, and negative air sizing should be calculated for the space in front of you. Where air exchange bottlenecks start creating schedule pressure shows how a configuration that worked fine on a similar-looking room can still fall short once the actual numbers are checked.

Verify performance during setup, not after. A pressure reading taken at the start of a job, and rechecked at intervals through a multi-week phase, is a very different claim than a signature added the next morning. That distinction is what separates documentation from verification.

Standardize the physical setup so the correct answer doesn't depend on who's on-site. Equipment and workflow that produce the same result regardless of crew experience remove the guesswork that legacy habits quietly depend on. Infection control equipment that holds up under audit is equipment that performs the same way on job one and job fifty, which is a higher bar than "it worked last time."

Pair training with a system, not just tradition. Healthcare compliance training paired with a standardized infection control system turns institutional knowledge into a repeatable standard instead of something that gets slightly different with every new hire who learns it secondhand.

Watch for the operational patterns that expose an untested habit early. Seven signs a dust containment strategy is failing gives teams a way to catch a legacy gap before an auditor does, rather than after.

Common Questions

Does this mean every long-standing process needs to be replaced? No. Some habits are genuinely sound and will hold up fine once tested. The point is that survival without incident is not the same as verification, and the only way to know which habits are which is to actually check them against the current standard rather than assuming based on tenure.

What's the fastest way to find out if a legacy process would hold up under audit? Ask whether the process has ever been verified against a defined requirement, such as calculated room volume, ACH targets, or documented HEPA filtration efficiency, or whether it's simply the way things have always been set up. If the honest answer is the second one, that's the gap to close first.

Isn't experienced judgment valuable in infection control? Yes, and nothing here argues against it. The issue is when judgment substitutes for verification rather than working alongside it. Experienced teams that also validate their setup are in a stronger position than teams relying on either instinct or paperwork alone.

Why does this matter more now than it used to? Facilities are managing more contractor turnover, more locations, and tighter regulatory attention than they were even a few years ago. Why passing an audit isn't the goal today covers how expectations have shifted from proving compliance once to demonstrating it consistently, which is exactly the standard legacy habits were never built to meet.

Not Every Habit Is Equally Suspect

Treating every long-standing process as a problem is its own overcorrection, and it's not a realistic use of anyone's time. A more useful way to sort them is to ask which habits are quiet and which ones are noisy.

A quiet habit runs in a stable environment. The same crew handles the same rooms, on a predictable schedule, with little turnover in who's doing the work. There's a real chance that habit is fine, not because it was ever formally validated, but because the conditions around it haven't changed enough to expose a gap if one exists.

A noisy habit is a different situation. It's a process that started in one set of conditions and is now being run somewhere further from that original context: a barrier configuration built for a small outpatient clinic now getting reused on a larger hospital wing, a negative air setup that used to see the same two technicians now handed off between rotating contractors, a documentation habit built when one facility was audited every few years now expected to hold up across a health system with five locations and constant regulatory attention.

Noisy habits are where legacy assumptions get tested whether anyone intends to test them or not. A multi-site health system managing frequent contractor turnover across several buildings is carrying a different level of exposure than a single ambulatory surgery center running the same two-person crew on familiar rooms week after week. Both may have "always done it this way" somewhere in their process. Only one of them is likely to get away with it much longer.

That's the honest place to start: not a checklist applied equally everywhere, but an inventory of which processes have drifted furthest from the conditions they were originally built for. Those are the ones worth validating first, because they're the ones most likely to be asked about next.

The Next Time Someone Asks Why

Picture an auditor, a new infection preventionist, or a corporate risk manager stopping mid-walkthrough to ask why a barrier is configured a certain way, why the negative air machine sits where it does, why documentation gets filled out after setup instead of during it.

Two different teams can face that exact question. One answers with a shrug and a reference to habit. The other points to a calculated room volume, a pressure reading taken that morning, and a setup that would look identical if a different crew ran it across town next week. Same question, same job site, two very different outcomes once someone actually checks.

That's the test "we've always done it this way" was never built to pass. Age isn't what makes a habit risky. It's having nothing to point to besides age when someone finally asks.

Talk with the HEPACART team about finding out which answer your team would give, before that question gets asked by someone whose job is to disqualify the wrong one.