Tracking customer sites and equipment so you're not guessing on the next visit
The job isn't just the work. It's knowing what you're walking into before you get there.
The job isn't just the work. It's knowing what you're walking into before you get there.
Marco services 47 pools across San Diego. Every Thursday he's at the Hendersons' place on Maple - a Pentair variable speed pump, a salt cell that's been acting up since March, and a gate code that changes every quarter. Every other Tuesday he's at the Riverside HOA - three pools, two of which share a heater, one with a chemical feeder that needs priming before treatment.
He keeps all of this in his head.
It works - until it doesn't. Until he shows up without the right salt cell tester because he forgot the model. Until a new tech covers a Tuesday route and calls three times because nobody wrote down the gate code. Until a customer asks when the pump filter was last replaced and Marco has to say "sometime last spring, I think."
That "I think" is the problem. And it's exactly what ToolBerry's Sites and Assets modules are built to fix.
Why Do Field Teams End Up Guessing?
The information exists. It's just scattered - in someone's head, in a text thread, in a notebook in the glovebox of a truck that's out on a job right now.
Site knowledge - things true about a location. The gate code. The dog that needs to be put away before you open the side gate. The water shutoff behind the back fence. The HOA contact who actually approves the work.
Equipment knowledge - things true about a specific piece of equipment at that location. The model number. The install date. What was replaced last time. What broke the time before that.
Both types get scattered because there's never been a clean place to put them. A notebook gets left in the truck. A spreadsheet goes out of date. A text thread is impossible to search six months later.
The result: every return visit starts with a guess.
What Happens When Knowledge Walks Out the Door?
Marco has been doing this for nine years. He doesn't need to look anything up - it's all up there.
But what happens when he takes a week off? When the business grows and he brings on a second tech? When a customer calls the office asking about their equipment history and Marco is on the other side of the city?
Knowledge that lives in one person's head is a single point of failure. It works perfectly - right up until it doesn't, and then there's no backup. That's the real cost of not tracking sites and equipment properly: a business that can't scale, can't cover absences, and can't answer basic customer questions without one person on the phone.
How Can You Store Site Access and Equipment History in One Place?
ToolBerry separates site knowledge and equipment knowledge into two distinct modules - Sites and Assets - and ties them together so each detail is stored where your team expects it.
Sites: Everything About the Location
A Site in ToolBerry is a physical location where work happens. One customer can have multiple sites - a property management company might have twelve buildings, each with their own access details, contacts, and history.
Each site record holds:
- Full address with map coordinates
- Access notes - gate codes, entry instructions, parking details
- Linked contacts - the onsite manager, the emergency contact, the person who actually lets you in
- A complete job history for that location
- All assets installed or serviced there
For Marco, the Henderson pool is a site. The Riverside HOA has three sites - one per pool. When he opens the Henderson record before leaving the shop, the gate code is right there. So is the note about the dog. So is the name of the contact who signs off on chemical changes.
He's not guessing. He's reading.
Assets: Everything About the Equipment
An Asset in ToolBerry is a specific piece of equipment at a specific site. Not "a Pentair pump" in general - the Pentair SuperFlo VS installed at 2847 Maple Drive in March 2022, serviced four times since, with a note from the last visit about unusual bearing noise.
Each asset record holds:
- Asset type and model
- Install date and full service history
- Notes from every visit - what was done, what was found, what to watch next time
- Linked relationships for complex systems - a heater connected to two pools, a controller managing multiple zones
When Marco's new tech covers the Thursday route for the first time, he opens the Henderson site, taps the pump asset, and reads three visits worth of notes. He knows what to check before he even gets out of the truck.
How Does a Visit Change When the Previous One Was Documented?
Before leaving the shop, Marco opens ToolBerry and pulls up the next site. Gate code is current. The salt cell is a Hayward T-Cell-15 - last visit note says output was at 68%, worth monitoring. He creates a work order, links it to the site, and heads out.
At the property, he runs the service. Output has dropped to 61%. He adds a note to the asset record, attaches a photo of the reading, and marks the work order complete. The customer history now shows a documented trend - three visits, output declining - that he can present when he recommends a replacement next month.
No "I think." No "sometime last spring." A clean record with dates, readings, and photos, attached to the exact piece of equipment it belongs to.
How Does ToolBerry Handle Equipment That Serves Multiple Areas?
Pool service businesses deal with this constantly - one heater feeding two pools, an irrigation controller managing six zones, a booster pump connected to three outlets.
ToolBerry lets related equipment stay connected. The main heater links to each pool it serves. Service history flows through the right level - work on the heater logs to the heater, work on a specific pool logs to that pool - so nothing gets mixed up and nothing gets lost.
For Marco's Riverside HOA: three pools, one heater serving two of them. Every visit is logged to the right place. Six months from now, Pool B's chemical history is three taps away.
What Are the Honest Tradeoffs?
It takes setup time upfront. The Sites and Assets modules pay back once your data is in them - but you have to put the data in. For an existing business with 40+ active customers, that's a few hours of entry before the system starts earning its place. The payoff is meaningful, but not immediate.
It works best when the whole team uses it consistently. One tech who skips visit notes breaks the chain. The value is cumulative - each visit builds on the last.
Equipment specs require manual entry. ToolBerry lets you define asset types and models with custom fields, but it doesn't auto-populate manufacturer specs. You add what you know. That's a one-time cost per model that pays back every time someone looks it up.
How Can You Start Without Migrating Everything at Once?
You don't have to enter 47 pools before the system is useful. Start with your three most active customers.
- Open ToolBerry at toolberry.app - no account, no signup, free to start.
- Add your first customer and create a site for their location.
- Add the key access note - gate code, entry instructions, whatever you'd tell a new tech.
- Add one asset - the main piece of equipment you service there. Model, install date, one note.
- Log your next visit as a work order against that site. Attach a photo. Add a note to the asset.
After one week of doing that for your most active sites, you'll have more reliable records than most field service businesses accumulate in a year of notebook entries.
Marco still has a notebook in his truck. But the Henderson gate code, the salt cell model, and the bearing noise note are in ToolBerry now. The next tech who covers that route doesn't need to call him. The customer asking about their equipment history gets a real answer, not a best guess.
That's the difference between a business that runs on one person's memory and one that runs on a system.
Have a question?
We're always happy to help.
Email us at contact@toolberry.net. Get ToolBerry on the App Store and Google Play, or read more at toolberry.net.
Free. Works offline. No account required. Start on your next job.
Further Reading
- Why ToolBerry Is Offline-First - why the app works with zero signal
- Going Paperless at Your Own Pace (You Don't Have to Ditch the Notebook) - a phased approach for moving off paper without forcing your whole team to switch on day one.
- Handyman: From Sticky Notes to a Simple Job Tracker- One place that remembers what a sticky note forgets