Healthcare
Rolling out performance management in a hospital group
Clinical competency is usually already documented somewhere. Moving it into one platform is a migration with four decisions attached — here is the order they are best made in.
By the CLEAR Talent team7 min read
The organisation in this example
- Setting
- A multi-site hospital group with ward, theatre and allied health teams
- Constraint
- Rotational shifts, an accreditation calendar, and assessors who are often not the line manager
- Owner
- HR working with clinical education
- Starting point
- Competency records held per unit, in spreadsheets and signed paper forms
Decisions that shape the rollout
- Which competencies each role genuinely requires, before anything is imported
- Who counts as a qualified assessor when the line manager did not observe the work
- Whether a rating requires written evidence, and at which proficiency levels
- What the reassessment cadence is, and which stage deadlines it implies
Almost no hospital group starts from nothing. There is already a competency framework, already a reassessment schedule somebody maintains by hand, and already a folder of signed forms in each unit. A rollout is therefore a migration, not an invention — and that changes what the first month should be spent on.
The work that determines whether this succeeds is not configuration. It is deciding which of the standards currently in circulation survives contact with a single shared library, and who is allowed to sign a rating off. Get those settled and the build is quick. Skip them and you have digitised the disagreement.
Start from what the accreditation calendar already demands
Clinical competency is rarely undocumented. It is usually documented several times over, in different formats, by people who each reasonably believe theirs is the current version. The value of moving to a platform is not that the evidence starts existing; it is that there stops being a question about which copy counts.
That makes the accreditation calendar the natural anchor for the whole rollout. Whatever your programme requires — annual reassessment, reassessment on role change, reassessment after extended absence — is the cadence the platform should be configured around, because it is the deadline that will not move to suit the project plan.
The first job is not configuring software. It is deciding which of the standards already in circulation becomes the standard.
Four decisions that shape everything after them
Each of these is a policy question wearing a configuration question’s clothes. Answering them in this order avoids rework, because each one narrows the next.
Which competencies each role actually requires
A ward-based nurse and a theatre practitioner can draw from the same library and still be held to different standards. In CLEAR Talent each competency carries the roles that require it and the department it belongs to, so the mapping you agree here is what later lets a skills matrix be read by ward or unit without a separate spreadsheet.
Who is allowed to assess
Rotational staff, bank and agency cover and cross-site working mean the person who observed the work is frequently not the person on the org chart. Peer and skip-level assessment covers this, but somebody has to decide what makes an assessor qualified before it is switched on — that is a clinical governance decision, not a platform setting.
Whether evidence is required, and where
Ratings can require observable evidence rather than accept it optionally. Requiring it everywhere is a good way to stall a first cycle; requiring it nowhere removes the reason for doing this at all. Most groups land on requiring it at the levels that carry a sign-off consequence.
What the reassessment cadence is
Each assessment period carries its own deadlines for self-assessment, assessor review, calibration and final rating, with automated reminders on whatever is outstanding. Set those dates to what your accreditation programme calls for; the platform runs the process and holds the evidence, it does not certify your compliance.
What actually gets built
The guided onboarding wizard tailors the initial setup to organisation size, industry and performance management maturity, and saves progress at every step. What follows is the clinical detail that only your team can supply.
- The competency library
- Nursing, allied health and physician starter sets are fully editable. For each competency you define the proficiency levels and the behaviours expected at each one, so an assessor is rating against a description rather than a number.
- Role profiles per position
- Each role carries its required competencies and target levels, built from reusable templates. This is what makes a gap visible: required level against assessed level, per person, without anybody assembling it.
- The organisation structure
- Departments, locations, roles and reporting lines are first-class concepts, with bulk import to load them and staff transfers for when people rotate — which, in a hospital group, is continuously.
- The assessment period
- One period, with a deadline on each stage and reminders attached. When a period closes, so does the window to quietly amend it.
Run the first cycle narrow
A first period run across the whole group tests your project management. A first period run across one directorate tests your standards, which is the thing you actually need to learn.
Staff evidence as they go
Each entry records the situation, the action taken and the result, dated by month and tagged, with supporting files attached. Started early, the reassessment reviews a year of evidence rather than the last fortnight.
The assessor rates and signs off
Self-rating, assessor rating and final rating are held as separate values, each with its own comments. A preceptor or charge nurse can moderate a self-assessment without overwriting what the clinician originally recorded, and the sign-off is attributed and time-stamped.
Calibrate before ratings go final
Bring assessors to a common standard while the ratings are still provisional. Reviewers work from what is already in the platform — ratings with their evidence, goal scores and structured feedback — rather than from memory and advocacy.
Close the period and read the gaps
Skill-gap analysis feeds development plans, and individual, team and organisation reports export to PDF or Excel in one click. The output of a first cycle is a list of the standards that turned out to mean different things in different units.
What you can put in front of a surveyor afterwards
The output of a cycle is not only a set of ratings. It is a record with a specific shape — dated, attributed, and reviewable by someone who was not there at the time. That is what determines whether the next accreditation visit is a retrieval exercise or a reconstruction project.
- Evidence packs on demand
- One clinician for one period as a PDF, a whole department as a PDF, or competency history, calibration and team analytics as spreadsheets.
- Before-and-after values, not just events
- A moderated rating keeps the original self-rating, the assessor rating and the final value side by side with their comments, so a question about why a rating changed is answered from the record rather than from a mailbox.
- Access logged, not only edits
- Sign-ins, sign-outs and exports are recorded against the user who made them, and generated documents are served through signed links that expire after 24 hours.
- A reduced compliance surface
- CLEAR Talent holds employee performance data, not patient data, which keeps it outside most of the estate your information governance team worries about.
One boundary worth stating plainly, because it comes up in every procurement conversation: CLEAR Talent is not a credentialling or primary source verification system. It covers what happens after someone is credentialled — ongoing competency assessment, the evidence behind each rating, and the record of who signed it off — and runs alongside whatever you use to verify licences and privileges.