How to Draft a Feeder Schedule and Coordinate It with a Single-Line Diagram

An electrical feeder schedule organizes distribution-circuit information that would otherwise be scattered across single-line diagrams, plans, equipment schedules, and notes. It gives designers and reviewers a structured place to compare feeder origins, destinations, wiring descriptions, raceways, and related remarks.

The schedule is not a substitute for engineering calculations or a complete single-line diagram. Its value is coordination: each feeder can be identified once and then referenced consistently throughout the drawing set. A well-managed schedule also makes revisions easier because the drafting team can trace a feeder across multiple views without relying on visual guesswork.

What an electrical feeder schedule documents

A feeder schedule is usually presented as a table. Each row represents a feeder or another clearly defined distribution connection. The columns describe that connection using the project team’s approved terminology.

Depending on project scope, useful fields may include:

• Unique feeder identification
• Source equipment
• Destination equipment
• System or service description
• Overcurrent device reference
• Phase and conductor description
• Equipment grounding conductor information
• Raceway or cable type
• Parallel-run designation where applicable
• Routing or installation notes
• Drawing or detail references
• Revision status or coordination comments

Not every project needs every field. The table should reflect the information required to understand and coordinate the design, not become a storage location for unrelated specifications.

Feeder schedule versus panel schedule

Although the names sound similar, feeder schedules and panel schedules serve different documentation purposes.

A feeder may appear as a labeled line on the single-line diagram, connect to equipment represented on a floor plan, and terminate at a panel that has its own schedule. The feeder ID provides the common reference among those drawing elements.

Start with a stable feeder identification system

Assigning IDs before building the schedule reduces ambiguity. A useful ID must remain unique even when two feeders have similar destinations or wiring descriptions. It should also be short enough to fit beside single-line graphics without crowding the diagram.

Feeder IDs may follow equipment relationships, system groupings, sequence-based naming, or another office convention. Whichever approach is chosen, apply it consistently. Avoid using a conductor description as the ID because conductor or raceway information may change during design.

The ID should appear in the same form wherever the feeder is referenced:

• Beside the corresponding line on the single-line diagram
• In the feeder schedule row
• At relevant plan callouts or home-run notes
• In details that apply to that specific feeder
• In calculation or coordination records when the project workflow supports cross-referencing

Build the schedule from system relationships

Record the source and destination separately

Source and destination are among the most important columns. Separate fields are clearer than a combined description because they can be checked independently.

Use equipment tags rather than informal location phrases. For example, a source should reference the same switchboard, panel, transformer, generator, or other equipment tag shown on the diagram. The destination should match the receiving equipment tag exactly. If an equipment tag changes, both the diagram and the schedule need coordinated updates.

Separate identification from technical description

Keep the feeder ID in its own column and place wiring information in dedicated fields. This allows a feeder to retain its identity while technical data develops. It also makes sorting, auditing, and schedule extraction more reliable.

Where conductor details are displayed, use a consistent sequence established by the project team. Do not mix several description formats within one table. Abbreviations should be defined in the drawing legend or notes, particularly when they could be interpreted in more than one way.

Use notes for exceptions, not basic data

A remarks column is useful for conditions that do not fit the standard fields, such as a special routing reference or coordination requirement. It should not become the main location for source, destination, or wiring information.

If the same note applies to many feeders, place it in general schedule notes and reference it only where necessary. Repeating long text in multiple rows makes the schedule difficult to scan and increases the chance of inconsistent edits.

Coordinate the schedule with the single-line diagram

The diagram and schedule should be treated as two views of the same distribution model. The diagram explains connectivity; the schedule provides structured detail. Coordination requires more than confirming that the feeder ID appears in both places.

For each scheduled feeder, verify the following relationships:

• The source equipment exists on the single-line diagram.
• The destination equipment exists and is connected to the intended source.
• The feeder ID is unique and readable.
• The system description agrees with the connected equipment.
• Protective-device references do not conflict with the diagram or associated equipment schedule.
• Any parallel or multi-run representation is interpreted consistently.
• Normal, emergency, standby, and other distribution paths are not inadvertently mixed.
• Notes and detail references point to existing drawing content.

Direction also matters. Even if a distribution line is graphically simple, the schedule should make the source-to-load relationship unmistakable. This becomes especially important where transfer equipment, multiple sources, or alternate operating paths are represented.

Drafting the table in CAD

Choose a maintainable table method

A feeder schedule can be created with a native CAD table, linked project data, or carefully controlled linework and text. The best method is the one the project team can revise reliably. A visually polished table is not useful if editing it breaks alignment or creates duplicate information.

Native table objects can help preserve row and column structure. Data-linked workflows may reduce repetitive entry, but they require clear ownership and update procedures. If ordinary text and lines are used, establish fixed text styles, alignment rules, and row spacing so revisions remain orderly.

Control column widths by content

Do not give every column equal width. IDs and compact references generally need less room than conductor descriptions or remarks. Column headings may be wrapped if doing so produces a more readable table.

Test the schedule at its intended plotted presentation, not only at a comfortable on-screen zoom level. Confirm that headers, grid lines, row text, and note references remain distinguishable from one another.

Keep schedule graphics on controlled layers

Place schedule text, borders, headers, and related references on layers that follow the project’s CAD standards. Separating these elements can make plotting and global revisions easier. However, excessive layer subdivision may complicate editing, so use only distinctions that support the actual workflow.

Managing revisions without losing coordination

Feeder changes often affect several drawings. Changing only the schedule can leave the single-line diagram, equipment plan, or associated schedule out of date. A revision workflow should therefore begin with a feeder-centered impact check.

When a feeder is added, removed, or modified:

• Locate every appearance of its ID.
• Check the source and destination equipment tags.
• Review the single-line connection.
• Review associated plan callouts and equipment schedules.
• Confirm whether notes, details, or calculations require updates.
• Remove obsolete references rather than leaving them hidden or crossed out in working files.
• Record the change according to the project’s revision procedure.

If schedule data comes from an external source, identify whether CAD or the external file is authoritative. Uncontrolled editing in both locations can cause one version to overwrite correct changes from the other.

Common drafting problems

Duplicate feeder IDs

Duplicate IDs make cross-references unreliable. Search the complete drawing set or source data before assigning a new identifier, especially when copying diagram branches or schedule rows.

Equipment tags that do not match

Small differences in punctuation, spacing, or abbreviations can make one piece of equipment appear to be several different items. Use the project’s approved tag format and avoid manually retyping tags when a controlled data workflow is available.

Too much information beside diagram lines

Placing complete feeder descriptions directly on a single-line diagram can crowd equipment symbols and obscure connectivity. A compact feeder ID linked to a schedule often produces a clearer diagram, while selected essential information may remain on the line where the project convention requires it.

Unexplained abbreviations

Abbreviations save space only when readers can interpret them. Define project-specific shorthand and avoid using the same abbreviation for different concepts.

Rows that no longer connect to anything

Copied or abandoned rows can survive long after a diagram revision. Every issued schedule row should correspond to an intentional distribution connection or be clearly identified for its documented purpose.

Final feeder schedule quality-control checklist

• Every feeder ID is unique.
• Each row has an identifiable source and destination.
• Equipment tags match the plans, diagrams, and schedules.
• Feeder descriptions follow one consistent format.
• Abbreviations are defined.
• Schedule notes are concise and correctly referenced.
• No unexplained blank fields remain.
• Diagram connectivity agrees with the tabulated relationship.
• Text and grid lines are readable at the intended plotted presentation.
• Obsolete rows and references have been removed.
• Technical values have been checked by the responsible project professional.

A coordinated schedule is a navigation tool

The strongest electrical feeder schedule does more than compress technical information into rows and columns. It helps readers move confidently between the distribution diagram, equipment plans, panel information, and supporting details.

CAD blocks and schedule templates can improve consistency, but they do not validate design data. Feeder sizes, protective-device information, system arrangements, and installation descriptions must be developed and verified for the specific project. When stable IDs, structured fields, and disciplined revision checks are used together, the feeder schedule becomes a practical coordination tool rather than another isolated table.