Annex SL Explained: Simplifying Management Systems for ISO Standards

As noted, there are many reasons for management system standards (MSS) writers to adopt the foundational Annex SL., including

• Eliminating conflicts in MSS platforms
• Faster development of standards
• Less duplication of concepts, terms and potentially shared text
• Less low value revisions to common or shared areas
• Integrating high level, common business management goals, issues, needs

Annex SL addresses these needs by alignment of similar clauses. This, in turn, fosters easier integration by adopting similar formats and similar terms and definitions. In addition, this addresses key high-level components which are being driven by market forces such as:

Risk Management

• Annex SL. now elevates the preventive and corrective action concept into a more encompassing risk assessment process. It proactively wants risks to be anticipated and addressed in the planning phase, not as something to which one reacts. Essentially, it asks the organization to use the inputs it has gained, add its experience and provide a reasonable analysis of risks and successful responses to them. It also asks for a more measurable approach to planning, using metrics of what will be attained that are meaningful to support implementation.

Accessible Documentation

• Recognizing the reality of more modern methods of information dissemination, Annex SL outlines additional, specific requirements to both document and communicate the quality management system. An example is making sure that there are true work instructions written down for everyone in the organization, even if a set of tasks seem obvious. The idea is reasonable since documentation not only helps maintain consistency of tasks between workers, it helps the organization plan for growth in adding or replacing resources. 

This expanded approach to documentation is meant to allow and support other means of viewing, storing, revising and distributing documentation such as via internal and external networks (i.e. cloud computing) and a wider array of formats.

Wider Involvement

• Annex SL asks standard drafters to consider the “Context of the Organization.” This requires the company (and the auditors who are being asked to certify their quality system) to listen not only to customers, employees and suppliers, but also to those whose operations may also affect such as the communities in which they operate or have significant influence. 

Quality planning then becomes a broader search to uncover potentially relevant issues that may affect operations, and the development of a quality policy for a “newer age” for instance as a deeper information base to decide how risks might be better anticipated.

High-level structure

The major clause numbers and titles of all management system standards will be identical. They are

Introduction 

1. Scope 
2. Normative references 
3. Terms and definitions 
4. Context of the organization 
5. Leadership 
6. Planning 
7. Support 
8. Operation 
9. Performance evaluation 
10. Improvement.

The Introduction, Scope and Normative references will have content that are specific to each discipline and each standard.

Overall, there is a reorganizing of management system requirements into this structure that may be unfamiliar to those using and assessing current MSS. However, some management system standards (such as ISO 22301:2012 Societal security – Business continuity management systems – Requirements) have already successfully migrated to this new structure.