Skip to main content
GullySystem

Rescue, slip and lost child reports for a park

Incident and rescue reports give a water park one place to write down what happened at the pools. Rescues, slips, lost children and complaints are logged with place, hour and the staff on duty. A signed summary then reaches the duty manager and the insurer.

What an incident or rescue report holds

A report is written while memories are fresh and read months later by people who were not there. It has to stand on its own. Four kinds of fact give it that strength, and each is entered at the time.

Type of event

Each report is marked as a rescue, a slip, a lost child or a complaint. The type decides who is told and which summary is printed. A complaint about eye irritation sits beside the pool’s readings. Types stay consistent.

Place and hour

Each entry names the attraction and the spot, such as the slide landing or the wave pool shallows, and the hour it happened. Place and time link the event to counts, weather holds and guard posts. They anchor it.

Staff on duty

The guards and staff on duty at that place and hour are named on the report, drawn from the roster. A rescue shows which guard acted. Who was posted is a matter of record, not memory.

The signed summary

When a report is complete, a signed summary is produced. It reaches the manager and the insurer. The signature shows who confirmed the account. Insurers and managers read the same page, so nothing is retold by phone.

From the tower to the insurer’s file

An incident moves from the pool edge to an office on the same day. Four moments follow a report from the first call to the file that an insurer may later open. Each starts with a person at the water.

Guard writing up a rescue

After a rescue at the wave pool, the guard records what happened on a phone. The place and hour are filled from the post. The guard adds a few lines. The head guard reviews the entry.

Lost child at the gate

A parent reports a lost child near the lazy river. The gate desk opens a report with the place last seen and the hour. Staff on duty are noted. It stays open until the child is found.

Slip on a slide stair

A guest slips on the stairs to a slide. First aid is given by a certified guard. This entry names the stair, the hour and the guard. The technician reads it and checks the surface.

Complaint at the guest desk

A guest complains of stinging eyes. The desk logs the complaint against the pool and hour. The manager reads the readings for that time beside it. The reply to the guest is based on the record.

Who writes and reads the reports

Reports pass through a short chain of people. Those who see an event write it, those who lead the shift review it, and the manager and the insurer receive the summary. Four roles carry the work.

Head guards and lifeguards

Lifeguards write up rescues and slips, and head guards review them. Guards see the place and hour already filled in. They see their own entries. A head guard sees every report from the shift and its status.

Duty managers and park owners

Managers and owners read the incident and rescue log by attraction, and receive the signed summary. They decide what follows an event. The log shows patterns, such as repeated slips on one stair. Patterns prompt action.

Ticket counters and guest desk

Counter and desk staff log lost children and complaints that reach them. They enter the details a guest gives. They do not see rescue notes. The matter passes to the manager on shift. Nothing waits in a drawer.

Plant technicians after an event

Technicians read reports that point at a surface, a pump or a reading. They raise a ticket from the record where work is needed. The repair is linked to the event that prompted it. Cause and fix sit together.

Decisions to settle for incident reports

Incident records touch safety, guests’ privacy and the park’s insurance, so the rules are settled with the owner and the duty manager before the first entry. GullySystem staff then set up the forms.

Who signs the summary

Decide who signs a summary before it goes to the manager and the insurer. A park might name the duty manager for serious events and the head guard for minor ones. The summary shows the signer.

Which event types are logged

The park lists the event types it wants to record: rescues, slips, lost children, complaints and any others. A minor graze may be left out. The list shapes what the log can show later. Decide it carefully.

How old records come across for incident and rescue reports

Past incident notes from paper books can be keyed in for recent seasons or left in the file. That choice is the park’s. GullySystem staff agree the approach with the manager. The first live report starts the history.

Which report matters first for incident and rescue reports

The incident and rescue log by attraction is the report to read first. Decide who reads it, how frequently, and what is done when one attraction appears again and again. One named person owns the follow-up.

How reports link to the rest of the product

An incident is rarely about one thing. It involves a guard, a pool, a reading and sometimes a repair. Reports draw on those records and pass the facts back, so a manager reads one account instead of five. Five links keep the story whole and traceable.

  • Lifeguard roster supplies the staff on duty
  • Pool register supplies the place and its zones
  • Water quality log shows readings near the hour
  • Maintenance tickets follow a slip or a damaged surface
  • Capacity counter shows the crowd at that attraction

Where incident reports stop

Reports record and summarise. They do not give first aid, judge fault or decide a claim. The duty manager, the park’s adviser and the insurer do that. Any report to a regulator, and any legal view on what happened, stays with the owner. A park with a rare incident may keep a signed log book.

FAQ

Frequently asked questions

Which staff are named on an incident report?

It names the guards and staff on duty at that place and hour, taken from the roster. A rescue shows the guard who acted. Names appear only for people who were posted there. Nobody is added later.

Who receives the signed summary of an incident?

The duty manager and the insurer receive it. Who signs, and who else is copied, is the park’s decision. The summary is produced from the report, so it matches the record entered at the time. It is not rewritten.

Can a lost child report be closed when the child is found?

Yes. It stays open until someone closes it with the hour the child was found and who found them. The time between is visible. The record then moves to the incident log. It remains on file.

Does the system file reports with any authority?

Filing is not part of the product. It produces the report and the signed summary. Any notice to a regulator or another authority is a decision for the owner and their adviser, who may use the summary as a source.

Can guests’ personal details be kept out of the log?

Which guest details a report holds is the park’s decision. A report can record the event without naming a guest. Privacy rules for your country are for your adviser to confirm. Raise it at set-up with us.

Where it fits

How this feature fits the system.

Water Park Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.

Tickets and wristbands

Counters sell entry, child rates and bundles from one price list, and a wristband balance is spent later at stalls and kiosks.

Point of Sale Billing

Lifeguard roster and rotation

Guards clock in at their tower or slide top, and rotation breaks are logged so the head guard sees who is due to move.

Attendance & Time Tracking

Pump, filter and slide maintenance

Backwash cycles, pump service dates and slide surface checks are scheduled by attraction, with outside inspector dates held beside each.

Asset AMC Tracking
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements