Before You Approve That Rekey: The One Question That Protects Your Master Key System (Georgia

Before You Approve That Rekey: The One Question That Protects Your Master Key System (Georgia

Ask this before you rekey: a Georgia policy you can run tomorrow

Before any rekey in a master key system, require the approver to ask and answer one question in writing: “What else does this change affect?” That litmus test forces an impact analysis before parts are ordered or cylinders are turned, so you preserve the hierarchy, limit the blast radius, and keep operations moving. Authorization sits with the named system owner and designated approvers. Custodians who issue keys and vendors who perform work do not approve changes. That separation of duties makes approvals defensible and keeps audits clean.

Keep the opening move simple and consistent. No rekey proceeds until the approver documents the litmus-test answer, confirms scope against the keying chart, and sets timing that keeps life safety and operations intact. Mandatory rekeys follow clear triggers, including lost or stolen keys, unreturned keys at separation, compromised cylinders or cores, keyway policy changes, and boundary changes from renovations. Capture the reason and level of impact early so the right people review it before any core is pulled.

Keep the hierarchy intact

A master key system is a hierarchy that allows different levels of access within a facility. In standard practice, the top key opens the top lock group and all locks below it, while masters open their assigned groups and change keys open only their specific doors. This structure delivers targeted access and, when something goes wrong, a smaller and more cost-effective response because you can rekey only the affected sets rather than the entire facility. Industry guidance consistently reinforces two habits that protect this value over time, limit master key usage and keep records tight so the hierarchy remains trustworthy and auditable.

Hierarchy drift starts quietly and becomes expensive. Undocumented, ad hoc cross-keying, uncontrolled duplication, and casual issuance erode the design and make future rekeys larger and slower. Your policy should prohibit ad hoc cross-keying outright. Planned cross-keying can be necessary and safe when managed properly, for example to support shared service spaces or temporary operational overlaps, and is allowed only with elevated approval, explicit notation in the keying chart, justification tied to a business need, and a documented blast-radius analysis that calls out the added interchange risk. Treat these as time-bound exceptions that receive special scrutiny during impact reviews and incident response, and retire them when the underlying need ends.

Definitions: what this policy means by key terms

Change key refers to the lowest level in the hierarchy, typically opening a single room or office. A master key opens a defined group of change-keyed doors, and grand masters open multiple master groups; some large campuses also use a great-grand master above that. A keying chart maps these relationships and the bitting codes that produce them so approvers can see what any change will touch. Progression is the planned sequence of key cuts used to build a hierarchy, and MACS is the maximum adjacent cut specification that prevents weak keys and mechanical interference.

Interchangeable core systems, including SFIC and other IC platforms, use a removable core that swaps quickly with a control key. A control key is not a door-opening key; it removes and installs cores and therefore requires special governance. Restricted keyways are patented or controlled key systems that limit unauthorized duplication through manufacturer or distributor authorization. Cross-keying means intentionally keying multiple masters to an opening; undocumented cross-keying is prohibited in this policy. Interchange risk refers to unintended openings caused by overlapping bitting in a poorly governed or depleted progression.

Plan the impact before you touch a cylinder

Answer the litmus test by mapping the blast radius at the requested level and then testing that map against your records. Identify which doors and cores are affected, which key sets must be recollected or reissued, which shared spaces or after-hours vendor routes are implicated, and which records will change. A simple example illustrates why: a lost change key typically requires only the rooms and suites in that change key’s run to be rekeyed, while a lost area master may force a larger, phased response to avoid disrupting operations across multiple departments. Master keying exists to provide layers of access, use those layers to keep disruptions small and to target rekeys where they matter most.

Technology choices drive outage windows and future flexibility. Interchangeable cores shorten downtime because trained technicians can swap cores quickly, then cut new change keys and masters to match the updated chart. User-rekeyable cylinders can reduce labor in high-churn, low-risk locations that are not part of a master-keyed stack and do not sit on restricted keyways, because authorized staff can change the working key at the door without removing the lock or dispatching a vendor. For example, a Georgia campus managing frequent move-ins and move-outs in swing spaces can reset those cylinders during unit turnover walkthroughs, avoiding a separate truck roll, after-hours scheduling, and key collection loops that would otherwise tie up custodial and locksmith time. Their limitations are real, most user-rekeyable platforms do not support complex hierarchies, and some cannot live on restricted systems, so high-security or master-keyed critical areas should avoid them unless the chosen brand explicitly supports the hierarchy you need. Conventional cylinders remain appropriate for stable, low-risk openings where downtime can be scheduled and progression headroom is not a concern.

Define control-key custody for IC and SFIC systems as a distinct policy class. Name specific custodians who may hold a control key, store control keys separately from door-opening keys in access-controlled storage, and maintain a sign-out log that records requestor, reason, locations to be serviced, and return time. Require dual control for issuing control keys for field work, prohibit personal retention or take-home practices, and restrict duplication to the system owner with documented approval. Transport control keys and loose cores in tamper-evident bags and reconcile bag serials at handoff, and conduct periodic reconciliations of control keys and control-keyed cores against records so discrepancies surface quickly. If a control key is lost or suspected compromised, treat it as a distinct incident class with immediate containment, swap affected cores to a safe series and suspend any work-in-progress that depends on the compromised control key until you re-establish custody.

Mechanical changes rarely live in isolation. Coordinate rekeys with updates to electronic access and HR offboarding so card and code rights keep pace with mechanical changes. For first responders and life safety, any change that touches fire department access requires prior coordination and documented approval from the authority having jurisdiction, and those keys and cores remain outside normal rekey scope unless the AHJ directs otherwise. Common examples include Knox boxes, fire service elevator controls, alarm rooms, and riser rooms, all of which must retain responder access throughout your work. When master keys are rotated, update the Knox box inventory and replace affected keys in the box so responders retain the intended access profile, and capture the AHJ’s sign-off in your records before closing the request.

If you need to see how these plans turn into field work you can audit, walk through the staging and documentation steps in Rekey Services: A Practical Walkthrough.

Governance: who can say yes, and what a complete request must contain

Good governance separates design, approval, custody, and execution. The system owner is accountable for the hierarchy, the records, and the authorization model. Approvers evaluate risk, ask the litmus-test question, and authorize changes. Custodians issue and track keys and cores against the chart and the issuance log. Vendors and technicians perform the work and return documentation so the record stays authoritative. No one should grade their own homework, and no work starts until an approval is recorded.

A complete, auditable change request contains one concise package of scope, impact, and controls. At minimum, include:

  • Affected buildings, areas, and openings; the key level involved; and the rationale and timing constraints
  • A written blast-radius analysis that answers “What else does this change affect?”
  • Progression impacts documented by the vendor or system owner, including available changes left in the relevant key section, MACS compliance, interchange checks, and remaining capacity in affected sub-master groups
  • The approval trail, with elevated approval and a second reviewer for any request that touches a master, grand master, or multiple buildings
  • A restricted-key authorization and chain-of-custody plan for ordering, transporting, and issuing keys and cores
  • The specific record updates to be made on completion, including keying charts, bitting codes, and issuance logs, plus stakeholder communications and validation steps

Approval timing should match the risk. Low-impact change-level work can be approved on a routine cadence, while anything that reduces progression headroom or exposes interchange risk should be escalated. Record approvals before any cores or keys are ordered, cut, issued, or swapped. If the documented progression shows low remaining capacity, pause and redesign that branch before you spend the budget on changes you will soon have to undo.

Records, restricted keys, and incident response

Your keying chart, bitting codes, and key issuance logs are the system of record. Treat them like a source code repository by versioning and dating every change, recording who approved it, and retaining prior states so you can reconstruct conditions before and after an incident. Industry sources emphasize that keeping accurate key records is essential to preserve security and auditability, and that a well-governed hierarchy with limited master key usage improves overall control while keeping rekeys targeted and cost-effective.

Restricted systems require administrative rigor. Maintain current authorization or signature cards with the OEM or distributor, and audit signatories after personnel changes so only current leaders can place restricted orders. Define how to add, update, or revoke authorizations, and expect identity verification steps and lead times from distributors before they release restricted keys or cores. Document the pickup or delivery method, log custody from vendor to custodian to end user, and store restricted stock separately from unrestricted keys. Transport any restricted keys or loose cores in tamper-evident bags, and reconcile bags against issuance logs at handoff.

When something goes wrong, time is policy. A lost or stolen change key should trigger a rapid, contained rekey of the affected openings after you disable access for that key set and notify occupants. A lost or stolen master or higher escalates to the system owner immediately, followed by visible containment to reduce exposure while you stage a phased rekey, for example temporarily restricting after-hours movement in the affected areas, issuing short-term keyed-different cylinders in critical openings, posting staffed access control at chokepoints, and aligning electronic access changes to mirror the new mechanical boundaries. Control-key loss is a distinct, faster-moving incident class, execute immediate core swaps in the affected series and block any openings you cannot swap yet with temporary hardware until containment is complete.

Prepare so you can move fast without improvising. Keep an inventory of pre-keyed spare cores or locks for critical areas, a written rapid-swap run book your teams can follow, and vendor on-call SLAs to meet your containment timelines. Recognize that restricted systems may have procurement lead times, define contingencies such as temporary keyed-different cores, short-term area lockdowns, or staffed guard posts while awaiting new components. Close the loop with validation, record updates, signed key receipts, and a short post-incident review to confirm the hierarchy remains intact and progression headroom is still healthy.

For related details, review Restricted Keys and Key Control for Georgia Businesses: Stop Unauthorized Copies Without Constant.

The workflow is straightforward and repeatable: intake the request, ask and answer “What else does this change affect?,” approve with separation of duties, execute with the chosen technology, validate access, update records, and communicate. Hold to those steps and the litmus test, and your Georgia facilities will preserve security, limit blast radius, and keep operations moving even when the unexpected happens.

Leave a Comment

Your email address will not be published. Required fields are marked *