All facility types / Waterfront
Telure for a waterfront · $299/mo
Open water, not a treated pool
Open water is not a pool. There is no controller trending anything, the bottom is only as visible as the weather left it, the boundary moves, and the dock comes out every fall with a crew that never wrote anything down. Telure turns the boundary check, the bottom sweep, the dock walk and the PFD count into one dated, attributed, tamper-evident record that outlives the season the people who made it worked.
The demo is a full fictional facility, Thornmere Park District Waterfront, with a year of records. No account needed.
Day to day
The clipboard in the boathouse stops being the system. A QR opens the morning walk on the phone of whoever is setting the beach up, so the boundary, the dock and the rescue gear are answered while somebody is standing in front of them rather than from memory at close. Two guards can split the swim area and the dock and watch answers fill in live, the monthly bottom sweep arrives as a task with an assignee and an overdue escalation instead of a good intention, and guard cards show as expiring 30 days out rather than on the first morning of the season.
When a claim surfaces
Seasonal staff leave in August and the questions arrive in November. Every item is timestamped the moment it is tapped, by the person who tapped it, on an append-only hash-chained ledger, so a guard who has gone back to school is still the attributed author of the walk she ran. Corrections appear as visible amendments beside the original, never as quiet edits, and logging an incident freezes a hash-locked snapshot of the history that existed at that moment.
At renewal
Open water is the line item a carrier asks about hardest, and describing your program is not the same as showing it. Instead you hand over a dated, verifiable export: a season of boundary checks, bottom sweeps, dock and ladder walks, PFD counts, closures and staff currency, with per-item attribution and integrity anyone can check at floorkept.com/verify. A documented program like that can factor favorably into underwriting, and a board or a parent asking the same question gets the same packet.
What you get, running a waterfront
The boundary is a registered asset, not a rope somebody re-set
Each buoy line, corner marker and swim platform goes on the registry with its manufacturer, model, installed date and its own intervals, so the anchor set under it has a history instead of a memory. The weekly check records the line's condition against that specific line, and the day somebody re-set it after a storm is a dated, attributed event rather than something three people half remember.
The bottom sweep becomes a record somebody signed
A sweep of the swim area bottom is the most valuable check on a waterfront and the least likely to be written down anywhere. Here it is a recurring task with an assignee, a reminder and an overdue escalation, and what the sweep found opens a corrective-action item against the zone it was found in, so a submerged branch is an open item with an owner and a closing date rather than something that got mentioned.
Docks and ladders that carry their own history
Dock sections, swim ladders and platforms are registered separately, because a ladder is replaced on its own clock while the dock it hangs on is not. Dock in and dock out become dated interval completions against each section, so the condition it went into the water in is a description on the record rather than a guess in April, and a ladder that came off in July is visibly off until somebody with a name puts it back.
PFDs counted against a registry instead of a memory
Register each rack or batch as its own item, with the size range and the count in its label the way the rack card already reads them, and its installed and replacement dates on the row. The weekly check then becomes a count against that registry rather than a glance at a wall of jackets. A batch nearing its replacement date counts itself down on the record, and the jackets that went out on a trip and did not come back are a flagged item on that batch, with a note, a count and the name of whoever found them gone.
Craft with their own history, hull by hull
Canoes, kayaks, rowboats, paddleboards and the rescue board go on the registry with hull numbers and their own service intervals. Damage found on a rack check is an attributed event on that hull, a repair is a dated completion against it, and pulling a craft out of service keeps it visibly out of service until somebody returns it, so "which boat was that" is never a question on a rack of eight identical hulls.
Rescue gear that dates itself
Rescue tubes, reach poles, ring buoys, rescue boards, the backboard with its straps and head immobilizer, and the AED are registered items with intervals, so pad and battery expiry dates count down on the record instead of being read off a sticker by whoever happens to look. The weekly readiness check records what was there, at which stand, and who looked.
Guard cards and small craft sign-offs on one board that counts down
People down one side, topics across the top: open water lifeguard currency, first aid and CPR, small craft rescue, the rescue board, and the emergency procedure for this specific site. A colleague certifies each item as they watch it done, renewals count down from the date it was completed, and anyone a topic does not apply to is marked so rather than left looking overdue. Telure records what you tell it and when it lapses; it does not issue, verify or endorse anybody's credential.
Closing the water is a record, not a rope across the path
Pulling the deep area, closing the swim area for weather or a sweep finding, or shutting the whole waterfront is a recorded event: who closed it, why, and who authorized reopening. Declared closure days are cross-referenced by the gap report, so a two week dock repair never reads as a month of missed walks, and the off-season reads as an off-season instead of a hole in the record.
Records that cannot be quietly edited
Entries are immutable once submitted (enforced by the database, not policy) and hash-chained so alteration is detectable. Corrections appear as visible amendments beside the original. A log anybody can tidy up after a drowning or a near miss is worse than no log at all, and this is the difference between a checklist app and evidence.
An incident freezes its history
Logging an incident writes a hash-locked snapshot of the prior 90 days of inspection history for that waterfront into the incident itself: exactly which boundary checks, bottom sweeps, dock walks, PFD counts and closures existed at that moment, provable years later, whatever the file looks like when it is finally opened.
The export a board, an audit or an insurer can verify
A dated, paginated PDF for any period, or a roll-up across every site in the district or the association: adherence and gaps reported explicitly, per-item attribution shown, closures cross-referenced, integrity verification printed on the cover and checkable by anyone at floorkept.com/verify.
The Telure Standards for a waterfront
A Telure-curated list of recurring inspections and reviews. In the product it works as an alignment tracker: you turn it on, match the work you already run to the clauses it covers, and record a reason for any clause that does not apply here. Turning it on adds no tasks, and it is not a certification. The manufacturer’s manual governs all equipment intervals.
- Swim area boundary check: buoy lines, corner markers and depth transitionWEEKLY
- Dock, ladder and swim platform walkWEEKLY
- Rescue equipment and guard stand readiness checkWEEKLY
- PFD count and condition check, rack by rackWEEKLY
- Bottom hazard sweep of the swim areaMONTHLY
- Buddy board, tag and headcount station checkMONTHLY
- Guard stand sightline and zone coverage observationMONTHLY
- Watercraft hull, fitting and paddle inspectionMONTHLY
- Powered rescue craft readiness checkMONTHLY
- Anchor, chain and mooring tackle inspectionQUARTERLY
- Waterfront season opening and closing inspectionSEMIANNUAL
- Open water staff currency reviewSEMIANNUAL
- Full waterfront inspection (qualified person)ANNUAL
These checks carry no published references; the basis register shows what informs the program instead. See the full basis register
The starter daily walk
- Buoy line complete and in position: every buoy on the line, none adrift, sunk or dragged
- Deep water transition and the drop off marked and visible from every staffed stand
- Water clarity checked at the deep end: bottom visible at the depth the site marks it at
- Swim area walked or waded at the shallow edge: no glass, hooks, branches or dropped hardware
- Rescue tube on every staffed stand; reach pole, ring buoy and rescue board at station
+ 9 more, editable at onboarding
A registry that speaks waterfront
Register equipment by position with serials. Recalls are checked against this registry daily, serial ranges included.
Roles your staff already have
Waterfront Director · Aquatics Director · Parks Operations Supervisor · Head Lifeguard · Lifeguard · Small Craft Instructor · Swim Instructor · Waterfront Maintenance · Front Desk
Pick your name, walk the check, tap pass or flag, PIN to sign. No shared logins, and staff never need an inbox.
The demo facility
Walk Thornmere Park District Waterfront before you sign anything
A fictional waterfront with a year of real-shaped records: clean days, a flagged item that opens and closes a corrective loop, an amendment, an incident with its frozen history. Every demo PIN is 0000.
$299/mo · 30-day trial
Start the record for your waterfront
The trial is the full product for 30 days, with the Telure Standards for a waterfront ready to enable and the starter walk ready to edit. No card to start, and nothing is charged unless you add one. Add billing before day 30 to keep recording after the trial.