Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can prepare a formal IT specification for consideration by ISO, but a correctly formatted draft is not automatically an ISO standard. ISO standards are developed through technical committees and member-body procedures. Start with ISO’s drafting resources, apply the current ISO/IEC Directives, Part 2 for structure and drafting, and work through the relevant committee’s process under Part 1.
What it means to publish an IT specification through ISO
ISO publication is the outcome of a standards-development process, not a self-publication route. An expert can propose or contribute text through the appropriate technical committee and national standards-body channels. The committee determines how the work proceeds, and member review and voting apply at the relevant stages. A template-compliant draft can still be returned, revised, or stopped; formatting alone does not secure acceptance or publication. See ISO’s foreword explaining how standards are developed.
If you do not know which committee covers your subject, contact your national standards body or ask an ISO committee manager to identify the appropriate route. The IT subject, whether the work is new or a revision, and the intended publication type all affect the process.
Recommended Free Tools
Choose the scope and publication type before drafting
Define the specification’s boundaries
Write a concise proposal that states the problem, intended users, systems or processes covered, exclusions, and the outcomes the document should establish. Identify terms that need consistent definitions and distinguish requirements from guidance. Check related standards and established terminology so the proposal does not duplicate or contradict existing work.
Agree on the deliverable with the committee
An International Standard is not the only possible ISO deliverable. A Technical Specification (TS) can suit work that is still developing or for which immediate agreement on an International Standard is not possible. A Publicly Available Specification (PAS) can address an urgent market need and provide a basis for feedback toward a later International Standard. The right choice depends on the work’s maturity, urgency, agreement, and applicable procedure—not simply on the author’s preference. Confirm the proposed deliverable and route with the committee; consult ISO’s overview of deliverables and the current Part 1 rules.
Draft to ISO’s structure and style rules
Use the current edition of Part 2 as the drafting authority. It sets principles and rules for structuring and drafting ISO and IEC documents. Pair it with the appropriate template or model and ISO House Style, all available from ISO’s drafting resource page. The page includes a model International Standard with instructional notes and guidance for preparing material.
Rank #2
Build the technical content around a clear scope and consistent terminology. For each normative requirement, make the subject, condition, and expected outcome understandable and verifiable. Separate requirements from recommendations and explanatory material, and use the document structure and conventions required by Part 2 rather than inventing a layout. Check the current Directives and project instructions before relying on clause numbers: editions and amendments can change, and management-system documents may have additional drafting rules.
Part 1 governs the technical work and publication procedure. Drafts that do not conform to Part 2 can be returned for correction before registration. The Directives and committee rules therefore matter alongside the technical merit of the text.
Rank #3
Develop the text in ISO’s current platform
Since January 2025, Online Standards Development (OSD) has been ISO’s default platform for developing ISO deliverables, replacing the former Word-based process. Check the project’s access arrangements and instructions with the committee; do not assume a legacy Word workflow applies. ISO’s drafting resources link to OSD information and its Knowledge Base.
Expect committee review, ballots, and revisions
Work typically moves through committee drafting and review before member voting. At the Draft International Standard (DIS) enquiry stage, ISO members receive the text for a vote and comments. An FDIS ballot may follow when the procedure requires it. Under the current Part 1 procedure, the FDIS vote lasts six weeks; approval requires at least two-thirds of votes cast by P-members to be positive and no more than one-quarter of total votes cast to be negative, subject to the exclusions in the Directives. Check the current consolidated text for the precise counting rules.
Use earlier review stages to resolve technical disagreements. Technical changes are not accepted after FDIS approval. The committee process is not just proofreading: comments may require substantive revision, further review, or a change in the project’s course.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Submit the final text and complete publication checks
Follow ISO’s current submission requirements for document files and technical assets. Project-specific instructions can affect what the committee needs and how it accepts material, so confirm them with the committee manager rather than relying on an old checklist.
Before publication, the final text is sent to the secretary or committee manager and project leader for review. The committee secretariat submits the final text; the Office of the CEO handles validated errors and publication. Under the current Part 1 procedure, publication is processed within six weeks after validated errors have been identified and confirmed. This is a procedural timeframe, not a promise that a draft will reach publication by a particular date.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Clear copyright, permissions, and patent issues early
Keep a record of the origin and permissions status of borrowed text, figures, tables, and other source material. ISO/IEC Directives Part 1, clause 2.10, states: “The copyright for all drafts and International Standards and other publications belongs to ISO, IEC, or ISO and IEC, as appropriate, as represented by the Office of the CEO.” That rule does not mean third-party material is automatically cleared for inclusion; address separate rights and permissions with the committee while the draft is being prepared. Raise relevant patent issues through the applicable committee process as well.
Use related standards only for their specific purpose
ISO/IEC/IEEE 26514:2022 addresses the design and development of information for users of software. It may be relevant if an IT specification includes software user information, but it does not replace Part 2 drafting rules or the committee’s Part 1 process.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
