Pool inspection logs: what an inspector asks for and what most portfolios have

A health inspector does not ask whether you maintain the pool. They ask for the log.

Most properties produce a clipboard from the pump room with a week of readings, a gap where somebody was on vacation, and handwriting from four different people. That is not a compliance position, and the gap is the part that gets cited.

The gap is the finding, not the readings

Worth understanding how this is actually assessed.

An inspector reading a log with consistent daily entries and readings inside range concludes the pool is managed. An inspector reading a log with three missing days concludes the log is unreliable, and an unreliable log means the readings that are there prove less than they appear to.

So consistency matters more than any individual reading. A property with slightly imperfect chemistry and a complete log is in a better position than one with perfect chemistry and an incomplete one.

That is also why a paper log on a wall fails structurally rather than through carelessness. It depends on one person being present, having the clipboard, and remembering.

What the log has to contain

Requirements are set locally and your jurisdiction is the authority, so confirm specifics. Broadly, an inspection record needs:

Date and time, which matters because some jurisdictions require readings at particular frequencies.

Chemical readings, typically free chlorine and pH at minimum, sometimes total alkalinity and cyanuric acid.

Who took them. An initial is not a name.

Corrective action taken when a reading was out of range, which is the entry most logs omit entirely. An out-of-range reading with no recorded response is worse than no reading.

Equipment checks: pump operation, filter pressure, and safety equipment presence.

The safety-equipment items are the ones that become liability

Chemistry gets attention because it is a daily task. The items that generate the expensive claims get checked less often.

Gates and self-closing latches. Depth markings. The life ring and hook. Signage. The main drain cover, which is the one with a federal dimension.

Those are not daily readings. They are periodic inspections, and they are exactly the kind of item that a general preventative maintenance calendar swallows, because a missed latch check looks the same on the list as a missed filter change and has a wildly different consequence.

What GetDone does with it, and where the boundary is

Pool inspections run as a high-risk compliance workflow rather than a recurring task: a checklist that cannot be skipped or reordered, required photos, supervisor approval before close, and an exportable pool log PDF covering whatever period you need.

That last item is the whole point. When an inspector asks for a year, the answer is a file rather than a search through a clipboard and somebody's memory.

Where the boundary sits, stated plainly: we do not encode your jurisdiction's specific chemical thresholds or inspection frequencies. The workflow enforces that the inspection happened, was documented, and was reviewed. Determining what your county requires is yours, and any vendor claiming to keep up with local pool code across every market you operate in is overclaiming.

Seasonal properties have a specific failure

A pool closed for winter and reopened in spring generates two compliance events most logs miss entirely: the closing procedure and the opening inspection.

The opening one matters more. A pool that sat for four months needs a full equipment check, and it is the moment when a latch that failed over the winter gets discovered, or does not.

Schedule those as their own events rather than assuming the recurring calendar covers them, because a recurring daily task that was paused for four months does not resume with an inspection.

At 86 properties, the question is which ones are behind

At 86 properties, some with pools and some without, the question is not whether each property has a log. It is whether you can tell which properties are behind without visiting.

Before high-risk workflows were enforced in our own portfolio, 116 high-risk work orders were open with 90 aged past two days. Not carelessness. A high-risk order looked like every other order in the queue, so it got treated like one.

Consistency across that many sites is a systems problem rather than a training problem, which is the argument for gating rather than reminding.

Ask your worst property for 90 days of readings

Ask your worst-performing property for the last 90 days of pool readings.

If it takes more than an hour to produce, or it has gaps, that is your answer, and it is the same answer an inspector would reach.

Could you produce a year on request today?