Lubinpla

How often a supplier should review a customer's program

Summary

Review monthly when failure would be costly or the site changes often, quarterly when conditions are stable, and add one full program review each year. One public water treatment agreement sets visits at least monthly unless agreed otherwise, a written report after each, and an annual program review (OECM, 2024); the risk-based split is a planning rule, not a standard.

  • Ontario's OECM agreement 2023-438 for cooling and heating water treatment sets service visits "at least once per month or as mutually agreed upon with the supplier", with a written report after each monthly visit (OECM, 2024).

  • The same agreement adds a meeting with the customer to review the overall water treatment program once a year (OECM, 2024).

  • CDC's Legionella water management toolkit, version 1.2, says to review program elements at least once per year and again after set trigger events (CDC, 2025).

  • A routine service visit can include calibrating control and feed equipment, verifying chemical dosage and calculating consumption rates (Jamestown Technologies, accessed 2026).

This answer is for a supplier reviewing a chemical treatment or process chemical program at a customer site that is running without complaints. Where a contract, a permit or a regulation sets the review interval, that interval governs. It does not cover reviews after a failure, which follow the customer's incident process.

Which factors decide how often a customer program is reviewed?

Four factors set how often a customer program is reviewed: the consequence of failure, how fast the site changes, what the contract or rules require, and how much data reaches the supplier between visits. They fit the risk management cycle that ISO 31000:2018, a guideline ISO last reviewed and confirmed in 2023, describes as identifying, analyzing, evaluating, treating, monitoring and communicating risks (ISO 31000:2018, 2023). The review interval is the monitoring step of that cycle.

Consequence of failure comes first. Losing a program that protects a production line, a product quality limit or a safety system costs far more than losing one on a lightly loaded heating loop, so that program earns closer attention even while nothing is wrong. Rate of change comes second. Seasonal raw water, frequent product changes, new staff and ongoing projects all pull a site away from the conditions the program was designed for faster than on a steady site.

The contract or rule sets the floor: the OECM water treatment agreement in Ontario sets monthly visits unless the parties agree otherwise (OECM, 2024), and a building covered by a Legionella water management program reviews it at least once per year (CDC, 2025).

Data between visits is the last factor. If the customer logs daily tests and sends them in, the supplier can check trends without a visit and keep the full review for the scheduled date. If no data arrives, the visit is the only time anyone looks, so the interval should be shorter.

How often should a supplier review a customer program at each risk level?

Review a customer program monthly when failure is costly or the site changes often, quarterly when both are low, and in full once a year at every risk level. The decision table below sets the routine interval from those two conditions. Intervals that no cited contract or source sets are illustrative planning values.

Your conditions

Review frequency

Why

Cooling or heating water program under an agreement like OECM 2023-438

Visit at least monthly unless agreed otherwise, written report each visit, annual program review (OECM, 2024)

The contract sets the floor

Building water covered by a Legionella water management program

Program review at least once per year and after each trigger event (CDC, 2025)

The program itself requires it

Costly failure and a site that changes often

Monthly data review and visit (illustrative)

Drift starts between visits

Costly failure and a stable site

Monthly data review, quarterly visit review (illustrative)

Data catches drift; the visit confirms it

Low-cost failure and a site that changes often

Monthly data review, quarterly visit and a review after each change (illustrative)

Change causes drift even when little is lost

Low-cost failure and a stable site

Quarterly review (illustrative)

Little changes, little is lost

Any program

Full annual review of the overall program (OECM, 2024; CDC, 2025)

Checks that the design still fits the site

The row that matters most is costly failure on a changing site. There, a monthly review is the only interval short enough to catch slow drift before it reaches the customer's product or equipment. Every other row still keeps the annual full review, because a stable site can change in ways no single visit shows.

To place a customer, rate consequence of failure and rate of change separately, each as high or low, and agree the result with the customer's maintenance or utilities lead. Write the chosen interval and the reason into the service plan, so a new service representative inherits the logic and not only the date. Revisit the rating at each annual review.

Which events should trigger a program review outside the schedule?

Any event that changes what the program has to control should trigger a review outside the schedule, whatever the routine interval is. CDC's Legionella toolkit lists the triggers for building water programs: data that shows control measures persistently outside control limits, a major maintenance or water service change such as new construction, equipment changes, changes in treatment products, changes in water usage or changes in the municipal water supply, disease cases thought to be linked to the system, and changes in applicable laws, regulations, standards or guidelines (CDC, 2025).

Industrial programs follow the same logic. Review the program when production rate or product mix changes, when the raw water source or blend changes, when a pump, controller, heat exchanger or other piece of equipment is replaced, when the customer's operators or the supplier's service representative change, and when the contract terms or scope change.

A trigger review need not be full. It checks whether the change affects dose, control limits, test methods or safety documents, and records the answer. If the answer is yes, the routine interval may also need to shorten until the program settles again.

What should a supplier check in a routine program review?

A routine review answers two questions: does the customer program still deliver its results at the planned dose, and do the records support that conclusion? Use the checklist below, built from the OECM agreement's visit requirements (OECM, 2024) and one supplier's published visit list (Jamestown Technologies, accessed 2026).

  1. Review the customer's daily test records since the last visit and compare them with control limits and past months.

  2. Calibrate control and feed equipment and verify the dose actually delivered.

  3. Calculate chemical consumption from inventory and compare it with the expected material balance for the period.

  4. Test samples from each treated system and record the results with the method used.

  5. Inspect accessible equipment, corrosion coupons and deposit points.

  6. Confirm that chemicals and storage are labeled and that safety data sheets (SDS) at the site are current.

  7. Discuss operating changes and problems since the last visit with the customer's operators.

  8. Write the findings and recommendations into a report for the customer.

The material balance step is the one most often skipped. It compares the chemical the site actually used, taken from inventory, with the dose the controller reports. When the two do not match, something is wrong with the pump, the controller or the records, even if every test result looks fine.

What mistakes make routine program reviews miss problems?

Routine reviews miss problems mostly because they compare the latest reading with a limit instead of comparing the trend with the customer's own history. Five mistakes repeat.

First, a reading inside its limit gets called fine even when it has moved in the same direction for months. Slow drift stays inside limits until late. Second, the review trusts the controller's reported dose without a calibration check, so a worn pump looks like a healthy program. Third, the review skips the material balance, which is often the only cross-check between what the controller says and what the site used.

Fourth, the review covers only the visit day, while the customer's own logs between visits sit unread; the US Department of Energy advises keeping a log of make-up, blowdown, conductivity and cycles of concentration for cooling towers and monitoring trends to spot deterioration (US DOE FEMP, accessed 2026). Fifth, the annual review repeats the routine checks instead of asking whether the program design still fits the site, so a changed process keeps running on a program built for the old one.

Each of these is easy to fix with a fixed review checklist and a trend view of the customer's data.

How do you share a program review result with the customer?

Send a short written report after every review, with findings, recommendations and the test data attached, to a named contact who can act on it. The OECM agreement requires a complete written report after each monthly visit, covering all findings and recommendations and including the test report (OECM, 2024), and the US Department of Energy expects treatment programs to include routine chemistry checks with regular service reports (US DOE FEMP, accessed 2026).

Put the conclusion first: whether the program is in control, what changed since the last review and what the customer needs to do. Give each recommendation an owner and a date. Attach the test results with method and sampling point, so the next review can compare them. For the annual review, add the year's trends, the number and nature of visits, and recommendations to change the program, which the OECM agreement lists among annual review topics (OECM, 2024).

The channel matters too. Reports buried in an email thread are hard for the customer's staff to find later. For the trade-off between a portal and email, see whether an SDS portal or email works better for service reports.

When should a supplier bring in a specialist for a customer program review?

Bring in a specialist when the review finds a problem the routine checks cannot explain, or when a trigger event changes the program's design basis, the conditions the program was designed for. Four cases call for one. First, control measures stay outside control limits after the feed equipment has been calibrated and the dose verified, which points to a change in demand or chemistry. Second, corrosion coupons, deposit analysis or microbiological results are worse than in past reviews at the same location. Third, a building water system covered by a Legionella water management program has a disease case thought to be linked to it, which CDC lists as a review trigger (CDC, 2025) and which also involves the customer's public health obligations. Fourth, a major process, water source or equipment change needs a new program design rather than a dose adjustment.

Before changing hazardous chemical feed, such as acids, oxidizers or biocides, check the change against the product's SDS and the site's chemical handling rules. The specialist's findings belong in the same review record the customer already receives. In Lubinpla, the supplier registers the review result document to the customer account and shares it item by item with the customer contact through Field Care; no notification is sent, so the contact sees it on their next visit.

Frequently asked questions

Does a remote monitoring system replace routine program reviews?

No. Remote data shortens the time to spot a change, but it does not calibrate pumps, inspect coupons and deposits, check SDS files or talk with operators. Use the data to review trends between visits, and keep the on-site review for checks that need a person present.

How long should a routine customer program review take?

It should take as long as the checklist needs for that site. A single cooling tower may need one visit, while a site with boilers, closed loops and process systems needs more. Set the time by the number of treated systems and tests, not by a fixed figure.

Who at the customer should receive the program review report?

Send it to the person who can approve the recommendations, usually the maintenance, utilities or plant engineering lead, and copy the operators who run the daily tests. Name one contact as the owner of open actions, so recommendations do not stall between visits.

Related posts