What Are General Industry Standards Also Called

You're reading a contract, a spec sheet, or a compliance checklist, and there it is: industry standard. But then the next document calls it a consensus standard. The one after that says voluntary standard. Another references a de facto standard.

Wait — are these all the same thing?

Short answer: mostly, yes. Long answer: the differences matter more than you'd think.

What Are General Industry Standards (and What Else Are They Called)

At its core, a general industry standard is a documented agreement containing technical specifications or precise criteria designed to be used consistently as a rule, guideline, or definition. It ensures materials, products, processes, and services are fit for their purpose.

But the terminology? That's where it gets messy.

You'll hear them called:

• Consensus standards — because they're developed through a formal consensus process
• Voluntary consensus standards — emphasizing that adoption isn't legally mandated (until it is)
• Industry consensus standards — same thing, just scoped to a specific sector
• Technical standards — focusing on the engineering/technical content
• Reference standards — because other documents reference them
• Normative standards — the ones with "shall" statements you must follow
• Codes of practice — common in UK/Commonwealth contexts
• Specifications — when they're highly detailed and prescriptive
• Protocols — especially in tech and comms
• Benchmarks — when used for performance comparison
• Best practices — the softer, guidance-oriented end of the spectrum
• De facto standards — the ones nobody voted on but everyone uses anyway

And that's not even an exhaustive list.

The consensus standard — the gold standard of terminology

If you work in standards development, consensus standard is the precise term. But no single interest dominates. Also, it means something specific: a standard developed through an open, balanced, transparent process where all materially affected parties have a voice. The outcome represents general agreement — not necessarily unanimity, but broad alignment.

Organizations like ASTM International, ASHRAE, IEEE, NFPA, UL, and ISO operate this way. Their standards carry weight because of the process.

But here's the thing — most people outside the standards world don't use that term. They say industry standard and move on.

De facto standards — the ones that just happen

Then there's the other major category: de facto standards. Consider this: no SDO (standards development organization) published them. On top of that, these emerge organically. Worth adding: no committee voted on them. They become standard because the market converged on them.

Think: the QWERTY keyboard. 5mm headphone jack. The 3.Now, the PDF format (before ISO 32000). USB-C — which started proprietary, became de facto, and is now formalized.

De facto standards can be powerful. They can also be messy — proprietary, fragmented, or controlled by a single vendor. That's why many eventually get adopted or adapted into formal consensus standards.

Why the Terminology Matters

You might wonder: does it actually matter what we call them?

In practice? Yes. For three reasons.

1. Legal and regulatory weight

A voluntary consensus standard referenced in a regulation becomes mandatory. OSHA does this. Worth adding: the FDA does this. Building codes do this. The moment a law says "comply with NFPA 70," that voluntary standard isn't voluntary anymore for the people in scope.

But a best practice guide from a trade association? Rarely gets that treatment. The label signals enforceability.

2. Procurement and contracts

Government procurement (especially U.Plus, s. federal) is legally required to use voluntary consensus standards where they exist. That's not a suggestion — it's in OMB Circular A-119 and the National Technology Transfer and Advancement Act (NTTAA).

If you're a vendor, knowing whether a standard is a consensus standard vs. a technical report vs. a guideline determines whether you can bid, what you must certify, and what liability you carry.

3. Liability and due diligence

In product liability cases, courts look at whether a manufacturer followed applicable consensus standards. In practice, not best practices. Not industry norms. Consensus standards.

The label carries evidentiary weight.

The Main Categories of Standards Terminology

Let's break this down properly. Not all "standards" are created equal, and the terminology reflects real differences in development process, legal status, and intended use.

Consensus standards (the formal ones)

Developed by accredited SDOs following ANSI Essential Requirements (U.Here's the thing — s. ) or ISO/IEC Directives (international).

• Open participation
• Balance of interests (no single stakeholder group > 1/3 typically)
• Due process (appeals, public review, comment resolution)
• Consensus vote (not unanimity — usually supermajority)
• Regular maintenance cycles (typically 3–5 years)

Examples: ASTM D638 (tensile testing), ASHRAE 90.1 (energy code), ISO 9001 (quality management), IEEE 802.3 (Ethernet).

Technical reports and specifications (the "not quite standards")

SDOs also publish documents that aren't consensus standards. Important distinction.

If you found this helpful, you might also enjoy can i weld in my apartment or before excavation work begins employers must.

• Technical Reports (TR) — informative, not normative. Data, background, rationale. No "shall" statements.
• Technical Specifications (TS) — ISO term for a document not yet ready for full standard status. May become one.
• Publicly Available Specifications (PAS) — BSI term, fast-track, sponsored by one org but open for comment.
• Workshop Agreements (IWA) — ISO fast-track for emerging areas, no full consensus required.

These don't carry the same regulatory weight. But they're useful — often precursors to full standards.

De facto standards (the market decides)

No process. No committee. Just adoption.

• Proprietary de facto — owned by one company (e.g., early PDF, Flash, .doc format)
• Open de facto — community-driven but not formalized (e.g., Markdown, JSON before RFC 8259)
• Consortium standards — industry groups like W3C, OASIS, Bluetooth SIG, PCI SSC. Formal process, but not ANSI/ISO accredited. Often called consortium standards or industry specifications.

Consortium standards blur the line. But they're not "consensus standards" in the ANSI sense. They have process, governance, IPR policies. In practice, many regulators treat them similarly.

Guidelines, recommended practices, and codes of practice

Softer language. "Should" not "shall." Advisory.

• Recommended Practice (RP) — API, ASME, and others use this for guidance that's strongly advised but not mandatory
• Guideline — general term for non-mandatory guidance
• Code of Practice — UK/Commonwealth

and Code of Practice — UK/Commonwealth usage for non-mandatory guidance with industry-specific application.

These advisory documents serve as bridges between rigid regulatory requirements and practical implementation. They're essential for emerging technologies where formal consensus processes haven't yet crystallized requirements. Here's one way to look at it: NIST Cybersecurity Framework started as voluntary guidance before influencing regulatory adoption.

The Relationship Between Standard Types

Understanding these categories isn't academic—it affects compliance strategies. Standards form a hierarchy:

1. Mandatory regulations (laws, building codes) cite specific consensus standards as the compliance mechanism
2. Voluntary consensus standards provide the technical foundation for industry best practices
3. De facto standards often get absorbed into consensus processes once their dominance is proven
4. Guidelines and reports inform future consensus standards

Consider how Bluetooth SIG's consortium standard evolved: early specifications became widely adopted, then ANSI/IEC accreditation followed once market dominance was established. This progression matters legally—regulators can't mandate non-consensus standards without due process.

Practical Implications

For practitioners, the distinction determines liability and compliance pathways:

• Using consensus standards in regulated environments provides legal defensibility. If you follow ISO 13485 for medical devices, you can demonstrate due diligence.
• Implementing de facto standards without formal process creates risk. Early adopters of proprietary formats faced obsolescence when vendors shifted direction.
• Following guidelines offers best practices but no regulatory protection. You might do everything "right" according to a technical report and still fail compliance audits.

IPR considerations vary too. Consortium standards often have RAND-Z (reasonable and non-discriminatory with zero royalty) licensing terms, while consensus standards typically require RAND-F (reasonable and non-discriminatory with fair consideration). De facto standards may have no licensing structure at all.

The Evolution of Standards

Standards aren't static—they evolve through predictable phases:

1. Problem identification — industry pain points or regulatory gaps
2. Exploratory work — technical reports, workshop agreements, informal specifications
3. Consensus development — formal standards committee formation
4. Market adoption — de facto standard emergence
5. Regulatory codification — incorporation into laws and regulations
6. Maintenance and revision — regular updates to reflect technological change

This lifecycle explains why some documents carry more weight than others. A PAS document represents industry consensus but lacks the mature governance structure of a full standard. A de facto standard may have broader adoption but no formal appeals process if you disagree with its direction.

The key insight: Authority derives from process, not popularity. A widely-implemented proprietary format remains legally precarious. A carefully developed consensus standard with limited adoption remains authoritative for compliance purposes.

Conclusion

Standards terminology isn't bureaucratic jargon—it's a map of authority, process, and risk. That said, technical reports and specifications provide valuable guidance without formal authority. Plus, consensus standards offer regulatory defensibility through documented due process. De facto standards reflect market reality but may lack procedural safeguards. Guidelines offer flexibility but no compliance guarantee.

For any organization navigating technical compliance, understanding these distinctions is critical. It determines which documents you cite in audits, which risks you accept, and which standards you help shape through participation. The next time you encounter a "standard" in your field, ask: What process created it? And who controls it? And what happens if you disagree with its direction?

The answers will shape your technical and legal strategy for years to come.