0%
Clause 4

ISO/UNDP 53001 clause 4: what the auditor checks

ISO 53001 clause 4 covers the context of the organization. The auditor checks that SDG-related issues and the expectations of interested parties have been identified, that the scope of the management system is clear and justified, and that the SDGs selected genuinely follow from this analysis rather than from communication choices.

Updated: · edition covered: ISO/UNDP 53001:2026

ISO 53001 clause 4: what the requirement asks for

In ISO 53001, clause 4 is the starting line: an organisation cannot set SDG objectives before it knows where it stands. The reasoning is the one found in every management system standard built on the harmonized structure. The organisation determines the internal and external issues that bear on its ability to achieve the intended outcomes, identifies the interested parties whose expectations matter and decides which of those expectations become requirements, draws the boundaries of the system, and organises its processes into a coherent whole. Everything that follows rests on this foundation: the policy and roles covered by clause 5 on leadership draw directly on it.

What changes when the subject is the SDGs

In a quality standard, a typical external issue is a market trend or a customer demand. Here, reading the context means examining the organisation's contribution to the Sustainable Development Goals (SDGs): what its activity does, for better or worse, to people, ecosystems and the economy, and the goals on which it has real influence. The choice of priority SDGs is rooted in that reading. According to BSI, publisher of the British edition (BS ISO/UNDP 53001:2026), every organisation has to cover SDGs 5, 8 and 13, alongside whichever goals its own context brings out.

The circle of interested parties is also wider than usual: local communities, workers in the supply chain, funders, public authorities and the partners the organisation works alongside, a point that connects with SDG 17 on partnerships. The mandatory goals, such as gender equality under SDG 5, are analysed at this stage too. The auditor then looks for a visible thread running from the mapping of impacts to each goal retained or set aside.

Subclause by subclause: the auditor's angle

SubclauseWhat the auditor seeks to establishHow it is assessed
Understanding the organization and its context (4.1)That internal and external issues linked to the SDG contribution are identified, dated and reviewed, and that they explain the goals selectedDocument review of the context analysis; interview with top management on the trade-offs made; cross-check against the activity observed on site
Understanding the needs and expectations of interested parties (4.2)That relevant interested parties are known, that their expectations are described and that those adopted as requirements can be tracedInterviews with the people in charge of external relations; sampling of a few expectations to follow how each was handled
Determining the scope of the management system (4.3)That the scope is worded without ambiguity, covers the activities that carry the impacts and that every exclusion is justifiedReading of the declared scope; comparison with the sites, activities and entities visited; questions on exclusions
Management system (4.4)That the necessary processes exist, interact and are run as a system rather than as a collection of separate projectsReview of the process map; observation of how processes operate at stage 2; interviews with process owners

Possible findings and what tips the balance

  • Conformity: the context analysis is current, the SDGs selected follow from it in a readable way, and the scope matches what the auditor sees on the ground.
  • Minor nonconformity: an isolated weakness that does not undermine the system's ability to achieve its results, such as an interested party listed without any description of its expectations, or an analysis not revisited after a limited change of activity.
  • Major nonconformity: the weakness compromises the system's ability to deliver its intended outcomes. Examples include a scope that leaves out the most exposed activity without justification, a choice of SDGs with no demonstrable link to the context analysis, or no analysis at all.
  • Opportunity for improvement: a remark that is not a nonconformity, for instance a sound analysis that is rarely used when decisions are taken.
  • What tips the balance: a minor finding becomes major when the gap touches the foundations of the system, namely the scope or the selection of SDGs, or when several minor findings point to a general lack of control.

Gaps often raised on this type of requirement

The standard is new, so no audit history specific to it exists yet. The gaps below are those commonly seen on clause 4 of management systems built on the harmonized structure.

  • A context analysis written once for the certification file and never revisited.
  • A list of interested parties with no expectations attached, or with the same generic expectations for each of them.
  • A scope narrower than the actual activity, with no written justification.
  • A mismatch between the SDGs highlighted in external communication and those the system actually covers.
  • A process map that does not reflect the organisation described by the people interviewed.

Clearing findings raised on context

Clearance rules follow ISO/IEC 17021-1. For a major nonconformity, the organisation corrects the gap, analyses its cause and takes corrective action; the certification body verifies both the correction and the corrective action before any favourable decision. On clause 4, that verification may call for a return visit, because a redefined scope changes what has to be audited.

For a minor nonconformity, the certification body accepts a corrective action plan, and its implementation is examined at the next audit. The audit report is sent within 10 working days and the certification decision is taken no more than 3 weeks after the audit, by people who did not carry out the audit. Details are set out in the certification rules.

Frequently asked questions

Is clause 4 audited at stage 1 or at stage 2?

Both. Stage 1 checks that the context analysis, the interested parties and the scope have been designed consistently with the intended SDG contribution. Stage 2 verifies on the ground that this analysis actually feeds decisions and that the declared scope matches the activities observed. A weakness spotted at stage 1 is reported so that the organisation can deal with it before stage 2.

Can an organisation exclude an activity from the scope?

The scope may be limited to certain sites or activities, provided it is clearly worded and justified. The auditor checks that the exclusion does not serve to set aside the activities with the largest effects on the SDGs. An unjustified exclusion of that kind can lead to a major nonconformity, because it distorts the whole system.

Must the selected SDGs cover all 17 goals?

No. The organisation selects the goals on which it has real influence, based on its context analysis. Three SDGs, 5, 8 and 13, are to be addressed by every organisation, according to BSI, publisher of the British edition (BS ISO/UNDP 53001:2026). The auditor judges whether the choice is coherent, not how broad it is: a handful of well-justified goals carries more weight than an exhaustive list that nobody manages.

Does the auditor interview interested parties outside the organisation?

The audit takes place at the audited organisation. The auditor questions top management and the people in charge, reviews documented information and samples expectations to follow how they were handled. No survey of the interested parties themselves is carried out, but the auditor may rely on the records of exchanges the organisation keeps with them.

Official sources

Gardiant Certification is preparing its application for accreditation by COFRAC. Certificates will be issued once accreditation is granted.

Request a quote