The short answer
A complete pool service customer record ties together contact and service address, the pool's specs (gallons, surface, sanitizer type), gate and access notes, service day and frequency, a per-visit chemical and service history, billing terms with a card on file, and dated notes and photos. Together they let any tech service the pool and prove the work.
The question comes up twice: once when you set up a new customer and guess at which fields matter, and again when you inherit half a route and discover the previous owner's "records" were a name and a phone number on a legal pad. A record missing the pool's sanitizer type, the gate code, or last month's readings does not fail all at once - it fails the one day a fill-in tech needs it, or a customer pushes back on what you did.
A complete customer record isn't paperwork for its own sake. It's what lets any tech on your crew service any stop without a phone call, what proves you did the work when a customer disputes a visit, and what a buyer pays more for when you sell part of your route. Here's what belongs on the record - the pool's specs, the access notes, the chemical and service history, and the billing details - and what happens when any one of them is missing.
At a glance
Key takeaways
- A complete pool service customer record covers seven groups: contact and address, pool specs, access notes, the service plan, visit and chemical history, billing, and dated notes or photos.
- Store pool specs - gallons, surface type, and sanitizer type - on the pool itself, since one customer can have more than one pool with different specs.
- Keep gate codes, pets, and restricted times in the customer or pool notes field so any tech covering the stop has them, not just the tech who runs it every week.
- Log every visit's chemical readings and doses to the specific pool's record - that history is your proof when a customer disputes a charge or a visit.
- Keep rate, terms, invoice status, and card-on-file status on the same record so invoicing never has to be rebuilt from memory.
- A route sells for more when every stop carries a complete record instead of just a name, an address, and a rate.
- Migrate old paper or spreadsheet records in stages - contacts and specs first, history backfilled after - rather than waiting for a perfect transcription before you start.
What should a pool service customer record include?
A pool service customer record should include seven field groups: contact and service address, pool specs, access notes, the service plan, visit and chemical history, billing details, and dated notes or photos. Miss one and the record works until the day it doesn't - a tech shows up without the gate code, or a customer disputes a charge with nothing behind it. Good pool service record keeping means these seven groups exist on every account from day one, not backfilled after a dispute.
| Field group | What it covers |
|---|---|
| Contact and service address | Name, phone, email, and the property address the pools sit at |
| Pool specs | Type, shape, gallons, surface, and sanitizer type, set per pool |
| Access notes | Gate or lock code, pets, restricted times - kept in the notes field |
| Service plan | Frequency, scope, and service day |
| Visit and chemical history | Every visit's readings, doses, and technician notes |
| Billing | Rate, terms, invoice status, and card on file |
| Notes and photos | Anything else worth flagging, dated to the visit it came from |
One record beats a notebook, a spreadsheet, and three text threads
Good customer management software lets you keep every customer, pool, and visit in one record, so all seven field groups live in one place instead of being scattered across a notebook, a spreadsheet, and three separate text threads with your crew. If you're starting from nothing, think of it as a pool service customer information sheet that lives in your software instead of on a clipboard.
Some operators call it a pool service client record or a pool service customer profile instead of a customer record - same seven pieces either way. Think of it as a pool customer database with one row per account, not a stack of index cards you re-copy every time a detail changes, and keep the pool service customer file complete before you need it, not after.
Pool specs are the record's technical core
Store six fields on every pool under the customer: nickname, type (residential or commercial), shape, gallons, sanitizer type (chlorine, salt, bromine, or other), and surface type. These tell a tech - especially one covering someone else's stop - what they're walking into before they open the gate. A tech who knows a pool runs 18,000 gallons on salt with a plaster surface doses differently than one on chlorine with a pebble finish, and guessing wrong wastes a stop and can damage the surface.
A customer can have more than one pool - a residential account with a pool and a spa, or a commercial account with three pools on one property - so specs live per pool, not per customer, and each one keeps its own record and its own visit history.
Where do gate codes and access notes belong on the record?
Gate codes, alarm codes, dog-on-property warnings, and restricted service times belong in the pool service customer notes field, not on a sticky note in one tech's truck. There's no dedicated gate-code field - these live as free text on the account's notes - but putting them there, instead of in a tech's head or a group text, is what lets any tech on the crew cover any stop.
Take a Cape Coral, Florida operator running 210 residential stops across Cape Coral and Fort Myers. He inherited about half the route from a retiring owner whose records were a legal pad: names, addresses, and a dollar amount. Nobody had the salt cell model or the gate code for three of those pools, so a fill-in tech skipped them one week, and a customer called convinced her pool had sat green for two weeks. Once every stop carried a full record - specs, sanitizer type, the gate code in the notes, and a reading history - any tech could cover any stop, and when the next "you never showed" call came in, he pulled up dated readings and a photo from every visit.
Chemical and visit history is what turns a record into proof
Every visit should log free chlorine, combined chlorine, pH, total alkalinity, calcium hardness, cyanuric acid, salt level on saltwater pools, and water temperature - eight readings, tied to that specific pool's record, plus the technician's notes, a checklist, and photos. That running history is what proves what you added on each visit when a customer disputes a charge or claims you skipped a week.
A record with three months of dated readings settles a dispute in the time it takes to open the app. A record with nothing behind it is your word against the customer's, and in that argument the customer usually wins.
Billing details tie the record to what the account owes and how it pays
The billing side of the record carries the service rate, payment terms, invoice status (draft, sent, paid, or void), and whether a card is on file for automatic charging. Keeping this on the same record as the pool specs and visit history is what turns a complete record into an invoice without retyping anything - the invoice pulls from the visits already logged against that customer.
Some operators go looking for a pool service CRM to hold all of this. Pool service customer management software that keeps one complete record per customer - contact, pools, visits, and billing - covers the same ground without the sales-pipeline features a service route doesn't need.
A complete record is what makes a route worth more when you sell it
A route sells on its records as much as its revenue. A buyer evaluating 60 stops pays more for accounts that come with full pool specs, a chemical and visit history, and clean billing status than for a pool route customer list that's just names, addresses, and a monthly rate. The record is what lets the buyer's techs start servicing those pools on day one instead of relearning each one by trial and error.
When that same Cape Coral operator later sold 60 of his stops, the buyer paid a higher multiple because every account came with a full record instead of a name and a number.
FAQ
Frequently asked questions
Should I keep customer records in a spreadsheet or in software?
A spreadsheet works for a handful of pools, but it breaks down past 15-20 accounts because it can't hold a chemical history, photos, or a visit-by-visit log the way software can - you end up with one tab for contacts, another for a route, and a photo folder that never matches either. Software keeps the pool specs, the access notes, the visit history, and the billing status on one customer record, so pulling up an account during a phone call takes one search instead of three files. The switch usually happens the first time a spreadsheet-run operator can't answer "when did you last service this pool" without scrolling through weeks of rows. If you're still on a spreadsheet, carry over the pool specs and any access notes first - those are the fields that cost you a wasted stop if they're missing.
Who on my crew should be able to see a customer's gate code?
Any tech who might actually service that stop, including a fill-in covering someone else's day off. Gate codes and access notes belong on the account precisely so coverage isn't limited to the one tech who normally runs that route - if only one person has the code in their head or their phone, you have a single point of failure the day they call in sick. Keep access notes inside your service software rather than in a group text or a shared spreadsheet that outlives employees who've moved on. When a technician leaves, that's also the moment to think about whether any codes should change, the same way you'd change a lock after losing a key.
How long should I keep a customer's records after they cancel?
Keep them indefinitely if storage is cheap, which it is in software - there's little reason to delete a canceled customer's record rather than just marking the account inactive. A former customer sometimes comes back a year or two later, and having their pool specs and service history already on file saves you from onboarding them from scratch. Records also protect you after the account ends: if a canceled customer later disputes something about the last months of service, a complete history is your evidence. The only case for deleting rather than archiving is a specific customer request tied to your state's data-retention rules, which is worth checking with someone who knows the law there, not a default to reach for on your own.
What records does a buyer want to see if I sell part of my route?
A buyer wants the same seven things a good customer record already has: contact and address, pool specs, access notes, service plan, chemical and visit history, billing status, and any notes or photos worth knowing. What they're really pricing is predictability - an account with three months of clean readings and no billing disputes is worth more than one with a name and a rate and nothing else, because the buyer's techs can start servicing it on day one instead of guessing. If you plan to sell stops eventually, the cheapest thing you can do now is keep every account's record complete as you go, rather than trying to reconstruct it right before a sale.
Do I need a customer's permission to keep their card on file?
Yes - get their consent when you collect the card, and say so plainly in your service agreement rather than assuming it's implied. In practice this means the customer enters their own card during signup or a billing setup step, which itself is the consent, and your agreement should state that the account is billed to the card on file each cycle. Card data itself isn't something you store directly - the payment processor holds it and your software just references it, which is also why you shouldn't accept a card number over the phone and type it in yourself. Put the billing terms in writing at signup and this rarely becomes a problem later.
What's the one field new operators forget to fill in?
Sanitizer type. It's easy to skip because most techs can eyeball whether a pool is obviously salt or chlorine, but a record without it forces every tech to re-diagnose the pool from scratch, and a fill-in tech dosing a salt pool like a chlorine pool can cause real problems. The other one operators skip is access notes - gate codes, pets, restricted times - because the tech who normally runs that stop already knows it by heart and never writes it down. Both cost you exactly once, on the day someone other than the usual tech shows up and has to guess. A few minutes filling in sanitizer type and access notes when you add a pool saves a wasted stop later.
Can I move my old paper or spreadsheet records into one system?
Yes, and most operators do this in stages rather than all at once. Start with contact info and pool specs, since those are the fields you need before you can even schedule a route, then backfill visit and chemical history from whatever paper or spreadsheet records you have, even if it only goes back a few months. Don't wait for the migration to be perfect before you start using the new record going forward - every visit you log from today is a record you'll never have to reconstruct later. A clean record for new activity plus a best-effort backfill of history covers you far better than staying on paper until everything is perfectly transcribed.
