Cross-standard coverage: one act, several certificates

A facility holding a safety certificate, a quality one and an environmental one lives with a recurring question: are we redoing the same work for every certificate? A management review for safety, another for quality, a third for environment — is that three meetings? And a document register — is that three registers?

The answer is in the standards themselves: their structure is shared (Annex SL), and many of their clauses ask the same question in different words. goiso does not tell you that as a slogan; it shows it as a number from your own data.

How does the system know two clauses are one?

By the simplest and most honest evidence available: the shared signal.

Every automatically measured clause is bound to an "operational signal" — a measurement rule that reads one specific register in your platform: "a recently sealed management review", "a controlled document register", "live, measurable safety objectives". If a clause in ISO 45001 and a clause in ISO 41001 are bound to the same signal, then in measurement terms they are one question. That is not a guess but a definition: the platform compares no texts and judges no title similarity.

Why do we refuse textual similarity? "Internal audit" in a safety standard and "internal audit" in a quality standard share a name but not a meaning: auditing the safety system is not auditing the quality system. Merging them is a compliance judgement, not a screen's inference — so we do not merge them.

And where do you see it?

In two places, both of which appear on their own with no setup:

1. The coverage panel at the top of the compliance page: one row per shared signal, with chips for the clauses it satisfies across your standards, the widest-reaching first. Its header line sums it up: how many signals cross, how many clauses they satisfy, across how many standards.
2. A line inside a clause when you expand it: "The same signal also satisfies: …" with links to its counterparts. A line, not a button — context that reassures you your work is counted twice, not an action to click.

Three constraints guard the number's honesty

1. Only the standards you activated. Telling you that your work "satisfies a clause in ISO 41001" when you do not track 41001 is advertising inside a compliance screen, not coverage information. The panel reads what you activated.

2. Shared means two standards or more. A signal belonging to a single standard is not integration, and showing it as "1" makes an empty box look full. So it is not shown.

3. Cards never cross. A clause that takes its colour from your work cards belongs to its own standard: your cards, your plan. Crossing applies only to automatically measured signals.

And the panel hides itself entirely when nothing crosses for you — with a single standard, for instance. An empty panel under a grand title reads as a gap in the platform, not a truth about your state.

What crosses today?

The universal governance signals — tools no management system is without:

And the operational signals — what you do in the field, not on paper:

Why "and its counterparts"? Because a signal does not know a clause number; it knows the register it reads. The same hazard survey satisfies clause 6.1.2 in ISO 45001, the "risk measurement programme" item in the Jordanian model, and the site risk-survey clause in ISO 41001 — three numbers for one act.

So one management review you seal satisfies clause 9.3 in every standard you track. One document register you control satisfies 7.5 in all of them. And one job description its holder acknowledges satisfies 5.3 across six standards.

Measured, but not yet crossing

Some signals the platform measures automatically live in a single standard, so they do not appear on the panel — the second constraint above is why: shared means two standards or more. Today that is the case for quality objectives, environmental objectives, energy objectives and facility-management objectives: each has exactly one standard asking for it in our catalogue. They are measured and they colour their clause like any other signal, but they do not count as integration until a second standard shares them.

This is not a gap we hide: the panel shows what actually crosses for you, not what we wish did. The moment a signal is bound to a clause in a second standard it appears on its own, with no setup from you — which is what happened to evaluation of legal compliance once three standards read it instead of one.

One deliberate exception: objectives

Clause 6.2 asks each management system about its own objectives: quality objectives for the quality system, energy objectives for the energy system. Reading the whole objectives register as one signal would tell you that an energy objective greens "quality objectives" in ISO 9001 — a claim that collapses in front of the first auditor.

So every objective carries its scope when created (safety · quality · environment · energy · facility), and objectives are read against each standard by its scope. Crossing survives wherever it is true: one safety objective satisfies 6.2 across every safety standard you track — the international one and the local regulatory ones alike.

Where to find it: sidebar → Compliance — the panel at the top of the page, and the line inside any clause you expand.