Cable schedule · editable CSV · no signup
Control Cable ScheduleTemplate & Field Guide
Trace every automation cable from source equipment through routes, glands, cores and terminals to its destination—and carry installation evidence into handover.
What this document controls
A cable schedule is the controlled register of cable identity, construction, source, destination, route, glands, conductor/core use, terminal references, installation status and testing. For PLC and instrumentation projects it is the bridge between schematics, layout/routing, junction boxes, panel terminal plans, I/O assignments and field commissioning.
File facts
- Format
- CSV / spreadsheet
- Account
- Not required
- Project data upload
- None
- License
- CC BY 4.0
Field dictionary
Columns worth keeping
| Field | Why it exists | Example |
|---|---|---|
| Cable ID | Unique controlled identifier printed on labels and referenced in drawings and tests. | CBL-PT201-01 |
| From / to equipment | Names both physical endpoints so routing and installation scope are unambiguous. | PT-201 → JB-201 |
| From / to terminals | Traces individual landing points and supports point-to-point verification. | PT +/− → TB1:01/02 |
| Cable type | Controls construction, conductor size/count, pair/triad, shield, armour and rating. | 1P x 1.5 mm² OS |
| Used cores / spares | Maps the functional assignment and prevents undocumented reuse. | Pair 1 used; pair 2 spare |
| Signal / service | Separates analog, discrete, network, power and special circuits for design/segregation. | 4–20 mA AI |
| Route / tray | Connects the cable to layouts, tray fill, segregation and installation work packs. | TR-2A → RISER-04 |
| Length | Supports drum planning, voltage/burden calculations and as-built records. | 86 m installed |
| Gland / entry | Controls enclosure interface, armour bonding and hazardous-area requirements. | M20 Ex e, both ends |
| Shield / earth | Records the project-specific termination rather than relying on a universal rule. | Drain bonded at PLC cabinet |
| Drawing reference | Links the row to schematic, loop diagram, termination and routing evidence. | LD-PT201 rev B |
| Test / status | Carries continuity, insulation, termination and loop-readiness status. | Continuity pass; loop open |
Workflow
Build it in the right order
- 01
Define the schedule boundary
State whether the register covers control, instrumentation, industrial Ethernet, safety, panel-internal and power cables. Avoid hidden package boundaries.
- 02
Seed endpoints from drawings and registers
Use I/O lists, instrument indexes, motor lists, network architecture and panel terminal plans to create the first cable records.
- 03
Assign construction and routing
Select cable construction from the approved engineering specification, then coordinate tray, conduit, segregation, glands and length.
- 04
Issue installation work packs
Freeze an approved revision containing cable IDs, endpoints and terminations. Record field redlines against that revision.
- 05
Reconcile and hand over
Capture actual length/route, core use, test results and as-built terminals; resolve temporary cables and abandoned cores before acceptance.
Quality gate
Review before issue
- Cable IDs are unique, physically labelable and consistent with the project naming standard.
- Both equipment endpoints and terminal endpoints are present; “panel to field” is not enough.
- Cable construction comes from the electrical/instrument specification and calculated duty.
- Network cable type, connector and topology are coordinated with the selected industrial protocol.
- Shield and armour terminations are project-specific and consistent with EMC/hazardous-area design.
- Spare cores are identified and safely terminated or insulated according to the project standard.
- Field redlines update the register and affected termination/loop drawings together.
- Continuity and insulation testing use methods appropriate to connected electronic equipment.
Worked record
Worked route: PT-201 to PLC analog input
A complete record exposes every boundary. If PT-201 lands through a junction box and marshalling cabinet, use linked cable segments or explicitly record each intermediate termination—do not hide them in a note.
| Cable ID | From → To | Terminals | Construction | Route | Signal | Status |
|---|---|---|---|---|---|---|
| CBL-PT201-01 | PT-201 → JB-201 | PT +/− → TB1:01/02 | 1P x 1.5 mm² OS | Field conduit C-14 | 4–20 mA | Installed / continuity pass |
| CBL-JB201-01 | JB-201 → PLC-201 | TB1:01/02 → AI-03:07 +/− | 12P x 1.5 mm² IS | TR-2A / RISER-04 | Analog multicore | Terminated / loop check open |
Connect it to the rest of the project
PLC I/O list builder
Connect cable/core records to the exact rack, slot, channel and signal tag.
Open reference →PLC wiring diagrams
Understand digital, analog, relay and specialty I/O circuit patterns.
Open reference →Loop-check procedure
Prove the installed cable as part of the complete field signal path.
Open reference →Frequently asked questions
What is the difference between a cable schedule and a termination schedule?
A cable schedule controls each cable as an asset and route between endpoints. A termination schedule focuses on conductor/core landings at terminals. Projects may combine them, but the combined file must still trace every used core and terminal.
Should Ethernet and fieldbus cables be included?
Include them when they are in the register boundary. Record protocol-specific media, connector, topology and test requirements rather than treating all network cable as generic Ethernet.
Do I record estimated or actual cable length?
Design revisions often carry estimated length for procurement and routing. The as-built revision should record actual installed length where the project requires it, while preserving the revision/change trail.
Can this CSV be used as an Excel template?
Yes. Import it into Excel, Google Sheets or LibreOffice and add project-specific validation lists, document-control fields and protected columns. Do not rely on color alone to communicate status.
Share or cite this template
Link to this landing page so readers receive the field definitions, use boundary and future revisions with the file.
https://plcprogramming.io/tools/cable-schedule-template