The organizations
Who writes C++? Who approves it?
The international language specification is ISO/IEC 14882, developed through ISO/IEC JTC 1, SC 22, WG21. ANSI represents the United States at ISO. INCITS/C++ (formerly PL22.16) is the U.S. Technical Advisory Group (TAG) to WG21. They are connected but distinct.
Technical development and national-body governance
What about “ANSI C++”? This is historical shorthand, not a second C++26 technical design committee. ANSI coordinates U.S. participation and positions. A separate American National Standard or national adoption designation, if applicable, is not the same as approval of features by WG21.
| Body | Primary role | What its decision is not |
|---|---|---|
| ISO / IEC | International standards organizations; C++ is ISO/IEC 14882 through JTC 1 and SC 22. | Independent design of every C++ language feature. |
| WG21 | Expert working group that develops, refines, and adopts draft technical text. | A final publication decision by ISO. |
| INCITS/C++ | U.S. Technical Advisory Group: coordinates U.S. technical consensus and positions. | A substitute for all other national-body votes. |
| ANSI | U.S. ISO member body coordinating the U.S. national position. | A separate C++26 feature-selection committee. |
A proposal is a process, not a switch
The C++ approval pipeline
- 01
Idea and P-paper
State the problem, design tradeoffs, examples, implementation experience, and proposed standard wording.
- 02
Study and evolution
A study group may incubate a proposal. EWG or LEWG discusses language or library design and can request revisions.
- 03
Wording review
CWG or LWG verifies normative language, consistency, and implementability; insufficiently precise text returns for work.
- 04
WG21 plenary
Accepted motions add wording to the working draft; papers may instead be revised, deferred, or rejected.
- 05
National-body review
ISO/IEC Committee Draft (CD) consultation gathers national comments; WG21 addresses issues.
- 06
DIS ballot and publication
National bodies vote on the Draft International Standard. ISO/IEC applies approval, any required final steps, and publication.
Revision loop: A failed consensus check, wording problem, committee decision, or national comment can return a proposal to earlier stages. A study group is not mandatory for every proposal.
How a paper wins consensus
Most proposals start as numbered P-papers. Experts must explain the motivation and alternatives, demonstrate what code means, discuss implementation experience, and—when ready—supply exact wording. SGs (study groups) are often optional incubators. EWG evaluates language evolution, LEWG library evolution; CWG and LWG review final wording. A consensus poll is a signal of support in the working group, not a national-body ISO ballot.
EWG / LEWG
Design consensus: advance, revise or defer a language/library feature.
CWG / LWG
Normative wording, defects, compatibility and integration into the draft.
WG21 plenary
Motions adopt technical wording. That is not the final ISO publication vote.
ISO / IEC national bodies
CD comments and DIS ballots; additional editorial or FDIS steps as applicable.
The international approval graph
From C++ working draft to published ISO/IEC 14882
Even after WG21 accepts technical wording, formal international standardization involves national member bodies. The Committee Draft (CD) stage solicits national comments, followed by the Draft International Standard (DIS) enquiry ballot. Comments or failed approval criteria can reopen work; the final approval route, including whether FDIS is needed, follows ISO/IEC procedures.
ISO/IEC approval and revision pipeline
- 30.00–30.99
Committee stage (CD)
National experts review the Committee Draft and submit comments; disagreements can require another revision.
- 40.00–40.20
Enquiry stage (DIS)
The Draft International Standard is registered and balloted by ISO/IEC national members.
- 40.60+
Ballot result and comment resolution
The result and any technical/editorial comments determine whether further work is needed.
- 50.x (if applicable)
Approval stage
Final text or Final Draft International Standard (FDIS), under applicable ISO/IEC procedures.
- 60.00–60.60
Publication stage
ISO/IEC publishes the new edition of ISO/IEC 14882 after required approvals.
Decision gate: Has the national comment set been resolved, and has the DIS met the applicable ISO/IEC approval criteria? If not, the draft can return to WG21 for corrections and a revised ballot or other disposition. Publication is not automatic.
| Event | Meaning | Does it finish standardization? |
|---|---|---|
| Subgroup consensus | Technical group supports a direction or wording. | No |
| WG21 plenary motion | Technical wording is accepted into the working draft. | No |
| ISO/IEC DIS ballot | National bodies review/vote on the international draft. | Only if all applicable approval requirements are subsequently completed |
| ISO/IEC publication | The new ISO/IEC 14882 edition is formally published. | Yes, for that edition; implementation remains separate |
The U.S. role in the global process
The ANSI / INCITS/C++ path is not a second C++ committee
Engineers and organizations in the U.S. participate in international WG21 technical meetings. Separately, the U.S. Technical Advisory Group, INCITS/C++, helps develop a U.S. consensus position that is represented through ANSI as the U.S. ISO national member body. Both paths meet during international standardization, but a WG21 technical vote and an ANSI-transmitted national position are not the same vote.
U.S. experts and national ballots — parallel routes
The C++26 example
“C++26 is done” is not “ISO has published it”
WG21 finished the C++26 technical feature set in March 2026, including major work on compile-time reflection, contracts, standard-library hardening and std::execution. The international standards lifecycle continues separately.
International CD consultation starts.
WG21 finalizes the feature set.
ISO stage 40.20: 12 weeks.
Pending formal ISO/IEC process, not yet published as of this article.
The most recent published C++ edition on this date is ISO/IEC 14882:2024 (C++23). After ISO publication, teams still need to verify compiler versions, feature availability and the migration risks of adopting C++26.
From de jure standard to production toolchain
Approval is not the last engineering checkpoint
There are two different senses of “C++26 support.” The first is what the international standard specifies; the second is what a particular compiler, standard library, linker and build toolchain have shipped and validated. Versions, feature flags, platform ABIs and defect reports matter.
Reflection
Evaluate compiler support, compile-time performance, tooling, metaprogramming patterns and generated APIs.
Contracts
Document supported contract behavior, build profiles, verification limits and what happens when an assertion fails.
Library hardening
Test hardened standard-library modes, diagnostics and compatibility with existing dependencies.
Execution
Benchmark and validate the sender/receiver execution model, scheduling choices and cancellation semantics where implemented.
A sound rollout requires compiler-version matrices, CI feature checks, reproducible builds, ABI policies, conformance tests and an explicit rollback. No language-standard ballot guarantees operational readiness.
Insights
What engineering teams should take away
Follow the P-paper revision
Votes in a subgroup, plenary adoption and an international ISO ballot are not the same milestone.
Account for iteration
A paper may loop through revisions after study, evolution, wording, plenary or national comments.
Separate paper from product
A finalized draft does not mean GCC, Clang and MSVC all implement a feature the same way.
Plan real migrations
Reflection, contracts, library hardening and std::execution affect tooling, testing and deployment decisions.
A programming-language standard is not a certification of a cloud provider, software product, or organization. Standardization and compliance assurance are different processes.
Primary sources and editable Markdown graphs
All three canonical Mermaid diagrams—proposal branching, ISO CD/DIS approval and ANSI/INCITS national representation—are retained in the source Markdown. The diagrams above are static, accessible web equivalents that do not require JavaScript or a third-party CDN.
- ISO/IEC DIS 14882 status ↗
- International C++ working group WG21 ↗
- WG21 organization and stages ↗
- INCITS/C++: U.S. technical advisory group ↗
- ANSI: U.S. representation in ISO ↗
- ISO/IEC JTC 1/SC 22 ↗
- March 2026 C++26 committee report ↗
Independent editorial explanation. Not an official statement on behalf of ISO, IEC, WG21, ANSI, or INCITS. Status is current to the publication date; consult the source links for updates.