What Should Be Included in Access Control Project Closeout Documentation?

Project information, door schedules, and naming

Start with the customer, site, project contacts, system platform, approved scope, and responsible trades. The final door schedule becomes the index that connects drawings, software names, panel points, cable labels, test results, and service history.

Use a stable door identifier based on the building, floor, architectural opening, or another agreed convention. Avoid names such as “front door” when a site has several entrances or remodels may change how areas are described.

• Door ID, architectural number, software name, building, floor, room, and opening description
• Opening type, handing, swing, ingress and egress direction, and existing mechanical hardware
• Normal schedule, unlock behavior, access groups, lockdown functions, and exceptions
• New, modified, relocated, removed, reused, and out-of-scope openings
• Owner, facilities, security, IT, locksmith, fire-alarm, electrical, and service contacts

Readers, locks, REX devices, and door-position switches

Document every field device associated with the opening and explain how it is expected to behave. Include model information, mounting, wiring, voltage, contact state, power source, and programmed function where those details support future service.

• Reader manufacturer, model, serial number, technology, interface, keypad, and location
• Electric strike, magnetic lock, electrified trim, exit device, lockset, or gate hardware
• Lock voltage, current, fail-safe or fail-secure behavior, suppression, and power source
• Request-to-exit motion, button, touch sensor, crash-bar switch, or other egress input
• Door-position switch type, normal state, alignment, and forced or held-open timing
• Intercom, operator, break-glass, sounder, strobe, key switch, or specialty device

Controllers, modules, panel networking, and software

Panel documentation should allow a technician to trace the opening from the software database to the controller, module, input, output, and enclosure. Record capacity and spare points as well as the points currently used.

• Panel ID, enclosure location, manufacturer, model, serial number, firmware, and tamper
• Controller, downstream board, reader module, input module, and output module addresses
• Door, reader, lock output, REX input, DPS input, and auxiliary point assignments
• Hostname, IP address, subnet, gateway, VLAN, switch, switch port, and address method
• Server, application, database, cloud tenant, software version, license, and backup location
• Secure administrator access, support responsibility, and recovery process

Power supplies, batteries, and power-loss behavior

Power documentation explains which supply operates each lock and panel, whether backup capacity is available, and how the opening behaves when normal power is lost. This information is essential for troubleshooting intermittent or load-related problems.

• Power-supply ID, location, manufacturer, model, voltage, rating, and dedicated circuit
• Distribution board, output, fuse or PTC, connected load, and lock association
• Battery quantity, chemistry, rating, manufacture date, test result, and replacement date
• Grounding, surge protection, disconnect, cabinet key, and environmental notes
• Observed fail-safe or fail-secure response during normal-power loss and restoration

Credential formats and input/output mapping

Credential information should describe the format and technology needed to support enrollment, reader replacement, or migration without including unnecessary cardholder data. Input and output mapping should state both the physical terminal and the programmed purpose.

• Credential technology, bit format, facility code, number range, encryption, and mobile platform
• Reader protocol, OSDP address and secure-channel status, or legacy interface
• Input name, terminal, normal state, supervision, programmed function, and associated door
• Output name, relay or terminal, energized state, programmed function, and load controlled
• Schedules, holidays, access levels, threat states, and naming standards transferred
• Credential issuance, revocation, recovery, and secure administrator-custody responsibility

Wiring, cable labels, and fire-alarm interfaces

Cable records should identify the route and termination of reader, lock, REX, DPS, network, power, and interface wiring. Shared enclosures make clear labels and terminal mapping especially important.

Where a fire-alarm interface is present, document the access-control side, the fire-alarm connection, the normal state, the expected release response, the responsible parties, and the joint test record. Follow the approved design and applicable requirements rather than relying on a generic sequence.

• Cable ID, type, conductor count, gauge, shield, rating, color, and approximate length
• Origin, destination, panel terminal, power output, opening device, and intermediate junction
• Conduit, tray, sleeve, riser, door loop, power transfer, and concealed route
• Fire-alarm relay or module, access-control input, power-supply release, and supervision
• Elevator, intercom, intrusion, operator, video, or building-system interface mapping

Functional, credential, and fail-behavior testing

Test the complete opening sequence. A successful card read does not prove that the door relocks, the position switch restores, the request-to-exit prevents a forced-door alarm, or the opening responds correctly to loss of power.

• Valid, invalid, expired, disabled, and out-of-schedule credential results
• Reader indication, unlock time, relock, DPS transition, forced-open, and held-open behavior
• Request-to-exit operation, free egress, operator sequence, and nuisance-alarm prevention
• Fail-safe or fail-secure behavior during power loss and backup-power operation
• Fire-alarm or emergency release where applicable and coordinated with responsible parties
• Technician, date, witness, expected result, actual result, deficiency, and retest

Deficiencies, photos, as-builts, and software handoff

Closeout should reconcile the physical opening, software name, controller points, panel terminations, cable labels, door schedule, and drawings. Corrected deficiencies should retain their original condition and final retest evidence.

The handoff record should identify configuration backups, licenses, administrator custody, training, spare credentials, keys, manuals, warranties, and unresolved exceptions without exposing active passwords in general files.

• Deficiency ID, affected door, impact, owner, correction, completion date, and retest
• Door overview, reader, lock, REX, DPS, panel, power, label, and termination photos
• Final door schedule, panel maps, point assignments, cable records, and network details
• Database or configuration backup, software version, license, and secure access handoff
• Technician, project-manager, customer, and required interface witness sign-off
• Final revision, open exception, delivery method, and customer receipt confirmation