Pool Property Notes That Keep the Next Tech From Looking New

The next tech should not look new at a pool you have cleaned for three years. That blank stare at the side gate is a property-note failure wearing a friendly voice. Every season, operators lose 20-40 minutes a day to access theater: codes in old texts, chemical preferences only one person remembers, and a pump that “always needs a kick” that was never written down.

This guide covers the fields every pool property needs, how to write notes a tech will actually read, who updates them after a visit, and how to handle codes without spraying them across a group chat. The goal is a stop the helper can run without a phone tree. The same writing rules as lawn care property notes apply. The facts are pool facts: cages, salt cells, and who likes chlorine a little high.

Note fields every pool property needs

If you only store a name and an address, you have a contact list, not a CRM. The property record has to answer the questions a tech asks before the cage opens.

The must-haves

If a note does not change what the tech does in the next 10 minutes, it probably belongs in a quieter history field - not in the line they see first.

Clubs and multi-body accounts add quiet hours, dock rules, and which body is which. The note still has to be on the property, not in the owner’s head.

Nice-to-haves that earn their keep

• Timer quirks (“pump off 2-4 while kids nap” is a preference, not a guess)
• Robot that actually works vs one that sits on the steps
• Neighbor who complains if the gate is left ajar
• Preferred start window (not a promise you cannot keep)
• Last green recovery date and why it went green
• Salt cell last acid-washed

Do not turn the record into a novel about the customer’s vacation. Techs scan. Owners reminisce. Write for the scan.

Write notes techs will actually read

Style is an ops problem. Long notes get skipped. Cute notes get ignored. Accusatory notes get argued.

Rules that work:

1. Lead with the action. “South gate” before “they’re nice.”
2. One fact per line when you can.
3. Date the change. “2026-06-12: new HOA code 2210 (old 4471 retired).”
4. Delete the lie. If the dog died, remove the dog line. Stale warnings train techs to ignore all warnings.
5. No essays. If you need a paragraph, you need a checklist plus a short note.

Great vs useless

The useful column is something you can train. The useless column is something you can only sigh about.

Worked example: before and after

Before: “Mrs. Hale - been with us forever, husband passed, dog sometimes out, gate is tricky, she likes it crystal, pump acts up.”

After:

• HOA gate 2210, then south latch, close cage
• Dogs: confirm inside; if out, do not enter, text office
• Park on street
• Salt; keep FC 4-5; no phosphate
• Filter 18 psi clean; cell last washed 2026-08-03
• Pump: prime once; timer west wall
• Owner authorizes extras; same-day invoice
• 2026-08-03: new latch; old “push hard” note retired

Same customer. The second version does not require a phone call. That is how you run a weekly route without a notebook.

Update notes after exceptions

A note that is only written at signup is a spring fiction by July. Codes change. Dogs change. Cells get replaced. The tech who hit the exception owns the update.

Close-out habit (30 seconds):

• Access failed? Write what failed and what worked.
• Extra work? Write what was done and whether it was billed - same habit as same-day invoicing.
• Customer asked for a permanent chem change? Change the preference line the same day.
• Equipment changed? Put brand, location, and baseline pressure on the next visit, not in a story at the shop.

If only the owner edits notes at 9 p.m., the afternoon helper will always be wrong. Someone owns the board. Someone owns the note.

Who edits what

Texts are for the window and the one-time exception. The permanent fact goes on the property. If you only text “new code is 2210,” the next truck will not have it. Conversations can carry the message. The property still has to hold the fact.

Privacy and code hygiene

Gate codes, lockbox numbers, and alarm notes are not marketing content. They are access secrets.

Practical hygiene:

• Store the code on the property record the tech uses for the stop
• Do not paste codes into a 12-person group text that outlives the helper
• Do not put codes on invoices or review-request emails
• When the customer changes the lock, retire the old code in the same edit
• Limit admin access if your shop has seasonal people who do not need the whole book

You still need the code on the truck. Hiding it in a binder only the owner has is how techs lean on fences. The point is a controlled record, not a scavenger hunt.

If a helper leaves on bad terms, change the codes you can influence and rotate anything that lived in personal phones. That is ugly. It is cheaper than a Sunday surprise.

Multi-property and landlord traps

One customer is not one note. Landlords, snowbirds, and small clubs often have two addresses and three phone numbers.

For each property, store:

• Who gets access texts (tenant vs owner vs club manager)
• Who authorizes extras (salt cell vs “just a weekly”)
• Who pays
• Which note applies only to that body of water (the spa’s timer is not the pool’s timer)

If you copy-paste one note onto both properties, you will send the tech to the wrong lock. The CRM should make the property the unit of truth. The customer is who pays and who you market to.

A 12-line template you can paste

Use this on every new stop, then delete unused lines:

1. Enter / park:
2. Community gate / house gate / cage:
3. Dogs / animals:
4. Kids / hours:
5. System (salt / chlorine / other):
6. Chem preference (FC range, no-go products):
7. Pump / timer location and quirks:
8. Filter type and clean psi:
9. Salt cell location / last wash:
10. Scope extras (tile, polaris, no-go):
11. Billing vs site contact:
12. Last change date:

If a line is empty, you have not finished signup. Empty is more honest than “see texts.”

Notes that change pricing and dispatch

A good note is also a quoting tool. Poor access, long carries, and equipment that always needs priming belong on how you price the weekly, not only in a warning the tech swears at.

Dispatch uses the same lines to match tech and time. Putting a green helper on “two gates, 200 ft carry, prime twice, picky FC” is how quality complaints and overtime arrive together. That matching is why a second truck needs notes first.

Storm days need notes too: “screens load with oak - extra skim time” or “cover on, skip unless they text.” That sentence saves a wasted trip and a callback.

Seasonal note review

Once per season, filter properties with:

• Codes older than a year with no confirmation
• Dog notes with no date
• “Picky” or “careful” with no specifics
• Commercial stops missing quiet hours
• Filter psi with no baseline
• Any stop that generated a tech call last month

Fifteen minutes a week beats a Saturday of “we need to clean up the CRM.”

New-customer intake is the cheapest time to get this right. Before the first weekly, ask on the quote call or site visit: how do we get in, where do we park, animals, salt or chlorine, target chemistry, equipment locations, who authorizes extras, and who do we text if we cannot get in. Write the answers on the property the same day. A charming conversation that never hits the record is how the second tech calls you from the driveway.

If a helper says “the note was wrong,” treat that as a gift. Fix the line, date it, and thank them. Techs stop reporting bad notes when the office argues. The truck is closer to the latch than you are.

Chemical tracking on Growth can log what you applied. It will not replace a chemistry lab app. The preference still belongs in plain language on the property: “keep FC 4-5, kids at 4.” The lab can do the math. The note tells the next tech what “good” means at this house.

How MowProHQ helps pool property notes

MowProHQ keeps notes on the property next to the schedule, quote, and invoice so the field and the office share one story. Core CRM, scheduling, quotes, invoices, dual Regular vs Cash pricing, the customer portal, and the website editor are free with two seats. iPhone and Android apps are free, which is the point: the note has to be on the phone at the gate. Growth is $39/month with unlimited seats and no seat fees - dispatch and routes, GPS, chemical tracking, timeclock, a live site with leads, and card processing at 3.5% + $0.30 versus 4% + $0.30 on Free. Pro at $89 adds AI website help, Get Found, and reviews. Optional business phone is $19/month; AI receptionist is $29/month (40 conversations, then $0.79).

Start at signup if the note still lives in a text thread. The free core is enough to stop the driveway phone call. See pool service and pool service software for a small route company for the rest of the shop.

Your reputation lives on the water. The facts that protect the next tech should live on the property - short, current, and boring on purpose.

Frequently asked questions

What should be on every pool property record?

Access (community gate, side gate, cage latch), parking, dogs, chemical preferences, pump and filter notes, and who authorizes extras versus who pays. If the next tech still texts from the driveway, the note is missing or unreadable.

How do I write pool property notes a tech will actually read?

Keep them short, scannable, and current. Lead with the action: “South gate, code 4471, dogs inside, keep FC 4-5.” Date changes. Delete stale lines. A paragraph of history nobody has time to read is how techs skip the note and call you anyway.

Who should update pool property notes?

The tech updates after an exception the same visit. The office fixes billing and contact roles. If only the owner edits notes at night, the truck will always be behind the truth. Make “note or it did not happen” a close-out habit.

Is it safe to store pool gate codes in software?

Store codes on the property record the tech needs for the stop - not in a group text that lives forever on everyone’s phone. Limit who can see them, do not paste codes into invoices or review emails, and retire the old code when the customer changes the lock.

What is an example of a good pool property note?

Good: “HOA gate 2210, then south side latch. Park on street. Two dogs - confirm inside. Salt system, keep FC 4-5, kids swim at 4. Filter pressure 18 clean. Owner authorizes extras.” Bad: “Nice people, picky pool, watch the dog.” The first is a job. The second is a vibe.

How often should I review pool property notes?

Spot-check problem stops weekly and do a seasonal pass when codes, dogs, and equipment change. After any complaint or extra, update the same day. Notes that only get edited at spring opening are stale by June.

Do pool notes belong in the CRM or in texts?

In the CRM, on the property, attached to the stop. Texts are for a one-time window change, not for the code that will be needed all season. If the note lives in a thread, the next helper will not have it.