Customer Disputes Streaking or Water Spots - The Response Standard

Purpose

This SOP guarantees that a streaking or water-spot complaint gets the same sequence every time, acknowledge, look before diagnosing, and land on a disposition the crew can defend, rather than each crew lead negotiating a one-off outcome from a phone call that later customers compare notes on. A dispute handled on instinct swings between two costly extremes: caving to a free redo on a cause the shop never controlled, which trains the account to complain its way to free work, or arguing with a customer before anyone has actually looked at the glass, which turns a fixable relationship into a lost account over a phone call that never needed to happen. The fix is not a friendlier tone. It is a procedure that separates "look" from "promise" and routes the outcome through a rule the shop already trusts.

Scope

Covers a customer report of streaking, spotting, or glass that is not clean after a completed cleaning visit, from intake through disposition and record close. It does not cover the technical diagnosis of which mechanism produced the marks, technique, total dissolved solids in the rinse water, or a glass-surface condition unrelated to the wash, all owned by the applicable decision trees on this shelf, this SOP's step 3 routes into whichever tree fits the reported pattern rather than restating any of them. It does not cover the free-revisit-versus-charge-versus-fire decision itself, owned in full by the recurring-complaint decision matrix, this SOP is the procedure that executes whichever outcome that matrix selects, not a second version of the same logic. It does not cover a scratch or physical-damage complaint, a different failure mode with its own response.

Roles and the handoff between them

The procedure

1. Acknowledge the complaint the same business day and schedule a reinspection visit, do not diagnose over the phone. Acceptance: the customer is contacted by end of the next business day and a reinspection visit is scheduled, typically within a few days rather than weeks. Wrong looks like promising a specific cause or a free redo before anyone has looked at the glass in person. Stop rule: if the customer demands an immediate answer with no visit, explain that spot and streak patterns require an in-person look under the right light to diagnose correctly, and hold the schedule rather than guessing over the phone, a wrong guess given now becomes a promise the visit may end up contradicting. Hazard: none, this step is a phone or message exchange.

2. Pull the account's prior record before the visit, not on arrival. Review any prior photos, work order notes, or a logged total-dissolved-solids reading if the shop tracks one for that route. Acceptance: whatever record exists is reviewed before the technician arrives, and its absence is noted if there is none. Wrong looks like showing up cold and relying entirely on what is seen that day, with no reference to whether this is a first complaint or a repeat. Stop rule: none, this is desk preparation. Hazard: none.

3. Run the field diagnostic at the reinspection visit, routed through the matching decision tree for the reported pattern. Check the marks at low angle in raking light, run a wet test if hard water is suspected, and read the spot or streak pattern against the shop's known signatures. Acceptance: a stated cause, routed through the correct tree, documented with photo evidence. Wrong looks like eyeballing the glass and pronouncing "that's just water spots" without actually running the pattern read. Stop rule: if the pattern does not cleanly match a known signature, droplet, streak, film, treat it as undetermined and default toward the customer's benefit at the disposition step rather than arguing an inconclusive read. Hazard: a reinspection at height runs under the same access and fall-protection controls as any other elevated work, it does not get a shortcut because it is framed as just a look rather than a full clean.

4. Apply the revisit-free-versus-charge-versus-fire matrix to the diagnosed cause, and state the disposition to the customer on-site with the reasoning, not just the outcome. Acceptance: a disposition is selected and the customer can repeat back the reason correctly, the reasoning is what makes the call defensible later, not the outcome alone. Wrong looks like caving to a free redo under pressure when the diagnosis points to an external or out-of-scope cause, exactly the trade the matrix warns against. Stop rule: if the diagnosis in step 3 was genuinely undetermined, do not select charge or fire, default to a free correction and revisit the classification if the same pattern recurs. And if a technician is tempted to promise a free redo on-site despite a clearly external or out-of-scope cause, that promise routes through the office before it is made to the customer, never granted unilaterally under the pressure of a live conversation. Hazard: none.

5. Execute the redo or scope the paid add-on with a concrete next step, the same visit if possible, scheduled before leaving if not. Acceptance: a dated next step exists, not an open-ended "we'll get to it." Wrong looks like leaving without a scheduled resolution when the fix could not happen on the spot. Stop rule: if the fix requires equipment or product not on the truck that day, the next visit is scheduled before the crew leaves the property, not left for the office to arrange later, and if that does not hold before departure, the office calls the customer with a date within one business day rather than letting the open item go quiet. Hazard: whatever the redo itself involves, ladder, water-fed pole, or ground-level work, carries the same controls as the original visit; a second attempt under time pressure to make up for the first is not a reason to skip a stable base or a spotter.

6. Log the account history and flag a repeat pattern, closing the loop this complaint opened. Add this complaint to the account's history alongside prior ones, and if this is the second or third instance, surface that pattern explicitly to whoever owns the fire decision rather than leaving it buried in separate work orders nobody cross-references. Acceptance: the complaint is logged against the account, and a repeat count is stated if this is not the first. Wrong looks like treating each complaint as a fresh, isolated event with no reference to history, which is exactly how a chronic account keeps drawing free revisits past the point the matrix would have called for firing it. Stop rule: none, this step always completes once the disposition is set. Hazard: none, this step is a record entry.

The record this produces

• Prior record: whether one existed, and what it showed.
• Diagnosis: the stated cause, the tree it routed through, and the photo evidence.
• Disposition: free, charged, or an undetermined default, with the reasoning stated.
• Resolution: the concrete next step and its date.
• Account history: this complaint logged against any prior ones, with a repeat count.

The account history is what turns a single friendly free redo into a documented pattern the next reinspection or the next contract renewal can actually see.

One run of this standard, filled in

A monthly storefront account, third streak complaint logged against it in the current year.

• Step 1: the property manager calls the morning after the visit. Office acknowledges the same day and schedules a reinspection two days out.
• Step 2: the file shows two prior complaints this year, both logged as workmanship misses with free redos, both corrected on the spot.
• Step 3: at the reinspection, the technician runs the pattern read under raking light. The streaks trace to a landscaping company's new sprinkler head, installed the prior month, spraying hard water directly onto the lower storefront glass each morning. Diagnosed as an external, ongoing cause, not a workmanship issue, documented with a wet test and photos of the sprinkler's spray arc reaching the glass.
• Step 4: on-site, and eager to avoid another confrontation on a third complaint, the technician tells the property manager "we'll take care of it, no charge." Fail. The stop rule calls for routing a free-redo promise through the office first when the diagnosis points to an external cause; the technician promised it unilaterally, on the spot, under exactly the pressure the rule anticipates.
• Step 5: back at the office that afternoon, the diagnosis and the promise are both reviewed together. The external cause is confirmed against the matrix as a paid add-on situation, a recurring pre-clean rinse pass before the monthly service, quoted separately. But the promise was already made to the customer's face. The office honors the free redo this one time to protect the relationship, schedules it for later that week, and flags the technician's judgment call for coaching rather than reversing a promise already given.
• Step 6: the account history is updated with the sprinkler-caused pattern, the free redo honored despite the diagnosed external cause, and a note that the next occurrence of this same sprinkler-driven streak routes straight to the paid add-on with no exception, since the cause and the fix are now both established.

The technician's instinct to keep the peace was not wrong on its own, keeping a good account happy has real value, but making that call without the office meant the shop absorbed a cost the matrix would have scoped differently, and the account's history now carries a harder line for next time specifically because this time went soft.

References

• See related: the revisit-free-versus-charge-versus-fire recurring-complaint decision matrix, which owns the disposition logic step 4 applies.
• See related: the applicable streaking and water-spot decision trees on this shelf, which own the field diagnostic method step 3 routes through.
• IWCA (International Window Cleaning Association) business and operations guidance on scope of work, callbacks, and documentation of completed work to support dispute resolution.