ISO 19600
ISO compliance standard
ISO 19600, Compliance management systems - Guidelines, is a compliance standard introduced by the International Organization for Standardization (ISO) in April 2014. As its title suggests, it operates as an advisory standard and is not used for accreditation or certification.
This standard was developed by ISO Project Committee ISO/PC 271, which was chaired by Martin Tolar. In recent times technical committee ISO/TC 309 has been created and the maintenance and future development of ISO 19600 will be undertaken by members of this committee.
Currently, ISO/TC 309 is in the process of developing ISO/DIS 37301 [1], which is expected to replace ISO 19600. The main difference between these two standards is that, when published, ISO 37301 will establish requirements for the implementation of a compliance management system, as opposed to USO 19600 which only provides recommendations. This means that in the future, organizations can have their compliance management system (CMS) verified through an independent third party [2]
Origins
Standards Australia proposed a new ISO standard, based on the existing Australian standard "AS 3806 - Compliance Programs", which was issued in 1998 and updated in 2006. The handbook to accompany AS 3806 was developed by a working group of the Australasian Compliance Institute members. This standard is more widely used in the financial industry, being endorsed by Australian Prudential Regulation Authority and the Australian Securities & Investments Commission. The published version of ISO 19600:2014 is similar to AS 3806:2006 standard, and will replace it.
“ISO 19600” enters the record as iSO compliance standard. Crown Archives preserves that source wording while asking what compliance and standard can confirm, complicate or overturn.
Why this record matters
“ISO 19600” is worth following because a concise public description often conceals a longer documentary argument. Here, compliance and standard provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 29, 2024. The linked authority identifier is Q18752526. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2014, 1998 and 2006.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “ISO 19600”, its source revision and the description used here.
- Expand the search: follow ISO 19600 primary sources, ISO 19600 archive and compliance research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “ISO 19600”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “ISO 19600” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.