Loading Help…
Read the recorded evidence, review and recognition states alongside publication and access information.
RPF has generated a starting point from available inputs (e.g. a Flow assembled from a Role’s linked profiles). Generation alone does not establish that someone has reviewed the result.
For you: a fast orientation, free to explore.
An author has developed the content. Read its supporting sources and recorded review status; authorship alone does not establish panel verification.
For you: citable content you can already put to work.
A named verification panel has reviewed the submitted relationships. Consult the recorded scope, outcome and version. Public summaries and member records may show different levels of detail.
A panel outcome has been recorded for the stated scope and version.
A professional body has formally recorded that the content meets its standard. Recognition badges always name the body, so the endorsement is attributable — never anonymous.
The named body’s recognition is recorded for its stated scope. It is distinct from evidence approval and panel verification.
Published records a publication state. Authored describes development of the content; Verified records panel review; Recognised records a body’s endorsement. These are separate facts. Public visibility also depends on the applicable access and organisation settings.
Authors develop content, reviewers examine evidence, panels verify submitted relationships, and professional bodies may recognise content. Check which actions are recorded for the version you are reading.
The boundary, stated plainly: RPF defines and carries the standard, and emits unsigned credential templates. Your assessment partner measures against it; your body issues and signs the credential. RPF never assesses individuals and never holds learner records.
