Loading Help…
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.
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.
What a recognition attaches to — and what it does not.
A recognition record can be linked to a role, a profile or a flow — the things a body recognises. It is not attached to smaller building blocks like individual information uses or items. One record can cover as many roles, profiles or flows as the body recognises, and one role can carry many records — or none.
Linking or unlinking a recognition changes only what RPF displays. It never alters the role, profile or flow itself — competence items, levels and relationships are untouched.
A recognition record has a status. Only an active recognition, on a formal role, produces a badge or a downloadable template.
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.
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.
Once the record is active and the role is formal, the badge appears on the role page and the template becomes downloadable.
