Pool incident documentation: what a good shift log records

A written record after every shift protects the board and helps the manager run the pool. Here's what a useful incident log captures, and how to bring it to the board meeting.

Pool attendant recording a shift note on a tablet at a palm-lined community pool

Every community pool has incidents. A resident slips on the steps, two families argue over a cabana, a teenager climbs the fence after close, someone finds broken glass in the planter. Most of these are small. A few turn into insurance claims, complaints at the board meeting or a letter from an attorney months later.

When that letter arrives, the board's best friend is a record written the same day by the person who was there. Memory fades fast. Notes written that afternoon don't.

Why boards want a record after every shift

A shift record isn't only for the bad days. On a quiet Tuesday, the log might say the pool opened on time, the attendant checked in a few dozen residents, a lounge chair strap broke and it was too windy to open the umbrellas. That sounds dull, and that's fine. A long run of dull, consistent entries is what makes the unusual entry believable.

Consistent records do real work for an association. They show the pool was staffed and opened as promised. They give the manager the details needed to fix problems, such as which gate and which chair. And when something serious happens, they show the board had a routine and followed it.

There's a practical side too. A manager overseeing several communities can't be at every pool. The shift log is how the manager knows what happened without driving over, and it's how the attendant on Wednesday learns what the attendant on Tuesday dealt with.

What a good incident entry records

An incident entry should let someone who wasn't there understand what happened. A useful one includes:

  • Date, time and place. The time the incident happened and the time it was written down, plus a specific location such as "shallow-end steps" or "north gate," not just "the pool."
  • Who was involved. Names where they're known and the person agrees to give one, or a description and unit number when they aren't. Witnesses go here too.
  • What the attendant saw. Facts only, in plain order. "Resident slipped on the second step and sat down hard" beats "resident fell due to slippery steps." The attendant describes; the board and the carrier draw conclusions.
  • What the attendant did. Called 911, called the manager, closed the area, asked the guest to leave, set out a wet-floor sign. Include the times of calls.
  • What happened next. The person left on foot, an ambulance arrived, the manager arrived, the group left when asked.
  • Photos. The step, the broken latch, the spilled glass. A photo taken in the moment ends a lot of later arguments.
  • Follow-up needed. Repair the latch, replace the strap, review the guest list for that unit.

What the entry should leave out matters just as much. Opinions about fault, guesses about someone's health and comments about residents' character don't belong in an incident record. Attendants aren't medical staff and shouldn't write like they are. Keep the language neutral, because people other than the manager may read it someday.

The routine entries matter too

Beyond incidents, a good shift report covers the basics every time: opening and closing times, headcount or check-in totals, guest numbers, weather closures, maintenance issues spotted on rounds and anything the next shift needs to know. If the community uses digital check-in, the totals can come straight from the tablet rather than a tally sheet.

Rounds deserve their own line. A note that the attendant walked the deck, checked the restrooms and confirmed the gate latched every hour or so is evidence the pool was being watched. If a round was skipped because the attendant was handling a problem at the gate, the report should say so.

Make it easy to write well

Attendants write better records when the form does some of the work. A few things help:

  • A fixed template. The same fields in the same order every shift, with incident details as a separate section that only appears when needed.
  • Writing it during the shift. An entry written within the hour is better than one reconstructed at closing. A tablet at the gate makes that realistic.
  • A clear send. Reports go to the manager the same day, every day, without anyone having to ask.
  • Training with examples. Show new attendants a good entry and a poor one side by side. Most people get it right away.

At The Pool Attendant Company our attendants file a report at the end of every shift, with incident details and photos attached when something happens, and the manager gets it the same day.

Using reports at the board meeting

Shift reports are also one of the more useful things a manager can bring to a board meeting, as long as they're summarized rather than dumped in the packet.

A one-page season summary might include:

  • Days and hours the pool was staffed against what was planned.
  • Weather closures and early closings.
  • Check-in and guest totals by month, which show whether the guest policy is being used the way the board intended.
  • Incidents by type, with the serious ones listed individually.
  • Maintenance issues reported, and which ones are still open.
  • Rule problems that keep coming up, such as glass or after-hours entry.

Patterns are where the value is. If most guest disputes happen on Saturday afternoons, the board can add a second attendant for those hours. If the same gate shows up in the maintenance list all summer, it's time to replace it. If after-hours entry is rising, a lock or a camera may be cheaper than another season of complaints.

How long to keep records

Ask your association attorney and your insurance carrier how long to keep shift and incident records. The answer depends on your state and your governing documents. Whatever the period, keep the records somewhere the board can reach even if the management company or the staffing vendor changes. A shared folder the association controls is better than a vendor's portal the board can't open.

A short checklist for your vendor

When you talk to a staffing vendor, ask to see a sample shift report and a sample incident report with the names removed. Ask when reports arrive, who receives them, whether photos are included and how the association gets its records back at the end of the contract. A vendor that can't show you an example probably isn't writing them.

Want to see what our reports look like? Request a free, itemized proposal and we'll include a sample shift report with it.

  • Incident reports
  • Shift reports
  • Board meetings
  • Documentation

Planning next season?

Tell us about your pool and we'll send an itemized proposal: hours, coverage and what's included.