Home › Guides › AutoCAD Schematics & Panels

AutoCAD Electrical Schematics, Panels and Terminal Strips

A single simple schematic is a good start, but real projects are sets of drawings that must agree with each other: multi-wire power schematics, control schematics spread over several sheets, panel layouts showing the physical enclosure, and terminal plans showing exactly which wire lands where. This intermediate guide explains how those drawings relate, how to build multi-wire schematics properly, how to lay out a panel, and how to handle terminal strips and wire numbering across a whole project. It builds directly on our AutoCAD Electrical basics guide, so if projects, wires and component tagging are new to you, start there first.

As with all our software guides, this is generic educational material from standard drafting practice. It does not reproduce any software manual, screenshot or proprietary content, and hands-on practice requires a licensed copy of the software, an authorised trial, or an academic licence from the vendor. The habits in this guide — one source of truth for each piece of data, drawings that agree with each other, and layouts a panel builder can actually build from — are what separate a set of drawings that looks professional from a set that works professionally.

From one drawing to a drawing set

A real panel project typically contains several drawing types, and each has a distinct job. Power schematics show the distribution: incomers, busbars, feeders and protection, usually as multi-wire drawings where each phase and neutral is drawn separately. Control schematics show the logic: push buttons, relays, contactors and interlocks, usually as ladder diagrams. Panel layouts show the physical enclosure: the mounting plate, the devices mounted on it, and the wiring ducts. Terminal plans show the terminal strips and every wire connected to them. And general arrangement or cover drawings show the enclosure itself, its doors, and its external features.

The project manager is what holds this set together. Drawings are ordered, named and described consistently, and project-wide commands — renumbering, retagging, cross-reference updates, and reports — run across the whole set rather than one drawing at a time. When you add a drawing, add it to the project with a proper name and description immediately, and keep the drawing order logical: power first, then control in operating order, then panel and terminal drawings. A drawing set that is ordered like the story of the panel is a drawing set that can be checked, built and maintained.

Multi-wire schematics done properly

Single-line diagrams are useful for showing a system at a glance, but panel wiring needs multi-wire schematics, where each conductor is drawn individually. The discipline here is spacing and alignment: phases kept in consistent order, neutrals and earths clearly distinguished, and wire runs kept parallel and tidy so that a reader can follow one conductor through a busy drawing without losing it. Use the software's multi-wire tools rather than drawing parallel lines by hand, because the tools keep the wires connected to the components they join and keep wire numbers consistent across the run.

Cross-references become essential at this scale. A contactor coil on a control drawing and its power contacts on a power drawing are the same device, and the software's parent-child cross-referencing is what links them. When a reader sees a contact on a power schematic, the cross-reference tells them exactly which drawing and rung hold the coil that drives it, and vice versa. Check cross-references as part of your drawing review: a contact with no cross-reference, or a cross-reference pointing at the wrong drawing, is a wiring error waiting to happen, even if both drawings look correct in isolation.

Panel layouts: from schematic to enclosure

A panel layout translates the schematic into physical reality. Start from the schematic's bill of materials: every device that must be mounted, its physical size, and its catalogue footprint. Place the larger and heat-producing devices first — contactors, transformers, power supplies — with space around them for cooling and for hands to work, then fill in the smaller devices, keeping related devices together and keeping terminals accessible. Leave room for wiring ducts and for the terminal strips themselves, which beginners routinely forget until there is nowhere left to put them.

Use the software's panel tools to insert footprints linked to the schematic components, rather than drawing rectangles by hand, because linked footprints carry the component data with them: the tag, the catalogue number, and the connection information. That link is what makes panel reports accurate and what lets a change on the schematic flow through to the layout. After placing footprints, check clearances, door swing, cable entry points, and whether a technician can actually reach every terminal with a screwdriver. A layout that is electrically complete but physically unbuildable is not a finished layout.

Terminal strips and wire numbering

Terminal strips are where the schematic meets the field, and they deserve the same care as the schematic itself. Each terminal is a connection point with a number, and the terminal plan shows which wires land on each terminal, which side of the terminal they come from, and what they connect to on the other side. Build terminal strips from the schematic connections using the software's terminal tools, so that the terminal plan is generated from the same data as the schematic rather than typed separately. When a wire changes on the schematic, the terminal plan should change with it.

Wire numbering across a project needs a scheme decided up front and applied everywhere: for example, numbers that identify the circuit and the wire within it, with consistent formats for power, control and signal wires. The software can assign numbers automatically according to the project format, and it can renumber a whole project when the scheme changes — but only for wires drawn with the electrical wire tools. Wires drawn as plain lines, or numbers typed as text, sit outside the system and will be wrong the first time anything changes. Decide the scheme, document it in the project, and never hand-number a wire that the software can number for you.

Keeping a drawing set consistent

Consistency checks are a regular habit, not a final step. Run project-wide error checks after every significant change: duplicate tags, missing cross-references, unconnected wires, components on the layout with no schematic parent, and schematic components with no layout footprint. Generate the bill of materials and compare it with what you expect to buy and install. Generate the wire list and check it against the terminal plan. Each of these reports is a different view of the same project data, and disagreements between them are findings, not paperwork.

Revisions need the same discipline. When a drawing changes, update its revision, record what changed and why, and re-run the project checks and reports so that every document in the set reflects the same revision. A panel built from a mixture of revisions — a schematic at revision C, a layout at revision B, a terminal plan at revision A — is a panel built from three different designs, and the errors that follow are entirely predictable. Version control for drawings is not bureaucracy; it is how a team knows which design is the real one.

Common intermediate mistakes

The most common intermediate mistake is drawing panel footprints by hand instead of linking them to schematic components, which breaks the data link and makes panel reports unreliable. The second is building terminal strips manually instead of generating them from schematic connections, which guarantees that the terminal plan and the schematic will drift apart. The third is inventing wire numbering on the fly instead of following the project scheme, which produces a wire list that nobody can trace. All three share the same root cause: bypassing the electrical tools because plain drafting felt faster in the moment.

The other common mistake is scale: trying to fit too much onto one drawing. A control schematic that spans five sheets because it was drawn too large, or a panel layout crammed onto one sheet at an unreadable scale, both fail at their basic job of communication. Split drawings at logical boundaries — one function per sheet, one panel section per layout — and let cross-references carry the reader between sheets. Readability is a design requirement, not a luxury.

What to learn next

From here, move on to reports, title blocks, PLC I/O drawings and automation, which turn a consistent drawing set into the full document package a project needs. For the logic those drawings describe, see our PLC basics and advanced ladder logic guides, and for the power systems behind them, our ETAP load flow and short-circuit and protection guides. Our AI tools for engineers page covers documentation workflows, while the drafting discipline here remains human work.

Frequently asked questions