Help · Recognition · Across jurisdictions

Recognition, markets and the metro map

How recognition is scoped to a market or worldwide, how the metro map signals recognition coverage per discipline, and the item-to-credential evidence link.

Recognition is not always global. A body's recognition may apply to one specific market — a country or a defined region — or worldwide. RPF respects that scope on the badge, in the credential template and in the metro-map coverage signal.

This page is for practitioners reading the metro map, administrators recording market-scoped recognitions, and anyone wanting to understand how recognition signals propagate.

Market or worldwide

Every recognition record either applies to one specific market, or is explicitly recorded as worldwide.

Market-specific

The recognition applies to one jurisdiction. The badge and credential template appear in the context of that market — a reader in another market sees nothing for this record.

Worldwide

The recognition applies everywhere. The badge and credential template show in every market the role itself is published in.

The metro-map coverage signal

On the Transformation Metro Map, each discipline carries a recognition signal — at a glance, how many of its roles are backed by a body.

Per discipline, the metro map shows the share of formally-published roles in that discipline that carry at least one active recognition. The denominator is the discipline's formal roles; profile- and flow-level recognitions appear on those entities but do not count toward the per-discipline role signal.

The signal is read-only and follows the same gate as the badge: a recognition only counts when its record is active and the role it attaches to is formal.

What the signal means
A discipline with high recognition coverage is one where a named body backs many of its roles. A discipline with low coverage is not a worse discipline — it is a market where recognition has not yet been recorded.

Item-to-credential evidence

A second relationship — different from recognition — connects competence items to the credentials they help satisfy.

A credential's evidence requirements are written in plain language on the recognition record. To make them concrete, an administrator connects individual competence items to the credentials they help satisfy. Working on an item, RPF records which credential or credentials it supports; working on a credential, RPF shows the items that satisfy it.

The connection is two-way and visible from both sides. A practitioner reading a competence item can see that it contributes to a recognised credential. An issuer downloading a template sees the concrete items standing behind the body's evidence requirements.

A distinct relationship
Recognition attaches a body to a whole role, profile or flow. The item-to-credential evidence link connects items to a credential's requirements. They are different relationships — and changing the evidence link changes the next template download.
RPF
Recognition scope, metro-map coverage and the item-evidence link are three signals that together tell a reader where a role leads, who backs it, and what concretely satisfies the credential.