Log every chemical reading and keep a history for every pool

Log free chlorine, pH, total alkalinity, calcium hardness, and cyanuric acid on every visit, plus salt level for salt pools and water temperature. Those are the readings that tell you whether the water is safe, balanced, and sanitizing the way it should. Free chlorine confirms the pool is actually being disinfected; pH governs how effective that chlorine is and how comfortable the water feels; total alkalinity buffers pH so it doesn't swing; calcium hardness protects plaster and equipment from scaling or corrosion; and cyanuric acid keeps chlorine from burning off in sunlight. Salt pools add a salt-level reading so you can watch the cell, and temperature feeds the water-balance math. PoolBoss presents these fields in the order a tech actually tests the water and hides the salt field for non-salt pools, so logging a reading takes seconds at the poolside instead of scrolling past fields that don't apply. Each value saves to that pool's history rather than just the visit, which is what lets you see a trend instead of a single snapshot. Logging the same parameters every time is what makes the history useful: a pool that drifts low on chlorine week after week is a different problem than a one-off bad reading, and you can only tell the two apart when the data is captured consistently on every stop.

Pool-specific software does; general field-service software usually does not. This is the dividing line between a tool built for pool routes and a generic scheduling-and-invoicing app that happens to be used by a pool company. PoolBoss logs structured water-chemistry readings - free chlorine, pH, total alkalinity, calcium hardness, cyanuric acid, salt, and temperature - and saves each one to the pool's own history, on every plan including the free one. That means the readings are real data you can trend, flag, and attach to a service report, not free-text typed into a notes box. Generic field-service tools like Jobber and Housecall Pro were built for trades like HVAC, plumbing, and cleaning, where there's nothing to test, so they have no structured place for water chemistry. Companies using those tools end up keeping chemistry in a separate app, a spreadsheet, or paper logs that never connect to the customer record or the invoice. For a pool company that's a real gap, because water chemistry is the actual service being delivered. When you're evaluating software, the test is simple: can a tech log a numeric reading that saves to the pool and shows up on the customer's report, or are they typing notes that nobody can trend later. PoolBoss is built around the first answer.

No. Jobber is general field-service software built for trades like landscaping, cleaning, HVAC, and plumbing, and it has no structured way to log pool water chemistry. There's no field for free chlorine, pH, alkalinity, calcium hardness, or cyanuric acid, and no per-pool chemical history that trends those readings over time. Pool companies that run on Jobber end up recording chemistry in free-text job notes, a separate water-testing app, or paper logs - none of which connect back to the customer record or the invoice, and none of which let you spot a pool that keeps drifting out of range. Jobber handles scheduling, quoting, and invoicing competently for general service work, so the gap isn't that it's a weak product; it's that water chemistry simply isn't part of what it was designed to track. For a pool route, that's the part of the job that matters most. PoolBoss is built for pool chemistry specifically: the reading form follows the order a tech tests the water, every reading saves to the pool's history, out-of-range values flag, and the readings attach to the service report the customer receives. If chemical tracking is the reason you're shopping for software, that's the difference between the two - a generic tool you'd have to work around versus one where logging chemistry is the core workflow.

No. Housecall Pro is general field-service software, built for trades like HVAC, plumbing, and home cleaning, and it does not track pool water chemistry in any structured way. There are no dedicated fields for free chlorine, pH, total alkalinity, calcium hardness, cyanuric acid, or salt, and no per-pool history that lets you trend those readings across visits. Any water chemistry a tech wants to record has to go into a generic notes field, which means it can't be flagged when it's out of range, can't be charted over time, and doesn't attach cleanly to the customer's service report. Housecall Pro does scheduling, dispatch, and invoicing well for the trades it targets, so this isn't a knock on the product - water chemistry just isn't something it was ever designed to capture. For a pool service company that's a meaningful limitation, because logging and proving water chemistry is the actual deliverable, not an afterthought. PoolBoss handles it as the central workflow: structured readings logged in testing order on any phone, saved to each pool's history, flagged automatically when they fall outside target ranges, and paired with the service report the customer gets. If you're comparing the two for a pool route, chemical tracking is the clearest reason a pool-specific tool wins over a generic field-service platform.

Track chemical history by logging readings that save to the pool itself, not just to the visit, so every pool carries its own running record. In PoolBoss, when a tech logs free chlorine, pH, alkalinity, and the rest at a stop, those numbers attach to that specific pool. Open the pool from the customer's record and you see the full history laid out over time: what the chlorine and pH were doing week to week, when the water last went out of range, the dose that was added, and any notes the tech left. Because a customer can have more than one pool, the history is kept per pool rather than lumped at the account level, so a residential customer's spa and pool, or a commercial client's multiple bodies of water, each have their own trend line. That history is what turns guesswork into a decision. A pool that keeps creeping low on chlorine is a standing problem worth a conversation about usage or equipment; a single bad reading after a storm is not, and the record makes it obvious which one you're looking at. It also protects the business: if a customer claims a pool was neglected, the timestamped history of readings and visits shows exactly what was done and when. None of it requires extra data entry - the history is a byproduct of the tech logging the visit they were already doing.

LSI, the Langelier Saturation Index, is a single number that tells you whether pool water is balanced, scaling, or corrosive. It's calculated from pH, water temperature, calcium hardness, and total alkalinity, and it captures something no individual reading does on its own: how those factors interact. Water can have an acceptable pH and still be aggressive or scale-forming once temperature and calcium are accounted for. A balanced LSI - generally near zero - means the water is in equilibrium with the surfaces it touches. Drift negative and the water turns corrosive, etching plaster, dissolving grout, and attacking metal equipment and heater components. Drift positive and the water scales, leaving calcium deposits on surfaces, in pipes, and on the salt cell. For a pool service company, LSI matters because both failure modes are expensive and slow to show up: by the time a customer sees etching or scaling, the damage is done and it's the service company that gets blamed. Watching LSI lets you catch water that's quietly out of balance before it costs anyone a resurface or a heater. PoolBoss captures the readings that feed the index - pH, temperature, calcium, alkalinity - so balance is something you can monitor as part of normal logging rather than a separate calculation a tech has to run by hand at the poolside.

Prove what was done with the service report generated from each visit, which lists the readings taken and the notes the tech left, with a timestamp for when the stop happened. Instead of a verbal "we took care of it," the customer gets a record: the free chlorine and pH the tech measured, what was out of range, what was added, and any issues found at the pool. In PoolBoss that report is produced automatically as a byproduct of the tech completing the visit in the app, so there's nothing extra to assemble - the proof exists the moment the work is logged, and it goes to the customer right after the visit. By the time the monthly invoice arrives they've already seen each visit's proof, and the bill itemizes the visits it covers, which is one of the most effective things a pool company can do for billing, because it answers the question behind most slow or disputed payments: did the service actually happen and was the pool cared for. A customer who opens a bill and recognizes the visits and readings they were already shown approves it and pays without a back-and-forth. The same record protects the business in the other direction. If a customer claims a pool was neglected or that a chemical was never added, the timestamped history of readings shows otherwise. For commercial and HOA accounts, that documentation is frequently a contractual requirement rather than a nicety, and having it generated automatically means it's always there when someone asks.

PoolBoss flags out-of-range readings automatically by comparing each value a tech logs against target ranges, so a low free chlorine or a high pH stands out instead of getting lost in a column of numbers. When a reading falls outside its acceptable band, it's marked at the point of entry, while the tech is still standing at the pool and can act on it - add chemical, retest, or note why it's off - rather than discovering the problem days later back at the office. That immediacy is the point: water chemistry problems are cheap to fix on the spot and expensive to fix after a pool has gone green or a customer has complained. The flag also carries into the pool's history, so a one-time out-of-range reading and a pool that's chronically off look different when you review the record. A single high pH after a rainstorm is routine; the same pool flagging low on chlorine three weeks running is a standing issue worth a conversation about bather load, equipment, or service frequency. For an owner, the flags turn a long list of readings into an exception report you can scan - you don't have to read every number on every pool, you look at what got flagged. And because the check runs the instant a tech logs the reading, nothing depends on someone remembering to review the data later.

Track chemical cost per pool by configuring what each chemical costs you and letting the doses logged on visits do the math. In PoolBoss you set a per-unit cost for each chemical in settings - chlorine, acid, salt, and the rest - and as techs log what they add at each stop, the cost of those doses rolls up against the pool they were added to. That gives you a chemical cost per pool per month built from real service data rather than a guess, which is the number owners use to find unprofitable accounts. A pool that needs far more chemical than its service price covers - because it's oversized, heavily used, or fighting a chronic balance problem - is invisible on a schedule but obvious in a cost report. Once you can see it, you can act: reprice the account, adjust the service plan, fix the underlying chemistry problem driving the demand, or let the account go. The same data feeds route profitability, where chemical cost is weighed against what a route bills, so you can tell a busy route that earns from a busy route that just looks productive. Because the cost side is assembled from the doses techs already log, tracking cost per pool doesn't add a data-entry step - it's a report drawn from the chemistry tracking that's happening anyway. It turns a gut feeling about which accounts pay into a number you can sort.

The core difference is where the chlorine comes from. A traditional chlorine pool is dosed directly - the tech adds chlorine as liquid, tablets, or granules to keep free chlorine in range. A salt pool makes its own chlorine on site: a salt cell runs an electrical current through salted water and converts it to chlorine continuously, so instead of adding chlorine you manage the system that produces it. That changes what you track. On a salt pool you still log free chlorine, pH, alkalinity, calcium hardness, and cyanuric acid, but you add salt level to the list, because the cell needs salt in a specific range to generate chlorine efficiently, and you keep an eye on the cell's output and condition. Salt pools also tend to push pH up over time, so acid management is a recurring task. Chlorine pools skip the salt reading and the cell entirely but usually demand more hands-on dosing each visit. PoolBoss handles both by showing the salt field only when a pool is set up as a salt pool, so a tech servicing a chlorine pool isn't tapping past a field that doesn't apply, and a tech on a salt pool captures the salt reading as part of the same quick form. Either way the readings save to the pool's history, so the record reflects how that specific pool is actually managed.

A green pool is almost always an algae bloom that took hold because sanitizer dropped too low, and clearing it chemically follows a consistent sequence. First test the water and get a real reading - pH, free chlorine, alkalinity, cyanuric acid - because the cyanuric acid level determines how much chlorine you'll actually need to reach an effective dose. Balance pH into range so the chlorine you add works, then shock the pool with a heavy dose of chlorine sized to the water volume and the severity of the bloom, often well above a normal weekly dose. Brush the walls and floor to break up algae, run the filter continuously, and clean or backwash it as it loads up with dead algae. Retest and re-shock over the following days until free chlorine holds steady, which signals the bloom is dead, then clarify or vacuum out the residue. PoolBoss supports this without pretending to do it for you: the tech logs the readings at each visit, the dose guidance estimates a starting amount from the pool's size and the reading, and because every reading saves to the pool's history you can watch chlorine finally hold across the recovery visits instead of guessing whether you're winning. The water-balance reading helps confirm the pool is back in equilibrium once it clears. The chemistry decisions stay with the tech; the software keeps the record that shows the recovery actually happened.

The best app for logging pool chemical readings is one built specifically for pool chemistry that saves each reading to the pool's own history and keeps working in the field, where pools actually are. A generic notes app or a general field-service tool can capture text, but it can't trend a reading, flag one that's out of range, or attach it to the customer's service report - and those are the things that make logging worth doing. PoolBoss is built for this. The reading form is ordered the way a tech tests the water, so free chlorine, pH, alkalinity, hardness, and cyanuric acid take seconds to enter with wet hands and more stops to go, and the salt field appears only for salt pools. Every reading saves to the pool, not just the visit, so the history is there the next time anyone opens that pool. Readings flag automatically when they fall outside target ranges, and they flow into the service report the customer receives and into the cost and profitability reports the owner runs. It works on any iPhone or Android phone, so there's no tablet to buy for every truck, and because pools sit in back yards where signal drops, the app keeps logging offline and syncs when the phone reconnects. The test for any chemical-logging app is whether the reading becomes usable data or just text in a box - PoolBoss is built around making it data.