Objective. The student will correctly apply authorization verification procedures and applicable legal obligations to five scenario-based case studies and produce a compliant code work service record for each, with no legal or ethical errors.
This lesson, its worked examples and its practice questions has not yet been verified by a credentialed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Code work — looking up, originating, or decoding a key code — is one of the most legally sensitive tasks a locksmith performs. The reason is straightforward: a key code gives whoever holds it the ability to cut a working key to a specific lock, vehicle, or safe. If a technician provides that information or a physical key to the wrong person, the result can be theft, burglary, or worse. The locksmith who handed over the code without proper verification can face civil liability, loss of licensure, and in serious cases, criminal charges as an accessory.
Every state that licenses locksmiths includes provisions governing code work. The specific wording varies, but the core obligations are consistent: verify that the person requesting the service has legal authority over the property in question, document that verification, and protect the code itself from unauthorized disclosure. Check the statute summary your instructor has provided for the exact language that applies in your jurisdiction.
Before any code is looked up or any key is cut from a code, you must establish authorization — proof that the requester has the legal right to access the property. Authorization is not optional, and a customer's verbal assurance that they own the property is not sufficient on its own.
Common forms of authorization include:
When you cannot obtain satisfactory authorization, the correct action is to decline the job and explain what documentation is needed. This protects the customer's legitimate interests too — a responsible locksmith refusing a job without proper paperwork is exactly the kind of safeguard the public expects.
A caller asking for a safe combination or a vehicle key code over the phone presents an elevated risk. You cannot verify identity remotely with the same reliability as an in-person encounter. The standard industry practice is to require the customer to appear in person with identification and supporting documents. Do not quote codes over the phone, and never email or text a code to an unverified requestor.
Requests for master key codes in apartment complexes or commercial buildings deserve extra scrutiny. A person claiming to be a property manager must provide documentation — typically a management agreement, a business card alone is insufficient. Because a master key code gives access to every lock in a keying system, the authorization standard is higher, not lower. When in doubt, contact the property owner directly through a verified phone number rather than one provided by the requester.
Code databases — whether in print or software — contain restricted information. The ALOA Code of Ethics and most state statutes require that locksmiths protect code data from unauthorized access. Practical obligations include:
Violating these protections exposes you and your employer to civil suits from property owners whose security was compromised, and potentially to regulatory action resulting in license suspension or revocation.
If a locksmith cuts a key for an unauthorized person and a crime results, the locksmith and the employing company can be named in a civil lawsuit. Plaintiffs may argue negligence — that a reasonable professional would have required proper authorization. Thorough documentation is your primary defense. A service record that shows you checked ID, recorded the document type and number, and confirmed authorization demonstrates due diligence. A blank or incomplete record suggests the opposite.
Remember that your state license is your livelihood. A single serious violation of authorization requirements can trigger a licensing board investigation. Protecting your license means following authorization procedures on every job, not just the ones that feel suspicious.
Every code work transaction must produce a written service record before the job is closed. A compliant record includes:
1. Date and time of the transaction.
2. Customer name exactly as it appears on presented ID.
3. ID type and number (e.g., state driver's license, number redacted to last four digits per your company policy, or full number as required by your state statute).
4. Property description — vehicle year, make, model, and VIN for automotive; address and lock description for residential or commercial.
5. Authorization type and document reference — title number, lease number, or other document used to verify ownership.
6. Code referenced or originated — recorded in the locked job file, not on the customer's copy.
7. Keys produced — quantity and type.
8. Technician name and signature.
No field may be left blank. If a field does not apply, write "N/A" and initial it. Incomplete records are treated the same as missing records during a licensing board audit.
The ALOA Code of Ethics reinforces the legal requirements with professional obligations. Members and credentialed technicians commit to serving clients honestly, refusing work that would harm the public, and upholding the reputation of the trade. Refusing an improperly authorized code request is not just legally correct — it is the ethical standard the industry sets for itself and that employers, courts, and licensing boards expect you to meet.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.