South Dakota is one of the few states that spells out 'contract operator' by name -- and requires its Board to formally approve every contract.
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.
South Dakota spells it out directly: "contract operator" is a defined term in its rules (ARSD 74:21:02:67-69), meaning a certified operator who isn't employed by the system but works under a written contract that the state's Board of Certification must approve. The same term and the same rules cover both drinking water and wastewater. There's no separate wastewater version. The license grade that matters is a "class and category" match: a contract operator (or any operator in direct responsible charge, the person legally in charge of running the plant) needs a certificate for the right class (I through IV) and the right category, such as water treatment or water distribution, matching the system's own classification under the state's point system (ARSD 74:21:02:58-65). The same class-and-category rule applies to wastewater. Every system serving 500 or more people needs a certified operator in direct responsible charge.
Source: Contract operator qualifications, verified 2026-07-16.
South Dakota doesn't use the term "ORC." Its phrase is "direct responsible charge," or DRC (ARSD 74:21:02:35), meaning the person legally in charge of running the plant. At smaller facilities, DRC means the person responsible for the plant's day-to-day performance. At larger facilities that run shifts, it means being on site daily to direct the work and being in charge of a shift or a major part of the system. The definition is the same for water and wastewater. Naming a contract operator isn't a quiet notification, it's a full Board approval. The system files a request at least 21 days before the Board's next regular meeting, with the contract and proof it meets the qualification rules. The Board then gives 14 days' notice and approves the contract for compliance with SDCL 34A-3. We looked for a backup-operator rule and couldn't confirm one is currently in force -- a claim we found elsewhere about a one-month-absence hire trigger didn't hold up under a full check of the statute. Confirm with SD DANR before you rely on this.
Source: Board approval of contract operators, verified 2026-07-16.
South Dakota requires every contract-operator arrangement to be affirmatively approved by the Board of Certification itself, not merely filed/noticed: the system submits the contract 21 days ahead of a scheduled Board meeting, the Board places it on the agenda, gives 14 days' notice to both system and operator, and formally approves (or does not) the contract for SDCL 34A-3 compliance purposes. This is a heavier-touch gate than a simple notification/registration model.
South Dakota's contract must be filed with the Board at least 21 days before its next regular meeting. The contract itself has to spell out: both parties' names, addresses, and phone numbers; specific start and end dates; the minimum number of monthly on-site visits and minimum time per visit; each party's duties; and both signatures (ARSD 74:21:02:68). There's no fixed statewide expiration or renewal schedule beyond whatever dates the contract itself states. Board approval attaches to that one written agreement, not to a standing registration.
Source: Contract provisions, verified 2026-07-16.
South Dakota sets no limit on how many systems a certified or contract operator can serve. We checked the full list of all 26 sections in SDCL 34A-3 and found nothing capping the number. The real limit comes instead from the visit-frequency and availability rules below: a contract operator must be on site at least weekly (more if the Board decides the system needs it) and able to respond within an hour. That puts a practical ceiling on how many contracts one person can responsibly handle.
Source: Water Supply and Treatment System Operators, verified 2026-07-17.
A South Dakota contract operator must be on site at least once a week, or more often if the Board decides the system needs it. The contract must also separately spell out the exact minimum visit count and time per visit (ARSD 74:21:02:69(4), 74:21:02:68(3)). The same weekly-minimum-plus-Board-discretion rule applies to wastewater; there's no separate wastewater version. On top of the visit minimum, the contract operator must live close enough to respond within one hour, and be on call 24 hours a day, able to get on site in an emergency (ARSD 74:21:02:69(2)-(3)). A separately designated operator at the plant's classification level must also be available for every shift (ARSD 74:21:02:70). South Dakota's rules don't treat remote monitoring or SCADA (automated remote-control systems) as their own category. The weekly visit minimum plus the one-hour response rule are the closest thing to an answer.
Source: Contract operator qualifications, verified 2026-07-16.
South Dakota DANR's Office of Water publishes a "Look up operators in your area" PDF guide on its Operator Certification program page. We couldn't confirm how operators get added to it, or whether listing happens automatically from certification records or is something you opt into. The PDF's own link returned a 404 error when we tried to open it directly, so we couldn't check the details there either. The rules we reviewed don't cover the listing process. Confirm directly with SD DANR before you assume how this works.
Source: South Dakota Drinking Water Program, Operator Certification, verified 2026-07-16.
South Dakota has no state business registration, insurance, or bonding rule specific to contract operators. The real gate is the Board-approval process itself (ARSD 74:21:02:67-69): matching certificate class and category, the residence and response-time rule, 24/7 availability, and the on-site visit minimums. There's no rule written specifically for water or wastewater contract operators on whether they count as an independent contractor or an employee. The state's general independent-contractor rules (ARSD 47:03:07) are labor and workers'-comp rules that apply broadly, not rules written for this work.
Source: Board approval of contract operators, verified 2026-07-16.
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.
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.
South Dakota requires every contract-operator arrangement to go through full Board approval, not just a notification. That's a stricter process than most states use. Confirm the current text with SD DANR before you commit.
Rules change. Check the current text before you commit.
SD Dept. of Agriculture & Natural Resources: Drinking Water