Document the opening as a complete system
An access-controlled door is a coordinated assembly, not a single device. The reader, credential, lock, request-to-exit device, door-position switch, power supply, controller programming, fire-alarm interface, and mechanical hardware all have to behave together.
Build the documentation around a stable door ID. Use that same identifier on the door schedule, drawings, controller points, cable labels, test records, photos, and software. This creates a record that can be followed from the physical opening back to the panel and database.
Project, site, and access-control scope
Record the project boundaries and operational intent before listing devices. This distinguishes new work from reused openings and clarifies which party owns mechanical hardware, life-safety interfaces, network access, and credential administration.
- Customer, site, building, floor, project number, phase, and access-control platform
- Security, facilities, IT, fire-alarm, locksmith, electrical, and general-contractor contacts
- New, modified, relocated, removed, and existing controlled openings
- Operating schedules, access groups, lockdown functions, elevator or intercom interfaces, and exclusions
- Owner-furnished hardware, approved substitutions, change orders, and deferred work
- Installation, database, test, training, and closeout milestones
Door inventory, naming, and schedules
The door schedule should be the central index for the system. A clear door number connects the architectural opening, access-control software, controller point, wiring, and service history.
- Door ID, software name, architectural number, room or area, floor, and opening description
- Single door, pair, gate, turnstile, elevator, cabinet, or specialty opening type
- Normal operating mode, schedule, unlock behavior, and after-hours expectations
- Ingress and egress direction, handing, swing, frame, and existing mechanical hardware
- Controller, panel, reader port, lock output, input points, and power-supply association
- Special notes for delayed egress, stairwell reentry, ADA operators, or coordinated sequences
Use a name such as B1-1F-D102-NORTH-ENTRY rather than “front door.” A stable ID prevents confusion when a site has multiple entrances or software names change.
Readers, locks, REX devices, and door-position switches
Each opening record should identify every field device and explain its function. Model and serial information is important, but so are voltage, contact type, mounting location, wiring method, and the expected response.
- Reader manufacturer, model, serial number, technology, interface, keypad, and mounting details
- Electric strike, magnetic lock, electrified trim, lockset, exit device, or gate-operator information
- Lock voltage, current, fail-safe or fail-secure behavior, suppression, and power source
- Request-to-exit motion, button, crash-bar switch, touch sensor, or other egress input
- Door-position switch type, contact state, magnet alignment, and forced or held-open timing
- Intercom, operator, sounder, strobe, break-glass, key switch, or local annunciation associated with the opening
“D102 lock output 24 VDC, fail secure, powered by PS-2 output 4” is actionable. “Electric lock at north door” is not.
Controllers, expansion modules, power, and batteries
Panel records make it possible to trace a door from software to hardware. Document the enclosure, controller, modules, input and output assignments, power distribution, backup capacity, and network relationship.
- Panel ID, enclosure location, manufacturer, model, serial number, firmware, and database name
- Controller and expansion-module addresses, downstream buses, reader interfaces, and capacities
- Input and output mapping with normal states, end-of-line values, and programmed function
- Power-supply model, voltage, load, distribution outputs, fuse or PTC ratings, and lock power
- Battery quantity, chemistry, rating, manufacture date, load-test result, and replacement date
- Dedicated circuit, disconnect, grounding, tamper, cabinet key, and environmental notes
Credential formats, panel networking, and system records
Credential and network documentation prevents database migrations, reader replacements, and panel service from becoming guesswork. Record formats and ownership without including personal cardholder data that does not belong in the field closeout package.
- Credential technology, bit format, facility code, number range, encryption, and mobile credential platform
- Reader protocol, OSDP addressing and security status, or legacy interface information
- Panel hostname, IP address, subnet, gateway, DNS, VLAN, switch, and switch port
- Server, application, database, cloud tenant, software version, license, and support responsibility
- Time schedules, access levels, holidays, threat levels, and naming standards delivered
- Secure administrator credential handoff and configuration or database backup location
Wiring, cable labels, and system interfaces
Access-control cables often converge in a shared enclosure, making consistent endpoint and conductor records especially important. Identify each cable, terminal, splice, pathway, and external interface.
- Cable ID, type, conductor count, gauge, shield, rating, color, and approximate length
- Origin, destination, panel terminal, power output, door device, and intermediate junction
- Reader, lock, REX, DPS, auxiliary input, relay output, network, and fire-alarm cable labels
- Conduit, tray, sleeve, riser, door loop, transfer hinge, power transfer, and concealed route
- Fire-alarm release interface, relay state, supervision, responsible contractor, and test reference
- Elevator, intrusion, intercom, operator, video, or building-system input and output mapping
Record both sides of a release interface: access-control relay or power-supply input, fire-alarm module, normal state, activation result, and the joint test date.
Functional and credential testing
Test every opening as an operating sequence, not a collection of isolated devices. Verify granted and denied access, egress, door monitoring, schedules, alarms, loss of power, and applicable release behavior.
- Valid, invalid, expired, disabled, and out-of-schedule credential responses
- Reader indication, unlock time, relock, door position, forced-open, and held-open behavior
- Request-to-exit operation, nuisance-alarm prevention, and free egress
- Fail-safe or fail-secure response during loss of normal power and backup-power operation
- Fire-alarm or emergency release sequence where applicable and coordinated with responsible parties
- Technician, date, witness, expected result, actual result, deficiency, and retest evidence
A passed card read is only one step. Open the door, confirm the position switch changes, allow the door to close, verify secure status, and test the forced and held-open timers.
Deficiencies, photos, as-builts, sign-off, and closeout
Reconcile the physical opening, panel terminations, software name, door schedule, and final drawings before turnover. Preserve corrected issues with their retest results rather than erasing the failure history.
- Deficiency number, affected door, operational impact, owner, correction, completion date, and retest
- Door overview, reader, lock, REX, DPS, panel, power-supply, label, and termination photos
- Final door schedule, panel maps, point assignments, cable records, network details, and field changes
- Configuration backup, licenses, spare credentials, keys, manuals, and training materials delivered
- Technician, project-manager, fire-alarm witness where required, and customer sign-off
- Open exceptions, responsibility, target date, final revision, and delivery confirmation
A consistent field record
Standardize documentation without slowing the work.
Standardized access-control forms keep the door schedule, panel points, cable labels, testing, and as-built record aligned. That reduces missed information at turnover and gives service teams a clear path from the opening back to the controller.
View the Access Control Documentation Pack