New

Now in Claude, ChatGPT, Cursor & more with our MCP server

Back to docs
accreditation12 min

Course Evaluation Evidence for Professional Body (PSRB) Accreditation

How to turn student course-evaluation feedback into accreditation-ready evidence for Professional, Statutory and Regulatory Bodies (PSRBs) — Engineering Council, BCS, NMC, HCPC, GMC, SRA and more — with a requirement-to-output mapping and an honest note on where a survey alone is not enough.

Koji Education Team

Product

Professional, Statutory and Regulatory Bodies (PSRBs) accredit, recognise, or approve programmes that lead to a professional qualification or exemption from professional exams. Unlike a national quality agency reviewing a whole institution, a PSRB scrutinises a specific discipline against its own professional standards. Student course-evaluation feedback is not the headline of a PSRB submission — competence standards and assessment are — but it is consistently part of the evidence base for the continuous-improvement and student-engagement expectations that almost every PSRB now embeds. This guide explains what PSRBs look for, maps those expectations to concrete evaluation outputs, and is honest about where a static survey falls short.

Answer first: PSRBs expect programmes to demonstrate a working quality loop — that student feedback is collected systematically, that it feeds programme change, and that the changes are documented. Your course-evaluation system supports this by producing standardised, comparable evidence over time and by tracking the actions taken in response. Where PSRBs go beyond most national frameworks is in wanting to see feedback tied to professional competence outcomes, not just satisfaction — which is exactly where conversational, thematically-analysed feedback outperforms a Likert grid.

What a PSRB actually is (and how review works)

PSRBs are external bodies that accredit programmes in regulated or chartered professions. Common examples include the Engineering Council (via institutions such as the IET, IMechE and the Joint Board of Moderators), BCS – The Chartered Institute for IT, the Nursing and Midwifery Council (NMC), the Health and Care Professions Council (HCPC), the General Medical Council (GMC), the Solicitors Regulation Authority (SRA), the Royal Society of Chemistry, and many chartered institutes across architecture, psychology, accounting, and social work.

Accreditation usually involves either a visit — where a programme team meets PSRB representatives (and, notably, current students) — or scrutiny of programme documentation, or both. Accreditation is granted for a defined period, after which re-inspection is required to retain recognition. Between visits, most PSRBs require annual monitoring, and each body sets its own standards, sometimes including assessment rules that differ from the university's (for example, a higher pass mark or specific mandatory modules).

Two verified examples illustrate the role of feedback:

  • Engineering Council (AHEP4): accredited engineering degrees must meet the fourth-edition Accreditation of Higher Education Programmes learning outcomes (published August 2020). Continuous improvement under this model requires regular, documented assessment and evaluation of student outcomes, used as input to change curriculum and teaching.
  • BCS: an accreditation visit typically begins with a meeting with students, followed by a meeting with the head of department and senior staff on quality management and enhancement — placing explicit weight on the synergy of quality-assurance and enhancement arrangements.

In both cases, the PSRB wants evidence that student voice is heard and acted upon — not merely gathered.

Mapping PSRB expectations to course-evaluation outputs

The table below maps the recurring PSRB expectations to concrete outputs a modern evaluation system can produce. It is deliberately framed around what PSRBs generally look for; always check your specific body's current handbook for exact wording.

PSRB expectationWhat the panel wants to seeCourse-evaluation output that supports it
Systematic student feedbackFeedback collected on every module, every cohort, consistentlyStandardised evaluation run to a fixed protocol across all modules, with response-rate reporting
Continuous improvement (the loop)Feedback demonstrably drives programme changeAction tracking: issue raised → change made → outcome, documented per cycle
Student engagementStudents consulted and their concerns representedVerbatim, thematically-analysed student accounts, ready to present to a visiting panel
Feedback tied to professional competenceEvidence linked to learning outcomes, not just satisfactionThemes mapped to programme/competence outcomes (e.g. AHEP4 or NMC proficiencies)
Longitudinal quality assuranceTrends across the accreditation period, not a single snapshotCohort-over-cohort comparison and longitudinal reporting
Response to specific incidentsHow a known issue (e.g. a weak module) was addressedFormative mid-module feedback plus the documented remedial action
Data protection and anonymityStudent data handled lawfully; feedback is safe to giveGDPR-compliant, EU-hosted collection with anonymity safeguards

How Koji produces each of these

Koji for Education is built to generate exactly this evidence:

  • Standardised, comparable collection. The same AI moderator runs every interview to a fixed protocol, so evidence is consistent across modules and cohorts — the comparability a PSRB panel expects.
  • Automatic thematic analysis. Instead of a spreadsheet of Likert means, Koji surfaces the recurring themes across a cohort and links them to programme outcomes, so you can show a panel what students said about competence development and why.
  • Closing-the-loop action tracking. Koji records the issue, the change made, and the result — the documented loop that AHEP4-style continuous improvement and BCS-style enhancement reviews want to see.
  • Formative and summative. Mid-module conversational check-ins let you address a problem within the accreditation period and evidence that you did.
  • GDPR-first handling. EU hosting and anonymity safeguards make the evidence defensible under data-protection scrutiny.

The conversational interview engine is shared with the main Koji platform used for customer and user research — the same technology, applied to student voice.

Turning a cycle of feedback into a submission

A practical workflow for a PSRB submission or annual monitoring return:

  1. Run standardised evaluations on every module each cycle, capturing both ratings and conversational depth on the competence areas the PSRB cares about.
  2. Extract themes per programme, mapped to the relevant professional outcomes (for example AHEP4 learning outcomes, NMC proficiencies, or BCS learning-outcome sets).
  3. Document the actions taken in response, with dates and owners, using action tracking rather than institutional memory.
  4. Show the trend across the accreditation period so the panel sees a functioning quality culture, not a one-off.
  5. Prepare the student-meeting narrative. Because BCS-style visits begin with students, arrive with a clear, evidenced account of what students raised and what changed — so the live meeting confirms your documentation rather than contradicting it.

When a survey (or a competitor) is the better choice — an honest note

Course evaluation is necessary but not sufficient for PSRB accreditation, and no evaluation tool should overclaim. Student feedback is one strand of evidence; the core of any PSRB case is the competence standards, the assessment map, and external examiner input. A conversational tool does not replace those.

There are also cases where a traditional survey platform is the pragmatic choice. If your PSRB submission mainly needs high-level satisfaction trend metrics and you already run everything through an incumbent like EvaSys, Explorance Blue, or a deeply LMS-native tool such as Watermark, a static survey may be adequate for the numeric evidence. Where conversational evaluation earns its place is the qualitative and closing-the-loop evidence — the "why" behind a competence gap and the documented response — which static Likert surveys capture poorly. Many programmes combine both: survey metrics for trends, conversational interviews where the professional-competence "why" matters most.

Finally, PSRB requirements evolve. Treat this guide as an orientation, not a substitute for your specific body's current accreditation handbook, and confirm exact evidence expectations with your PSRB liaison.

Discipline nuances: practice-based and placement professions

The evidence a PSRB expects varies sharply by discipline, and your evaluation approach should flex accordingly. Practice-based and placement professions — nursing and midwifery (NMC), the allied-health professions regulated by the HCPC, medicine (GMC), and social work — assess competence partly in clinical or field settings, so the PSRB wants feedback on the placement experience and the quality of practice supervision, not just the taught modules. A single end-of-module Likert survey rarely reaches this. Conversational, formative feedback collected during placements captures issues while they can still be fixed and gives the panel evidence that the practice-learning environment is monitored, not assumed.

Chartered and design-led disciplines — engineering (Engineering Council/AHEP4), computing (BCS), and architecture — weight the demonstration of applied competence and, often, an accredited individual project or capstone. Here the useful evidence is qualitative: what students say about how the programme built their ability to solve open-ended problems, mapped to the competence outcomes. Regulated legal and financial professions (SRA, chartered accountancy bodies) emphasise assessment rigour and specific mandatory content, so feedback evidence typically supports — rather than leads — the case.

Common evidence mistakes to avoid

  • Satisfaction without competence. Presenting only "4.2/5 overall" tells a PSRB nothing about professional-competence development. Tie feedback to the body's learning outcomes.
  • Collection without closure. Feedback with no documented action is the single most common gap panels flag. Always show the loop: issue, change, result.
  • A single snapshot. One cohort's data is not a quality culture. Show the trend across the accreditation period.
  • Losing the student-meeting thread. Because bodies like BCS begin visits with students, your documented evidence must match what students will say in the room.
  • Data-protection afterthoughts. Confirm lawful basis, anonymity, and EU hosting before collection, not during the visit.

Related Resources

Ready to build PSRB-ready evidence? Explore Koji for Education to see standardised conversational interviews, automatic thematic analysis mapped to professional outcomes, and closing-the-loop action tracking.