What to put in a contract operator agreement
A good agreement puts your name on the responsibility, in writing, before you ever set foot on site.
Put responsible charge in writing
Start with the line that protects everyone: who is in direct responsible charge. EPA's operator hiring guide puts it plainly: the ORC can be a permanent employee or a contract operator, but the responsibility of being ORC cannot be delegated. Your agreement should say it in so many words, something like "[Name] will be in direct responsible charge of all operations and maintenance of the public water system."
That sentence does two things. It tells the board, in writing, that a licensed operator is accountable for the water quality and system-integrity calls. And it tells you, in writing, what you signed up for. A handshake and a sampling schedule is not an agreement. A named ORC, on paper, is where a real one starts.
Response time and the duty list
EPA's guide is specific about what belongs in the agreement beyond the obvious. It should name compensation, operator time, and emergency response time, then list the actual duties and how often each one happens. Owner and operator jointly work out the acceptable response time, which moves with the system's size, remoteness, and the kind of problem you might be called on.
The duty list matters more than it looks like it should. Write down every task, not just sampling, and how often each one gets done. Real maintenance has a way of quietly falling off the page when only sampling and meter reading are named. If it is not written down and scheduled, it does not happen, and neither the board nor you can prove it did.
The licensed substitute clause
Life happens. Vacations, illness, an emergency on another system. The agreement should require you to supply a licensed or certified substitute operator whenever you are unavailable or unreachable, and that substitute should hand over a current copy of their license too. EPA's guide lists the same idea for permanent staff: more than one certified operator, a certified circuit rider, or a shared operator arrangement with another system.
Covering the gap is the owner's responsibility on paper, but in practice it is yours to solve, because you are the one who knows who else is licensed and available. Naming the substitute clause up front means nobody is scrambling to find a body the week you are out.
A sampler is not an operator of record
Here is the trap EPA calls out directly: running a "monthly sampler" as if that were a remote operator. Pulling a sample once a month is not operating the system. Small-system rules expect documented site visits and real supervision, not a drive-by with a bottle.
If your agreement only describes sampling frequency, you are not protected and neither is the board. Name the visit frequency separately from the sampling schedule, and make clear what responsible charge actually looks like in practice: active oversight, documented visits, someone who runs the system, not someone who signs a form once a month.
Treating a contract operator as if a name on a form transfers the legal responsibility is the other half of the same trap. It does not. Write both pieces into the agreement so nobody, board or operator, is confused later about what the sampling visit was actually supposed to cover.
Liability stays with the board
The one thing a contract does not do, no matter how well it is written, is transfer legal responsibility off the board's desk. EPA is direct about this: hiring or contracting an operator helps a system stay compliant, but it does not remove the decision-maker's legal responsibilities. The board still owns compliance. You own the work.
That split is worth saying out loud to a board that is nervous about handing off day-to-day operations. You are not asking them to give up their legal standing, because they cannot give it up even if they wanted to. You are asking them to trust you with the operational load they were never equipped to carry alone. A written agreement that names both sides of that split, clearly, is what makes a board comfortable signing.
See it run on a real contract operation
A written agreement is the first document. If you run several systems, the harder problem shows up a year in: keeping every duty list, visit schedule, and licensed-substitute record straight across a growing book of business. That is what our contract-operator setup is built around. If you want to see how the record actually holds up system to system, the demo is the fastest way to look at it.