Locked or Inaccessible Window During Scheduled Service - The Response Standard

Purpose

This SOP guarantees that a technician who arrives for a scheduled visit and finds a window blocked by a locked room, an absent occupant, security bars with no key on-site, or furniture that cannot be moved, has one standing sequence: attempt reasonable access, decide, adjust the bill, and document, rather than either skipping the pane silently or forcing an entry that creates a different problem. A silently skipped pane costs the shop later, at invoice time, when the customer notices they were billed for glass nobody touched. A forced entry, prying a painted-shut sash, moving a customer's furniture without asking, trades a minor scheduling inconvenience for the exact kind of damage claim the rest of this shelf exists to prevent.

Scope

Covers an interior-access or occupancy barrier, a locked room, an absent tenant, security bars with no available key, furniture blocking interior approach, on a routine residential, multifamily, or light-commercial recurring or one-time visit. It does not cover an exterior physical or fall-safety barrier, a roofline obstruction, a ladder angle that will not clear, a missing anchor point, all owned start to finish by the window-cannot-be-safely-reached decision tree, including its own non-negotiable safety script; this SOP is the full standing procedure for the interior-access barrier that tree scopes out to a single "ask the customer" step. It does not cover determining fault for the locked door, nobody is at fault, this is a scope-exclusion event, not a liability event, and it does not route through any of this shelf's fault-finding procedures.

Roles and the handoff between them

The procedure

1. Attempt every access channel documented on the work order or account file, in order, before excluding anything, within a bounded window on-site. Text or call the customer, check for a stated arrangement already on file, a gate code, a lockbox, a property manager contact, and give it a defined window, ten minutes is a common default, tune it to your route density, before moving on to the rest of the visit. Acceptance: every documented channel has been tried and the outcome noted, within the stated window. Wrong looks like skipping straight to exclusion without checking whether the office already has an access arrangement on file for that account. Stop rule: if no documented arrangement exists and nobody answers within the window, the window is excluded for this visit; the tech does not search the property for an undocumented way in, trying other doors, moving furniture without permission, and if the urge to "just check" one more thing shows up, that urge gets the same stop an undocumented action gets anywhere else on this shelf, it does not happen without it being on file first. Hazard: forcing a stuck or painted-shut sash to gain access counts as force on window hardware, which risks a tech-caused damage claim exactly like the ones the rest of this shelf covers, attempt stays attempt, it never becomes pry.

2. If reached, confirm with the occupant directly whether the barrier resolves within the visit window or genuinely cannot today. Ask plainly: can the room be unlocked or the furniture moved right now, or is this a no for today. Acceptance: a stated yes or no, and if yes, a specific time the access will be ready, checked against whether the crew can actually wait that long without the rest of the day's route slipping. Wrong looks like waiting indefinitely "just in case" while the rest of the scheduled route falls behind. Stop rule: if the promised access window would push the day's remaining stops past their own scheduled windows, the tech moves on and offers a return visit rather than holding the whole route hostage to one pane. Hazard: none, this is a conversation.

3. Exclude the window from today's scope with a specific, not generic, reason. Write the actual barrier: locked room, tenant absent, security bars no available key, furniture not moved, matched against the occupant's own words where they were reached. Acceptance: a specific reason is logged, not a vague "couldn't get to it." Wrong looks like a generic inaccessible note that tells the next technician nothing about what would need to change. Stop rule: none. Hazard: none.

4. Adjust the invoice or the recurring-contract count before it goes out, closing the exclusion rather than leaving it for a customer to catch later. Confirm which pricing model applies to this account, a flat recurring rate typically absorbs an occasional single-pane exclusion without adjustment, a per-pane or itemized rate typically deducts it, and apply that rule before the invoice is sent. Acceptance: the invoice reflects the correct treatment before it goes out, not corrected after a dispute. Wrong looks like invoicing the full scope and hoping the one untouched pane goes unnoticed. Stop rule: if the account's pricing treatment for this situation is genuinely ambiguous, a new account with no stated policy, the office resolves it before the invoice ships, the tech does not guess in the field and the invoice does not go out on a guess. Hazard: none.

5. Give the customer written notice of the exclusion and any return-visit option before the crew leaves the property. A text, an email, or a copy of the work order note, matching the same-visit disclosure timing this shelf uses for any scope gap. Acceptance: the customer has a written record of what was excluded, why, and what their options are, a return visit, waiting for the next scheduled cycle, or resolving access themselves before next time. Wrong looks like relying on a verbal mention alone, or on a note the occupant left for the crew being treated as if it also closes the loop back to the occupant, it does not, the crew's own written notice is what closes it. Stop rule: if written notice was not sent before the crew left the property, it goes out before end of that business day, and if that does not hold either, the office sends it the next morning rather than letting the gap carry over unresolved into the next scheduled visit. Hazard: none, this step is a written message, not a site action.

6. Flag a repeat pattern on a recurring account rather than excluding the same pane silently a second or third time. If the same window or room has been excluded on two consecutive visits, a reasonable default trigger, tune it to your route, the account gets a scope conversation instead of a third silent exclusion; a room that is never accessible was either mis-scoped at signup or the barrier has become permanent, and the contract should say so. Acceptance: a two-visit repeat is surfaced to the office, not left to recur indefinitely in separate, uncross-referenced work orders. Wrong looks like excluding the same pane visit after visit with an identical note and never raising it, which quietly erodes what the customer believes they are paying for. Stop rule: none, this step always completes once the pattern check runs. Hazard: none.

The record this produces

• Channels attempted: what was tried, and the outcome of each, within the stated on-site window.
• Exclusion reason: the specific barrier, matched to the occupant's own words where reached.
• Pricing treatment: which model applied and how the invoice reflects it.
• Written notice: what was sent, when, and any return-visit option offered.
• Repeat count: whether this window has been excluded before, and on how many consecutive visits.

The repeat count is the field that turns an isolated inconvenience into a scope decision the office can actually act on, rather than a complaint the customer eventually raises first.

One run of this standard, filled in

A biweekly residential route stop, a home-office window at the back of the house, blinds drawn.

• Step 1: the tech knocks, checks the work order, no special access note beyond the yard gate code already used to reach the back of the house. The homeowner is inside but on a video call; a note taped to the door reads "in a meeting, back window can wait." Channel attempted within the window, outcome noted. Pass.
• Step 2: the taped note itself functions as the occupant's answer, cannot resolve within the visit window today. Pass.
• Step 3: the window is excluded with the specific reason logged: "home office window, occupant on a call, declined access this visit." Pass.
• Step 4: this account is billed at a flat recurring rate that absorbs an occasional single-pane exclusion; no invoice adjustment applies, confirmed against the account's stated policy. Pass.
• Step 5: the tech, satisfied that the taped note already communicates the situation, leaves without sending a text or work-order copy back to the homeowner. Fail. The acceptance calls for the crew's own written notice, not reliance on the occupant's note as proof the loop is closed in both directions. Stop rule taken once caught at day's-end review: the tech sends a text before the account is marked closed for the visit, confirming what was skipped and offering to catch it next time.
• Step 6: the office checks the account file and finds this is the second consecutive visit this exact window has been excluded. A scope conversation is scheduled with the homeowner ahead of the next visit, rather than letting a third silent exclusion happen.

The taped note in step 1 was genuinely useful, it answered the access question cleanly, but it was never a substitute for the crew's own written notice back to the homeowner, and the gap between "the customer left me a note" and "I confirmed back to the customer" is exactly where an exclusion turns into a dispute weeks later when nobody remembers who told whom what.

References

• See related: the window-cannot-be-safely-reached decision tree, which owns the exterior physical and fall-safety barrier types and their own non-negotiable safety script.
• See related: the weekly route maintenance contract structure reference and the commercial recurring contracts reference, for how a recurring account's pricing model should state its exclusion-handling policy up front.
• IWCA (International Window Cleaning Association) guidance on documenting site-access limitations and partial-service scope.