Low-Voltage & Wiring
Building a Structured Cabling Point Schedule
A point schedule is the single document that turns a floor plan into a buildable job. Get it right and the installer knows exactly what to pull and where. Get it loose and you are paying for re-work on site. Here is how to build one that survives contact with the real world.
What a point schedule actually is
A point schedule lists every outlet / device in the job: where it lives, what it is, what it needs, and how it connects back to the room / IDF / main distribution. It is the bridge between the architect's plan and the installer's cable drum. It answers one question above all: how many points of which type go where.
Step 1 — Walk the plan, count the types
Start from the floor plan and count points by type, room by room. The usual families:
| Type | What it covers |
|---|---|
| Data (network) | RJ45 outlets for computers, phones, printers, access points |
| Voice | Phone outlets — separate line, or data + voice on one structured outlet |
| Security | CCTV cameras, door access, intrusion, intercom |
| AV | HDMI / USB / AV outlets, wall plates, projector feeds |
| Control / automation | Lighting control, HVAC sensors, occupancy, IoT devices |
Do not just count sockets — count the type at each location. A conference room may look like "6 points" but is 2 data, 2 AV, 1 camera, 1 door access, and each connects differently.
Step 2 — Define the point's identity
Every point gets a stable identifier and enough context to build from:
- Point ID — a scheme like
F1-D-01(floor, type, sequence) that survives to labelling on the faceplate. - Room / location — where it physically lives, matching the plan.
- Type & service — what it is and what it carries.
- Backbone route — which room / IDF / rack it home-runs to, and the run distance.
- Remarks — special mounting, fire-rating, conduit, or termination notes.
The identifier is the part people skip, and the part that saves the most time later. "Third outlet on the north wall of Room 214" becomes label F2-D-08 and the installer never guesses again.
Step 3 — Add the quantities that drive material
From the per-point schedule, roll up the numbers that buy cable, faceplates, patch panels and labels:
Sum by type and by run destination. This is where the schedule earns its keep: a schedule that counts points but not cable length produces a site that runs out of cable on the last floor.
Where the spreadsheet breaks down
For a handful of points in one room, a spreadsheet is fine. For a whole floor or a multi-storey building, three things quietly break:
- Consistency — rooms get renamed, points get moved, and the "final" sheet is now three conflicting copies.
- Roll-ups — material counts, run lengths and type totals have to be recomputed every time one cell changes.
- Connectivity — the schedule is usually drawn from a plan, and re-drawing it by hand in a grid loses the spatial sense.
The fix is not a bigger spreadsheet; it is keeping the point list structured — one field per attribute, a stable ID, and roll-ups that recompute automatically.
Best-practice checklist
- Every point has a unique, buildable ID.
- Type and service are explicit, not implied.
- Backbone destination and run length are on the row.
- Material quantities roll up automatically from the schedule.
- Changes update totals in one pass, not by hand.
LowVoltStudio keeps the point schedule structured
Point lists with IDs, types, backbone runs and automatic roll-ups, plus room / UPS and subsystem planning — fully offline, built for medium and large low-voltage jobs.