The Infiltrator Surprise: A Septic Tank Story
This one is offbeat, but it connects. Bear with me.
We scheduled a septic system service call after a few years of (admittedly overdue) neglect. The contractor came out, did the initial assessment, and said something like "alright, we'll pump the tank and then I'll scope the corrugated lines to make sure they're in good shape." Standard procedure for the type of system he assumed we had based on the age of the property and what's common in our area.
Except when he started digging around the distribution area, what he found wasn't corrugated pipe at all. It was an infiltrator system. Completely different technology, completely different maintenance profile, and precisely zero documentation in our property records about when it was installed or why the previous owner chose it.
Corrugated vs. Infiltrator: A Quick Primer
For anyone who hasn't spent a Saturday afternoon talking septic with a contractor (and I realize that's most people), the difference matters:
| System Type | How It Works | Common Issues |
|---|---|---|
| Corrugated pipe | Perforated pipes in gravel trenches distribute effluent into surrounding soil | Roots infiltrate perforations, gravel compacts over time, pipes can crush under load |
| Infiltrator chambers | Arched plastic chambers (no gravel needed) create air space for effluent to contact soil | Less prone to root intrusion, lighter, more surface area for absorption, but need periodic inspection of chamber integrity |
The infiltrator system is generally considered a more modern approach. Open-bottom plastic chambers sit directly on prepared soil, providing more storage volume and more soil contact area than traditional gravel-and-pipe setups. They're lighter to install, don't require trucking in gravel, and tend to have longer service lives when properly maintained.
The key phrase there being "when properly maintained," which requires knowing what system you have.
The Troubleshooter's Mindset
It's funny in retrospect that the contractor's reaction mirrored exactly what happens when an engineer opens a ticket assuming one architecture and discovers another. He paused, reassessed his assumptions, pulled up some reference material, and then adjusted his maintenance plan on the fly. No panic. No frustration. Just a recalibration based on new data.
This is the troubleshooter's mindset in action: hold your assumptions loosely, verify before you act, and adapt your approach when reality differs from expectation. The contractor didn't get flustered about being wrong. He got curious about what he was actually looking at and what it needed.
I respected that enormously. It's the same quality I look for in engineers during incident response: the ability to say "my initial hypothesis was wrong" without ego, and immediately pivot to investigating what's actually happening.
The Documentation Angle
The part that stuck with me (and the reason this connects to everything else I write about) is the documentation gap. Somewhere along the line, a previous owner made a significant infrastructure decision (installing an infiltrator system instead of the more common corrugated approach), and that decision was never captured in any property documentation we received at closing. The county records showed a septic permit but didn't specify system type. The inspection report from our home purchase mentioned the septic system existed and was functional, but didn't document the specific technology.
This is the residential equivalent of undocumented infrastructure, the exact scenario I wrote about in documentation as a leadership practice. A system that works fine until someone needs to service it, at which point the lack of documentation costs time, creates confusion, and risks incorrect maintenance procedures being applied. If our contractor had assumed corrugated and just started pumping without investigating the distribution field, he wouldn't have caused damage, but he also wouldn't have provided appropriate maintenance guidance for the actual system.
What We Learned
The practical outcome was good: the infiltrator system was in solid condition, the contractor adjusted his maintenance recommendations accordingly, and we now have proper documentation of what's in our yard (stored in a shared household folder, because I learned that lesson the hard way from managing production systems). The inspection interval, the capacity, the approximate installation date based on chamber condition, all captured.
We also learned that our soil perc rate is apparently excellent for this type of system, which explains why the previous owner chose infiltrator over corrugated. It was the right engineering decision for the site conditions. Someone just forgot to write it down.
The Universal Pattern
Everything is a system. Your septic infrastructure is a system. Your property documentation is a system (or should be). The contractor's diagnostic approach is a system. And the failure mode that caused confusion wasn't in any of those systems individually. It was in the handoff between them: the gap where institutional knowledge should have been captured but wasn't.
Whether it's a septic system, a server cluster, or a child's IEP documentation, the lesson is the same: document the decisions, document the architecture, and make that documentation discoverable by whoever comes next. Because someone always comes next, and they shouldn't have to dig (literally, in this case) to figure out what they're working with.