How to Create a Company Linetype Standard: Names, Files, Units, and Governance
A company linetype standard is more than a shared LIN file. It defines names, units, visual proportions, dependencies, deployment, approvals, and the tests required before a pattern reaches production.
A controlled standard prevents duplicate names, broken SHX references, unreadable plots, and different departments quietly creating incompatible versions of the same utility or boundary line.
Define the Purpose of the Linetype Standard
Drawing Consistency
Specify which graphical meanings must look identical across drawings, projects, and offices. A named linetype should represent one approved purpose, not several unrelated conventions.
File Exchange
Define what external teams receive: the DWG record, source LIN files, SHX dependencies, fonts, legends, and installation instructions. Use the custom-linetype transmittal workflow as the delivery baseline.
Plot Readability
State the sheet sizes, viewport scales, lineweights, and PDF drivers used for approval. A pattern that works only at one screen zoom is not a production standard.
Automation
Design stable identifiers that can be used by templates, scripts, palettes, QA tools, and batch processors. Automation depends on exact names and predictable file locations.
Inventory Existing Linetypes
Standard AutoCAD Definitions
List the Autodesk definitions the company accepts without modification. Do not copy or rename them unless a documented difference is required.
Department-Specific Definitions
Collect libraries from architecture, structural, MEP, civil, survey, and facilities teams. Record the source, intended use, unit system, dependencies, and active projects.
Duplicate and Obsolete Definitions
Compare code, not only names. Two names may describe the same pattern, while one name may hide several incompatible definitions. Mark obsolete items and create a migration map before removal.
Create a Linetype Naming Convention
Discipline Prefixes
Use a controlled prefix such as ARC_, MEP_, CIV_, or a company identifier when discipline ownership matters. Avoid ambiguous generic names that collide with clients or consultants.
Descriptive Pattern Names
Include the function, not just appearance: CIV_GAS_EXIST is more useful than DASH_TEXT_01. The description line can contain a longer human explanation.
Metric and Imperial Suffixes
Add _M and _I only when separate numeric definitions exist. Do not label one definition as universal unless it was designed and tested for the chosen unit strategy.
Version Identifiers
Keep release versions in file names or documentation rather than changing every linetype name for minor corrections. Use a new resource name when two definitions must coexist safely in drawings.
Define the Approved Pattern Specifications
Dash and Gap Lengths
Set proportion rules and minimum printed gaps. Base them on actual project scales and lineweights, not arbitrary screen appearance.
Text Height and Spacing
Define the text style, non-annotative requirement, nominal height, label abbreviations, and clear space before and after text. Use the text-linetype guide for descriptor details.
Shape Size and Orientation
Specify the approved SHX file, shape origin, scale, rotation mode, and minimum radius. Archive the source SHP and compiled SHX together.
Minimum Plot Readability
Create pass/fail criteria for gaps, dots, labels, symbol separation, and intersections at each standard sheet scale.
Establish a Unit Strategy
Metric Projects
Define whether numeric elements are authored directly in millimetres or metres according to company drawing-unit practice. Align the library with the metric-versus-imperial scaling policy.
Imperial Projects
Document whether definitions assume inches, feet, or another project unit. Never rely on users to guess the source library.
Separate or Combined Libraries
Separate files make unit intent obvious. A combined file simplifies deployment but requires strict suffixes and documentation. Choose one method and test cross-unit insertion.
Organize the Master Linetype Files
Core Library
Store widely approved definitions with the highest change control. Keep this file small and stable.
Discipline Libraries
Separate specialized patterns by team so civil utility additions do not force every architectural user to update.
Project-Specific Libraries
Use them only for contractual or client requirements that should not become company defaults. Include an owner and retirement date.
Manage SHX and Font Dependencies
Use unique filenames, controlled support paths, and a dependency register. Prefer stable, licensed resources. Avoid annotative text styles and personal workstation fonts. Explain every dependency in the library readme and deployment package.
Integrate Linetypes with Layers and Templates
Layer Standards
Map each approved linetype to its normal layers, colors, and lineweights. This supports audits and reduces direct object assignments.
DWT Templates
Preload only production definitions and standard layers. A template should not become a warehouse of obsolete experiments.
Tool Palettes
Provide one-click tools that create the correct layer and linetype using the Tool Palette implementation guide.
Create a Linetype Quality-Control Process
Code Validation
Load each definition in a blank drawing and check syntax, unique names, external references, and intended numeric cycle.
Screen Testing
Test long, short, reversed, curved, polyline, block, and Xref examples at common zoom levels.
Plot Testing
Plot the approved test sheet with production lineweights and PDF presets. Archive the output with the release.
File-Exchange Testing
Open a packaged project on a clean Windows and, where supported, macOS workstation without private library paths.
Control Versions and Approvals
File Ownership
Name a CAD standards owner and backup. Limit edit rights to the controlled source while giving users read-only access.
Change Requests
Require the business reason, sample drawing, affected disciplines, unit system, dependencies, and backward-compatibility plan.
Release Notes
List added, modified, deprecated, and removed definitions, plus required template or support-path changes.
Deploy the Standard to Users
Distribute the same folder structure, support paths, templates, palettes, and optional loaders. Automate installation where possible, but keep a manual rollback package. Use the cross-platform batch loader for approved definitions.
Document and Train the CAD Team
Publish a visual catalog with name, use, prohibited uses, layer, units, dependencies, and plot samples. Train users to assign by layer, diagnose short geometry, and report missing resources without creating local replacements.
Audit Linetype Compliance in Project Drawings
- Compare loaded names with the approved register.
- Find same-name definitions from unapproved files.
- Review layers by linetype with layer filters.
- Find direct object overrides.
- Check missing SHX and fonts.
- Inspect nested blocks and Xrefs.
- Plot the standard QA sheet.
- Record exceptions and corrective ownership before issue.