An access-control project brief describes which doors and people a building needs to manage before any reader or locking device is selected. It is a planning record for the owner, manager and installer, not a design approval. A useful brief makes the intended boundaries visible, names the people who can authorize them and leaves unknown equipment details for assessment.
Write down the decision the system should support
Start with the property area, the authorized project approver and the person who will administer the system after handover. Explain the access problem in ordinary language. Perhaps a shared key group is difficult to manage, a storage entrance needs separately approved users, or an existing system no longer operates as intended. Avoid beginning with a reader model copied from another building; different doors and responsibilities may call for different work.
Give each included opening a stable ID. Mark a shared, landlord-controlled or tenant-controlled entrance accordingly. If another party must approve work on a door, record that approval as pending. The commercial door hardware inventory can hold model and symptom details without putting credentials in the project brief.
Describe people and boundaries
List roles and the openings each role needs, then list access that should remain separate. A delivery role that uses one entrance does not automatically need a building-wide credential. Describe any schedule or temporary-user requirement as a question to evaluate against the proposed system, not a function that every reader provides.
Keep names, sensitive plans and current credentials in restricted property records. The brief can use role labels such as “front-desk staff” or “approved contractor.” Do not place usable codes, account passwords or a public map of secure areas in material circulated for an initial enquiry.
Record the starting condition
For each door, note the existing lock or release device, visible reader and controller information, normal operation and known faults. Mark equipment “unknown” when it cannot be identified safely. A dragging or poorly latching door may need mechanical work before or alongside access electronics. Separate any door, frame, network, electrical or other trade work for qualified assessment.
The access-control installation page describes the service’s equipment and planning scope. If the issue is a fault in an installed system, use access-control repair to frame the diagnostic enquiry. This brief is for deciding requirements and ownership before a new or changed project.
Define handover before installation
Name who approves users, issues credentials, removes access and maintains administrator accounts. Ask the qualified installer to describe the proposed system’s supported behavior during relevant power or connectivity failures for the actual opening. Do not assume one powered-lock behavior is suitable everywhere.
List what must be demonstrated at handover: intended access, intended exclusions, normal door operation, administrator training, documentation and supported recovery procedures. Identify who will witness each check. If the project has phases, list completed and outstanding doors separately so a first installation is not mistaken for a finished building-wide system.
A brief you can adapt
Property area, purpose and authorized approver:
Door IDs, administrators and pending permissions:
User roles and intended access boundaries:
Current equipment, operation and observed faults:
Required functions to confirm against a proposed system:
Separate trade or building review needed:
Administrator, handover checks and phase exclusions:
Keep the detailed brief in the property’s controlled files. Send an initial description and the authorized contact through the contact page, then agree how to share any sensitive plans. Once a system is installed, the access-control handover checklist covers transfer of accounts, credentials and records to its operator.