Free Plumbing Maintenance Schedule Template

At least annually where the International Plumbing Code is adopted — IPC 312.10.2 requires testable assemblies to be tested at the time of installation, immediately after any repair or relocation, and at least annually thereafter. The important caveat is that this is a model-code floor, not the rule you are actually held to. Cross-connection control programs are run by the water purveyor or the health authority, and they set the certification your tester needs, the form the report goes on, and the submission deadline. High-hazard connections are often required more frequently than annually. Check the local program before you promise a customer annual testing, and note that the annual interval only exists in your jurisdiction if the code has been adopted there.

No, and that is the distinction this builder exists to make. Plumbing codes require a listed temperature and pressure relief valve to be installed on a storage water heater; they set no schedule for testing it. The annual test comes from the manufacturer — Watts’ T&P relief valve instructions state the lever must be operated at least once a year so the waterways stay clear, because mineral deposits can adhere to the valve and render it inoperative. Practically, that makes it more binding than a lot of people assume: it is a manufacturer instruction, so it is what a warranty claim gets measured against. Confirm the wording against the valve actually installed, since makers phrase it differently.

Because there is no single published figure, and inventing an average would defeat the purpose of the row. Anode inspection is a manufacturer requirement — it is the maintenance item most tank warranties are conditioned on — but A.O. Smith, Rheem and Bradford White each publish a different interval, and softened or phosphate-treated water shortens every one of them. An averaged number would match no manufacturer’s manual and therefore protect no warranty. The row ships with an empty interval and asks you to read the figure off the manual for the heater that is actually on the job, so the finished schedule cites that heater rather than a plausible-looking number with nothing behind it.

Service the unit once the combined accumulation of floating fats, oils and grease plus settled solids reaches 25% of the interceptor’s liquid capacity. Beyond that point the working volume is compressed, the wastewater no longer gets the residence time the unit was sized for, and grease passes through to the sanitary sewer. It is the trigger referenced by FOG programs almost everywhere. What it is not is a frequency — most local ordinances also impose a hard calendar deadline on top of it, commonly 30 days for under-sink hydromechanical grease traps and 90 days for in-ground interceptors, whichever comes first. That number is set by your sewer authority, so the builder leaves the interval blank for you to enter and keeps the 25% check as the rule that governs between scheduled visits.

Last completed visit plus the interval. "Last done" is not a field anybody types over — it is derived from the newest dated line in that task’s service history, so logging a visit appends to the record rather than overwriting the previous one. Everything then hangs off that date: the next-due date, the days-until-due figure, and the OK, due-soon or overdue verdict, all measured against the as-of date at the top of the sheet rather than against the clock. That last part matters more than it sounds — a report that reads the clock says something different every time you reopen it, and a printed schedule has to say the same thing in March as it did the day it was exported.

It counts only the overdue tasks whose interval carries a code or regulatory authority. A single blended overdue figure treats a missed backflow assembly test and a skipped sump pump check as the same event, and they are not: one is a violation of an adopted code or a utility’s cross-connection program, the other is a maintenance item nobody has published a rule about. Splitting the count is the fastest way to see whether a property has a compliance problem or just a to-do list, and it is the number worth putting in front of a building owner first.

No, and the builder labels them industry recommendation for exactly that reason. EPA’s SepticSmart guidance is to have a conventional septic system inspected generally every three years by a qualified professional and the tank pumped when needed, typically every three to five years; EPA also recommends testing a private well annually for total coliform bacteria, nitrates, total dissolved solids and pH. Both are federal agency guidance for property owners, not federal mandates — the Safe Drinking Water Act regulates public water systems rather than private wells, and enforceable septic intervals come from state or local health departments. Where your health department does mandate a figure, enter theirs and reclassify the row.

Yes. A custom row takes your own task name, location and interval, and asks you to classify it yourself as code, manufacturer or industry — or to leave it unclassified, which the export marks with a footnote rather than silently presenting as authoritative. Library rows work the other way round: their authority label comes from the source and is not editable, because the point of the label is that it reports what the citation says rather than what anybody would prefer it to say.

No, and every export says so in full. It is a record of planned and completed maintenance, not an inspection report, a compliance certificate, or a substitute for a test report filed with the authority having jurisdiction — a backflow test still has to go to the water purveyor on their form, signed by a certified tester. The authority labels describe the general basis for each interval; they are not a determination for your jurisdiction, since model codes only take effect as adopted and amended locally and a purveyor or health department can always require more than the interval shown.