The District has no operator-certification program of its own, so running systems for hire here means working under whatever state license you already hold.
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.
Here's the one fact that changes everything on this page: D.C. has no drinking-water primacy, meaning the District doesn't run its own version of the federal Safe Drinking Water Act program. EPA Region 3 runs that program directly for D.C. instead. No D.C. agency issues operator certifications, gives an exam, or sets license grades. We checked D.C. Code and every 21 DCMR water and sanitation chapter and found no system-classification or license-grade rules at all, for drinking water or wastewater.
That's not an oversight. D.C. has basically one water utility, DC Water, which handles both drinking-water distribution and wastewater treatment (at its Blue Plains plant) for the whole District. There's no crowd of small systems for a contract-operator law to regulate. If you run systems for hire in D.C., what matters is whichever state license you already hold, usually one from Maryland or Virginia.
Source: Find EPA Drinking Water Operator Certification Contact, verified 2026-07-16.
D.C.'s code never uses the terms ORC, CORC, or "operator in responsible charge" (the person a system names as legally accountable for running it). We checked the Water Pollution Control Act definitions in D.C. Code § 8-105.02, all 41 terms defined there, and none of them is "operator," "certified operator," or any other responsible-charge role.
DC Water's own operators reportedly hold certifications from Maryland, Virginia, or other reciprocity states. That's a hiring choice the utility makes, not a D.C. legal requirement. We found no form, portal, or filing that names an operator of record for a D.C. system. If you're setting up a contract-operator arrangement here, the paper trail is whichever home-state license and service contract you use, because D.C.'s own code says nothing on the subject.
Source: D.C. Code § 8-105.02, verified 2026-07-16.
DC is a genuine outlier structurally, not just a state-silent case. (1) EPA Region 3 directly implements SDWA for DC, DC holds zero primacy, so there is no DC agency issuing drinking-water operator certifications, no DC exam, and no DC operator-of-record regime for drinking water. (2) DC has essentially a single integrated public utility, DC Water (DC Water and Sewer Authority, an independent authority since 1996), which supplies both drinking water distribution and wastewater treatment (Blue Plains AWWTF) for the District, there is no landscape of many small systems that a contract-operator statute would normally address. (3) DOEE's regulatory role is narrow: water quality standards, NPDES/pretreatment permitting (21 DCMR Ch.5, 11, 15), MS4/stormwater, wetlands, and the Water Pollution Control Act of 1984 (D.C. Law 5-188), none of which contain an operator-certification, ORC, or contract-operator regime. (4) Individual DC Water operators reportedly hold certifications from Maryland, Virginia, or other reciprocity states (per the Field Guide row); this is an employment/HR practice observed at the utility, not a DC statutory or regulatory requirement, and no DC Code or DCMR provision was found mandating it. (5) The Washington Aqueduct (US Army Corps of Engineers) supplies finished drinking water to DC Water for distribution, adding a federal-facility layer with its own (non-DC) operator standards not in scope here. Net effect: a contract-operator-for-hire model as a discrete legal category simply does not exist in DC's regulatory structure, every one of the 14 topics is state-silent by design of the jurisdiction, not by gap in research.
We found no D.C. law or rule that requires a system to file paperwork or notify anyone when it hires a contract operator. That fits the bigger picture: D.C. has basically one utility, not a field of small systems, so the filing rules other states use to track contract operators were never written here. If a D.C. entity brings you on as a contract operator, don't expect a state form. Check with EPA Region 3 or DOEE (the D.C. Department of Energy and Environment) before you assume there's nothing to sign.
This question doesn't really apply here the way it would elsewhere. D.C. has one public water and wastewater utility, DC Water, so there's no group of small independent systems for a cap-on-systems-per-operator rule to cover, and we found no such rule. If your D.C. work is ever set up around several named systems instead of the one utility, confirm that arrangement directly with DOEE or EPA Region 3. This silence comes from how the jurisdiction is built, not from a gap in our research.
We found no D.C. rule setting a minimum visit frequency for drinking water or wastewater systems, and no D.C. text that allows or bans remote or SCADA-monitored operation (running a system by computer from off-site). The Blue Plains treatment plant's NPDES permit (No. DC0021199) might contain staffing rules, but the copies we found were image-based PDFs we couldn't read as text this round.
If remote monitoring or visit frequency shows up in your contract, that term comes from the contract and from whatever state license governs your work, not from a D.C. rule. Confirm any specific commitment with the permit holder before you build a schedule around it.
D.C. has no water-sector-specific business registration, insurance, or bonding rule for contract operators. What does apply to any business in the District, contract operators included, is the Basic Business License (BBL) from DLCP (D.C.'s licensing agency), under D.C. Code § 47-2851.03. There's no dedicated water or wastewater category. A contract-operating firm would file under the generic "Environmental services" category, one of eleven BBL categories the law lists. DLCP can create new categories by regulation, but none specific to water or wastewater operation existed as of this check.
Source: D.C. Code § 47-2851.03, verified 2026-07-17.
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.
Verify against the D.C. Code and DCMR sections below, and against EPA Region 3 directly, since D.C. has no primacy agency of its own.
Rules change. Check the current text before you commit.
DC Dept. of Energy & Environment (NO PRIMACY; EPA direct)