28/10/2026
DESIGN DRAWINGS, SHOP DRAWINGS, AND AS-BUILT DRAWINGS:
WHAT'S THE DIFFERENCE?
In building construction and ELV projects, the terms design drawings, shop drawings, and as-built drawings are often used interchangeably.
They should not be.
Each serves a different purpose, appears at a different stage of the project, and carries a different level of responsibility.
A simple way to remember the difference is:
DESIGN DRAWINGS show what should be built.
SHOP DRAWINGS show how it will be installed.
AS-BUILT DRAWINGS show what was actually built.
Understanding the distinction is important for building owners, contractors, systems integrators, ECEs, PECEs, architects, consultants, and technicians because many coordination problems start when one type of drawing is treated as if it were another.
DESIGN DRAWINGS: THE ENGINEERING INTENT
Design drawings are prepared during the planning and design stage.
Their purpose is to communicate the intended system architecture, device locations, major routes, equipment requirements, interfaces, and technical criteria needed to construct the project.
For ELV systems, design drawings may include:
- CCTV camera locations and coverage intent;
- FDAS device layouts and zoning or loop arrangements;
- structured cabling outlets and telecommunications rooms;
- Wi-Fi access point locations;
- access control devices and door interfaces;
- PA/BGM speakers and equipment locations;
- fiber backbone routes;
- riser diagrams and single-line diagrams;
- system schematics;
- equipment schedules;
- technical notes and specifications; and
- design calculations where applicable.
The design drawing establishes the engineering intent.
It answers questions such as:
What systems are required?
Where should the major devices be located?
How are the systems interconnected?
What performance or technical requirements must be achieved?
A good design drawing gives the contractor enough information to understand the project requirements while still allowing proper construction coordination in the field.
DESIGN DRAWINGS ARE NOT ALWAYS INSTALLATION-LEVEL DRAWINGS
A common misconception is that every conduit bend, cable support, rack elevation, junction point, mounting bracket, and exact routing detail must already appear in the original design drawing.
That is not always practical.
During design, many actual field conditions may not yet be visible.
Ceiling spaces may later contain air-conditioning ducts, sprinkler pipes, lighting fixtures, structural members, electrical trays, plumbing, and other systems.
The design professional may define the intended route or pathway, but the contractor may still need to develop more detailed installation drawings.
That is where shop drawings become important.
SHOP DRAWINGS: FROM DESIGN INTENT TO ACTUAL INSTALLATION
Shop drawings are typically prepared during the construction stage by the contractor, systems integrator, fabricator, supplier, or installation team.
Their purpose is to translate the design intent into coordinated installation details.
They answer a different question:
How exactly will this system be installed in the actual building?
For ELV systems, shop drawings may include:
- exact cable tray or conduit routing;
- coordinated ceiling device locations;
- detailed equipment room layouts;
- rack elevations;
- patch panel arrangements;
- cable numbering;
- equipment mounting details;
- door access control wiring details;
- fiber termination arrangements;
- detailed riser coordination;
- conduit and pull box locations;
- typical installation details;
- equipment dimensions and clearances; and
- interfaces with architectural, electrical, mechanical, fire protection, and other systems.
A shop drawing should not simply redraw the design plan.
Its value is in coordination and constructability.
It should reflect actual equipment dimensions, actual mounting conditions, actual pathways, actual interfaces, and practical installation requirements.
SHOP DRAWINGS SHOULD NOT QUIETLY REDESIGN THE PROJECT
This is an important point.
A shop drawing can develop installation details, but it should not silently change the engineering intent.
For example:
If a CCTV camera is relocated because of an obstruction, the revised location should still provide the required coverage.
If an FDAS detector is moved, the revised location should still satisfy the applicable detection and spacing requirements.
If a Wi-Fi access point is transferred to another location, wireless coverage should still be acceptable.
If an IDF rack is relocated, cable distances, backbone routes, power, grounding, ventilation, security, and accessibility may be affected.
If the proposed shop drawing introduces a significant change in system capacity, architecture, performance, or design basis, that change should be properly reviewed rather than treated as a simple drafting revision.
A shop drawing should develop the design.
It should not bypass it.
WHO PREPARES AND WHO REVIEWS SHOP DRAWINGS?
In many projects, shop drawings are prepared by the contractor or systems integrator because they are responsible for the detailed installation.
The reviewing engineer or consultant then checks whether the proposed details remain consistent with the approved design, specifications, project requirements, and coordinated field conditions.
Approval of a shop drawing should not be interpreted as transferring the contractor's responsibility for installation accuracy, dimensions, fabrication, workmanship, and site verification to the reviewer.
Each party still has its own role.
The contractor is responsible for properly developing and executing the installation.
The reviewing professional is concerned with whether the submitted details remain consistent with the engineering intent and technical requirements.
AS-BUILT DRAWINGS: THE FINAL RECORD OF WHAT WAS INSTALLED
Construction rarely ends exactly as originally drawn.
Devices move.
Cable routes change.
Equipment models are substituted.
Rack locations are adjusted.
Additional devices may be installed.
Some conduits are rerouted.
Field conditions force coordination changes.
Those changes must not disappear after turnover.
As-built drawings are intended to record the final installed condition of the project.
They answer the question:
What was actually built?
For an ELV project, a good as-built drawing may show:
- final CCTV camera locations;
- actual FDAS device locations;
- final cable tray, conduit, and backbone routes;
- actual telecommunications room and rack locations;
- final fiber routes and termination points;
- device and cable identification;
- revised risers;
- actual equipment installed;
- access control door locations;
- final network outlet locations;
- major approved field changes; and
- other information needed to understand the completed installation.
The usefulness of an as-built plan depends on its accuracy.
An old design drawing stamped "AS-BUILT" without incorporating actual field changes is not a meaningful record of the completed project.
WHY AS-BUILT DRAWINGS MATTER
Once the contractor leaves the site, the as-built documents may become some of the most important technical records available to the building owner.
They are useful for:
- maintenance;
- troubleshooting;
- future expansion;
- equipment replacement;
- renovation;
- system upgrading;
- fault isolation;
- asset management;
- future design work; and
- emergency response.
Imagine troubleshooting a fiber backbone several years later.
If the as-built drawing accurately shows where the fiber runs, where it terminates, and how the network is arranged, troubleshooting becomes easier.
If the drawing does not match the building, technicians may spend hours tracing cables that were relocated years earlier but never documented.
The value of an accurate as-built drawing often becomes obvious only after the original construction team is gone.
A PRACTICAL ELV EXAMPLE
Consider a CCTV system for a commercial building.
DESIGN DRAWING
The design plan identifies 32 cameras, their intended locations, the NVR, network switches, equipment room, and backbone arrangement.
SHOP DRAWING
During construction, the systems integrator discovers that one camera location is obstructed by an architectural feature.
The shop drawing proposes moving the camera approximately two meters, shows the actual cable pathway, identifies the switch port, and coordinates the mounting detail.
The change is reviewed to confirm that the intended surveillance coverage remains acceptable.
AS-BUILT DRAWING
After construction, the final drawing records the actual camera location, final cable route, final device identification, rack termination, and any other approved changes.
The three drawings are related.
But they are not the same document.
ANOTHER EXAMPLE: STRUCTURED CABLING
Design drawings may indicate the required data outlets, IDF/MDF rooms, backbone routes, and cabling category.
Shop drawings may develop the exact cable tray routing, rack layout, patch panel arrangement, outlet numbering, conduit sizes, and detailed pathways.
As-built drawings should then reflect the final outlet locations, cable identifiers, rack assignments, backbone routes, and installed telecommunications spaces.
The sequence creates a traceable technical record:
DESIGN INTENT → INSTALLATION DETAIL → FINAL INSTALLED CONDITION
THE IMPORTANCE OF REVISION CONTROL
One of the easiest ways to create confusion is to have multiple drawing versions circulating on site.
A contractor may be using Revision 1.
The consultant may already have issued Revision 3.
Another subcontractor may still be referring to the tender drawing.
This can result in installation errors and rework.
Every project should have clear document control.
Drawings should identify items such as:
- drawing number;
- drawing title;
- revision number or revision letter;
- revision date;
- description of revision;
- approval or review status; and
- issue purpose, such as FOR REVIEW, FOR APPROVAL, FOR CONSTRUCTION, or AS-BUILT.
Good document control is not merely clerical work.
It is part of maintaining technical traceability.
RED-LINE DRAWINGS HELP CREATE ACCURATE AS-BUILTS
During construction, site personnel often mark approved changes directly on working drawings.
These are sometimes called red-line drawings or mark-up drawings.
They can become an important source for preparing the final as-built set.
For this reason, changes should be recorded while the work is still accessible.
It is much easier to document a cable route before the ceiling is closed than to reconstruct that route several months later.
A disciplined contractor updates field mark-ups continuously rather than trying to remember all changes at the end of the project.
DESIGN, SHOP, AND AS-BUILT DRAWINGS SHOULD FORM A CONTINUOUS STORY
These documents should not exist as three unrelated drawing sets.
They should form a logical progression.
The design drawings establish the engineering intent.
The shop drawings develop coordinated installation details.
The as-built drawings document the completed installation.
When the process works properly, a reviewer should be able to understand how the project moved from the original design to the final built condition.
That traceability becomes especially valuable when major changes occur.
THE CONTRACTOR'S DRAWING IS NOT AUTOMATICALLY AN ENGINEERING DESIGN
Another important distinction is professional responsibility.
Producing a drawing using AutoCAD, Revit, or another drafting platform does not automatically make that drawing an engineering design.
Drafting and engineering are related but different activities.
A technician or drafter may prepare highly detailed shop drawings based on engineering instructions and project requirements.
However, technical decisions that involve engineering judgment, system design, capacity, safety, regulatory compliance, or professional responsibility must remain within the proper professional scope of practice.
Software proficiency does not replace engineering competence.
Similarly, a professional seal should not be treated as something that converts an otherwise unverified drawing into a professional design after the fact.
The professional who assumes responsibility for technical documents should have appropriate involvement in their preparation, review, supervision, or professional evaluation as required by applicable laws and regulations.
WHAT SHOULD PROJECT OWNERS ASK FOR?
For significant ELV projects, owners should not think only about the original design plans.
The project closeout requirements should also identify the documents needed at turnover.
Depending on the project, these may include:
- approved as-built drawings;
- equipment schedules;
- test reports;
- commissioning records;
- cable test results;
- fiber test results;
- device addressing or labeling records;
- equipment manuals;
- warranties;
- configuration backups where appropriate;
- training records; and
- other required turnover documentation.
A completed installation without useful records may become difficult and expensive to operate later.
THE SIMPLEST WAY TO REMEMBER THE DIFFERENCE
DESIGN DRAWING
What should be built?
SHOP DRAWING
How will it be installed?
AS-BUILT DRAWING
What was actually built?
All three can be important.
But they represent different stages of the project and should not be treated as interchangeable.
FROM PAPER TO PROJECT HISTORY
A drawing is more than a picture of devices and lines.
At the design stage, it communicates engineering intent.
During construction, it becomes a coordination tool.
At turnover, it becomes a permanent technical record.
That is why proper documentation should continue from the first design drawing until the final as-built plan.
In ELV work, good engineering is not only about designing the system correctly.
It is also about ensuring that the installed system can be understood, tested, maintained, expanded, and traced long after construction is finished.
DESIGN DRAWINGS SHOW WHAT SHOULD BE BUILT.
SHOP DRAWINGS SHOW HOW IT WILL BE INSTALLED.
AS-BUILT DRAWINGS SHOW WHAT WAS ACTUALLY BUILT.
When all three are properly prepared and coordinated, the project becomes easier to construct today and much easier to understand tomorrow.
DISCLAIMER
This article is intended for general educational and professional discussion. Specific drawing requirements, preparation responsibilities, approval processes, signing and sealing requirements, and project closeout documents may vary depending on the contract, applicable codes, permitting authority, project delivery method, professional scope, and current regulatory requirements.
