Homeowner Added Unapproved Additive Discovered Response

Purpose

An empty jug of drain opener sitting next to an open riser, or a chemical smell that is not sewage, means today's scheduled visit is not the visit that was booked anymore. Working through a routine pump-out or inspection as though nothing changed risks two failures at once: a caustic-shocked tank treated like a normal one exposes the tech to a chemical burn the standard atmospheric gates were never built to catch, and a silent record leaves the shop holding a drainfield dispute three months later with nothing written from the day the additive was actually found.

This SOP fixes the moment of discovery: what gets checked before the tech continues any part of the original job, who decides whether to proceed, and what gets offered and documented. It hands the additive's classification off to the sibling decision tree and the customer-education framing off to the additives reference, and it owns only the on-site response between finding the evidence and closing the ticket.

Scope

Covers the technician's response the moment evidence of an unapproved additive, a chemical product, a caustic or acid substance, or a habitual overuse pattern, is discovered during any other scheduled septic visit. Does not cover classifying which additive class was used or the aerobic-biology recovery timeline, owned by the customer-added-additive-before-call decision tree, and does not cover the customer-facing education content on what helps or harms a system, owned by the septic additives and myths reference. Does not cover a spill of a customer's own product actively occurring during application; that is a live chemical event outside a residential septic tech's scope and gets referred out.

Roles and responsibilities

Role Owns The handoff
Technician The immediate hazard check, the interview, the pH or DO reading, evidence preservation Calls the service manager before proceeding with, modifying, or halting today's original scope
Service manager The proceed-or-hold decision, the remediation offer, the customer conversation Owns the decision the tech is never asked to make alone
Office Flags the disclosure on the account, checks for a prior instance Escalates a second documented disclosure on the same account to the owner
Owner Habitual-use accounts, any service-agreement language on additive use Reviews flagged accounts and sets the escalation policy

Procedure

  1. Stop and assess for an active chemical hazard the moment additive evidence is found, before continuing any part of the scheduled work. An open or empty container at the riser, an unusual chemical smell, or discoloration at the opening all count as evidence. Back away from the opening, do not continue lifting or holding the lid, and do not assume the standard gas-testing SOP's gates cover this atmosphere, since a caustic or oxidizer dump changes the off-gas chemistry those gates were built around. Acceptance: the hazard assessed and named before the lid is touched further. Wrong looks like noting the container as a footnote and continuing straight into the scheduled pump-out. Stop rule: any solvent odor, a strong ammonia or chlorine smell, or a labeled hazardous product nearby means a full stop, then gas-testing per that SOP with longer ventilation dwell time than the standard minimum before any further opening, since mixing agents already in the tank, bleach meeting an ammonia-based cleaner, can generate chloramine gas at the riser.

  2. Interview the customer using three fixed questions before sampling anything. What was added, by brand and quantity; when, in hours or days; and why, what symptom they were treating. Acceptance: three answers written down, with the container retrieved and its label read where available. Wrong looks like guessing the class from smell alone. Stop rule: if the customer is unavailable or the substance is unknown, treat it as an unidentified chemical hazard, the strictest handling class, rather than defaulting to a harmless bacterial product.

  3. Photograph the label and log the class from the sibling decision tree's categories. Match what was found to the tree's six classes, enzyme or bacterial blend, caustic or acid, strong surfactant, root killer, folk remedy, or ATU-labeled seed, without re-deriving that framework here. Acceptance: a label photograph and a named class, both on the ticket. Wrong looks like relying on memory for the brand name after leaving. Stop rule: an unreadable label or an unrecognized product routes to step 4's field test rather than being guessed as benign.

  4. Take a pH reading at the riser before proceeding with any part of today's scheduled work, for any suspected caustic, acid, or surfactant class, or any unidentified product. Compare against a near-neutral baseline for a conventional tank; on an aerobic unit, take a dissolved-oxygen and settleability reading as well. Acceptance: a pH value recorded, with DO and settleability where an ATU is involved. Wrong looks like skipping the reading because the customer described it as "just Rid-X." Stop rule: a pH outside roughly 5 to 11, or a depressed DO reading on an ATU, puts today's original scheduled work on hold pending the service manager's decision in step 5, since pumping a chemically shocked tank under a normal routine can spread the contaminated load into the truck and mask what happened.

  5. Call the service manager before deciding whether to proceed, modify, or halt today's scheduled work. This is a joint technical and liability decision, not a field call. Acceptance: a logged decision, proceed as scheduled, proceed with modified scope, or hold and reschedule, recorded before the tech continues. Wrong looks like the tech making this determination alone on site. Stop rule: if the service manager cannot be reached and a hazard gate failed in step 4, default to hold, secure the site, and leave rather than guess at a safe path forward.

  6. Where the finding is benign, class 1, 5, or 6 in the sibling tree's terms, proceed with the original scope and document the disclosure as a non-event. Acceptance: the original service completed, with the additive disclosure noted on the ticket per the sibling tree's guidance. Wrong looks like refusing to work or alarming the customer over a harmless product. Stop rule: none; this is the low-risk branch included so the procedure does not force an escalation on every disclosure regardless of what was actually found.

  7. Where the finding is a chemical hazard, offer immediate remediation and get the customer's decision in writing before leaving. Recommend a pump-out to remove the chemical load, with reseeding where an aerobic unit is involved, stated plainly with the reasoning behind it. Acceptance: a written offer and a written response, accepted or declined, both on file before the tech leaves. Wrong looks like a verbal recommendation with nothing recorded about whether the customer took it. Stop rule: if the customer declines, document the decline in their own words where possible, since this exact record is what the shop needs months later if the field ponds and the customer disputes fault.

  8. Where the disclosure reveals a repeat pattern rather than a single event, escalate to the owner rather than filing it as another routine field note. Check prior tickets on the account for an earlier additive disclosure before closing this one out. Acceptance: a prior-ticket check logged, and a second documented instance routed to the owner. Wrong looks like treating each visit's disclosure in isolation, which lets a slow biology kill go unaddressed for years because no single visit ever crosses a threshold on its own. Stop rule: none; this is a pattern-detection control rather than a stop-the-job rule.

  9. Close the ticket only once the full record is in one place. Class, the interview answers, the label photo, the pH or DO readings, the service manager's decision, and the remediation offer and response all belong on one record, not split between a verbal note to dispatch and a separate line on the invoice. Acceptance: all elements present before the ticket closes. Wrong looks like a partial record scattered across two systems. Stop rule: the ticket does not close without every element from steps 2 through 7 that applied on this visit.

The record this produces

One additive-disclosure record on the ticket: the hazard assessment from step 1, the interview answers and label photo from steps 2 and 3, any pH or DO reading from step 4, the service manager's proceed-or-hold decision from step 5, the disposition from step 6 or 7, and the prior-ticket check from step 8.

The next technician on this account reads it before assuming a clean baseline. The service manager reads it the moment a customer disputes a later finding, since a documented pH reading and a written decline from months earlier is a far stronger position than a memory of a conversation. The owner reads the flagged repeat instances quarterly, because a habitual pattern is a service-agreement conversation, not a field note.

One run of this procedure

Scheduled annual inspection at a residential ATU. Technician opens the equipment enclosure to check the panel and notices an empty gallon jug labeled as a chlorine-based cleaner sitting beside the riser, with a faint sharp smell at the opening that is not typical septic odor.

Step 1 stops the visit cold. The smell and the labeled container together meet the stop rule: no further lid movement, gas test run per the gas-testing SOP with extended ventilation before the riser opens further, since a chlorine product near a tank that may also carry ammonia-based cleaner residue raises a chloramine risk the standard test gates do not address on their own. The extended ventilation clears with all gates passing before work resumes.

Step 2: customer states she poured about half the jug down a floor drain three days earlier, trying to "freshen up" the system after noticing a mild odor. Step 3: label photographed, product identified as a chlorine-based caustic cleaner, classed per the sibling tree as the high-stakes caustic/acid class. Step 4: pH at the riser reads 11.8, outside the roughly 5 to 11 range, and on this aerobic unit the DO reading comes back well below the unit's typical operating range, confirming a chemical hit to the active biomass.

Step 5: service manager reached by phone, reviews the pH and DO figures, and holds today's scheduled routine service; the visit converts to a documented finding-and-remediation-offer call instead. Step 7: remediation offered on the spot, a pump-out to remove the chemical load plus a reseeding plan for the aerobic unit, explained in plain terms. Customer accepts in writing on the tech's tablet before the visit ends. Step 8: prior-ticket check on this account shows no earlier additive disclosure, so no owner escalation is triggered on this visit; the record now exists in case a second one ever does. Step 9: ticket closed with the hazard assessment, interview, label photo, pH and DO readings, the hold decision, and the accepted remediation all on one record.

References

  • See related: the customer-added-additive-before-call-diy-induced-upset decision tree, which owns the six-class additive framework this SOP applies without re-deriving.
  • See related: the septic-additives-myths reference, which owns the customer-education content on what helps and harms a system.
  • See related: the gas-testing-before-anyone-opens-a-tank SOP, followed with extended dwell time under step 1's hazard condition.
  • US EPA, SepticSmart onsite system guidance, for baseline additive and system-care information.