Septic service readiness brief
This reads the septic record you built in the project planner and works out what is worth preparing for, what questions your unknowns generate, and what needs a professional on the property. It runs entirely in your browser and sends nothing anywhere.
What a readiness brief is for
Most septic visits begin with discovery. Where are the lids. When was it last pumped. Is there a pump. Does anyone have the permit. That hour is billable, it happens on the homeowner’s time, and almost all of it is information the homeowner either already has or can obtain for nothing before the van arrives.
The brief exists to move that work earlier and to be honest about the part that cannot move. It sorts what you have recorded into topics worth preparing for, and — the part that matters more — states plainly what is still not established for each one. A topic appearing here never means something is wrong. It means it is worth being able to answer.
It is deliberately unexciting. There is no score, no risk rating, no failure probability and no predicted replacement date. Those numbers are easy to generate and impossible to justify: they would compress unrelated unknowns into a single figure that a homeowner would read as a verdict about their system, and no basis exists for the weighting. What you get instead is a list, with the reasoning shown.
How the five applicability states are used
Every topic lands in one of five states, and the difference between the last two is the one people usually collapse.
| State | What it means |
|---|---|
| Needs to be covered | Something recorded makes this part of the conversation. It is not a finding about the system. |
| Worth confirming | Worth having an answer to before the visit, but nothing turns on it today. |
| May affect service preparation | Relevant only if particular conditions apply on the day — ground conditions, access, or what the work turns out to involve. |
| Not applicable | Nothing recorded suggests this applies. A judgement, made from real answers. |
| Not yet documented | Too little recorded to judge it either way. Deliberately not the same as “not applicable”, because an open question and a closed one call for different things. |
An unknown is never promoted. If pumping history is unknown, it stays unknown — it does not become “overdue”, because whether a system is due for service depends on design, use, condition and professional guidance together, and none of those is established by a date being missing.
Where the questions come from
Questions are generated only from unknowns that actually apply. A gravity system with no pump recorded produces no questions about a control panel. A record with a documented recent pumping produces no question asking when it was last pumped. This is why the question list on a well-filled record is often shorter than on a sparse one, and why a short list is a good sign rather than a thin one.
Each question is labelled with restraint: not yet documented, worth confirming, may affect service preparation, or requires onsite evaluation. None of them says “warning” or “red flag”, because a tool that shouts at you about every gap teaches you to stop reading it, and the gaps that matter are the ones a professional was going to ask about anyway.
What it will never tell you
- That your system has failed, or that your drainfield has. Several of the observations recorded here have explanations that are not the septic system at all, and distinguishing among them needs someone on the property.
- That pumping will resolve a symptom. Sometimes it does and sometimes it does not, and which is which is established onsite.
- When to pump. No interval is generated, ever.
- What anything will cost, or how long a system has left. Both would be invented.
- Whether anything complies with local rules, or whether a permit is required. Those are set by an authority with jurisdiction over your property, and SepticOwner does not maintain their requirements.
- Anything about a specific contractor. No ranking, no rating, no vetting claim.
These are not disclaimers bolted on at the end. They are enforced: the build fails if a page in this repository states any of them, and the readiness engine has no code path that could produce one.
Printing it
The print view drops the navigation, the buttons and the explanatory sections, and keeps the record id, the schema version, the generation date, the source labels, the unknowns, the professional-evaluation flags and the limitations. It reads in black and white, and it states on its face that it is not an inspection, a diagnosis, a permit record, a compliance certification, a maintenance guarantee, an estimate or a professional report.
Use your browser’s print-to-PDF. Nothing is uploaded to produce it, and no contact details appear on it unless you have entered them somewhere else entirely.
Where this fits
- Septic project planner — builds the record this brief reads.
- Ownership record and maintenance planner — the permanent history behind the record, and what is still missing from it.
- Site-visit checklist — what you can safely observe, and what only the visit can establish.
- Contractor scope request — the printable sheet you hand over on the day.
- Inspection-report decoder — if you already have a report and want the terminology explained.
- Questions to ask a septic contractor — the wider question set, before, during and after a visit.
About this brief
Does this tell me what is wrong with my system?
No, and it is built so that it cannot. It organises what you have recorded and works out which topics are worth preparing for. It does not name a cause, decide whether a component has failed, recommend a repair, or establish that anything needs replacing. Those require a qualified professional on the property.
Will it tell me when to pump the tank?
No. Pumping frequency depends on system design, use, condition and professional guidance together, and nothing here calculates it. If your pumping history is unknown, the brief records it as unknown — it never converts that into "overdue".
Where is my record stored?
In this browser, under one versioned key, at schema version 3. There is no account, no sync and no cloud backup, so it will not follow you to another device. If a stored record cannot be read, it is cleared rather than partly trusted — reading half a record is worse than reading none, because you cannot see which half survived.
Is anything sent to SepticOwner or a contractor?
Not from this page. Nothing here submits anything. If you later choose to send an inquiry, you review the exact list of what would travel with it first, and you can send the inquiry without sharing any of the record at all.
Why does it say "not yet determinable" instead of flagging a problem?
Because there is a real difference between "this does not apply" and "we cannot tell yet", and collapsing the two would be misleading. A topic stays open until enough is recorded to judge it either way.
Why are there so few warnings?
Deliberately. A tool that flags every gap as urgent trains you to ignore it. The conditions that generate a caution are a short, specific list, and each one says plainly that SepticOwner cannot determine what is producing it.