What changes, and what the public record will not tell you
The honest answer is short. ISO records a third edition at DIS ballot with the same title, the same committee and the same scope. It does not publish the draft clauses or a change list. Any site that offers a clause level "what changed" from the public record is inventing it. This page states what is confirmed and what the practical work is.
Edition 3, 101 pages
ISO records a 101 page draft prepared by ISO/IEC JTC 1/SC 7, replacing the 2018 second edition. The ballot runs for 12 weeks from 14 September 2026.
Same four purposes
The abstract keeps the four purposes: the processes, the guidelines for 15288 and 12207, the information items, and their content and format.
Same applicability
The abstract keeps the same three audiences: users of 15288 and 12207, requirements practitioners, and users of 15289 for the information items.
What is not public
The draft clauses, the change list and the disposition of comments are not public. ISO sells the draft. The public page provides the stage, the committee, the page count and the abstract. It does not provide the text. This site does not reproduce the text and does not turn a summary into a clause level claim.
What the public record suggests, carefully
Three inferences are reasonable, and each is labelled an inference, not a finding. First, a revision that keeps the same scope is likely to refine the existing content rather than replace it, so the current information items remain the right structure. Second, the page count of 101 is in the same range as the second edition, which suggests a revision rather than a new document family. Third, the 12 week ballot and the stage history since February 2026 suggest a normal ISO cycle, not an emergency rewrite. None of these is a statement about a clause.
What to do now
- Read the current clause record and mark the gaps that an assessor would find today. Those gaps are defects against the process the project claims, not preparation for a draft.
- Make sure the four information items exist and are baselined. A missing SRS on a 12207 project is a current gap.
- Put an owner and a verification method on every requirement. Those two fields carry the most weight in a review and are the most often missing.
- Record the edition and the clause set each specification cites. When the new edition is published, the reference update is then a controlled change, not a search.
- Choose a planning date and put it in the project calendar. The site's estimate is 12 September 2027; your date is yours.
Run the readiness check Open the clause record Back to the stage record
The rules this is built from
Every line names its source. The 60 records are written from the published ISO/IEC/IEEE 29148:2018, in our words, with the clause cited. The revision layer is read from the public ISO stage record and its scope abstract. Where the public record is silent, the page says so.
Clause by clause, and the information items
Each page states the requirement in our words, the evidence an assessor asks for, the common gaps and what to do before the edition changes.
Open the registerThe OpsCon content, labelled
Annex A content is part of a full conformance claim. Annex B is informative. Annex C is the tailoring process.
Open Annex ANo invented date
The DIS is at 40.20. The planning date is an estimate and is labelled wherever it appears.
Read the revision recordThe ISO/IEC/IEEE 29148:2018 text is not reproduced. The DIS requirement text is not public and is not reproduced. The record this site reads is linked on the standards page.