Your work. Your records.
Locksmiths and Safe Repairers: Workplace Records
A locksmith's employment concern may involve a disputed assignment, a handoff or a change to an access record. The timeline should explain your role without exposing the security information you handled. Identify the relevant authorized record and when it changed; do not make personal copies of keys, access details or protected client files.
Call now(800) 800-5555Free initial case evaluation. Representation depends on work state and case eligibility. This guide explains record preparation; it does not determine whether a legal claim exists.
A record map for your role
What to organize first
Assignment boundary
Identify your assigned role and any later change without disclosing access details.
Handoff timing
Separate the date of the work from the date information was supplied or entered.
Restricted evidence
Identify where an authorized reviewer can find a record instead of copying its security contents.
Unresolved issue
Keep the correction request and response status distinct from assumptions about who caused a discrepancy.
Start with the work you actually do
Repair and open locks, make keys, change locks and safe combinations, and install and repair safes.
O*NET classifies this occupation as Locksmiths and Safe Repairers (49-9094.00). Its description covers a typical occupation, not every workplace or individual job. It does not establish employee status, overtime eligibility or employer misconduct.
- Keep records of company locks and keys.Source task 7125 · updated 08/2025
- Set up and maintain master key systems.Source task 18790 · updated 08/2025
- Install door hardware, such as locks and closers.Source task 18791 · updated 08/2025
Record the scope of the assignment
Note the date, assigning role and permitted work-order reference for the task you were directed to perform. Distinguish installing hardware from maintaining an existing key system or updating a record. If the instruction changed, identify when you received it and whether you requested clarification. An account of an employment concern does not need a site address, access code or technical description of how a lock can be opened.
Separate the work from the record handoff
If a concern involves a lock or key record, note whether you created an entry, supplied information for someone else or were asked to reconcile a discrepancy. Identify the date and responsible team role rather than copying the security contents. Record any correction request and whether a response is pending. Do not silently amend earlier entries or infer that the last recorded handler controlled every preceding step.
Preserve employment evidence through permitted channels
Keep your own permitted work schedules, employment notices and communications about the disputed assignment. Where a relevant security record cannot be retained personally, note its location for authorized review without reproducing its contents. A missing handoff entry should be described as missing information, not proof of loss or misconduct. Continue to follow the workplace process for urgent access or security concerns; this timeline is not a substitute for that process.
What the source establishes
The selected O*NET 31.0 tasks describe company lock and key records, maintenance of master key systems and installation of door hardware. They are dated August 2025. They describe occupational work rather than the authorization rules of a particular property. This guide provides no bypass, entry or security-system instructions and makes no determination about misconduct, licensing or employment rights.
Choose your next step
Review the workplace retaliation guide, unpaid wages guide, or discrimination guide if those concerns fit your experience. A job title alone does not establish a claim.
Call now(800) 800-5555Current service-state coverage
AK, AL, AR, AZ, CT, DE, FL, GA, HI, IA, ID, IN, KS, KY, LA, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NM, NY, OH, OK, PA, RI, SD, TN, TX, UT, VA, VT, WI, WV, WY. Eligibility is evaluated individually; this list does not promise representation.
Explore state resources