What Is a Device Schedule? (And Why Every Security Install Needs One)

A marked-up floor plan tells you where every device goes. But a plan alone doesn't carry the detail a tech needs at the device: the model, the IP address, the mount height, the notes. That's the device schedule: a numbered table that pairs with the plan. The plan shows camera C4 on the wall; the schedule row for C4 tells the tech it's a 4MP dome at 10 ft, on the east wall, with these notes.

A useful schedule has a row per device with columns like:

• Label / ID: C1, CR2, SD3, matching the badge on the plan.
• Type: dome camera, card reader, smoke detector.
• Location: "main lobby, above east entrance."
• Model: the specific part number being installed.
• Mount: height and surface (ceiling, wall, pole).
• Status: planned, wired, installed, tested, approved.
• Page: which floor or plan page the device is on.

For access-controlled doors, the schedule groups the reader, strike, contact, and REX together so the crew sees everything that goes on each opening.

The device schedule is what keeps a multi-device job from turning into guesswork:

• For the install crew: a tech finds C4 on the plan, looks up its row, and knows exactly what to mount and where, without calling you.
• For the customer: it's a clear inventory of what they're getting, attached to the proposal.
• For closeout: as-built documentation of what was actually installed, where, and its final status.

The old way is to count icons on a plan and type them into Excel by hand, which is slow and wrong the moment the plan changes. The better way is to let the schedule come from the plan itself: every device you place in the markup already carries its label, type, location, model, and status, so the schedule generates automatically and exports as a clean appendix page or a CSV. Change a device on the plan and the schedule updates with it.