{"id":30202,"date":"2024-04-26T23:30:29","date_gmt":"2024-04-27T03:30:29","guid":{"rendered":"https:\/\/www.oxebridge.com\/emma\/?p=30202"},"modified":"2024-04-29T08:08:42","modified_gmt":"2024-04-29T12:08:42","slug":"iso-90012025-committee-draft-leaked-an-in-depth-look","status":"publish","type":"post","link":"https:\/\/www.oxebridge.com\/emma\/iso-90012025-committee-draft-leaked-an-in-depth-look\/","title":{"rendered":"ISO 9001:2025 Committee Draft Leaked: An In-depth Look"},"content":{"rendered":"<p>We got our hands on the Committee Draft (CD) of ISO 9001:2025, and here&#8217;s my detailed breakdown. No, I can&#8217;t publish the actual document, so don&#8217;t ask.<\/p>\n<p>This appears to be a copy and paste of the &#8220;Secret Draft&#8221; that was written as a precursor to the CD. They sort of skipped the usual working Draft (WD) this time entirely, suggesting they are pushing hard for a 2025 publication date.<\/p>\n<p><span style=\"font-size: 18pt;\"><strong>TL;DR Version<\/strong><\/span><\/p>\n<p>I&#8217;ll have a longer editorial on this thing shortly, but here&#8217;s the attention-deficit version.<\/p>\n<p>If you hated ISO 9001:2015, you will still hate this. They don&#8217;t fix anything, but (so far) they haven&#8217;t added any new world-breaking requirements. In fact, the new requirements are minimal. This may change with the next version, the DIS (Draft International Standard), but I doubt it.<\/p>\n<p>The new standard keeps nearly all the problems, errors, mistakes, blank clauses, non-requirement requirements, etc. from the 2015 version. Thsi is likely due to TC 176&#8217;s slavish adherence to the Annex SL core text.<\/p>\n<p>OMG, do the 100-year old, dimbulb TC 176&#8217;ers want you to know they are hip. They name-drop so many awkward and already dated terms like &#8220;<em>VR<\/em>&#8221; and &#8220;<em>Metaverse,<\/em>&#8221; you&#8217;d think they actually know how to boot their own computers.<\/p>\n<p>The standard adds a massive annex that reads like a consultant&#8217;s handbook to implementing ISO 9001. This was copied and pasted from the TC 176 document<em><strong> ISO 9001 for Small Enterprises<\/strong><\/em> published in 2016. This will increase the cover price immensely, as the page count is about to double or triple. The content is meh.<\/p>\n<p>Most of the clauses that would require TC 176 to actually know what happens on a shop floor &#8212; like all of clause 8! &#8212; remain largely untouched. They spent a lot of time twiddling words in the leather-elbow parts, like COTO.<\/p>\n<p>TC 176 still has no idea what a QMS actually is, and they break the PDCA and process approach midway through the standards.<\/p>\n<p><span style=\"font-size: 18pt;\"><strong>Changes to Clauses<\/strong><\/span><\/p>\n<p><strong>0.0 Introduction<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No real changes<\/p>\n<p style=\"padding-left: 40px;\">Still maintains the lie that &#8220;<em>risk-based thinking<\/em>&#8221; is part of the process approach. This was never true; still insists that risk-based thinking is to replace preventive action.<\/p>\n<p style=\"padding-left: 40px;\">Contains errors, such as still referring to ISO 9001:2008 &#8212; LOL.<\/p>\n<p><strong>1.0 Scope<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes<\/p>\n<p><strong>2.0 Normative references<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes, still only references ISO 9000<\/p>\n<p><strong>3.0 Terms and definitions<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Now adds definitions for: organization, interested party (stakeholder), top management, management system, policy, objective, risk, process, competence, documented information, performance, continual improvement, effectiveness, requirement, conformity, nonconformity, corrective action, audit, measurement, monitoring.<\/p>\n<p style=\"padding-left: 40px;\">This section like to get excised; the CD of ISO 9001:2015 also included definitions which were later taken out.<\/p>\n<p style=\"padding-left: 40px;\">Definition of risk is presented as &#8220;<em>effect of uncertainty&#8221;<\/em> and still claims it can be either &#8220;<em>positive or negative<\/em>&#8220;<\/p>\n<p style=\"padding-left: 40px;\">New definitions are added, rather than just referring to ISO 9000. Includes definition of &#8220;documented information,&#8221; which still insists it refers to both documents and records simultaneously.<\/p>\n<p style=\"padding-left: 40px;\">Still no definitions for &#8220;<em>strategic direction<\/em>&#8221; or &#8220;<em>opportunity<\/em>,&#8221; despite the terms being crucial for understanding the standard.<\/p>\n<p><strong>4.0 Context of the Organization<\/strong><\/p>\n<p style=\"padding-left: 40px;\">CD continues to present sub-clauses in the wrong order. You can&#8217;t identify issues until AFTER you identify your stakeholders, you window-licking morons! Just because Dick Hortensius is dyslexic doesn&#8217;t mean you need to copy and paste his mistakes.<\/p>\n<p><strong>4.1 Understanding the Organization and Its Context<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Adds climate change language from the ISO 9001:2015 Amendment 2024. Still didn\u2019t fix the error that the text of the clause never discusses \u201c<em>context<\/em>,\u201d and the standard never explains what that means.<\/p>\n<p><strong>4.2 Understanding the needs and expectations of interested parties<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Adds climate change language from the ISO 9001:2015 Amendment 2024.<\/p>\n<p style=\"padding-left: 40px;\">Minor language tweaks, no new requirements.<\/p>\n<p><strong>4.3 Determining the scope of the quality management system<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Minor language tweaks, no new requirements.<\/p>\n<p><strong>4.4 Quality management system and its processes<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Minor language tweaks, no new requirements.<\/p>\n<p><strong>5.0 Leadership<\/strong><\/p>\n<p><strong>5.1 Leadership &amp; Commitment<\/strong><\/p>\n<p><strong>5.1.1 General<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Adds requirements for top management to &#8220;<em>promote ethics and integrity<\/em>&#8221; and &#8220;<em>determine, implement and improve the organization\u2019s mission, vision and values, and promoting an aligned quality culture.<\/em>&#8221; More unenforceable platitudes keeping the clause largely useless and un-auditable.<\/p>\n<p style=\"padding-left: 40px;\">This means the rumors of a new clause related to the &#8220;culture of quality&#8221; were bogus. They just added a tiny note.<\/p>\n<p style=\"padding-left: 40px;\">The bit about &#8220;ethics and integrity&#8221; will ensure that ISO, itself, never adopts this standard. Snort.<\/p>\n<p><strong>5.1.2 Customer focus<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>5.2 Policy<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>5.3 Organizational Roles Responsibilities and Authorities<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>6.0 Planning<\/strong><\/p>\n<p><strong>6.1 Actions to address risks and opportunities<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Largely improved. Now distinguishes more clearly the difference between risk and opportunity. Adds sub-clauses 6.1.1.1 for risks, and 6.1.1.2 for opportunities.<\/p>\n<p style=\"padding-left: 40px;\">Still no requirement for procedure, process, records, root cause, or any legacy preventive action language, so this will remain a huge flaw in ISO 9001. TC 176 predictably ignored the world\u2019s feedback on \u201c<em>risk-based thinking<\/em>.\u201d<\/p>\n<p><strong>6.2 Quality objectives and planning to achieve them<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Adds a bizarre change now requiring that objectives be measurable only \u201c<em><strong>if practicable<\/strong><\/em>.\u201d Huge step backwards. Objectives should ALWAYS be measurable. tIt&#8217;s like they weren&#8217;t happy making Deming spin in his grave by invoking &#8220;<em>measurement by objectives<\/em>&#8221; in the first place, they want the poor guy to drill his way to China with more &#8220;<em>management by slogans<\/em>.&#8221;<\/p>\n<p style=\"padding-left: 40px;\">TC 176 still does not close the loop on the process approach as the core of a QMS, thinks process metrics and quality objectives are different things.<\/p>\n<p style=\"padding-left: 40px;\">6.2.2 maintains the cringeworthy \u201c<em>who, what, where,<\/em>\u2026\u201d language of Annex SL and ISO 9001:2015. Remains a blank clause, with not actual requirements. Still no editors stepping in to fix this glaring flaw.<\/p>\n<p><strong>6.3 Planning of changes<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes<\/p>\n<p><strong>7.0 Support<\/strong><\/p>\n<p><strong>7.1 Resources<\/strong><\/p>\n<p><strong>7.1.1 General<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>7.1.2 People<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>7.1.3 Infrastructure<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Continues to put the requirements into the note, keeping the error from ISO 9001:2015.<\/p>\n<p><strong>7.1.4 Environment for the operation of processes<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Continues to put the requirements into the note, keeping the error from ISO 9001:2015. Maintains the bonkers language on \u201csocial and psychological\u201d factors such as \u201c<em>emotionally protective<\/em>\u201d workplace. Adds new suggestions to consider \u201c<em>technological<\/em>\u201d and \u201c<em>cultural<\/em>\u201d aspects. The \u201c<em>technological<\/em>\u201d note adds cringeworthy name-drops of words like \u201c<em>AI, Metaverse, VR, chatbots.<\/em>\u201d Absolutely embarrassing.<\/p>\n<p><strong>7.1.5 Monitoring and measuring resources<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Still does not require a calibration log!<\/p>\n<p><strong>7.1.6 Organizational knowledge<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>7.2 Competence<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>7.3 Awareness<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>7.4 Communication<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Maintains the cringeworthy \u201c<em>who, what, where<\/em>,\u2026\u201d language of Annex SL and ISO 9001:2015. Remains a blank clause, with no actual requirements.<\/p>\n<p><strong>7.5 Documented information<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes except for possibly some minor word tweaks. Continues to mix up \u201c<em>documents<\/em>\u201d and \u201c<em>records<\/em>,\u201d keeping the section confusing and rambling.<\/p>\n<p><strong>8.0 Operation<\/strong><\/p>\n<p><strong>8.1 Operational planning and control<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes, maintains ISO9001:2015\u2019s errors of (a) not clearly explaining that the standard views \u201c<em>operational<\/em>\u201d and \u201c<em>organizational<\/em>\u201d processes differently, (b) not fixing the clause so that it can in any way be understood without a consultant, and (c) still tossing \u201coutsourced processes\u201d over the 8.4 rather than fleshing out the real ways companies should manage these.<\/p>\n<p><strong>8.2 Requirements for products and services<\/strong><\/p>\n<p><strong>8.2.1 Customer communication<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Adds a cringeworthy note defining what \u201c<em>customer communication&#8221;<\/em> is \u2013 really? we needed that? \u2013 then namedrops terms like \u201c<em>web site content, Frequently Asked Questions<\/em>\u201d as if it was written during the AOL era.<\/p>\n<p><strong>8.2.2 Determining the requirements related to products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Maintains bizarre language that this applies BEFORE a customer even exists (\u201c<em>products and services <strong><span style=\"text-decoration: underline;\">to be<\/span><\/strong> offered to customers\u2026<\/em>\u201d) Still haven\u2019t fixed that.<\/p>\n<p><strong>8.2.3 Review of requirements related to products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Still a mess (\u201c<em>to be offered\u2026<\/em>\u201d) and largely repeats what was said in 8.2.2. Old 2000 language was better, but they still won\u2019t restore it.<\/p>\n<p><strong>8.2.4 Changes to requirements for products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.3 Design and development of products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Maintains the jumbled nature of this clause from 2015, implying that design validation happens before you create design outputs, Again, the \u00a02000 language was better, but they won\u2019t restore it. Agile folks, you will still hate this.<\/p>\n<p style=\"padding-left: 40px;\">The fact that this was not touched at all so far suggests that none of the TC 176 authors understand product design. The clause <em><strong>STILL<\/strong> <\/em>does not discuss service design, despite it being in the title of the clause. This speaks to a gross lack of subject matter experts on the committee.<\/p>\n<p><strong>8.4 Control of externally provided processes, products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. This maintains the confusing repetition of requirements in 8.4.1 and 8.4.2. Also (again) the fact this wasn\u2019t touched suggests no actual SMEs are working on this standard. TC 176 doesn\u2019t know how supply chain management and procurement work.<\/p>\n<p style=\"padding-left: 40px;\">Still doesn\u2019t require that you communicate with suppliers in actual writing, so still no PO requirement!<\/p>\n<p style=\"padding-left: 40px;\">Outsourced process still get no love.<\/p>\n<p><strong>8.5 Production and service provision<\/strong><\/p>\n<p><strong>8.5.1 Control of production and service provision<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.5.2 Identification and traceability<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.5.3 Property belonging to customers or external providers<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.5.4 Preservation<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.5.5 Post-delivery activities<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. This clause still doesn\u2019t know what it wants to say.<\/p>\n<p><strong>8.5.6 Control of changes<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>8.6 Release of products and services<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Still maintains the horrid 2015 error or switching terms mid-standard. Until this clause, \u201c<em>measurement and monitoring<\/em>\u201d has been used to refer to inspection and testing. Now, at clause 8.6, they call inspection and testing \u201c<em>planned arrangements.<\/em>\u201d Readers would have no way to know this. Clause is still not about \u201c<em>release<\/em>\u201d (delivery) at all.<\/p>\n<p style=\"padding-left: 40px;\">Oh, and still no actual delivery clause! So product never needs to be shipped. TC 176 has never set foot in an actual company, I think.<\/p>\n<p><strong>8.7 Control of nonconforming outputs<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes, and we desperately needed fixes here.<\/p>\n<p><strong>9.0 Performance evaluation<\/strong><\/p>\n<p><strong>9.1 Monitoring, measurement, analysis and evaluation<\/strong><\/p>\n<p><strong>9.1.1 General<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes, remains nearly entirely useless. Never ties back to process approach, so breaks PDCA entirely.<\/p>\n<p><strong>9.1.2 Customer satisfaction<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes.<\/p>\n<p><strong>9.1.3 Analysis and evaluation<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Again, never ties back to process approach, so breaks PDCA entirely. Treats \u201c<em>performance and effectiveness of the quality management system<\/em>\u201d as something totally apart from process approach.<\/p>\n<p style=\"padding-left: 40px;\">Keeps \u201c<em>statistical techniques<\/em>\u201d as an afterthought note, ensuring problems for companies that use them.<\/p>\n<p style=\"padding-left: 40px;\">Fails to alert the reader to the (idiotic) fact that now, in clause 9, TC 176 is using the term \u201c<em>monitoring and measurement<\/em>\u201d in an entirely different context. Now it is NOT about inspection testing, despite that being understood up until clause 8.7. So, for those keeping tarack at home:<\/p>\n<p style=\"padding-left: 80px;\"><strong>Clauses 4 through 8.5<\/strong>: \u201c<em>monitoring and measuring<\/em>\u201d means inspection and testing.<\/p>\n<p style=\"padding-left: 80px;\"><strong>Clause 8.6:<\/strong> now, inspection and testing are referred to as \u201c<em>planned arrangements<\/em>\u201d you do prior to \u201c<em>release<\/em>.\u201d<\/p>\n<p style=\"padding-left: 80px;\"><strong>Clauses 9 &amp; 10:<\/strong> \u201c<em>Monitoring and measurement<\/em>\u201d now means a more holistic (and literal) monitoring and measurement of data related to the QMS, and not inspection and testing.<\/p>\n<p style=\"padding-left: 40px;\">Got it?<\/p>\n<p><strong>9.2 Internal audit programme<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Weird: changes name of clause to add the word \u201c<em>programme<\/em>.\u201d Then uses the word, but not consistently. Refers to auditing as a \u201cprocess\u201d then \u201c<em>programme<\/em>\u201d and then \u201c<em>process<\/em>\u201d again, <em><strong>all in one single sentence<\/strong><\/em>. What a bunch of shitbirds.<\/p>\n<p style=\"padding-left: 40px;\">Still no requirement or language about \u201c<em>process-based auditing<\/em>,\u201d so \u2013 again \u2013 PDCA and the process approach are abandoned by the time we get to clause 9.<\/p>\n<p style=\"padding-left: 40px;\">Odd how bad this is, since the TC 176 consultants love to write books about auditing, and they appear to have no clue how to do it.<\/p>\n<p><strong>9.3 Management review<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Nio changes. Maintains 2015\u2019s errors of (a) failing to tie back to PDCA and process approach, (b) conflating \u201c<em>process performance<\/em>\u201d with \u201c<em>conformity of products and services<\/em>\u201d when the two are very, very different things, (c)<\/p>\n<p><strong>10.0 Improvement<\/strong><\/p>\n<p><strong>10.1 General<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Still largely repeats what is later said in 10.3, making them effectively duplicates. Adds cringeworthy note namedropping terms like \u201c<em>incremental and breakthrough change<\/em>,\u201d \u201c<em>innovation and re-organization<\/em>,\u201d and \u201c<em>emerging technology<\/em>.\u201d<\/p>\n<p><strong>10.2 Nonconformity and corrective action<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes, doesn\u2019t\u2019 fix the confusion between this clause and 8.7\u2019s nonconformities. Still doesn\u2019t require a procedure because TC 176 is doing an outreach program for illiterates.<\/p>\n<p><strong>10.3 Continual improvement<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes. Still never ties back to processes or anything in clause 4 at all, so breaks the PDCA cycle one last time.<\/p>\n<p><span style=\"font-size: 18pt;\"><strong>New Appendix A<\/strong><\/span><\/p>\n<p>The standard adds an absolutely huge new appendix called &#8220;<em>Guidance on Use of this International Standard<\/em>.&#8221; While this was clearly written by a consultant, this will have some competing and contradictory ramifications. First, it might confuse people more, pushing folks to have to go out and hire a consultant. But, alternatively, this might cripple the sale of all those TC 176&#8217;er books, since this section essentially <em><strong>IS<\/strong> <\/em>an entire implementation guide. A shitty one, but still, a guide.<\/p>\n<p><em><strong>UPDATE<\/strong><\/em>: I since learned this is just the 2016 publication <em>ISO 9001:2015 for Small Enterprises -What to Do &#8211; Advice from TC 176<\/em> literally copied and pasted and put into the CD. The only change is where the original document says things like &#8220;<em>you should do XYZ<\/em>&#8221; the CD text says &#8220;<em>the <strong>organization<\/strong> should do XYZ<\/em>.&#8221; So TC 176 didn&#8217;t even work on this part during their breathless scrambling to develop ISO 9001:2025.] The problem here is that this publication is &#8212; as the title says &#8212; for SMALL enterprises, and the ISO 9001 standard is for everyone. So I have no idea what the authors were thinking of by including it, since it <em><strong>reduces<\/strong> <\/em>the scope of use for ISO 9001, and doesn&#8217;t expand it.<\/p>\n<p>I won&#8217;t go over this in detail, because it is absolutely massive. Here are some brief first impressions:<\/p>\n<p style=\"padding-left: 40px;\">Includes subsections on Clarification of Structure and Terminology, Clarification of Concepts, and then long-winded clarifications on each of the requirements clauses from 4 through 10.<\/p>\n<p style=\"padding-left: 40px;\">Repeats the mindbogglingly bad sentence, \u201c<em>Organizational knowledge is the specific knowledge of the organization<\/em>.\u201d Good lord, what utter morons these people are.<\/p>\n<p style=\"padding-left: 40px;\">Oh, they try to make a case for the design clause in 8.3 applying to a \u201c<em>coffee-shop<\/em>.\u201d Which is hyphenated, yes.<\/p>\n<p style=\"padding-left: 40px;\">The narrative on \u201c<em>internal audits<\/em>\u201d suddenly starts talking about conducting audits by process, but that was never indicated in the actual requirements of clause 9.2. So there\u2019s some cognitive disconnects here.<\/p>\n<p style=\"padding-left: 40px;\">Namedrops \u201cISO 9000:<span style=\"text-decoration: underline;\">2025<\/span>,\u201d suggesting that 2025 will definitely be the year ISO 9001 itself is published.<\/p>\n<p style=\"padding-left: 40px;\">On the benefit side, there are a few good nuggets amidst the piles of crap. There are a few guidance suggestions for service organizations, to help them understand this despite ISO 9001 still being written for widget manufacturers. So at least the service sector is getting a teeny bit of lip service.<\/p>\n<p><span style=\"font-size: 18pt;\"><strong>Remaining Bits<\/strong><\/span><\/p>\n<p>The last parts are:<\/p>\n<p><strong>Appendix B: Other Standards<\/strong><\/p>\n<p style=\"padding-left: 40px;\">Just the usual product placement and up-selling ads for other ISO standards.<\/p>\n<p><strong>Bibliography<\/strong><\/p>\n<p style=\"padding-left: 40px;\">No changes that I noticed.<\/p>\n<hr \/>\n<p><strong><span style=\"color: #ff0000;\">UPDATE<\/span> 29 April, 2024:<\/strong> Updated the text above to clarify that the new Appendix A is actually the 2016 publication, ISO 9001 for Small Enterprises, now plopped into the ISO 9001 standard.<\/p>","protected":false},"excerpt":{"rendered":"<p>Oxebridge has obtained the CD version of the new ISO 9001:2025 standards, and presents a breakdown of the changes and additions.<\/p>","protected":false},"author":2,"featured_media":30205,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","mc4wp_mailchimp_campaign":[],"footnotes":""},"categories":[5],"tags":[8471,158,43,8470,7934,251,42],"class_list":["post-30202","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-opinion","tag-cd","tag-committee-draft","tag-iso","tag-iso-9001-2025-cd","tag-iso-90012025","tag-quality-management","tag-tc-176","et-has-post-format-content","et_post_format-et-post-format-standard"],"_links":{"self":[{"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/posts\/30202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/comments?post=30202"}],"version-history":[{"count":8,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/posts\/30202\/revisions"}],"predecessor-version":[{"id":30233,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/posts\/30202\/revisions\/30233"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/media\/30205"}],"wp:attachment":[{"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/media?parent=30202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/categories?post=30202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oxebridge.com\/emma\/wp-json\/wp\/v2\/tags?post=30202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}