Help · Recognition · For recognising bodies

Recording a body's recognition

How an RPF administrator records, in RPF, that a body recognises one or more roles, profiles or flows — the fields, the lifecycle, and the formal-role gate.

A professional association tells the RPF team that it recognises some of RPF's roles as meeting its membership standard. An RPF administrator opens the recognition admin and creates a record — plain descriptive details about the body's offer, links to the things the body recognises, and a note of where the recognition came from.

This page is for RPF administrators and curators. It is also the page a recognising-body partner can read to see exactly what RPF is recording on their behalf.

What a recognition record carries

Every detail describes the role, profile or flow and the body's offer. None of it describes, identifies or is attached to any individual person.

Recognising body
The named organisation whose recognition is being recorded. Exactly one per record — recognition by two bodies is recorded as two separate records.
Credential type
The kind of credential the recognition leads to — a full membership credential, a continuing-development unit, or similar.
CPD points (optional)
Continuing-professional-development credit, counted in the body's own scheme. Optional: a recognition may carry no CPD value. Where a figure is given, it is shown in the body's own scheme rather than as a bare number.
Validity period & renewal (optional)
How long the credential stays valid and how often it must be renewed. Optional: a credential that never expires is allowed.
Evidence requirements
What the body expects a candidate to provide to earn the credential — written in plain language on the record. The concrete competence items behind it are added separately.
Body's own page
A link to the body's published page about this recognition — the canonical reference for anyone following the badge.
Market or worldwide
Whether the recognition applies to one specific market (a jurisdiction) or worldwide. The badge and credential template respect this scope.
Source
A note of where the claim came from — who recorded it, when, and a link or note to the body's statement. Lets a stale or disputed claim be traced back and checked.

Draft, active, withdrawn

A recognition record has a status. Only an active recognition, on a formal role, produces a badge or a downloadable template.

  1. 1DraftBeing prepared — no badge shows, and no credential template can be produced from it.
  2. 2ActiveLive — once the body has confirmed, the administrator marks the record active. The badge shows (on a formal role) and a template can be produced.
  3. 3WithdrawnThe body has ended its recognition. No badge, no template, but the record is kept for history.
The formal-role gate
An active recognition is necessary, but not sufficient. The role, profile or flow must also be in RPF's formal state. A recognition prepared on a draft or under-review role stays invisible until the role is marked formal.

Sourcing the claim

Every recognition record keeps a note of where it came from.

Who recorded the claim, when, and a link or note pointing to the body's statement the recognition is based on. This lets a stale or disputed claim be traced back and checked. RPF keeps this record of the source; it does not itself audit the claim.

RPF records, never assesses

Creating, editing, linking and removing recognition records is done by an RPF administrator. In this first release the recognising body does not log in to manage its own records — an administrator records them on the body's behalf. RPF never assesses whether any person has met a role, and never issues or stores a credential.

Next steps

Once the record is active and the role is formal, the badge appears on the role page and the template becomes downloadable.