Document a service visit for water chemistry and liability protection
domain: operations-documentation · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Record the date, time, and technician name for every visit as a baseline audit trail.
Log chemical readings taken at minimum: free chlorine, combined chlorine, pH, total alkalinity, cyanuric acid, and calcium hardness.
Record every chemical added and the quantity, along with any equipment issues or malfunctions observed during the visit.
Note any customer-facing safety hazards observed (e.g., damaged fencing/gate, missing or cracked drain cover) and who at the property was notified, with a timestamp.
Retain records for a defined period consistent with company policy and any applicable state recordkeeping requirement, and photograph notable issues where useful.
Known gotchas
A verbal-only warning about a hazard (e.g., telling a customer about a broken gate) provides essentially no liability protection if it isn't also documented in writing with a timestamp.
A logging system that captures only chemical readings and misses equipment/safety-hazard observations only protects half of the liability exposure a service visit actually carries.
This is general best-practice guidance, not a specific code-mandated logging format — a facility's actual chemistry-logging requirements are set separately by its local health code, which should still be followed on top of this.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?