Door Schedule Template for Access Control

What is a door schedule template?

One row per door: a door schedule is the tabular index of every access-controlled opening on a site.

Where a per-door wiring drawing shows how a single opening's devices land on the controller, the schedule shows all of them at once (so a service tech can scan for the door that never got its power source recorded); the two are matched views of the same facts, so see door controller wiring documentation for the drawing side and treat the schedule as its index.

You fill instead of format, because a template gives those columns a fixed shape. The value is discipline rather than decoration: every opening documented the same way, every field either recorded from the wiring or copied from what a professional specified.

What goes in each column?

Two kinds, and the columns split cleanly between them: facts you read straight off the wiring (door ID, controller and port, power), and values a qualified professional specifies that you only transcribe (the hardware set at the door).

Keeping that line bright is the whole trick to filling the schedule honestly.

You do not have to build this by hand. The free door-schedule CSV carries exactly these columns, so you can open it and start entering openings. Every field is either a fact you can point at on the wiring or a value someone qualified handed you.

How do you fill in the door schedule?

Fill it one opening at a time, working from the wiring and the installer's spec. Not from memory. The order below keeps the facts you own separate from the values you are only transcribing.

1. Give the opening a door ID that matches the floor plan and the architectural door number (Door 101, not "front door"), and record its location.
2. Record the controller and the exact port each device lands on, straight off the wiring drawing.
3. Transcribe the reader, lock hardware, REX, and DPS as specified by the licensed installer. You are copying a decision, not making one.
4. Record the power source: which supply and circuit, or the PoE switch port for a networked controller.
5. Put any professional-flagged value (fail-safe versus fail-secure, egress hardware) in Notes as a recorded value, attributed to whoever specified it.
6. Cross-check the finished row against the per-door drawing so every device appears on both, and every row points at a drawn opening.

Which fields do you own, and which belong to the AHJ?

Two columns in the table above carry a spec: Lock Hardware and REX Device (and any operation note that rides in Notes). Those are the values you are only ever recording. Your job is to make the record complete and unambiguous. Choosing what goes in it is not your job.

If you find yourself deciding a hardware value from a search result, stop: that is exactly the boundary this schedule exists to respect.

How do you keep the schedule in sync with the wiring?

Two views of one dataset: the schedule and the per-door drawing drift the moment you maintain them separately.

The cheapest way to avoid drift is to draw the door as devices with real ports, then let the row inherit those facts: in a port-aware tool you place the controller, reader, lock, DPS and REX as devices (custom devices if they are not in the library) and connect each to a real controller port; see adding devices and library and port-to-port documentation for the mechanics.

Whichever tool you use, the rule is the same: a device on the drawing is a fact in the row, and a row points at a drawn opening. When a reader gets swapped or a controller port moves, change it in one place and reconcile the other, then re-issue both with a fresh version stamp so the crew is never working from a stale copy.

Loose file names are not a version scheme; see versioning your documentation.

Where do power and the network land on the schedule?

Half of access-control troubleshooting is really a power question, which is why Power Source earns its own column rather than a footnote.

Record which supply and circuit feeds each opening, and which openings share a supply, so a single dead PSU maps instantly to the doors it takes down.

Networked controllers are also network hosts, and they do not stop existing just because they live on the door schedule. Give a managed panel a row on your IP schedule with an address, a VLAN and its switch port.

If it draws PoE from that switch, count it in your PoE budget like any other powered device, so it is a planned load instead of the reason a switch trips its power limit.

How should you name doors so the schedule lasts?

Naming is what keeps the drawing, the schedule, and the label on the cable all pointing at the same opening.

Anchor every door ID to the architectural door number so it never argues with the floor plan, then name each device by its door and role.

• Opening: Door 101, keyed to the architectural door number, never a nickname that changes with tenants.
• Devices: role plus door number, so RDR-101 is the reader, LCK-101 the lock, DPS-101 and REX-101 the switches, each feeding a controller port like ACP-2, port 4.
• Cables: a unique, permanent ID printed on both ends, matching the diagram and the schedule row.

Frequently asked questions

Is a door schedule template a wiring or code guide?

No. It is a documentation format: a place to record an access-controlled opening so the paperwork matches the real door. Hardware selection, egress, fail-safe versus fail-secure operation, fire-alarm interface, and all code compliance are the licensed installer's and the AHJ's decisions. Use the template to capture what they specify, not to make those calls yourself.

What columns should a door schedule have?

One row per opening with door ID and location, the controller and the exact port each device uses, reader type, lock hardware, REX device, door position switch (DPS), and power source, plus a notes field for professional-flagged values like fail-safe versus fail-secure; the free CSV ships with exactly these columns.

Where do I get a free door schedule template?

There is a free door-schedule CSV on the templates page with the columns above. No email gate. Open it, add one row per opening, then fill each field from the wiring or from the installer's spec.

How do I record fail-safe versus fail-secure on the schedule?

As a single value in the notes field, using what the licensed installer or AHJ specified for that opening. Attribute it to them. The schedule gives the value a consistent home; it is never the place to decide which behavior a door should have.

Do networked door controllers belong on my other schedules too?

Yes. A managed controller is a network host, so it also gets an IP schedule row with address, VLAN and switch port. If it is PoE powered, add a line in your PoE budget. Documenting it beside your AV and network gear keeps one source of truth instead of a mystery device on the switch.

Grab the free template

Open CSV templates for IP schedules, cable schedules, port maps, and more, no email gate.

Browse free templates · Or generate it from a diagram