How to fix a chemical reading your tech logged wrong

Last updated August 5, 2026

Correct it at the source rather than in a note: reopen the visit, fix the value, and save so the record shows the corrected reading. Do not overwrite quietly on anything a customer or inspector may have already seen. If the reading drove a dose, retest the pool before assuming the correction settles it.

Every route produces a bad number eventually. A tech taps 87 instead of 8.7, logs Tuesday's readings against the wrong pool on a property with two bodies of water, or writes salt in percent when the field wants ppm. The value is not a water problem. It is a typing problem, and the pool chemical log now says something that never happened.

That matters more than it looks. The automatic service report has usually already gone to the homeowner, the reading may have driven a dose, and on a commercial account the log is the document an inspector reads. So the fix has three parts: correct the record at the source, tell whoever already saw the wrong number, and decide whether the water needs a retest.

Key takeaways

  • Fix a wrong pool chemical reading at the source by reopening the visit - a correction written into next week's notes leaves the record a customer or inspector reads still wrong.
  • Decide first whether the record is wrong or the water is wrong: 30 ppm free chlorine on a residential pool is a units error, while 5 ppm the day after a shock is real.
  • Write one line naming the old value, the new value, and the reason, because a corrected record only helps you if the correction is visible.
  • Tell whoever already received the service report, the same day if you can - a one-line text beats a Thursday phone call.
  • Retest the pool whenever the wrong number changed what the tech did, especially on free chlorine, pH, and salt.
  • Treat a blank reading as a correction too - on a commercial log, a missing value reads the same as a skipped test.
  • Fixing the same typo every week is a form problem, not a tech problem: tighten the input before you tighten the technician.

How do I fix a chemical reading my tech logged wrong?

Reopen the completed visit, correct the value on the reading itself, and save so the log carries the right number instead of a note contradicting the wrong one. Editing a pool service visit after completion is the whole job - a correction written into next week's notes does not fix the record a customer or an inspector will actually read. Reopening a completed pool visit is a normal operation, not an admission that something went badly wrong.

In PoolBoss a completed visit can be reopened and corrected from the web dashboard, and a technician can correct one from the phone as well, so the person who made the typo is usually the person who fixes it. That phone-side correction needs a signal - it is switched off offline rather than queued, because a correction is a reopen plus a second write, and replaying those out of order would leave a finished visit reading as unfinished back at the office.

To fix a wrong pool chemical reading end to end, work in this order - it corrects the record without leaving the pool wrong:

  • Confirm it is actually a mistake. Pull the pool's reading history and compare it against the last few visits. A free chlorine of 11.0 ppm on a pool that has read 1.1 ppm every week with no shock recorded is a decimal slip. A pH of 8.7 after a fresh fill is plausible. Ask the tech before you assume, because the answer decides whether you also owe the pool a retest.
  • Reopen the completed visit and fix the value at the source. Correct the number on the reading itself rather than adding a comment underneath it, so the log reads correctly from here forward. The visit's original service date is preserved when you save, so a Monday visit corrected on Tuesday still shows as Monday's service rather than jumping a day.
  • Note what you changed and why, in the visit notes. This is operator practice, not something the software does on your behalf. One line - FC corrected from 11.0 to 1.1, decimal error confirmed with tech - is what separates a silently rewritten log from a defensible one.
  • Tell whoever already saw the wrong number. If the service report went out Monday evening, a one-line text Tuesday morning beats the customer calling you Thursday. Correcting a pool service report after the fact is a two-sentence message, not an apology tour, and customers read a same-day correction as diligence.
  • Retest the water if the wrong reading drove a dose or hid a real problem. A number that was only ever wrong on paper needs no field work. A number that stopped the tech from adding chlorine means the pool has been sitting under-treated since the visit, and that is a second trip, not an edit.

First decide whether the record is wrong or the water is wrong

The two failures look identical in the log and need opposite responses. A record error means the water was fine and the number is not. A water problem means the number is right and the pool needs treatment. Sort them before you touch anything, because quietly correcting a real out-of-range reading buries a pool that needs work.

Scale is the fastest tell. Residential free chlorine lives between 1-3 ppm, so 30 ppm is a units or decimal error nearly every time, while 5 ppm the day after a shock is real. pH runs 7.2-7.8 in a working pool, so a wrong pH reading logged as 87 is a keypad slip and 8.7 is plausible. Total alkalinity sits in the 80-120 ppm band, so 1,020 is a transposition of 120. Salt reads 2,700-3,400 ppm on most cells, so a value of 3.2 is percent typed into a ppm field.

Continuity is the second tell. One reading that jumps ten times its own history and returns to normal the following week was almost certainly never true, while a value that drifts across three visits is the pool talking to you. The harder cases sit in the middle - a pH logged as 8.7 when the pool actually read 7.8 looks entirely reasonable, and only the tech can settle it. When the numbers hold up and the water is genuinely out of range, the job is a dose and a retest rather than an edit.

Five ways a reading goes wrong, and the fix for each

Most bad readings come from one of five failures, and the right correction is different for each. Nearly all of them happen in the field, in a pool water testing app, with wet hands and a phone in direct sun - which readings belong on every visit is a settled question, so the failure is almost always entry rather than judgment.

Chemical reading error types and the correction each one needs
Error typeWhat it looks likeThe correctionRetest needed?
Transposed or slipped digitsFree chlorine 11.0 where history says 1.1; total alkalinity 1,020 instead of 120Reopen the visit, fix the value, note the changeYes, if the wrong number changed the dose
Wrong pool on a multi-body propertySpa readings saved against the main poolCorrect both records - the right pool is missing its readings tooNo, if both bodies were actually tested
Wrong unitsSalt logged as 3.2 instead of 3,200 ppm; percent typed into a ppm fieldConvert and re-enter the value rather than changing the fieldNo
Reading left blankCyanuric acid never entered on a stabilized poolEnter it if the tech still has the number; otherwise leave it blank and test next visitOnly if the missing value drives dosing
Dose applied but not loggedPool was shocked, the chemical was never recordedAdd the dose to the visit so chemical cost and the next reading make senseNo
  • The blank reading is the case operators under-rate. A missing value is a hole in your pool service record keeping, and on a commercial log a blank cell reads exactly the same as a skipped test.
  • The wrong-pool error is the only one that damages two records at once, so fixing one and stopping is worse than useless - it leaves both pools looking serviced when only one of them has real numbers.
  • An unlogged dose costs money quietly. Chemical cost per pool is built from what got recorded, so a shock nobody logged shows up as a pool that looks cheaper to service than it is.

A corrected record has to show that it was corrected

A silently rewritten log is worth less in a dispute than an honestly corrected one. If a customer or an inspector ever compares the service report they received against what the log says today, an unexplained difference reads as a cover-up even when the correction was right. Every argument for pool chemical tracking assumes the numbers are true, and the one case people skip is what happens when a number was not.

PoolBoss does not keep a revision history showing what a reading used to say, so the note you write is the amendment trail. That makes it operator practice rather than something the software handles: write the old value, the new value, and the reason in the visit notes; keep the original report you sent, because that is the document the customer holds; and send the correction to whoever got the wrong number instead of waiting to be asked. Whatever you use to log and review pool chemical readings, the correction belongs in the same place as the reading, not in an email nobody keeps.

This is the same argument that makes a chemical log worth keeping at all, applied to the case it usually skips. Why the chemical record is your defense in a dispute only holds if the record is amendable and the amendments are visible. A log nobody is allowed to correct becomes a log people quietly ignore, and pool chemical log accuracy stops meaning anything the first time a tech decides a wrong number is not worth the trouble of raising.

Commercial accounts tighten this further. The paper-log convention inspectors are used to is a single line through the old value, the new value written beside it, and initials - the correction stays visible on purpose. A digital log should carry the same information in the note, because your pool service audit trail is whatever you actually wrote down. Nobody is going to reconstruct your reasoning eight months later from a number that changed on its own.

If the wrong reading drove a dose, the pool needs a retest, not just an edit

An operator running 170 pools across Henderson and southeast Las Vegas with two techs reviews Monday's route on Tuesday morning and finds free chlorine logged at 11.0 ppm on a Henderson pool that has read 1.1 ppm every week for a month, with no shock recorded. It is a decimal slip. But two things have already happened: the service report went to the homeowner Monday evening showing a number that, if it were real, would describe a pool nobody should have been swimming in - and because the tech saw 11.0 on his screen, he added no chlorine at all. The pool has been sitting at 1.1 ppm since Monday.

That is the case that separates a record fix from a field fix. Correct the reading, text the homeowner one line before they call about it, and put the pool on Thursday for a retest, because the wrong number did not only misdescribe the water - it changed what the tech did about it.

The test is simple: did the wrong reading change an action? A mistyped calcium hardness on a pool nobody was dosing for calcium is a keystroke and nothing more. A mistyped free chlorine, pH, or salt reading usually is not, because those three drive same-visit decisions. When a dose was skipped or doubled because of a bad number, retest pool water within a day or two rather than waiting for the next scheduled visit - an under-chlorinated pool in Nevada summer heat does not politely stay merely under-chlorinated for a week.

Keep it to water and records. Your job is to get the chemistry back in range and the log straight; whether anyone should have been in the pool is not a determination to make in a text message to a customer.

Frequently asked questions

Can my technician fix a reading from their phone, or does it have to be done at the office?

It depends on the software, and it is worth checking before you build a process around it. Some field apps lock a visit the moment it is marked complete, which forces every correction back through whoever has dashboard access - that is workable on a one-truck operation and painful once you have three techs and 200 pools. Others let the technician reopen the completed visit and fix the value themselves, which is faster and more accurate, because the person who took the reading is the only one who actually knows what the test kit showed. Expect a phone-side correction to require a live connection rather than queueing offline. A correction is really two writes to the same visit, and if those replay out of order after a day in a dead-signal neighborhood, a finished visit can end up reading as unfinished back at the office. Waiting for a bar of signal is the cheaper failure.

What do I tell a customer who already got the service report with the wrong number?

Send two sentences, the same day you catch it: what the reading actually was, and what you are doing about it. Something like - the chlorine on Monday's report showed 11.0, that was a typo for 1.1, we are back out Thursday to bring it up and confirm. That is the whole message. Do not attach a long explanation, do not apologize four times, and do not wait to see whether they noticed, because a customer who spots the discrepancy on their own reads it very differently than one you told first. Most homeowners do not read their service reports closely enough to catch a decimal, but the ones who do are exactly the customers who will remember how you handled it. If the wrong number described a pool that would have been unsafe, say plainly that it was a recording error and the water was never in that condition, rather than leaving them to work that out.

How long after a visit is it still reasonable to correct a reading?

Correct it whenever you find it - a record that is right is better than a record that is consistently wrong, even months later. The practical distinction is not whether to fix it but how much explanation the fix needs. Inside a few days, a straightforward correction with a note is uncontroversial, and the tech still remembers the pool well enough to confirm the real number. After a few weeks, you are relying on the reading history around it rather than anyone's memory, so the note matters more and the claim should be softer: corrected to match surrounding visits, original value appears to be a data entry error. If the record has already gone to a health inspector, an insurer, or an attorney, the correction is still worth making, but make it visible and dated rather than quiet, and keep the version you originally handed over.

What if I think the tech never actually tested the water?

That is a different problem and it does not get solved by editing the number. A correction assumes a real test with a wrong value recorded; a fabricated reading means the visit itself is unreliable, and changing the value just makes a fake record tidier. Look at the pattern rather than the single entry - identical readings week over week on a pool that should drift, readings logged at implausible times, or a stop closed out in two minutes when the route average is fifteen. Then go re-test the pool yourself and compare. If the water is nowhere near what was logged, you have a personnel conversation, not a data-entry fix, and the honest handling of the record is to log your own retest as a new visit rather than overwrite the old one with numbers you did not take. On a commercial pool this stops being an internal matter quickly, because that log is a regulated document.

Do I have to keep the original wrong value?

Nothing generally requires a service company to preserve a mistyped number, but write it into the correction note anyway - it costs one line and it is what makes the amendment credible. A log showing free chlorine at 1.1 ppm with a note reading corrected from 11.0, decimal error tells a complete story. The same log showing 1.1 ppm and nothing else, after a customer received a report saying 11.0, tells a story you have to explain from memory later. Keep the original service report you sent as well, because that document exists in the customer's inbox whether you keep a copy or not. On commercial accounts the stronger habit is the paper convention: the wrong value stays legible, the right value sits next to it, and someone's initials are on the change. Preserve the trail, not the error.

How do I stop the same typo from happening every week?

Look at the input, not the technician. When the same error keeps recurring, it is almost always the form or the field conditions rather than carelessness - salt entered in percent because the label does not say ppm, spa readings landing on the pool because the two stops sit next to each other in the list, or decimals slipping on a phone screen in bright sun with wet hands. Fix the conditions that produce it: make sure each body of water on a multi-pool property is named clearly enough to tell apart at a glance, agree on units for salt and stick to them across the whole route, and have techs sanity-check a reading against last week's number before they save. That last habit catches most of these for free, since a value ten times the previous week's is visible immediately when the previous week's is on the same screen. If one specific field keeps failing across several techs, that is a form problem you own.

Does correcting a reading change the chemical cost the visit was charged?

No. A reading and a dose are separate records, so fixing the number a tech tested does not touch what the visit was billed - the cost follows the chemicals recorded as added, not the water chemistry that prompted them. If the dose itself was logged wrong, correct that on the visit too, and the pool's chemical cost updates from there forward. What does not happen automatically is an adjustment to an invoice you have already sent. If a corrected dose changes what a customer owes, that is a manual credit or a line-item fix on the next invoice, handled the way you would handle any other billing correction. On flat monthly pricing this rarely matters at all, since chemicals are bundled into the rate. It matters most on cost-plus commercial contracts where chemicals are billed through at cost, so check the invoice on those accounts whenever a dose gets corrected.

Run your pool routes on PoolBoss

Join the waitlist and start when PoolBoss opens. Flat-rate pricing by pool count, every feature on every plan.