Response When a Customer Cannot Verify Identity or Authority

Purpose

The Identity and Authority Verification SOP is the gate every job runs through before a tool comes out. This procedure covers what happens when that gate returns a fail or gets challenged, because the moment of failure is exactly when a technician is most likely to improvise: an insistent caller, a doorstep story that sounds plausible, a second person who shows up mid-job disputing the first. A shop with no scripted response to a failed gate ends up either assisting an unauthorized entry or locking a rightful occupant out of their own home, and both get defended the same way, with a record of exactly what was asked, said, and refused.

Without this procedure the failure gets handled ad hoc by whoever is on the porch that day, and ad hoc decisions made under social pressure trend toward "helping the customer," which is precisely the instinct that produces the liability event this SOP exists to prevent.

Scope

Covers the response once the identity or authority gate fails or is challenged, at intake, on arrival, mid-job, or after a job has already closed. Does not cover the gate itself or its document classes, owned by the Identity and Authority Verification Before Any Work SOP, which runs first and is assumed complete or attempted before this procedure starts. Does not cover the possession-specific document ladder for landlord and tenant disputes, owned by the Landlord Lockout Request Handling SOP. Does not cover a writ-executed job, which runs off the writ and the officer present, not off a doorstep negotiation.

Roles and responsibilities

The handoff that fails first is technician to lead. A technician who resolves an ambiguous doorstep call alone, either direction, has made a decision that was never theirs to make.

Procedure

Step 1: Control the physical situation before you say a word about documents. If the person's reaction to being asked for identity or authority proof turns aggressive, blocks your path back to the vehicle, or you arrive on a scene that is already volatile (raised voices inside, a visibly frightened second occupant, signs of a fresh domestic dispute), you disengage physically first and explain nothing on the spot. Acceptance: you can state you kept an unobstructed path to your vehicle for the whole encounter. Wrong looks like continuing to explain shop policy while standing inside a threshold with the door between you and your exit. Stop rule: if you cannot retreat cleanly, leave the property entirely and call from the vehicle or the road, dispatch first for a merely insistent person, the local non-emergency line for any threat of harm; never re-enter for a tool left behind, it is replaceable and the property is not worth the trade.

Step 2: Deliver the decline once, in the same words, and stop. State plainly what document or confirmation is missing, using the exact class named in the gate SOP, then stop discussing it. Acceptance: you can quote back what you said, verbatim, afterward. Wrong looks like negotiating a softer proof after the fact, "well I did see mail with your name on it," and proceeding on that instead. Stop rule: any attempt, yours or theirs, to trade the stated requirement for something lesser is itself the signal to call the lead, not a reason to keep talking.

Step 3: Call the lead live before you leave and before you consider proceeding. One phone call, person to person, reporting what was asked and what was refused. Acceptance: call placed, lead reached or the 10-minute window run out, decision recorded on the ticket in either case. Wrong looks like waiting until end of day to mention a doorstep decline. Stop rule: lead unreachable inside 10 minutes means the decline stands, the ticket is marked escalation pending, and a callback is scheduled; the technician never self-authorizes an exception, no matter how sympathetic the story.

Step 4: Treat a mid-job dispute as an automatic hard stop. If a second person arrives while you are partway through a cylinder pull or a re-pin and disputes the first person's authority, stop at the current step, do not complete the cut or the reinstall, and secure whatever hardware is disassembled so the door is either fully closed and lockable or both parties are told plainly it cannot be secured yet. Acceptance: door left in a known, stated state. Wrong looks like finishing "since you're basically done," which turns an honest accident into a provable choice. Stop rule: a disputing second party present in person is a hard stop no technician may override; only the lead may authorize continuing, and only after reaching both the original claimant and the disputing party, or with police present.

Step 5: Treat a dispute surfacing after the job closed as a records question first, not a fault question. Pull the verification block from that visit and confirm it actually contains what the gate required for that job's class: identity fields, authority documents, and for an elevated job, the second-channel callback log. Acceptance: every required field present and timestamped from that visit. Wrong looks like relying on memory that the visit "was done right" when the file itself is thin. Stop rule: an incomplete record for that job class means the shop cannot defend the visit, and the lead treats it as an incident, including notifying the insurer or bond if a claim looks likely; the file's job is separating provable from unprovable, not settling guilt on the spot.

Step 6: Log every decline, whether or not the job ever restarted. Record date, address, requester, stated reason, technician, and the lead's decision every time, not only once it becomes a problem. Acceptance: an entry exists for every step-1 through step-4 stop. Wrong looks like a log that only fills in after a complaint arrives. Stop rule: two declines at the same address inside 90 days triggers a required owner review before the next dispatch there, flagged on the address record so the next CSR is not dispatching blind.

Step 7: Resuming after a hazard-triggered withdrawal needs independent, physical confirmation the scene is clear, not a guess that enough time has passed. Before any technician returns to an address left under step 1, the lead confirms clearance from a named source, an officer's name or badge number, or direct contact with a calm occupant confirming the person of concern has left, and logs it. Acceptance: named confirming source and time recorded before dispatch. Wrong looks like returning because an hour has gone by and it is probably fine. Stop rule: no independent confirmation means no return that day; reschedule to daylight hours with a second technician present, or decline the job permanently.

Step 8: Resuming a step-4 mid-job stop needs a fresh acceptance check, not a continuation. Once the lead authorizes restart, the work resumes with the same acceptance conditions as a new job: the door's current state is verified, the customer of record is reconfirmed against the identity gate, and the delivered-key count at completion is checked against what the original ticket promised. Acceptance: a fresh verification block completed for the resumed visit. Wrong looks like picking the pin kit back up where it was left and finishing without re-checking who is standing there now. Stop rule: any change in who is present or what they are authorizing since the stop restarts the gate from step 1 of the Identity and Authority Verification SOP, not from where the technician left off.

The record this produces

One decline or escalation entry per event: date, address, requester and stated authority, the technician's account, the lead's decision, and for any hazard withdrawal, the confirming source and time before a resume. Where the job later restarts, the fresh verification block from step 8 attaches to the same ticket rather than replacing it, so a reader later sees the full arc, not just the ending. Readers later: the owner reviewing a pattern address, the insurer on a claim, a licensing board asking why a job was declined or delayed.

Worked pass: a rekey interrupted by a disputed authority

A residential rekey is dispatched at 14:00 for a woman who passed the gate cleanly that morning: current lease in her name, ID matching, no elevated class triggered. The technician is mid-cylinder, pins already pulled from the front door lock, when a man arrives, states he is her husband and this is also his home, and objects that he was not consulted.

Step 4 fires. The technician stops with the cylinder disassembled, reassembles enough hardware that the door still closes and the untouched deadbolt still locks, and tells both parties plainly the front knob cannot be secured again until this is sorted. He calls the lead per step 3's discipline, live, from the truck.

The lead reaches both parties by phone and separately runs a records check on the lease, not off either person's phone. The lease names only the woman as tenant. Under step 4's rule the husband's objection alone does not authorize continuing, but it also does not override a sole leaseholder's own authority over her unit; the lead authorizes resuming with the wife as the sole authorizing party, on the record that the objection was heard and did not change the underlying lease fact.

Step 8 governs the restart: the technician re-runs the acceptance check rather than simply finishing the pin job, reconfirms the wife's ID against the original morning verification, and completes the rekey. Two keys delivered, counted aloud, signed for at 15:20. The husband's objection, the lead's independent lease check, and the resumed verification block all attach to the same ticket per the record section above, so a later dispute has the full sequence rather than a rekey that simply happened.

References

• ALOA Security Professionals Association code of ethics, on opening or rekeying only for a person with proven authority over the opening
• State locksmith licensing and bonding rules on decline and incident record retention, which vary by state; confirm your own jurisdiction's requirement
• See related: Identity and Authority Verification Before Any Work SOP (owns the gate this procedure responds to), Landlord Lockout Request Handling SOP (owns possession-specific document classes)