Cylinder and key control specification what goes wrong: A fill-in workbook exposes common cylinder and key control failures and gives specifiers practical.

Pubblicato il: mag 19, 2026

Cylinder and Key Control Specification: What Goes Wrong on Smart Lock Projects

Cylinder and Key Control Specification: What Goes Wrong on Smart Lock Projects

Smart-lock projects rarely fail because a door lacks credentials. When teams ask the cylinder and key control specification what goes wrong, they usually mean that the schedule names a lock family but not who may hold a key, which cylinders sit outside the hierarchy, or what evidence proves the decision. This fill-in workbook turns those gaps into questions a door hardware consultant can complete, circulate and retain with the submittal.

Diagnose the cylinder and key control specification what

Direct answer. The recurring failure is an unclosed decision, not a missing feature. Mark each row

Failure signalFill-in answerEvidence to attach
Scope is not stated[boundary and population][issued schedule]
Hierarchy has no door list[assigned level per door][marked door schedule]
Cylinder data is not site-specific[door and lock references][dated dimensional data]
Exclusion cell is blank[reason and alternative route][authorised exception]
Approval is assumed[status, date and reviewer][signed review record]

Fill in the boundary before naming cylinders

The key control system is the record of who may hold a key. Start with the key control schedule. Define which doors, spaces and client functions sit inside that system; name the decision owner; and distinguish a deliberately excluded door from one not yet reviewed.

Fill-in fieldEntryWhy it matters
Physical or project boundary[door groups, spaces and exclusions][client owner and issue date]
Door population[door IDs and door set references][controlled and uncontrolled doors]
Decision owner[name and role][approval method]

Map the master key hierarchy to doors

A master key opens a defined group of locks; hierarchical levels sit below it. Record the doors or groups controlled at each level, who receives each key and which authority approves changes. Do not use a hierarchy graphic as proof that every door has been reviewed.

LevelDoor or groupHolder and issue recordChange authority
Master key[enter][enter][enter]
Subordinate level[enter][enter][enter]
Special or excluded[enter][enter][enter]

Keep the master key hierarchy separate from the electronic credential register, including their owners and approvals.

Match each cylinder submittal to the installed door

Each cylinder submittal should connect the proposed lock, cylinder and key arrangement to a measured door set. Backset is the distance from the door edge to the centre of the spindle or cylinder. Ask for backset, bore diameter, bolt-to-bore distance, and matching faceplate and strike details. Bore diameter and bolt-to-bore distance are separate measurements. Identify the case as mortise, meaning inside the door; rim, meaning surface-mounted; or multipoint, meaning several locking points operated by one gear. A brochure image cannot close these checks.

A smart lock key override must be described as an operating route, its intended users and its relationship to electronic access—not simply as “key access.” Mark whether it is routine, exceptional or both, and who approves that choice.

Door-set checkFill-in requirementReviewer note
Lock case[mortise, rim or multipoint][confirm fit]
Cylinder interface[proposed arrangement][confirm on dated page]
Dimensions[backset and separate bore data][match door record]
Faceplate and strike[matched pair][confirm installed set]
Key override[route, users and approval][confirm evidence]

CONFIRM-PER-SUPPLIER: Confirm on the dated product page for the specific SKU the cylinder, key override, case type, dimensions and supplied components.

Record deliberate exclusions and keep evidence traceable

A door outside key control needs a reason, operational owner, alternative access route and review date. Phrases such as “mechanical only,” “access-controlled separately” or “existing cylinder retained” may start an entry, but do not explain the consequence. Blank cells must not conceal an intentional exception.

The access control evidence must name a document, scope, holder and issue date. Keep a supplier statement separate from an approved arrangement; a general credential standard is not product-specific evidence. Use Clause Bank: Cylinder and Key Control Specification: Documents a Specifier Should Demand for missing documents and Cylinder and Key Control Specification: A Smart Lock Specifier Guide for the wider review sequence.

Close the workbook through a recorded review

Send the completed workbook with the product submittal, not as a separate informal note. The submittal is not approved until the review is recorded and dated. The supplier must correct missing fields and resubmit them; the reviewer should mark each return reason.

flowchart TD
  A[Complete workbook fields] --> B[Check door scope]
  B --> C[Resolve scope or exclusion]
  C --> D[Map hierarchy and cylinders]
  D --> E[Return incomplete submittal]
  E --> F[Request dated evidence]
  F --> G[Record review and approval]

Use Cylinder and Key Control Specification: Reviewer Checklist to confirm that every scheduled door has an owner, and Cylinder and Key Control Specification: Template Language for a Specification when a clause must require the same evidence set.

Compare the decisions instead of comparing key formats

Before accepting a cylinder or hierarchy proposal, compare the operating decisions. A cylinder cannot be treated as like-for-like if the door, holder or supporting evidence changes.

Decision pointOption AOption BRecord before selection
ScopeInclude in this phaseDefer with named ownerBoundary and review date
HierarchyGroup by shared access needGroup by legacy key patternGroups, levels and exceptions
CylinderSupply as coordinated setRetain existing arrangementDoor-set and interface evidence
OverrideRoutine routeExceptional routeUsers, approval and operating procedure

Record the selected option, rejected option and reason. An “or-equal” request is a request for review, not an approval.

Obtain decisions where escape, fire or access consequences change

Key-control decisions do not replace the locking arrangement or the door’s role as part of a door set. Where a project involves an escape route, a fire-rated assembly or an accessible approach, obtain the relevant decision from the authority or consultant rather than copying a generic clause.

CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the escape-route and locking-arrangement requirements that apply to the project and retain the written decision.

CONFIRM-WITH-FIRE-AUTHORITY: Confirm any fire-door consequence with the fire authority and retain the decision for the identified assembly.

CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the operable arrangement and approach with the access consultant where the project requires it.

Final handover fieldComplete
Approved schedule and exception list[insert]
Supplier evidence and dated review[insert]
Authority and consultant decisions[insert or “not applicable—reason”]
Record owner and handover date[insert]

A completed workbook lets the client, installer and supplier move without another meeting. It also leaves the next reader with the decision, the check and the evidence rather than an unexplained cylinder designation.

The commercial step that follows is to request a quote.

Il tuo carrello
La tua esperienza su questo sito sarà migliorata consentendo i cookie Informativa sui cookie
Chat on WhatsApp