Skip to content

Contract and remote water operations in Pennsylvania

Pennsylvania puts a name on hired-outside operation, calls it a circuit rider, and runs the whole arrangement on paperwork instead of a hard system cap.

Updated on: 2026-07-16

So you want to run water systems for a living

Being a contract operator means carrying responsible charge for systems you don't own, on rules that change at every state line. This page holds what this state actually requires, cited to the current rule text and dated. If you're earlier in the journey, start with the guides below.

What it takes at a glance
2026-07-16

Drinking water

License basis
The ORC (and any available operator making process control decisions) must hold a valid certificate whose class/subclassification corresponds to the water system's classification and subclassification per §§ 302.1002/302.901, i.e., certificate grade must match or exceed system classification (Classes A-D by plant hydraulic design capacity, plus subclasses 1-15+ by treatment technology and WE subclasses 7-14 for distribution), per the verified FG row and confirmed by § 302.1206's cross-reference.
Operator of record
'Operator in responsible charge', defined in § 302.101 as an individual designated by the owner to be the certified operator who makes the process control decisions directly impacting water quality/quantity; formalized further in § 302.1206. Note Chapter 302 also uses 'available operator' as the broader working term for any certified operator (onsite or reachable) making process control decisions, ORC is the owner-designated lead among available operators, with the specific duty to approve standard operating procedures and accountability for violations flowing from those SOPs.
Minimum site visits
No fixed numeric on-site visit-frequency table (e.g., X days/week by classification) was found in Chapter 302 for either water or wastewater. Instead, Pennsylvania regulates via the 'available operator' standard, a certified operator who is onsite OR able to be contacted as needed to make process control decisions in a timely manner (§ 302.101), and via the circuit-rider system-specific management plan, which must itself estimate the response time necessary to be physically present at the system (§ 302.1207(f)(4)). PLC/SCADA-monitored systems must separately demonstrate how continual staffing and monitoring will be maintained (§ 302.1208(d)). Checked §§ 302.1201, 302.1202, 302.1205, 302.1207, 302.1208, and the DEP classification-definitions page; none specify a numeric visit-frequency minimum.

Wastewater

License basis
Same class-must-correspond-to-system-classification rule applies on the wastewater side, keyed to § 302.1003 (wastewater certification classes/subclassifications, Classes A-D plus WWE4 Wastewater Collections subclass) and § 302.902 (wastewater system classification).
Operator of record
Identical term and mechanism ('operator in responsible charge,' §§ 302.101/302.1206) apply to wastewater systems, Chapter 302 uses one ORC regime across both water and wastewater.
Minimum site visits
Same finding as DW, no fixed numeric site-visit-frequency schedule found in Chapter 302 for wastewater systems; the code relies on the 'available operator' timely-contact/response standard and circuit-rider management-plan response-time estimate instead of a prescribed visit-days-per-week table.
Contract filing
Two filing tracks apply. (1) General available-operator/ORC changes: 10-calendar-day written notice to DEP via the GreenPort 'Change of Available Operator' form (§ 302.1202(c)). (2) Circuit-rider (multi-system contract operator) engagements specifically: the system owner must notify DEP within 10 days when a circuit rider is employed to operate the system (§ 302.1207(d)), and the circuit rider must submit a general work plan (business name/location, each system served, system classification, estimated weekly hours per system with visit-documentation method) plus a system-specific management plan (operators/certificates displayed, procedures/controls, emergency contact method, estimated response time to be physically present) that the owner must approve by signature before the operator may begin making process control decisions at that system (§ 302.1207(e)-(g)). Changes to these plans must also be reported within 10 days (§ 302.1207(h)-(i)).
Max systems
No numeric cap on the number of systems one operator (including a circuit rider) may serve was found in Chapter 302. § 302.1207(a)-(b) affirmatively allows an available operator to make process control decisions at more than one system, subject only to meeting all applicable requirements at each system and to the work-plan/management-plan approval process, the state regulates via disclosure and owner sign-off (estimated hours per week per system, response-time commitment) rather than via a hard system-count or distance limit.
Remote operation
Conditional. § 302.1208 explicitly allows PLC/SCADA use for process-control monitoring/decisions, but conditions it: (b) the available operator must monitor the PLC/SCADA and be ABLE TO ADJUST (or direct adjustment) when needed to maintain compliance; (c) the system must have a backup emergency plan for when the PLC/SCADA is inoperable; (d) if an owner wants a single PLC/SCADA to oversee more than one system simultaneously, the § 302.1207 system-specific management plan must additionally identify how non-automated process control decisions will be made and how continual staffing/monitoring will be maintained across those systems. Chapter 302 does not flatly prohibit off-site/remote monitoring, nor does it flatly allow unsupervised remote-only operation, it is allowed CONDITIONAL on documented monitoring capability, adjustment capability, and a contingency plan. This is a regulatory (not merely training-material) allowance, in scope.

What it takes to be a contract operator here

Pennsylvania has one rulebook, Chapter 302, for both drinking water and wastewater operators. It gives the hired-outside-operator setup a specific name: a "circuit rider." That means a certified operator making the day-to-day treatment decisions (the code calls these "process control decisions") at more than one system, where each system has different owners (25 Pa. Code § 302.101).

One certification scale covers both drinking water and wastewater. An operator's certificate has to match the system's own classification: Class A through D based on plant size, plus a subclass for the treatment technology, water distribution (WE7-14), or wastewater collection (WWE4) (§§ 302.1002, 302.1003, 302.1206). Pennsylvania's DEP Bureau of Safe Drinking Water certifies both water and wastewater operators under one program, so there's no separate wastewater board to track down.

Source: 25 Pa. Code § 302.1206, verified 2026-07-16.

Who can be the operator of record?

Pennsylvania calls the designated lead the "operator in responsible charge," or ORC. That's the person the owner names to make decisions that affect water quality or quantity (§ 302.101). The code also uses a broader term, "available operator": any certified operator who's onsite, or reachable enough, to make those decisions in time. The ORC is the owner's chosen lead among the available operators. The ORC signs off on standard operating procedures and is held accountable when a violation traces back to one (§ 302.1206).

Chapter 302 has no separate "backup ORC" term. Coverage while the ORC is away runs through that same available-operator idea, not a separate substitute role.

Source: 25 Pa. Code § 302.1206, verified 2026-07-16.

Pennsylvania's Chapter 302 is notable for regulating multi-system/contract operation almost entirely through PAPERWORK AND DISCLOSURE (10-day notice, general work plan, owner-signed system-specific management plan with self-estimated response time) rather than through hard numeric caps, no cap on number of systems per circuit rider, no fixed on-site-visit-days-per-week table, and PLC/SCADA remote oversight of MULTIPLE systems simultaneously is expressly contemplated (§ 302.1208(d)) provided the management plan documents how non-automated decisions and continual monitoring will be handled. This is a materially more flexible, disclosure-based model than states using a fixed visit-frequency or system-count formula.

Paperwork and deadlines

Owners have to report every change in available operators, including swapping the ORC, to DEP within 10 calendar days. They file through DEP's online GreenPort portal, using the "Change of Available Operator" form (§ 302.1202(c)). Circuit-rider arrangements add more paperwork on top of that. The circuit rider needs a general work plan naming the business, every system it covers, and the estimated hours per system. It also needs a system-specific management plan, which the owner has to sign before the operator can start making decisions there (§ 302.1207(e)-(g)). Any change to either plan has to be re-filed within that same 10-day window.

Source: 25 Pa. Code § 302.1207, verified 2026-07-16.

How many systems can one operator run?

Pennsylvania sets no numeric cap on how many systems a circuit rider can serve. § 302.1207(a)-(b) allows one available operator to work more than one system, as long as the work plan and the owner-signed management plan cover each one. That includes the estimated hours per week and a way to document every visit. In short, Pennsylvania controls workload through disclosure and owner sign-off, not a hard cap on the number of systems or the distance between them.

Source: 25 Pa. Code § 302.1207, verified 2026-07-16.

Site visits and remote operation

Conditional. § 302.1208 explicitly allows PLC/SCADA use for process-control monitoring/decisions, but conditions it: (b) the available operator must monitor the PLC/SCADA and be ABLE TO ADJUST (or direct adjustment) when needed to maintain compliance; (c) the system must have a backup emergency plan for when the PLC/SCADA is inoperable; (d) if an owner wants a single PLC/SCADA to oversee more than one system simultaneously, the § 302.1207 system-specific management plan must additionally identify how non-automated process control decisions will be made and how continual staffing/monitoring will be maintained across those systems. Chapter 302 does not flatly prohibit off-site/remote monitoring, nor does it flatly allow unsupervised remote-only operation, it is allowed CONDITIONAL on documented monitoring capability, adjustment capability, and a contingency plan. This is a regulatory (not merely training-material) allowance, in scope.

Chapter 302 doesn't set a fixed visit schedule, like "twice a week," for either drinking water or wastewater. Instead, it uses the available-operator standard: an operator has to be onsite, or reachable enough to act in time. A circuit rider's management plan also has to estimate the response time needed to show up in person (§ 302.1207(f)(4)).

Remote monitoring through SCADA, the computer system that lets an operator watch and run equipment from off-site, is allowed, but with conditions (§ 302.1208). The available operator still has to actively watch the system and be able to adjust it when needed. And the system needs a backup emergency plan for when SCADA goes down. If one SCADA system covers more than one facility at once, the management plan has to spell out how decisions get made when nothing is automated, and how monitoring keeps happening across all of them.

Source: 25 Pa. Code § 302.1208, verified 2026-07-16.

The business side

Pennsylvania doesn't require a contract-operator business to register, carry insurance, or post a bond. The requirement attaches to the individual's certification, not the company. The circuit rider's work plan does have to list the business name and location (§ 302.1207(e)(1)), but that's just disclosure, not a licensing hurdle. The Pennsylvania Rural Water Association and the Pennsylvania Water Environment Association both run job boards for operator work, but neither keeps an official state directory of contract operators for hire.

We run our own contract operation on Ziptility, so we've filed a work plan or two ourselves. Happy to walk through what that paperwork actually looks like day to day.

Source: 25 Pa. Code § 302.1207, verified 2026-07-16.

Carry liability insurance anyway

Most states don't make liability insurance a condition of holding a license. Carry it anyway. EPA's operator hiring guide puts it on the short list of questions every board should ask a contract operator: do you have liability insurance, and does it name the utility?

The reason is simple. You are making calls that affect public drinking water on systems you don't own. If something goes wrong, an uninsured operator puts the board's whole trust in you on the line, and boards that have been burned know to ask. Showing up to the first conversation with coverage in hand, and the certificate to prove it, closes the question before it opens. Talk to an insurance agent who handles utility contractors; policies that name each system you serve are the norm in this business.

You stay an operator. The app carries the backbone.

Every system you operate on one map, with the records, work orders, and compliance schedule your crew actually uses. We run our own contract operation on it, so the demo is the real thing, not a sandbox.

Verify against the current rules

Verify this against Pennsylvania DEP's Bureau of Safe Drinking Water directly. The circuit-rider filing requirements are more detailed than most states' and worth double-checking before you sign a management plan. Sources that carry the load here:

Rules change. Check the current text before you commit.

Pennsylvania DEP: Public Drinking Water

Contract operating in a nearby state?

Rules change at the state line. These neighbors have their own pages.