Proving a procedure change reached your operators takes five records. You need the approved version with its dates, a record of who it went to, and a named, timestamped acknowledgement. Where a mistake carries a safety or public health risk, you also need a training record and a supervisor's practical sign-off. Then you need an exception list naming who hasn't done it yet. Email can't reliably hold any of these. Keep all five together, and work the exception list every week.
An inspector asks a simple question: how do you know your operators are working to the current procedure?
You can probably answer the first half. The procedure exists, it's approved, and somebody can produce the PDF.
The second half is harder. "We emailed it out" tells the inspector what you sent. But, you’ve not answered the question. They want to know if your operators received and understood it.
For a water or wastewater utility, writing the procedure is rarely the issue. After all, you know how to write a chlorine dosing SOP. What’s difficult is proving afterwards which version is live, who received it, who read it and who understands it.
This is the evidence that usually ends up spread across inboxes, paper sign-off sheets, and shared drives.
In this article, we cover the five records you need and why email can't hold them. We trace one PFAS change from approval to exception list. Then we look at when simple acknowledgement isn't enough, how long to keep everything, and the weekly report that names who's outstanding.
You need all five of the records below. If any one is missing, expect an auditor to ask about it.
The first three records follow the procedure itself, from approval to the person reading it.
Start with the approved version. Your system should record when each version came into force and when it was replaced. If an incident is investigated 18 months from now, you'll need to show what the procedure said that day.
Next is the distribution record, which shows who the procedure went to. Send it by role and site rather than from a mailing list someone keeps by hand. That way, a new starter picks it up without anyone having to remember to add them.
Then comes the acknowledgement: a name and a timestamp showing that each person read it. Keep it in the system rather than someone's inbox, so it's still on file after that person leaves.
The training record and the exception list are about your people, so they each get their own section below.
Email is the obvious way to share a procedure change, and it's easy to see why. Everyone has it, and a sent message feels like a record. But it falls short in three ways.
So keep using email to tell people a change is coming. Just make sure you keep the evidence somewhere else.
If you run a drinking water system, you're working to the PFAS limits in the EPA's National Primary Drinking Water Regulation. The limit for PFOA and PFOS is 4.0 parts per trillion. Initial monitoring is due by 2027. Where results exceed the limits, solutions must be in place by 2029.
When you publish the sampling and reporting procedure that reflects this, the right software and processes should leave you with five records. Here's how they would look:
The rule may also change. In May 2026, EPA proposed two amendments. One would let systems request two more years to meet the PFOA and PFOS limits. The other would remove the limits for PFHxS, PFNA, HFPO-DA, and PFBS. Both are still proposals under public comment, so your procedure should describe them that way.
If either is finalized, you would then revise the procedure to version 1.1 and everyone acknowledges it again. Version 1.0 stays on file with the dates it was in force.
Suppose an incident in 2028 depends on what your operators were told in 2026. You can show which version they had, who read it, and how quickly you chased the four who hadn't.
An acknowledgement shows someone received the procedure. For some changes, you also need to know they understand it and can follow it.
Use this test on every change: if doing it wrong has a safety, regulatory, or public health consequence, acknowledgement alone is not enough. The change needs learning with a knowledge check. If the task is hands-on, it also needs a supervisor's practical sign-off.
That sorts your changes into two piles:
A course completion and a supervisor's sign-off prove different things, so record them separately. The course completion shows someone understood the procedure well enough to pass a knowledge check. The sign-off shows they can carry out the task correctly on site. For high-risk changes you need both, because passing a quiz doesn't prove someone can handle a sample properly.
Remember, neither one is an operator license. Your state issues and renews those, so keep license records separate too.
Now, back to sorting your changes. Be careful which pile each one goes into, because mistakes cost you in both directions.
Give every change a course, and operators will start clicking through without reading. But if a high-risk change only gets a tick, your evidence is weakest for the task where you need it most.
Running policy acknowledgement and training in the same system also makes it easier to change your mind. If you decide a change needs a course after all, you can add one without setting it up somewhere else.
A records schedule sets how long you keep each of these.
For a Florida public utility, that's the state's General Records Schedule GS14 for Public Utilities. It took effect in June 2023, and it applies to state, county, city, and special district records custodians. You use it alongside GS1-SL for common administrative records. Where a record series appears in both, the longer retention period applies.
We won't tell you which series your acknowledgement records fall under. Your records officer already knows, and they're the right person to ask.
Before you move any content into a new system, settle three things with your records officer and counsel:
The third is the one people forget. If you can't get your records out of a system, you're stuck with it.
A completion percentage looks reassuring, but it doesn't tell you who to chase.
At 96% acknowledgement of a chlorine handling change, some people handling chlorine still haven't read it.
The report you want names them. For example, say four operators, all on nights at the north plant, haven't acknowledged a revision published 11 days ago. Because you can identify them, that's one call to one supervisor and you can ensure that you reach 100% quickly.
Run the exception list every week, rather than the week before an audit. When an audit comes round, there should be no exceptions. A record of you chasing and closing those names each week is useful evidence too.
Claromentis Enablement Hub keeps the procedure, its approval history, and your staff follow-up records in one place. Three parts of it cover the five records:
For a compliance manager, that's one place to show an inspector the version, who received it, who read it, and who still hasn't.
Your utility owns the regulatory interpretation and the approval. Enablement Hub keeps the records that show a change reached your people and what they completed. We don't decide what a rule requires, and you should be wary of any vendor who suggests otherwise.
Some evidence also belongs elsewhere. Laboratory results and regulatory submissions stay in the systems built for them. And when you're scoping, ask us to show you the export for your own record types. It's the same test we'd tell you to apply to anyone.
We're ISO 27001:2022 certified, and you can host in our secure cloud or on your own infrastructure. Your IT team will ask about security and hosting. Your records officer will want to know where the records are held.
South Coast Water District supplies potable water, recycled water, and wastewater collection across South Orange County, California. It has around 100 staff split between offices and the field.
Its SOPs and communications had spread across shared drives, email, and standalone tools, all on a server due for decommissioning.
The district moved onto one hub. It now runs a knowledge base for SOPs and onboarding, and digital forms for employee requests and approvals. A mobile app lets field crews reach the current version from a phone. Having one place to find procedures is the first step toward keeping all five records.
You probably have two or three of these already:
Start with whichever one you can't produce. That's where an auditor is most likely to find a problem.
We've built a water utility SOP template with the approval, version, distribution, and acknowledgement fields laid out. Use it to see the model on paper before you decide anything about software.
Download the water utility SOP template
Or you can book a discussion call with one of our experts. We'll show you how your SOPs and policies could be reviewed, shared, supported with learning, and tracked in Claromentis Enablement Hub.