Proving HBT Log Reductions Through Real-World CCP Assurance

Turning One-Off Verification Into Everyday Proof

Hitting Health-Based Targets on paper is one thing, proving every day that your plant is still achieving its verified log reductions is something else entirely. Most drinking water and healthcare operators know their treatment trains were designed and commissioned to meet required log reduction values, yet that reassurance can feel thin when regulators and boards start asking, quite reasonably, whether performance is being maintained under real operating conditions.  

The practical challenge is the evidence gap. Commissioning and validation data show capability at a moment in time, with controlled tests and a lot of expert attention. Daily operations are messy, with changing raw water, staff turnover, competing priorities and the occasional equipment surprise. To respond confidently to questions about HBT compliance in Australia, we need a continuous, defensible way to show that the plant is still behaving as it was verified to behave.

At D2K Information, we see the answer as an evidence chain that links Health-Based Targets, verification results and Critical Control Point assurance. When CCPs are defined properly, connected to their verification basis and monitored in a structured way, CCP-in-control status becomes the most practical, auditable day-to-day proof that log reduction performance is being sustained.

From Health-Based Targets to Log Reduction Obligations

Health-Based Targets, as framed in the Australian Drinking Water Guidelines, are about delivering a clear health outcome, not just ticking process boxes. They express the required protection in log reduction values for different pathogen groups, and they tie those values back to the susceptibility of the population and the characteristics of the source water. Put simply, HBTs define how much risk reduction your treatment barriers need to deliver, not just what equipment you should install.  

In practice, the LRVs that show up in planning documents and risk assessments come from several inputs. Source water category, E. coli monitoring data and vulnerability assessments all feed into the tables in the ADWG when system-specific pathogen data is not available. This is why a simple statement like “6 log for viruses, 5 log for bacteria, 4 log for protozoa” can be useful shorthand, but not the whole story. Without the context of how those numbers were derived, which source water assumptions were used and how catchment risks might change, it is easy to misread what the HBT actually requires.  

The Victorian regulatory environment brings this into sharp focus. Treatment expectations are being tied more explicitly to HBTs, and there are defined duties to report log reduction shortfalls. That means drinking water providers and healthcare facilities need clear traceability from HBTs through to treatment design, verification evidence and day-to-day operational controls. For HBT compliance in Australia to stand up to scrutiny, especially when incidents or audits occur, that traceability cannot live only in design reports and commissioning files stored on a shared drive.

What Verification Really Proves and Where It Stops

Verification is the formal proof that a treatment process, configured in a specified way, can achieve the intended log removals. It brings together commissioning tests, challenge results, laboratory data and checks of process parameters like contact time, dose, turbidity and flow. Verification answers an important question: can this plant, when set up correctly, deliver the LRVs required by the HBTs that apply to this system?  

What it does not answer is the question operators get from boards and regulators later on: is it still doing it now? A plant that sailed through validation can still have days when raw water spikes, UVT drops, filters ripen slowly, valves stick or key people are covering multiple roles. None of that invalidates the original verification, but it does mean that relying solely on a historic report to prove current performance is risky.  

From an audit and incident perspective, this is where attention quickly turns. When there is a water quality complaint, a detection, or an operational event that could affect barriers, regulators want to see more than a static verification file. They look for a continuous evidence trail that supports ongoing log removal claims and any notification decisions that were made along the way. If that trail is patchy, or scattered across logbooks, spreadsheets and screenshots, it becomes hard to stand behind statements about meeting HBT-related obligations.

CCPs as the Operational Link Between Design and Proof

Critical Control Points are the stages in the treatment train where control is essential to achieving the required log reductions. These are the must-not-fail barriers: filtration steps with validated turbidity limits, UV reactors with validated dose and flow envelopes, disinfectant contact tanks that rely on minimum CT, and similar functions in healthcare water systems. When CCPs are in control, hazards are reduced to acceptable levels; when they are not, your log reduction assumptions can no longer be taken for granted.  

This is where the logic chain becomes powerful. HBTs set the target LRVs, based on source water and health protection expectations. Verification shows that, if CCPs operate within defined limits, the plant can deliver those LRVs. It then follows, in practical terms, that if you can show CCPs remained in control during operation, you have a reasonable basis to claim that log reduction performance has been maintained as designed. 

For that argument to hold up, CCP-in-control evidence has to be anchored to the verification basis. Operational limits must trace back to the conditions tested during validation, status changes need to be visible over time and any deviations must be clearly recorded with cause and corrective action. In Victoria, that evidence also needs to align with specific HBT treatment targets and the notification triggers that apply, for example, where a log reduction shortfall could prompt a Section 18 or 22 notification.

Why Manual CCP Management Breaks Under Real-World Pressure

Many teams start by managing CCPs manually, often with a mix of SCADA alarms, daily checks and spreadsheets. This can work for a simple system, but modern CCP logic is rarely simple. It often depends on multiple parameters at once, such as flow plus turbidity plus UVT plus lamp status, or disinfectant residual over a defined contact time. It also depends on process states, like whether a unit is online, bypassed or in recycle, and on specific delay or persistence rules before an exception is declared.  

Under that kind of complexity, manual systems start to show their limits. Typical failure modes include:  

• Missed exceptions when people are busy or the data is split between systems  
• False alarms when simplistic rules trigger on harmless blips, creating fatigue  
• Records scattered across screenshots, handwritten logs, email trails and shared drives  
• Long delays when trying to reconstruct a clear story after an event or during an audit  

All of this feeds back into the challenge of HBT compliance in Australia. If the organisation cannot reliably detect, classify and document CCP exceptions, it becomes hard to say with confidence that verified log reduction performance is being achieved consistently enough to satisfy HBT-related reporting expectations. The risk is not just operational; it is also about governance and trust.

Turning CCP Status Into a Defensible Evidence Trail

For water and healthcare operators, proof is not a slogan, it is evidence. A defensible CCP assurance record shows, in a way that a regulator or board member can follow, what happened, when it happened and how it was managed. That usually means an integrated record of CCP status over time, parameter values, exceptions detected, corrective actions and the point where each CCP returned to control, all in a form that can be exported and shared when needed. 

In our work at D2K Information, we see several elements as essential in that kind of record:  

• Time-stamped changes in CCP status, clearly showing in control, in exception, and back in control  
• Linked operator actions, so it is clear who did what, when and why  
• Annotations that add context, such as raw water events or maintenance activities  
• Reporting views that map directly to HBT treatment targets and Victorian regulatory triggers  

Our CCPWatch module, delivered through the Information Engine platform, is designed around those needs. Using existing SCADA and telemetry data, it applies agreed CCP rules to automatically assess status, flags issues at a glance and reduces transcription errors by generating logs and reports from the system record, not from manual re-entry. The point is not that software creates log reduction, it is that it helps you show that the verified barriers stayed in the performance envelope you claim for them.

Using CCP Assurance to Stand up Your HBT Story

When CCP assurance is structured properly, it gives operators and managers a clearer footing for decision-making. Not every exception is a crisis; some are minor operational blips that sit within your validated assumptions, while others point to a potential log reduction shortfall that may intersect with HBT-related notification duties. Having a transparent view of CCP status, duration of exceptions and CT or dose impacts helps separate those cases in a calm, documented way. 

Consider a typical narrative. A CCP exception is triggered when UV dose drops below the validated limit for a defined period. CCPWatch records the start and end of the exception, captures the relevant process data and logs the operator action, such as reducing flow and restoring dose. When it is time to report internally or respond to a regulator, the exported evidence can show that the exception was identified, classified, corrected and that log reduction targets were either maintained through redundancy or promptly restored.  

This is how the full chain comes together. Health-Based Targets define the health outcome, expressed as log reduction requirements. Verification proves that the treatment train can deliver those LRVs when CCPs operate within specified conditions. CCP assurance, grounded in real-time data and clear rules, provides the day-to-day proof that those conditions are being maintained, and that exceptions are managed in line with regulatory expectations. For organisations preparing for tighter expectations around HBT compliance in Australia, building CCP-focused evidence systems is one of the most practical ways to show that verified log reductions are not just a design ambition, but a sustained operational reality.

Strengthen Your HBT Compliance With Data-Driven Water Insights

If you are ready to take the guesswork out of HBT compliance in Australia, our team at D2K Information can help you turn your water data into reliable, defensible evidence. We work closely with you to understand your network, risks and reporting obligations so your decisions are backed by robust analytics. Reach out to contact us and start building a clearer, more compliant picture of your water infrastructure.