Draft International Standard, close of voting
ISO 20996 Revision Checker
ISO/IEC DIS 20996 gives cloud service customers guidance on business continuity and resilience. The ballot closed on 24 September 2026. This page records where the draft stands and checks your estate against the continuity evidence a customer will be asked for, in about a minute.
328 days to the planning date57 cited requirements4 markets covered
Where does your cloud estate stand?
Five answers. The check compares them with the record and returns a position, the gaps that matter and three dated actions. Nothing is sent anywhere and no account is needed.
Your position
| Area | Your answer | Reads as |
|---|
Three dated actions
This is a reading of your answers against a public record. It is not an audit, not legal advice and does not certify anything. The DIS text is not public, so no clause of it is assessed.
What the public record says today
| Status | Under development, stage 40.60 Close of voting |
|---|---|
| Stage date | 2026-09-24 |
| Planning date | 2027-09-13, 328 days away, an estimate and not an ISO commitment |
| Committee | ISO/IEC JTC 1/SC 38 |
| Edition and length | Edition 1, 45 pages |
| Classification | ICS 35.210 |
| Official source | ISO record ISO/IEC DIS 20996 |
The ballot closed on 24 September 2026. ISO has not yet recorded the outcome. The next recorded stages are 40.92 if the draft is referred back, 40.93 if a new ballot is decided, and 40.99 if it is approved for registration as a Final Draft International Standard. Each of those has a different consequence for your timetable, which is why the watch exists. Read the full timeline.
What does the draft cover, and what can this site state?
ISO describes the document as guidance to cloud service customers on business continuity and resilience when using cloud services. That is the whole of the public description. The draft is 45 pages and ISO sells it, so its clause list and its annexes are not public.
Two things follow. First, nobody outside the committee can truthfully show you the clause text today, and any site that does is guessing or breaching copyright. Second, the preparation work does not have to wait. The guidance sits on the continuity management system a customer already runs, and that system is published, held here, and cited.
So this site records the stage file exactly, states plainly what is not held, and gives you the baseline register with a cloud-specific test for every clause. What is missing, and why.
- Held: the ISO stage record, dates, scope description, committee, page count and classification.
- Held: the ISO 22301:2019 continuity baseline, 57 clauses, exported and preflighted with zero placeholders.
- Not held: the DIS clause structure, its annexes and any requirement text. Nothing on this site is presented as one.
The rules this is built from
Every requirement on this site is written from a held rule and points to the clause it came from. Nothing is invented while you wait.
- Read from the real rules, not invented
- 57 official requirements behind it
- Cross-checked against 7 continuity and resilience frameworks
- Check any line yourself
How the record is made and where each source comes from. The continuity baseline is ISO 22301:2019, read here.
What should a cloud customer have ready before publication?
The short answer: a scope that names the services and regions, a restore you have run yourself, contracts that state recovery, data return and exit, and a dated plan with an owner. The check above turns those into a position. The register turns them into 57 citable requirements.
Before the ballot outcome
Fix the scope and run one restore. Those two answers change the position more than any document rewrite.
Before the FDIS
Review the three contract terms on every critical service and record what the provider says in writing.
Before publication
Put the results through a management review with owners and dates, so the evidence is current on the day.
Two ways to use it
Preparation kit, one off
USD 799
The register of 57 continuity requirements, the evidence list and a dated plan, as PDF, CSV and XLSX.
Buy the kitChange watch, monthly
USD 49 a month
An email when the stage record, the planning date or the baseline changes, with what changed and the source.
Start the watchOne click to Stripe. No account needed. Prices in United States dollars, charged by Stripe. Cancel the watch any time.
Questions people ask
Is ISO/IEC DIS 20996 published yet?
No. ISO records the document as under development at stage 40.60, close of voting, with that stage dated 24 September 2026. It is a draft International Standard in the enquiry phase, not a published standard.
When is ISO/IEC 20996 expected to be published?
The planning date used here is 13 September 2027. It is an estimate derived from the stage record, not a date ISO has recorded. ISO has not published a publication date, and the ballot outcome is not yet recorded.
What does the draft cover?
ISO describes it as guidance to cloud service customers on business continuity and resilience when using cloud services. The draft runs to 45 pages. Its clause and annex structure is not public, so this site states no clause of it.
What does the free check actually measure?
Five facts about your cloud estate: how many services carry a critical activity, whether a critical service has been restored or failed over in the last year, whether contracts state recovery, data return and exit terms, whether the scope names services and regions, and whether a dated plan exists. The result is a reading of your answers against the record, not a certification.
What is in the preparation kit?
The register of 57 continuity requirements, each stated in our own words and cited to its clause, with the evidence an auditor asks for, the common gaps, a cloud-specific test, and a dated plan that works back from the planning date. Delivered as PDF, CSV and XLSX.
What does the change watch send?
An email when the ISO stage record changes, when the planning date moves, or when the baseline or the four-market view changes. Each alert quotes the old value, the new value and the source.