Skip to content

Contract and remote water operations in Utah

Utah doesn't call it 'contract operator' on the drinking water side. It calls it a Regional Operator, and it puts a one-hour travel-time clock on you.

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
Operator grade/discipline must match the drinking water system's classification under R309-300-11/-19: systems are classified via the Facilities Classification System (Small Water System, Treatment Grades T1-T4, Distribution Grades D1-D4), with the coagulation/filtration classification system in R309-300-19 applying only to systems operating coagulation and/or filtration treatment plants (chlorination-only systems are excluded from that specific sub-scheme). Minimum qualification points per grade are set out in 'Table 5' referenced by R309-300-12 (not independently re-derived, ). The 24-hour shift rule (from our Field Guide research, corroborated by program notes) requires one operator per shift to be certified at the classification of the system operated.
Operator of record
'Direct Responsible Charge' (DRC), same construct as wastewater. Defined at R309-300-4: active on-site charge and performance of operation duties, generally the operator who independently makes decisions affecting sanitary quality/safety/adequacy of delivered water. Where only one operator is employed by the system, that operator is automatically considered DRC. Specialists (any discipline/grade) are barred from being DRC or supervising DRC. The multi-system version of DRC is termed 'Regional Operator' (see co_term_dw).
Minimum site visits
SILENT in our review. R309-300-5 (General Policies) contains no minimum site-visit frequency tied to system classification/grade, only the one-hour regional-operator travel-time and 10-day change-notification requirements. No numeric visit cadence (e.g., 'X visits per week for Grade I systems') was found in R309-300-5, -11, -12, or -19 in our review.

Wastewater

License basis
R317-10-5 requires the chief operator/supervisors designated as DRC to be certified 'at no less than the level of the facility classification' (facility classification set under R317-10-6). Minimum qualification points to sit for each grade (R317-10-7): Grade I = 13 points min. (incl. 1 yr operating experience), Grade II = 14 points min. (2 yrs experience), Grade III = 16 points min. (4 yrs experience), Grade IV = 18 points min. (6 yrs experience); high school diploma/equivalent = 12 points baseline; education-for-experience substitution allowed at higher grades but not Grade I; specialized operator training may substitute for education at Grades III/IV (25 CEUs = 1 year of education).
Operator of record
'Direct Responsible Charge' (DRC), enforced through the 'Chief Operator' role, R317-10-4 defines Chief Operator as the supervisor in DRC of all shift operators for a collection or treatment system, and R317-10-5 requires the chief operator/supervisor(s) designated to be in DRC to be certified at no less than the facility's classification level.
Minimum site visits
Utah does not set a single fixed statewide visit-frequency number in rule text; instead R317-10-5 requires that when DRC services are contracted, the contract itself must specify 'the frequency of visits' as negotiated content, meaning visit frequency is a contract-term the owner and contract operator must agree to and document, not a rule-set number. No underlying regulatory minimum (e.g., 'X visits/week per Grade') was found in our review.
Contract filing
WW (R317-10-5) explicitly authorizes contracting for DRC services and mandates that any such contract include 'a clear description of the overall duties and responsibilities of the facility owner, and the responsibilities of any contracted DRC operator related to the supervision of the facility's operation, including the frequency of visits and the duties to be performed', i.e., Utah regulates DRC contracts by requiring specific content (owner/operator duties, visit frequency) rather than setting a fixed statewide visit-frequency number or a separate contract-filing deadline distinct from the 10-working-day DRC-change notice above. DW rule text found in our review does not contain an equivalent explicit 'contract for services' provision; DW's regional-operator mechanism (R309-300-4/-5) is the closest analog and carries only the change-notification (10-day) and travel-time (1-hour) requirements, not a contract-content mandate. Treat DW contract-content requirements as SILENT pending further check.
Max systems
SILENT on drinking water side in our review, R309-300-5 sets a one-hour travel-time requirement for regional operators relative to each system served (extendable by Director approval) but does not cap the number of systems one operator/regional operator or contract firm may serve. WW side (R317-10-5) likewise sets no numeric cap on systems per DRC contract operator; the only numeric constraints found are experience/education points for grade eligibility (R317-10-7), not caseload caps.
Remote operation
Silent. SILENT on SCADA-monitored/off-site remote operation as a distinct regulatory allowance or prohibition, in our review, on both barrels. Neither R309-300-5 (DW, checked specifically for this) nor R317-10-5 (WW) contains SCADA or remote-monitoring rule text; the closest DW provisions (one-hour regional-operator/backup-operator travel time) imply an expectation of physical proximity/response capability rather than affirmatively authorizing or barring SCADA-based remote operation. WW's 'on duty or on call' standard (R317-10-5) permits on-call (non-physically-present) discharge of duty but does not specifically address SCADA monitoring as the basis for that. No training-material SCADA-capability language was found in scope (out of scope regardless).

What it takes to be a contract operator here

Utah uses different words on each side. The drinking water rule never uses the phrase "contract operator." Instead it defines a "Regional Operator": a certified operator in direct responsible charge of more than one public water system (R309-300-4). That operator has to stay within one hour's travel time of every system they cover, unless the Division's Director approves more time (R309-300-5). Wastewater rule text is more direct: an owner "may enter into a contract for DRC services" - DRC means direct responsible charge, more on that below - with a certified person, or with "another public or private entity with operators certified at the appropriate level" (R317-10-5). That means a firm can hold the contract, not just an individual.

Either way, whoever covers your system needs a certification grade that matches or beats your system's classification. Drinking water grading runs through R309-300-11 and R309-300-19 (Small Water System through Treatment Grades T1-T4, Distribution Grades D1-D4). Wastewater grading runs through R317-10-6 and R317-10-7 (Grades I-IV, with minimum experience and qualification points rising by grade). Two different agencies handle certification: the Division of Drinking Water (DDW) for water, the Division of Water Quality (DWQ) for wastewater.

Source: Utah Admin. Code R309-300-11, verified 2026-07-16.

Who can be the operator of record?

Utah calls this Direct Responsible Charge, or DRC - being the certified operator actively in charge on-site, generally the one who independently makes the calls that affect water quality, safety, or supply. That core definition is the same on both sides (R309-300-4, R317-10-4). On the wastewater side, DRC runs through the Chief Operator role: the person supervising every shift operator at a collection or treatment system, certified at least as high as the facility's classification (R317-10-5).

If a drinking water system has only one certified operator, that operator automatically counts as the DRC. That default doesn't apply if the system instead uses the Regional Operator setup. Either way, someone who just drops in once a month to pull water samples isn't the DRC. The DRC is the person the state tracks as actually in charge of operating decisions.

Source: Utah Admin. Code R309-300-4, verified 2026-07-16.

No unusual/nonstandard statewide operator model found. Utah's structure is conventional DRC/backup (DW) and DRC/chief-operator (WW) certification tied to system classification, with the DW-specific 'Regional Operator' construct as the named mechanism for one certified operator (individual or, per WW's parallel provision, a firm) serving multiple systems, and RWAU's Circuit Rider program providing separate non-regulatory training/TA support (2 water + 1 wastewater field staff, min. 35 contacts/month, training-focused not fix-focused per the FG baseline).

Paperwork and deadlines

Drinking water: if the Distribution Manager, Treatment Plant Manager, or DRC operator changes or leaves, the water system has ten days to notify the Secretary to the Operator Certification Commission, in writing, through DDW (R309-300-5). Wastewater: the facility owner has to notify the Director in writing within 10 working days after a chief operator in DRC leaves or becomes unable to serve (R317-10-5). Neither rule names a specific form or portal, based on what we reviewed - confirm the exact way to submit with DDW or DWQ directly.

Source: Utah Admin. Code R317-10-5, verified 2026-07-16.

How many systems can one operator run?

Utah sets no cap on how many systems one operator, Regional Operator, or contract firm can serve. We checked R309-300-5 on the drinking water side and R317-10-5 on wastewater. The only numeric limits that exist are the experience and education points needed to sit for each grade (R317-10-7), not a limit on how many systems you can cover.

What actually limits things in practice is the one-hour travel-time rule for Regional Operators (R309-300-5). If your systems are spread an hour or more apart, response time starts working against you long before any written cap ever would.

Source: Utah Admin. Code R309-300-5, verified 2026-07-16.

Site visits and remote operation

Silent. SILENT on SCADA-monitored/off-site remote operation as a distinct regulatory allowance or prohibition, in our review, on both barrels. Neither R309-300-5 (DW, checked specifically for this) nor R317-10-5 (WW) contains SCADA or remote-monitoring rule text; the closest DW provisions (one-hour regional-operator/backup-operator travel time) imply an expectation of physical proximity/response capability rather than affirmatively authorizing or barring SCADA-based remote operation. WW's 'on duty or on call' standard (R317-10-5) permits on-call (non-physically-present) discharge of duty but does not specifically address SCADA monitoring as the basis for that. No training-material SCADA-capability language was found in scope (out of scope regardless).

Utah's wastewater rule doesn't set a fixed number of visits. Instead, R317-10-5 requires that when DRC services are contracted, the contract itself has to spell out "the frequency of visits" - visit schedule is something the owner and operator negotiate and put in writing, not a rule with a set number. The drinking water rules we reviewed (R309-300-5, -11, -12, -19) say nothing about visit frequency at all.

On being available: drinking water requires a backup operator within one hour of the system if there's only one certified operator on staff (unless a Regional Operator covers it). Wastewater requires "an operator certified at the facility level on duty or on call" (R317-10-5) - meaning on-call counts, not constant physical presence. Neither rule directly addresses SCADA or remote monitoring. The closest signal is that Utah's travel-time and on-call language cares more about proximity and response speed than about being physically on-site around the clock. Confirm current SCADA-based staffing expectations with DDW or DWQ before you build a remote-monitoring plan around this gap.

Source: Utah Admin. Code R309-300-5, verified 2026-07-16.

The business side

Utah's wastewater rule (R317-10-5) explicitly allows the contracted DRC party to be a firm - "another public or private entity with operators certified at the appropriate level" - as long as its operators hold the right certification.

We found no state-mandated business registration, bonding, or insurance rule specific to contract operators in R309-300 or R317-10, and no rule dictating employee-versus-independent-contractor status beyond the certification requirement itself. For new wastewater facilities, an appropriately certified (or restricted-certificate) operator must be hired within one year of the system being deemed operable (R317-10-5). Confirm any business-side rules beyond certification with DDW or DWQ before you draft an agreement.

Source: Utah Admin. Code R317-10-5, 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

Confirm current text with Utah's Division of Drinking Water (DDW) and Division of Water Quality (DWQ) before you commit to anything.

Rules change. Check the current text before you commit.

Utah DEQ: Division of Drinking Water

Contract operating in a nearby state?

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