The context and interested-parties registers — the auditor's first stop
Clause 4 (context of the organization) is the external auditor's first stop, because it quickly reveals whether your system is built on your reality or copied from a template. In goiso it is two separate registers, because they are two separate requirements in an auditor's eyes.
4.1 — Context issues
What actually affects your ability to achieve your system's outcomes? Each issue is recorded with its kind:
- Internal: ageing equipment, high turnover on the night shift, a shortage of maintenance staff.
- External: power outages, a regulatory change, seasonal production.
Each issue has an impact field: how it specifically bears on the management system. That field is what separates a real register from a decorative list.
4.2 — Interested parties
Who has a stake in or an effect on your system, and what they require of you: workers and their representatives, regulators, customers, suppliers, insurers, neighbours. The requirements field is the heart of the clause — the auditor asks: "You identified the parties; which of their requirements bind you?"
Freshness makes the difference
Every row carries a review stamp: who reviewed it and when. The stamp is set automatically on creation and edit, and you renew it manually by selecting rows and pressing "Confirm review" — without changing a word of their content.
The clause colour follows from it:
| State | Colour |
|---|---|
| The register is empty | Red |
| It has an active row unreviewed for more than 12 months | Amber |
| Not empty and every active row reviewed within 12 months | Green |
One forgotten row pulls the whole clause down — deliberately so. A context register written once three years ago is not context, and it is the first thing an auditor exposes by asking: "when did you last review this?"
Archive, don't delete
When an issue ends or a party leaves the picture, archive it rather than deleting: it drops out of the colour calculation and out of the review inputs, while remaining in your record as history — and restoring it is one click.
What feeds on them
- Clauses 4.1 and 4.2 in every standard you have activated (45001, 50001, 41001) read the registers directly — no document to upload, no attestation to click.
- Management review: the "context changes" section shows the delta since the last sealed review — what was added, edited, archived — not the whole list. Management is asked about what changed, which is literally what clause 9.3 requires (see Management review).
Where to start
Sit for half an hour and write five internal and five external issues you already know by heart, then name your five biggest parties and one requirement for each. That is enough to turn the clause green — the rest is maintained by an annual review just before the management-review session.