Skip to main content

Financial services

Rolling out performance management in a regulated firm

In a regulated firm the hard part of a rollout is not the workflow — it is deciding what the rating is made of, and being able to show that years later.

By the CLEAR Talent team5 min read

Individual performance report in CLEAR Talent

The organisation in this example

Setting
A regulated firm with front-office, control and operations functions
Constraint
A rating has to hold up to a sceptical reader years after it was made
Owner
HR working with compliance and reward
Starting point
A composite rating that, in practice, is dominated by revenue

Decisions that shape the rollout

  • What the two rating streams are, and how much each one weighs
  • Who approves an assessment, and at which point it stops being amendable
  • Whether a competency rating requires written evidence to be submitted
  • What the second line and the remuneration committee each need to see

Firms in banking, insurance and asset management rarely arrive without a performance process. They arrive with one that works well enough for the conversation and badly for the record — where the rating was reasonable at the time, the reasoning lived in a manager’s head, and nobody can now reconstruct it.

So a rollout in a regulated firm is less about workflow than about composition: what the rating is made of, who has to stand behind each part, and what remains visible afterwards. Those three questions are worth settling before anybody opens a configuration screen.

The problem is usually the weighting, not the process

Most firms already know that a scorecard dominated by revenue tells people what is genuinely rewarded, whatever the conduct policy says. What they usually lack is a mechanism that holds the intended balance in place once a strong quarter arrives and the argument for making an exception is at its most persuasive.

CLEAR Talent treats goals and KPIs as one stream and competency assessment as another, combining them into a single composite rating. Weightings are configurable per level, so a control function and a front-office desk can sit on the same platform without being measured the same way — which is usually the first thing a second line asks about.

A rating you cannot decompose afterwards is a conclusion, not a record. The point of the rollout is to keep the parts visible.

Settle these before configuring anything

  1. What each stream is worth, per level

    Decide the split between goals and KPIs on one side and competency assessment on the other, and whether it differs for revenue-generating and control roles. Weightings are configurable per level, so this is a policy choice the platform will enforce rather than a guideline managers interpret.

  2. What a KPI is allowed to mean

    The KPI library holds reusable, role-aware metric templates with performance bands and guardrails. Agreeing those bands centrally is what makes “exceeded target” mean the same thing across the business — and what stops each desk quietly recalibrating its own definition.

  3. Who signs, and when it closes

    Configurable approval chains route each assessment to the reviewer and the approver who has to stand behind it. Each period stage — self-assessment, assessor review, calibration, final rating — opens and closes on the dates you set, and a closed period stays closed.

  4. What evidence a competency rating carries

    Competency ratings can require observable behavioural evidence at the point of assessment. This is the single decision that most affects whether an audit two years from now is a search or a scramble.

What gets built

Role profiles per function
Define the competencies each role genuinely requires, with behavioural indicators at every proficiency level, then reuse that profile across assessments, reviews and promotion decisions rather than restating it each cycle.
The KPI library and the weighting model
Reusable metric templates with bands, guardrails and evidence linking, plus the weightings agreed above applied per level.
Role-based access with ownership checks
Access runs across administrator, manager and employee roles with ownership checks on individual records, so managers work within their own reporting line and access itself is logged.
The reassessment schedule
Set the cadence your compliance function requires and let the platform issue the reminders, rather than tracking renewal dates in a side spreadsheet that one person maintains.

The first cycle, and the calibration that follows it

Calibration is where a set of individual manager judgements becomes one firm-wide standard, and it is the stage a second line will look at hardest. Reviewers work from what is already in the platform — goal scores, competency ratings with their evidence, and structured 360° input — rather than from recollection and advocacy.

Because the streams stay separate until the composite is formed, a calibration session can interrogate one of them without disturbing the other: a desk whose numbers were exceptional and whose behavioural ratings were not is visible as exactly that, rather than averaged into an unremarkable middle.

Expect the first cycle to surface disagreements about the bands rather than about individuals. That is the cycle doing its job.

What survives the cycle

An audit log that records the change, not just the event
Every rating, comment, approval and file access is recorded with the user and timestamp behind it, including the values before and after. The trail exists whether or not anyone ever asks for it.
Committee-ready exports
Individual, team and organisation-level reports export to PDF or Excel in one click, so risk, compliance and remuneration committees review the same underlying data HR is working from.
Answers for the security questionnaire
Google Cloud Platform hosting with continuous threat monitoring through Security Command Center Premium, end-to-end TLS, generated files served through signed URLs that expire after 24 hours, and a top Mozilla Observatory rating across the platform.
A narrower data footprint than expected
CLEAR Talent holds performance and development data. It is not a payroll engine or a system of record for customer data, which keeps it out of the most sensitive parts of your estate.

Questions this raises

What has to be decided before configuration can start?
The weighting between the goals and KPI stream and the competency stream at each level, the performance bands a KPI is allowed to use, the approval chain for an assessment, and whether competency ratings require written evidence. Each is a policy decision the platform then enforces, so agreeing them first avoids rebuilding the configuration twice.
Should the first cycle run across the whole firm?
Rarely. A first cycle covering one division surfaces the disagreements about bands and weightings while they are still cheap to resolve, and the period stages can then be reused as configured for the wider rollout.
What does the security review usually want to see?
The common answers: Google Cloud Platform hosting with continuous threat monitoring through Security Command Center Premium, end-to-end TLS, generated files served through signed URLs that expire after 24 hours, role-based access with ownership checks and logged access, GDPR support including DSAR exports and right-to-be-forgotten workflows, and the fact that CLEAR Talent holds employee performance data rather than payroll or customer data.
What comes out of the first cycle for a remuneration committee?
Individual, team and organisation reports exported to PDF or Excel, drawn from the same goal scores and evidence-backed competency ratings the calibration session worked from — so the committee and HR are reading one set of numbers rather than two.

Walk through this with your own structure

Book a session against your competency framework, your cycle dates and the constraints your managers actually work under — not a generic slide deck.