Standards show up everywhere, but most people never think about how they start. Your phone charger works across brands, and airplanes fly safely, because rules were agreed on ahead of time.
Still, standards do not appear by magic. Someone spots a gap, experts write drafts, stakeholders argue over details, and governing groups vote before anything gets published. If you’re a business, inventor, or even a curious buyer, it helps to know what happens behind the scenes.
In plain terms, the path runs from a proposal, to expert committee work, to public feedback, and finally to voting and approval. Along the way, organizations like ISO, IEEE, and ANSI play key roles.
What Sparks the Idea for a New Standard?
Most new standards start because real work hits a wall. Maybe a product causes safety issues. Maybe devices do not “talk” the same way. Or maybe laws and buyer needs change faster than industry habits.
From there, proposals usually begin in one of two lanes. One lane is international, often linked to ISO. The other lane is more technical and use-case focused, where IEEE steps in for many engineering areas. In the U.S., ANSI helps coordinate input so U.S. stakeholders can influence global standards.
ISO typically begins when stakeholders find a need and ask their national member body to start work. Then ISO brings that request into the official development process, with experts planning drafts, sharing for comment, and voting on consensus. You can see ISO’s overview of this flow on the Developing standards page.
For a quick example, imagine electric vehicle charging. If charger behavior differs by region, drivers and charging networks get frustrated. A standard helps align connector behavior, safety checks, and communication rules, so equipment works more predictably across markets.
Meanwhile, IEEE starts with a structured project launch. When a group wants a new standard or major update, they submit a Project Authorization Request (PAR). That PAR defines scope and goals. Then IEEE’s leadership reviews whether the project makes sense before deeper writing begins.
ISO’s Proposal Kickoff
In the ISO pathway, the “spark” becomes a formal request. Stakeholders ask their national member body to propose a new ISO deliverable. That step matters because it turns a need into something ISO can plan and resource.
After the request gets traction, ISO typically organizes the work around a technical committee and related working groups. Those groups focus on specific parts of the topic. They also help decide how complex the draft should be, plus how long it should take.
ISO also assigns projects to a development track, which sets target timelines like 18, 24, or 36 months. That structure helps teams move without endless delays. ISO lays out these stages and resources in its Stages and resources for standards development guidance.
In practice, the kickoff stage is where experts start shaping definitions, boundaries, and the “must-have” requirements. It’s also where early checks happen, like patent and scope concerns.
IEEE’s PAR Approval
IEEE’s process puts a gate in front of drafting. That gate is the PAR. In other words, IEEE wants to confirm that the project is worth doing before the writing marathon starts.
A PAR covers the purpose, scope, and stakeholders for the project. It also explains what problem the standard will solve. Then IEEE channels review through its process for PARs, including how the request moves forward once submitted.
IEEE explains PARs and forms, plus how the project gets started through its systems, on the PARs, PAR Forms & Continuous Processing page.
This early review helps reduce wasted effort. It also forces clarity, so later drafts do not wander away from the original goal.
Assembling the Dream Team of Experts
After the proposal stage, committees form. These groups are where standards shift from “ideas” into detailed requirements.
Think of it like a superhero team-up. One person has deep theory. Another has real-world deployment experience. A third knows what users actually need. Together, they build a set of rules that most stakeholders can accept.
Most committees include industry specialists, academics, and other affected groups. They also include people who represent public interest, depending on the topic. For ISO, work happens through technical committees and working groups supported by ISO member countries. IEEE builds similar working groups under its societies, with many projects running at once.
IEEE’s scale is huge. In 2026, IEEE tracks over 2,360 active standards and related projects. That means many teams are drafting, balloting, and maintaining standards at the same time.
ANSI adds another layer in the U.S. ANSI helps organize how U.S. input flows into standards work and how U.S. groups coordinate participation. You can read about ANSI’s role and how it supports engagement through its ANSI’s Roles page.
Who’s on These Committees?
Committees usually include people with three traits: expertise, interest, and ability to participate. The goal is not to pack the room with random voices. The goal is to get relevant knowledge on the table.
Common participants include:
- Industry specialists who understand what works in real products
- Researchers and academics who can test assumptions and methods
- Consumer or user representatives who can point out practical harm
- Government or public-interest participants when safety and policy connect
In IEEE work, this matters even more because engineering standards can affect whole systems. If a committee misses a key stakeholder, the draft can fail later during voting or public review.
Drafting, Debating, and Getting Feedback
Drafting is where the “magic” becomes paperwork. A committee writes a first version, then keeps revising it through discussion.
Usually, the process runs through multiple draft levels. Each round tightens language. Each discussion tries to resolve disagreements. In short, experts argue on paper, then adjust until they can all support the direction.
Public feedback also matters. Without it, a standard can become too narrow for real adoption. That feedback catches confusing definitions, missing use cases, and unclear requirements.
IEEE and ISO both use comment periods and revision loops. IEEE often uses formal balloting and review cycles with set time windows. ISO also runs staged reviews with member comments before major approval steps.
The Public Comment Phase
The public comment phase makes standards more than an internal club. It gives outside stakeholders a chance to weigh in.
Typically, anyone with a direct interest can submit comments. Some groups share the draft openly, while others distribute it through formal review channels. Either way, the point is consensus building, not one side “winning” by force.
Then comes the hard part: the committee must read feedback and decide what to change. Sometimes the committee rejects comments, but it usually has to explain why. Other times it accepts edits and rewrites sections to fix the issue.
That back-and-forth improves clarity. It also helps reduce risk during final voting, because more problems get caught earlier.
Reaching Agreement: Voting and Final Approval
Once drafts look solid, committees move into voting. Here’s the key idea: standards do not require total agreement. They require broad consensus.
In most cases, voting needs majority agreement and strong support. If major concerns remain, the committee revises again. Then it votes again.
For ISO, committees often vote on draft stages and send the text forward through defined approvals. For IEEE, committees and oversight groups review balloted results. Then governing bodies give final approval based on procedural rules.
When final approval happens, the standard becomes official and gets published. That last step is not just ceremony. It confirms the document met the required process, version control, and governance steps.
Consensus vs. Unanimity Explained
Consensus usually means broad agreement, not everyone saying “yes” with no exceptions. That approach works because standards serve many groups with different goals.
Here’s how the two ideas differ in real life:
| Term | What it means | Why it matters |
|---|---|---|
| Consensus | Broad agreement from stakeholders | Faster global alignment |
| Unanimity | Everyone agrees without exception | Often too slow for tech change |
In other words, consensus balances speed with fairness.
The Final Sign-Off
Final sign-off comes from governing boards or oversight councils in each organization. These boards check whether the process rules were followed and whether the text reflects the required edits.
After sign-off, the standard gets published. It also enters a maintenance cycle. Most standards do not stay frozen, because technology and safety needs keep changing.
In IEEE’s case, the maintenance work never really stops, given the size of its portfolio.
How Long It Takes and What Happens After
Timelines vary by scope. Still, many standards take a while, because experts need time to draft and review.
ISO often targets about three years from proposal to publication. ISO also uses project tracks that can speed up or slow down work, depending on complexity. As a result, some projects finish sooner, while tougher topics can stretch longer.
After publication, standards move into the maintenance phase. Committees review new evidence, update requirements, and respond to changes in markets. Over time, old versions get replaced, and organizations plan transitions for users and certified products.
That last part matters. Even if a standard updates today, people need time to comply. So adoption can include training, new tests, and changes in procurement.
As technology evolves, standards act like living guides. They don’t just describe what exists today. They also help systems work together tomorrow.
Conclusion
Standards start when someone spots a real problem, then turns it into a formal proposal. Next, experts draft text, debate the details, and collect feedback from affected groups. Finally, governing bodies vote and approve the standard so it becomes publishable.
The biggest takeaway is simple: approval comes from process, not from luck. When ISO, IEEE, and ANSI work in structured ways, standards tend to earn trust across regions and industries.
Want to get involved? Join a committee, follow public review periods, or use standards in your projects so your needs become part of the next update. When you see standards as a shared effort, the whole system makes more sense.