Michigan lawmakers are approaching a decision that water professionals have watched for years. Abigail Mihaly reported for Circle of Blue on October 17, 2026, that the state Senate was poised to pass a statewide septic code intended to increase inspections and reduce human fecal waste entering lakes, rivers, and groundwater. The report on Michigan's proposed septic requirements describes the closest lawmakers have come in nearly four decades to establishing such a code.
For utilities, health departments, laboratories, engineers, and onsite wastewater contractors, passage would be a starting point rather than the final control. A septic code can create authority and minimum requirements. Whether it improves water quality depends on what triggers an inspection, what inspectors document, how failures are classified, and whether owners can complete the required response.
Define the inspection event
A requirement to inspect septic systems needs an operational trigger. Possible triggers include a property transfer, a recurring interval, a complaint, a building permit, or evidence of a discharge. Each reaches a different portion of the system inventory.
Transfer inspections may identify problems when financing is available, but they can miss properties that remain under the same ownership for decades. Periodic inspections provide broader coverage but require more administrative capacity. Complaint-driven programs direct resources toward visible trouble, although subsurface failures may not produce an obvious complaint. A workable program can use more than one trigger, provided the rules prevent unnecessary duplication.
The inspection itself also needs a defined scope. Locating a tank is not the same as assessing treatment and dispersal. Records should distinguish structural condition, liquid levels, signs of hydraulic overloading, evidence of surfacing effluent, and the condition of the dispersal area. If inspectors use inconsistent terms, the resulting database will describe activity without reliably describing risk.
Separate system failure from environmental confirmation
An onsite system can fail by more than one mechanism. A damaged tank, blocked outlet, saturated drain field, poor siting, excessive water use, or groundwater intrusion can produce different symptoms and require different corrections. A code should therefore avoid treating every unfavorable inspection as the same type of case.
Water sampling has a related but separate role. An inspection can identify defects or operating conditions without proving that a particular well, stream, or lake has received contamination from that system. Conversely, a microbial result in groundwater may justify investigation without identifying one septic system as the source. Sampling plans need appropriate locations, methods, holding times, and quality controls. Results also need interpretation within hydrogeologic and land-use context.
This distinction matters for laboratories and local agencies. If every inspection finding automatically generates the same analytical package, laboratories may receive samples that cannot answer the underlying question. Agencies should define what decision each test supports, whether that decision concerns immediate site conditions, a repair priority, or broader watershed surveillance.
Make records usable beyond enforcement
A statewide code can also improve infrastructure visibility. Many jurisdictions have incomplete information about system age, location, design, maintenance, and repair history. Standardized digital records could help officials identify inspection backlogs, recurring failure mechanisms, and areas where onsite treatment is constrained by soils, groundwater, density, or lot size.
That value depends on disciplined data design. A useful record should identify the parcel and system without exposing unnecessary personal information. It should preserve the inspection date, trigger, method, findings, required action, completion status, and supporting documents. Controlled terms are preferable to free-form notes for statewide analysis, while narrative fields remain useful for unusual site conditions.
Utilities also need boundaries around how they use the information. Septic records may support source-water planning or help explain patterns near well fields, but they do not replace monitoring at public water systems. Likewise, a mapped concentration of older systems indicates where investigation may be useful. It does not by itself establish that contamination is occurring.
Plan for the repair queue
Inspection programs can reveal more problems than the local market can promptly correct. Before implementation, agencies should estimate needs for qualified inspectors, pumpers, designers, installers, laboratories, permitting staff, and record management. They should also define which findings require immediate action and which can enter a scheduled repair process.
Clear sequencing reduces avoidable conflict. Owners need to know what constitutes failure, what documentation can rebut or refine a finding, who may design corrective work, and how completion will be verified. Regulators need a consistent escalation path when access is denied or repairs remain incomplete. None of those functions is supplied by an inspection mandate alone.
The practical test for any statewide septic code is therefore not the number of inspections performed. It is whether the program turns comparable observations into proportionate action, preserves a usable record, and connects confirmed problems with realistic correction capacity. That is the administrative treatment train behind the physical one.