The Customer Key and Code Handling SOP

Purpose

This procedure guarantees that at the end of every working day the shop can say where every customer key is and who has seen every access code, and that a missing key is known to the owner and the customer the same evening rather than discovered weeks later. It turns the custody rules (where keys and codes may live, who sees them, how long they are kept; see related: Customer Keys, Codes and Lockbox Custody) into a sequence the newest dispatcher and the newest tech run the same way.

Scope

Covers physical keys, garage and gate codes, alarm codes, lockbox combinations and temporary smart-lock codes for residential and small commercial accounts, from the day a customer hands one over to the day it is returned or deleted.

Does not cover: a customer's report that a code was misused (see related: A Customer Says a Tech Shared Their Alarm Code); a field device holding codes going missing (see related: The Lost or Stolen Field Device SOP); and commercial accounts whose property manager runs its own key control, where the shop follows the customer's procedure and this one only for its internal log.

Roles and responsibilities

A backup custodian is named for every day the custodian is out, and has the cabinet code.

Procedure

1. Take nothing without a written authorization

When a customer offers a key or a code, the custodian sends an authorization by email or the customer portal stating what is being given, which services it is for, that only the assigned tech will use it, and when it will be returned or deleted (30 days after the last service on cancellation, unless the customer asks otherwise). Acceptance: the customer's written reply is attached to the account before the access is first used. What wrong looks like: a key handed to a tech in a driveway with nothing written. Stop rule: the tech brings it to the office that day, and it is not used again until the authorization is back. Hazard: none at this step, it is office paperwork.

2. Tag the key and give it one register line

The custodian puts each physical key on a ring with a coded tag that carries a number (K-0417) and the shop's main phone number, never an address or a name, and writes one line in the register: tag number, account number, which door, date received, authorization on file. Acceptance: the tag number appears exactly once in the register and the key carries no other marking. What wrong looks like: the customer's own tag with their street name, still on the ring. Stop rule: that tag comes off before the key goes in the cabinet. Hazard: none physical; do not photograph the key, because a clear photo of its cuts is a copy.

3. Put every code in the restricted field and delete it everywhere else

The custodian enters each code in the job software's restricted access field, which shows only to the tech assigned to that account's visit, and then deletes it from wherever it arrived: the text, the email, the voicemail, the sticky note. Alarm codes go in that field or the office password manager vault, never in the key register. Acceptance: the code exists in exactly one place, and searching the job notes for it finds nothing. What wrong looks like: the code is also in the notes, which print on the customer's service report. Stop rule: remove it from the notes and check whether any report has already gone out with it; if one has, tell the customer. Hazard: none at this step.

4. Store keys in the locked cabinet, with the register kept apart

Keys live in a locked key cabinet mounted out of view of visitors; the custodian and the backup hold its code. The register lives somewhere else (the job software or a locked drawer), so a stolen cabinet holds numbers with nothing to decode them. At opening, the custodian counts the keys in the cabinet against the register's "in" column. Acceptance: the two counts match. What wrong looks like: one more or one fewer than the register says. Stop rule: a mismatch at opening goes straight to step 9, before any keys are issued that day. Hazard: none at this step.

5. Check keys out only against today's schedule

The custodian issues a key only for a job on today's schedule, and writes the checkout line: tag number, tech, job, time out. Codes show to the tech automatically for the assigned visit; the custodian does not read codes out over the phone on speaker. Keys do not go home overnight unless the custodian approves it for a first-thing visit the next morning, and that is written on the line. Acceptance: every key out of the cabinet has a checkout line with all four entries. What wrong looks like: a tech asking for a key "for later in the week." Stop rule: not issued. Hazard: none at this step.

6. Carry it on your person and enter the way you said you would

The tech keeps the key on its own detachable ring in a pocket, never on the dash or in a door pocket of an unlocked truck. At the door, knock and announce before using the key, even when the customer said nobody will be home. If someone unexpected is inside, leave and call the office. If an alarm sounds and the code will not disarm it within the entry delay, step outside, call the monitoring number or the customer's number from the account, and wait in plain view with your shop ID out and hands visible if police arrive. Acceptance: the job record shows time in and time out. Stop rule: a code that fails twice is not tried again; call. Hazard: an alarm response, an unexpected occupant and a loose dog are each handled by stepping back outside first.

7. Re-secure it and prove it before you leave

On the way out the tech locks the door and tries the handle, re-arms the alarm if the customer asked for it to be armed and reads the armed state on the keypad, and closes the gate and pulls on it. A pool gate must swing shut and latch on its own; if it does not, it is a child-safety failure, the tech stays to fix it or calls the customer before leaving. Acceptance: door tried and locked, keypad showing armed where required, gate latched, and the key back in the tech's pocket. What wrong looks like: the key left in the lock or a gate resting on its latch. Stop rule: the tech does not leave the property until all three hold. Hazard: a pool gate that does not latch is the hazard; do not leave it.

8. Return every key and reconcile at close

Every key comes back to the cabinet by the end of the tech's shift, and the custodian writes the time-in on its checkout line. At close, the custodian counts the cabinet against the register again. Acceptance: the count matches the register and every checkout line from today has a time-in. What wrong looks like: a line with no time-in. Stop rule: any key not back at close starts step 9 immediately; the custodian does not leave it for the morning. Hazard: none at this step.

9. Escalate a missing key on a clock

Within 15 minutes of close, the custodian calls the tech, who checks their pockets, the truck and their memory of the last stop. If the key is not in hand within 2 hours of close, the custodian tells the owner, and the owner calls the customer that evening (or before 8:00 the next morning if close fell after 8:00 at night), says plainly what is missing, and offers a rekey arranged by the shop, with who pays decided by the shop's written policy. Acceptance: the customer has been told, and the decision (rekey, wait, or found) is recorded with times. Stop rule: nobody goes back to search a customer's property after dark, or at all without the customer's permission. Hazard: a tech hunting around a house at night is a trespass call waiting to happen; daylight, with permission.

10. Retire access when the service relationship ends

When an account cancels, or a seasonal account has had no service for 30 days, the custodian returns each key in person or by tracked delivery with a receipt the customer signs or replies to, deletes every code from the restricted field, tells the customer the codes have been removed and suggests changing them, and closes the register line with the date. Acceptance: register line closed, receipt on the account, restricted field empty. What wrong looks like: a key nobody returns because the customer "might come back." Stop rule: it is returned regardless, and re-taken through step 1 if they do. Hazard: none at this step.

The record this produces

Two documents, both kept by the custodian. The key register: one line per key with tag number, account, door, date received, authorization on file, and date returned. The daily checkout log: tag, tech, job, time out, time in, and the opening and closing counts. Exceptions (a mismatch, a missing key, a failed re-secure) get a written note with times and who was told. The owner reads the week's exceptions on Monday; the full register is read at the annual review (see related: The Annual Security Review SOP) to find keys held past the retirement rule; and an insurer or attorney reads it if a customer ever claims a key was misused.

Worked pass: a Tuesday on a pool route

• Opening count, step 4. Register shows 9 keys in; cabinet holds 9. Pass.
• Checkout, step 5. 4 keys out between 7:10 and 7:25 to two techs, each with a line for that day's scheduled jobs. One request for a Thursday job refused under the stop rule.
• Step 7, FAILED, not caught until later. At 2:40 the tech leaving the account for tag K-0233 closed the side gate, did not pull on it, and drove off with the key still in the gate's lock.
• Return, step 8, FAILED. At 5:30 close, 3 of the 4 keys were back. K-0233 had no time-in. Stop rule taken: step 9 started at once.
• Step 9. Custodian called the tech at 5:38, inside 15 minutes. The tech checked his pockets and truck and could not find it. At 7:30, 2 hours after close, it was still missing, so the custodian called the owner at 7:32. The owner called the customer at 7:45, explained that the key for the side gate was unaccounted for, and offered a rekey at the shop's cost, which the shop's policy allows the owner to do.
• The customer asked the tech to look in daylight. At 8:05 the next morning, with permission, he found the key hanging in the side gate's lock, where it had been since 2:40 the day before, a little over 17 hours, with the gate unlatched.
• Outcome. The customer chose to have the lock rekeyed anyway, because the key had been in reach of anyone walking past overnight. The owner agreed. The exception note records both failures and the times.

The step 9 clock worked: the customer heard about it that evening rather than at the next visit. Step 7 is the one that failed, and its stop rule existed and was skipped. The owner's fix was not a new rule but a habit: the tech says "door, alarm, gate" out loud and touches each one, every exit.

References

• Your job software's documentation on restricted fields, role permissions and access logs
• Pool barrier requirements in the residential code as adopted by your jurisdiction, for the self-closing, self-latching gate rule
• See related: Customer Keys, Codes and Lockbox Custody, A Customer Says a Tech Shared Their Alarm Code, The Lost or Stolen Field Device SOP