Home / Revision record
The public record of ISO/IEC DTS 25568
Everything on this page comes from the official ISO record, read on 20 October 2026. The draft is at stage 50.00. The clause text is not published, so this page states what the record contains and marks the rest as not public.
Identity
Identity
What the record says it is.
| Designation | ISO/IEC DTS 25568 |
|---|---|
| Title | Information technology, Artificial Intelligence, Guidance on addressing risks in generative AI systems |
| Edition | 1, first edition |
| Deliverable | Draft Technical Specification, published as ISO/IEC TS 25568, on publication |
| Status | Under development |
| Stage | 50.00, Final text received or FDIS registered for formal approval, recorded 29 September 2026 |
| Next stage | 50.20, Proof sent to secretariat or FDIS ballot initiated: 8 weeks |
| Committee | ISO/IEC JTC 1/SC 42, Artificial intelligence |
| ICS | 35.240.01, Application of information technology in general |
| Certifiable | No. A Technical Specification is guidance, and no certification scheme exists for it. |
| Prior edition | None. This is the first edition, so there is no earlier text to transition from. |
Lifecycle
Lifecycle
The whole public clock.
These are the recorded stages and their dates. The empty rows are stages ISO has not recorded yet. This site does not invent a date for them.
- 10.9912 February 2025New project approved
done - 20.0021 July 2025New project registered in TC/SC work programme
done - 20.2018 March 2026Working draft study initiated
done - 20.6014 April 2026Close of comment period
done - 30.005 May 2026Committee draft registered
done - 30.208 May 2026CD consultation initiated
done - 30.604 July 2026Close of comment period
done - 30.9911 September 2026CD approved for registration as DIS
done - 50.0029 September 2026Final text received or FDIS registered for formal approval
current - 50.20not recordedProof sent to secretariat or FDIS ballot initiated: 8 weeks
next - 60.00not recordedInternational Standard under publication
future - 60.60not recordedInternational Standard published
future
Scope
The published scope
What the guidance covers, in ISO's own summary.
The published abstract says the document gives guidance on addressing risks in generative artificial intelligence systems. It names three subjects: the objectives of generative AI systems when risks are identified; the risk sources and the stakeholders exposed to them across the life cycle; and guidance for risk analysis, risk treatment and controls.
Published
The abstract above is public. It names the objectives of generative AI systems when risks are identified, the risk sources and the stakeholders exposed across the life cycle, and guidance on risk analysis, risk treatment and controls.
Not published
- The clause text of the draft, including the wording of any requirement or recommendation
- The titles and contents of its clauses other than what the abstract names
- Any annex, its number or its title
- The number of pages
- The date the approval ballot closes at stage 50.20
- Any national adoption or any transition arrangement
The date
The date
Why the site uses 17 February 2027, and what it is not.
The date is a planning estimate: 120 days from the build date of 20 October 2026, at a point when ISO records stage 50.00. ISO has not announced a publication date. The record shows no date for 50.20, 60.00 or 60.60, so any date for those stages would be invented.
Use the date to schedule work. Do not use it as a contract term, a regulatory date or a transition deadline. If an auditor asks where it comes from, the answer is on this page and in the data file behind it.
What changes at the next stage
- At 50.20 the proof is sent to the secretariat or the approval ballot opens for eight weeks. The record gains a date.
- At 60.00 the text is under publication. The title and identifiers are fixed.
- At 60.60 it is published. The clause text becomes public, and this record is rebuilt from it rather than from the standards it currently reads.
Watch
Change watch
How a change reaches you.
The refresh script reads the ISO record and the stage feed, compares them with the data file behind every page, and fails loudly on any difference. The watch email carries that difference. It covers the stage, the stage date, the title, the committee, the ICS and every recorded date, and it also fires when the requirement record is refreshed after publication.