Most Shorthand Just Happens. Engineers Have Theirs Legislated

Engineering Has A Governed Vocabulary

Military jargon spreads through units and gets picked up informally. Medical abbreviations propagate through hospitals and get corrected only after someone gets hurt. Internet shorthand mutates by consensus, with no one in charge of it at all.

Engineering drawings work differently. The abbreviations on a stamped mechanical drawing aren't just common usage that caught on. In the US, they're governed by ASME Y14.38, a published national standard.

It's maintained by a standing committee. It has a formal revision process. And it carries legal weight once a licensed engineer's stamp goes on the page.

That standard didn't start under that name. Its original designation was ASME Y1.1. It was redesignated into the Y14 series — the family of standards that governs how engineering drawings are built, dimensioned, and interpreted — once its scope narrowed from general technical writing toward drawing practice specifically.

The Y14 Standards Committee maintains it the way most ANSI-accredited committees work. Open meetings. A formal revision process. A mandate to represent "the consensus of concerned interests" rather than one company's preference.

Anyone can propose a change. Revisions get incorporated periodically and supersede the previous edition industry-wide once approved.

That's an unusual level of formality for something as small as which three letters mean "bolt circle diameter." Most fields never bother.

Engineering did because of liability. A stamped drawing is a legal instrument. An abbreviation that reads two ways isn't just confusing — it's exposure, if a part gets built wrong because a term got misread.

So the standard runs as a controlled list, not a style guide. BHC means bolt hole circle. BHCS means button head cap screw. The distinction is fixed, not left to whoever's drafting that day.

But Mechanical Isn't the Only Discipline That Legislated Its Own Vocabulary

Each engineering discipline built its own system. Under its own committee. Often without much coordination with the others.

Electrical engineers work under IEEE 315, also published as ANSI Y32.2, for diagram symbols, and IEEE 280 for the letter symbols used for electrical quantities. That standard was developed with deliberate coordination between industry and the Department of Defense — specifically so the military and private sector wouldn't end up running two incompatible symbol sets.

Chemical and process engineers work under ANSI/ISA-5.1 instead. It governs the piping and instrumentation diagrams that map a plant's equipment and controls. FT for flow transmitter. FCV for flow control valve. LIC for level indicating controller. Each function letter is fixed, so an instrument tag resolves to exactly one meaning no matter who drew the diagram.

Civil engineers draw more from bodies like the American Concrete Institute and AASHTO than from a single unified drafting standard.

Software engineering, despite being just as acronym-dense as any of these, has nothing equivalent at all. No committee legislates what API or CRUD is allowed to mean the way Y14 legislates BHC. That vocabulary drifts the same informal way military slang does — right next door to fields that formally locked theirs down decades ago.

Even where the governed disciplines meet at the seams, the standards don't just merge cleanly. An electrical schematic referencing a P&ID's instrument tags. A mechanical assembly interfacing with an electrical one. Engineers still have to explicitly pick whose convention rules the handoff, and document that choice in the drawing's legend — because the standards were never fully reconciled with each other.

And That's Still Only the American Picture

Germany runs its own long-standing system through DIN. DIN 406 still governs how German drawings call out dimensions and tolerances, though an older sibling, DIN 6, has since been folded into the international ISO 128 standard rather than kept separate.

Japan runs JIS, administered by the Japanese Standards Association — a body reestablished after 1949 that has spent decades deliberately tightening its alignment with ISO instead of drifting further from it.

France has AFNOR. Australia splits its own AS1100 series into general principles, mechanical, and structural drawing as three separate documents. Korea and Sweden maintain their own systems too.

What's actually happening across all of this isn't fragmentation so much as slow convergence. ISO 128 has been adopted without modification as European Standard EN ISO 128, valid across individual European national standards rather than competing with them. JIS has been tightening toward ISO for the same reason.

Each country legislated its own version first, independently, often decades before coordinating with anyone else. The harder work of merging those systems into shared international ones is still incomplete even now.

That's the real shape of it: not one single global standard everyone already follows, and not total anarchy either, but dozens of independently governed national systems in the middle of a decades-long process of merging into fewer, shared ones — with engineers on international projects still needing to know, drawing by drawing, which system's rules are actually in force.

How One Engineer Actually Holds All of This in Their Head

Given how much of this is formally written down, the obvious question is how any one engineer keeps it straight. The honest answer: mostly they don't, not as a document.

GD&T training built around ASME Y14.5 explicitly warns against trying to memorize several hundred pages. That's not how the knowledge gets used day to day.

What actually happens is repetition on a much narrower working set. Any individual engineer's daily drawings pull from the same recurring few dozen terms specific to their discipline. Those become automatic through sheer use, long before anyone studies the full standard cover to cover.

The rest gets carried by tooling instead of memory. CAD platforms like SolidWorks, Fusion 360, and AutoCAD have the standard symbol and abbreviation libraries built directly into the drafting tools. Selecting a callout means choosing from a pre-loaded, compliant set — not typing one from memory and hoping it's right.

Company templates layer familiar abbreviations on top of that. And the standard itself becomes a reference to check for the unusual case, the way a style guide gets opened for an edge case rather than recited from memory.