Linetype Standards by Discipline: Architecture, MEP, Civil, Survey, and Utilities
Linetype meaning changes by discipline. An overhead architectural element, an underground civil utility, and an existing MEP service may all use dashed graphics, yet they must remain distinguishable when several consultant drawings are combined.
The standard must therefore define both the native discipline display and the rules used when drawings are attached as Xrefs at different scales.
Why Linetype Requirements Differ by Discipline
Each discipline communicates different states: visible versus hidden, existing versus proposed, above versus below, ownership, material, system, or legal boundary. A universal list without context produces collisions. Establish meaning, layer, scale, and coordination behavior for every approved pattern.
Shared Principles Across All Disciplines
Clear Visual Hierarchy
Primary design information must remain stronger than backgrounds. Use pattern, lineweight, and color together without assigning two meanings to one appearance.
Consistent Layer Assignment
Assign linetypes by approved layers so host drawings can control consultant backgrounds predictably.
Readability at Plotting Scale
Test the pattern at the scale of the coordinated sheet, not only in its authoring model.
Project-Specific Requirements
Client and authority standards can supersede company defaults. Record those exceptions in the project CAD execution plan.
Coordination Between Host Drawings and Xrefs
Define whether the host may override consultant linetypes, which overrides persist, and how nested Xrefs are handled. Use unique resource names to avoid collisions described in the Xref linetype guide.
Architectural Linetype Standards
Hidden and Overhead Elements
Use distinct patterns for concealed items and objects above the cut plane. Do not let both become the same generic dashed line when they carry different construction meaning.
Demolition and Existing Work
Coordinate linetype with phase color and lineweight. A demolition pattern must remain identifiable in monochrome output.
Property and Setback Lines
Keep legal or planning boundaries visually separate from walls, grids, and civil rights-of-way.
Section and Match Lines
These are annotation systems, often better managed with blocks and labels rather than relying on a decorative LIN definition alone.
Managing Architectural Linetypes in Referenced Consultant Drawings
Host Drawing Scale vs. Xref Scale
A consultant Xref authored for another native scale can become dense or sparse in an architectural 1:100 sheet. Test model, viewport, and Xref scale settings as one coordinated system.
Preserving Layer and Linetype Overrides
Save approved background overrides in the host and document whether reloads may reset them. Never edit a consultant source merely to make one host sheet lighter.
Structural Linetype Standards
Hidden Structural Elements
Differentiate concealed beams, foundations below, and structural items above the view where the project standard requires separate meanings.
Centerlines
Use the approved center pattern consistently for grids, members, and openings, with lineweight suitable for the structural sheet scale.
Elements Above and Below the View
Use patterns or layer names that explicitly identify vertical relation. Avoid depending on color alone.
Construction and Reference Lines
Keep non-plot construction geometry separate from plotted reference lines through layer policy.
Coordinating Structural Xrefs with Architectural Linework
Avoiding Hidden-Line Conflicts
When both disciplines use HIDDEN, use discipline-prefixed custom names or host layer overrides so the structural background does not merge with architectural hidden work.
Distinguishing Structural and Architectural Overhead Elements
Establish lineweight priority and a shared legend on coordination sheets.
Mechanical, Electrical, and Plumbing Linetypes
Ductwork and Piping Systems
Use system-specific layers and reserve text-based complex linetypes for routes where labels will remain readable.
Electrical Circuits and Conduits
Distinguish power, lighting, controls, underground, and overhead systems without creating an excessive number of nearly identical patterns.
Fire Protection Systems
Coordinate sprinkler, standpipe, and fire alarm graphics with life-safety plotting requirements.
Existing, New, and Demolished Services
Use phase layers and lineweight in addition to pattern. A text label such as GAS should identify system, not carry every phase meaning.
Managing MEP Linetypes Across Architectural Xrefs
Preserving Utility Labels at Different Viewport Scales
Test label height and spacing in every sheet scale. A complex pattern readable in the MEP model can become oversized in a detail or disappear in an overall plan.
Preventing MEP Patterns from Merging with Background Plans
Screen or lighten the architectural Xref while preserving MEP lineweight and pattern gaps.
Civil Engineering Linetype Standards
Roads and Alignments
Use clear conventions for centerlines, limits of work, existing edges, proposed edges, and temporary works.
Easements and Rights-of-Way
Keep legal corridors distinct from parcel boundaries and construction limits, especially where several overlap.
Existing and Proposed Features
Define whether state is communicated through pattern, layer suffix, color, or a combination that survives monochrome plotting.
Underground and Overhead Networks
Text-based GAS, WATER, SEWER, ELEC, and communication patterns require consistent text style, orientation, and spacing.
Displaying Civil Utility Linetypes in Architectural Xrefs
GAS, WATER, and SEWER Lines at Architectural Scales
At 1:100, long civil labels may dominate the floor plan. Provide a compact coordinated-sheet variant or controlled viewport override rather than altering the civil source definition.
Civil 3D Source Scale vs. Host Drawing Scale
Civil objects can obtain display from styles as well as AutoCAD layers. Coordinate with Civil 3D object-style behavior before assuming the LIN file alone controls the result.
Layer Overrides for 1:100 and Similar Plan Scales
Define which host layer overrides are allowed and verify they survive Xref reload and plotting.
Surveying Linetype Standards
Property Boundaries
Use legally clear patterns and lineweights. Do not obscure monuments, bearings, or parcel labels with oversized complex symbols.
Easements
Differentiate access, utility, drainage, and other easement classes through layer names and legends.
Fence and Vegetation Lines
Shape-based patterns are useful but require minimum-radius and plot-scale tests.
Survey Limits and Control Lines
Keep survey control distinct from design construction lines and non-plot geometry.
Coordinating Survey Xrefs with Civil and Architectural Backgrounds
Avoiding Duplicate Property and Easement Lines
Choose one authoritative source and freeze or screen duplicates in other Xrefs.
Establishing a Display Priority
Legal boundaries normally require stronger priority than approximate design backgrounds; document the project rule.
Utility Linetype Standards
Water
Define potable, fire, raw, and reclaimed systems with clear names and approved abbreviations.
Sanitary and Storm Sewer
Separate gravity, force main, sanitary, and storm systems while preserving flow and status conventions.
Gas
Use readable upright text, controlled spacing, and distinct existing/proposed layers.
Electrical and Telecommunications
Differentiate overhead, underground, power, fiber, and communication networks through a limited, documented set.
Managing Utility Linetypes Across Multiple Xref Levels
Nested Xrefs and Linetype Dependencies
Every workstation opening the final host must find the required SHX and font files, even when the utility drawing is nested.
Maintaining Text Orientation and Readability
Use upright rotation and test reversed routes, curves, and mirrored backgrounds with the orientation guide.
Resolving Duplicate Utility Linetype Names
Use company or consultant prefixes and a project mapping table rather than redefining generic GAS or WATER names.
Coordinate Linetypes Between Disciplines
Avoid Duplicate Meanings
One pattern should not mean demolition in one model and underground work in another coordinated sheet.
Resolve Naming Conflicts
Compare actual definitions, choose authoritative names, and document aliases before model exchange.
Create a Shared Legend
Show the plotted result and discipline owner, not only the software name.
Define Rules for Xref Layer Overrides
Specify who may override, which properties, at what sheet level, and how changes are reviewed.
Build a Discipline Linetype Matrix
Linetype Name
Use the exact controlled identifier.
Intended Use
State one approved meaning and prohibited alternatives.
Assigned Layer
List native layers and any host mapping.
Native Drawing Scale
Record the scale at which the pattern was designed.
Xref Display Rules
Document permitted screening, linetype, and lineweight overrides.
Plot Example
Include PDF samples at standard coordination scales.
Test Multidiscipline Linetypes in a Coordinated Sheet
Test Host and Xref Scale Combinations
Attach each discipline model to representative architectural, civil, and detail sheets.
Test Nested References
Confirm dependent names and external SHX resources remain available through every level.
Test Screen, PDF, and Printed Output
Compare the coordinated legend with the final output using the PDF test workflow.
Adapt the Standard to Client and Project Requirements
Keep company defaults as the baseline, then issue a project-specific deviation schedule. Map client names to company meanings, identify required custom resources, and remove temporary exceptions when the project closes.