A Guide to Your Competency Framework for 2026

You may already have the symptoms without calling them a competency problem. Hiring managers describe the same role in different ways. Performance reviews depend too much on who the manager is. Training requests pile up, but nobody can say which skills matter most. Career paths feel vague, and compliance tasks sit awkwardly beside development conversations.

That's where a competency framework earns its keep. In a UK mid-market business, it stops HR from running separate processes for recruitment, development, performance and compliance. It creates one shared definition of what good looks like, then carries that definition through your Microsoft environment so it can be used.

For organisations already invested in Microsoft 365, Dynamics 365, Dataverse, Power Apps and Power BI, the opportunity is bigger than producing a tidy PDF. You can build a framework that shapes hiring decisions, triggers workflow, supports Right to Work checks, strengthens GDPR-aligned retention practice and gives managers cleaner data for people decisions.

What Is a Competency Framework and Why Does It Matter

A competency framework is a practical blueprint for role success. It maps the skills, knowledge and behaviours required to perform well in a role and to progress beyond it. That matters because many issues in growing businesses start with unclear expectations, not bad intent.

When expectations are vague, every manager fills the gap differently. One manager recruits for technical depth. Another hires for attitude. A third promotes whoever communicates best in meetings. Over time, that inconsistency creates avoidable friction across the employee lifecycle.

The value of a framework is that it gives HR, line managers and employees a common language. The role profile stops being a shopping list of tasks and becomes a defined standard for capability.

What it fixes in practice

A good competency framework helps you:

• Standardise hiring: Interviewers assess against the same competencies rather than personal preference.
• Clarify progression: Employees can see what changes between their current role and the next one.
• Improve fairness: Performance discussions become more evidence-based.
• Target development: Learning plans focus on specific gaps instead of generic courses.
• Support governance: Regulated or compliance-heavy responsibilities can be embedded into role expectations.

The principle is well established. Instride's overview of competency frameworks describes a framework as a blueprint for success and notes that the OECD Core Competency Framework, used as a model in the UK, identifies four areas employers seek: critical thinking/problem solving, teamwork/collaboration, professionalism/work ethic, and oral/written communications.

Why HR directors should care now

For a UK HR Director, this isn't only about talent development. It's also about control. If you're running a business with multiple sites, hybrid teams or a mix of office and field roles, informal standards break down quickly.

Practical rule: If two managers would describe “good performance” in the same role differently, you already need a competency framework.

The strongest frameworks also prevent the false split between capability and compliance. In many organisations, HR teams track behaviours in one place and statutory obligations in another. That's inefficient. A better approach is to recognise that some competencies carry operational and compliance implications, especially in recruitment, employee record handling and retention practice.

A framework matters because it gives structure to decisions that are otherwise subjective. Once it's defined well, you can digitise it, report on it and make it part of everyday work rather than an annual HR exercise.

The Core Components of a Modern Framework

A modern competency framework isn't a long list of admirable traits. It's a working structure with distinct parts, each doing a different job. If you skip that structure, the framework becomes too abstract for managers and too vague for systems.

The three layers that usually matter most

Most organisations need three competency categories.

• Core competencies: These apply to everyone. They often reflect values or enterprise-wide expectations such as communication, collaboration or judgement.
• Role-specific competencies: These define what a person must do well in a given function. An HR adviser, payroll lead and people analytics specialist won't share the same technical expectations.
• Leadership competencies: These apply where people management, strategic ownership or cross-functional influence are required.

That separation matters because it keeps the framework usable. If you mix every expectation into one undifferentiated list, managers can't tell what's universal and what's role-dependent.

Behavioural indicators are the working part

A competency by itself is too broad. “Analytical thinking” sounds useful, but a manager still needs to know what it looks like in real work. Behavioural indicators solve that problem by translating a competency into observable actions.

For example, a behavioural indicator might describe how someone evaluates evidence, spots risk, challenges assumptions or presents options for decision-making. That gives reviewers something concrete to assess.

The framework only becomes operational when a manager can point to behaviour, not intention.

Progression levels stop it being binary

Strong frameworks measure growth. They don't split people into competent or not competent. That's why proficiency levels matter.

The JTF Core Competency Framework uses 8 Domains and expresses competency statements at three distinct levels: Fundamental, Skilled, and Advanced. That structure works because it supports progression and gives organisations a benchmark for competencies such as Analytical thinking and Technical/scientific credibility.

In practice, this means you can distinguish between someone who follows a defined process, someone who adapts it, and someone who improves it for others.

What to include in each competency record

A useful competency entry usually needs:

Many frameworks succeed or fail: If the wording is elegant but the behaviours aren't observable, managers won't use it properly. If the model is too complex, nobody keeps it current.

Designing Your Competency Framework Step by Step

A framework design project usually starts with a familiar problem. HR has one set of expectations, line managers have another, and your systems team is already asking how any of this will sit inside Dynamics 365, Dataverse, and the processes you already run. If the model stays theoretical, managers ignore it. If it is copied from another employer, it breaks as soon as you apply it to your own roles, controls, and reporting needs.

Start with the business problem you are trying to solve. For a UK mid-market employer, that is often inconsistent hiring decisions, weak people management, uneven capability across sites, or poor control over sensitive HR data. Those priorities should shape the framework before anyone debates wording.

Start with strategic intent

Define the outcomes first. Be specific.

If the priority is better first-line leadership, the framework needs clear management behaviours that can be assessed in probation, performance reviews, and promotion decisions. If the priority is cleaner employee data and stronger compliance, include competencies around process discipline, judgement, and handling confidential information properly under UK GDPR. If growth by acquisition is the issue, focus on creating common standards across legacy teams and job titles.

This decision affects the build. It determines how many competencies you need, which job families you cover first, and how you will structure records in Dataverse so the framework can be reused across recruitment, performance, learning, and reporting.

Build from evidence in real roles

Work from actual jobs, not idealised job descriptions. The fastest way to weaken a framework is to ask a room of managers to invent competency names from scratch. A better method is to collect examples of strong performance, recurring mistakes, and moments where judgement matters.

Use workshops and manager interviews to gather evidence such as:

• What high performers do consistently
• Where quality issues or delays occur
• Which parts of the role create legal, financial, or service risk
• What capability gaps will matter over the next 12 to 24 months

I usually ask for examples from recent work. What did the person do? What was the decision? What was the outcome? That gives HR enough material to write behaviours that managers can later recognise in practice.

Public sector frameworks can still be useful as a reference point if you treat them as input, not a template. The Government Statistician Group's 2016 competency framework, for example, set out a structured model for professional behaviours across the government statistics profession, as described by the UK Statistics Authority and Government Statistical Service framework materials. The lesson is the structure, not the wording. Clear behaviour statements travel well. Imported language usually does not.

This short video gives a useful prompt for thinking about practical framework design in real organisations.

Draft for use, then pilot in a live process

Keep the first version lean. A framework that looks polished in PowerPoint can still fail in operation if managers cannot score against it consistently or if the data model becomes too awkward to maintain in your Microsoft stack.

Write each competency so it can be assessed through observable behaviour, work output, or both. Keep the language plain. Remove duplicates. Check whether a manager could use the statement in an interview, a check-in, or a development conversation without needing HR to translate it.

Then test it in one controlled area.

1. Pick a contained pilot group: One function, site, or job family is enough.
2. Set up common scoring rules: Managers need the same interpretation of each level.
3. Use it in real activity: Apply it in hiring, probation, reviews, or talent discussions.
4. Check the data model early: Confirm how competencies, levels, roles, and evidence will be stored in Dataverse before the framework grows.
5. Refine quickly: Rewrite anything that creates inconsistent scoring or duplicate records.

For UK organisations, this is also the right point to test compliance edges. Check whether any competency evidence includes special category data, whether manager notes need retention rules, and whether role profiles touch regulated checks such as Right to Work. Design decisions made here affect how safely you can digitise the framework later.

Working advice: If two managers score the same behaviour differently, the issue is usually the wording, the level definition, or both.

Strong frameworks are built through live use. The document matters less than whether managers can apply it consistently and whether your systems can hold it cleanly enough to support reporting, audit, and change over time.

Mapping Competencies to Key HR Processes

A competency framework proves its value when it changes daily HR work. If it sits in SharePoint as a reference document, it's only half-built. Its full payoff comes when the same framework shapes recruitment, onboarding, performance and development.

Recruitment and selection

Before a framework, hiring often relies on inconsistent job adverts, broad interview questions and personal judgement. After a framework, each role has a defined competency profile that drives structured assessment.

That changes the quality of the process. Interview questions become behavioural. Scoring becomes role-linked. Shortlisting can focus on evidence tied to actual capability needs rather than generic “fit”.

For example, if an HR operations role requires analytical thinking, compliance discipline and stakeholder communication, those become explicit assessment areas. Your panel can then test each one with a common scoring model.

Onboarding and early capability building

Onboarding is usually where employers say what matters. A framework lets you show it. New starters can see the competencies attached to their role from the beginning, along with the expected level for each one.

That gives structure to probation, manager check-ins and early learning plans. It also helps people distinguish between learning systems, learning process and demonstrating judgement in live work.

Performance and development

Without a competency framework, appraisal forms often drift into subjective commentary. Managers discuss effort, attitude or outcomes, but the logic varies from person to person.

With a framework, reviews become more disciplined. Employees are assessed against expected behaviours and proficiency levels. That doesn't remove judgement, but it makes the judgement more consistent and easier to challenge if needed.

A sensible model looks like this:

Learning and career progression

L&D becomes more useful when it supports identified competency gaps. Instead of sending broad training catalogues, HR can map development to a person's current level and next role target.

That also improves career conversations. A framework shows the difference between performing well now and being ready for the next move. Employees can see what progression requires, and managers can support that with clearer evidence.

A framework creates a golden thread across HR processes only if the same competency language appears everywhere. Recruitment, onboarding, reviews and development should not each use different definitions of success.

If you want adoption, don't launch the framework as an HR initiative. Launch it as the standard for how people are hired, managed and developed.

Integrating Your Framework with Dynamics 365 and Dataverse

A mid-market HR team often reaches the same point. The framework exists in slides and spreadsheets, managers have seen it once, and nobody can tell which version is current. Reviews drift back to free-text opinion, recruitment uses different criteria, and compliance tasks sit in separate admin processes. If you are already running Microsoft tools, Dataverse is usually the point where the framework starts behaving like part of the HR operating model rather than a document.

In practice, the value comes from using one data model across Dynamics 365, Dataverse, Power Apps, Power Automate and Power BI. The same competency record can be referenced in role design, hiring, probation, performance reviews, learning activity and compliance workflows. That matters because UK HR teams rarely have the luxury of treating capability, auditability and employee data handling as separate topics.

What digitisation changes

A well-structured Dataverse model stores each competency as a record with linked behaviours, proficiency levels, role mappings, review evidence and workflow logic. Once that structure is in place, the framework becomes usable in day-to-day HR work rather than something managers have to remember manually.

That usually means four practical changes:

• Roles carry defined competency requirements: Each role profile can hold core, functional and leadership expectations in a controlled format.
• Employee records can be assessed against the same model: Managers record evidence against required proficiency levels instead of writing unstructured comments.
• Workflows can trigger action: Power Automate can route reminders, approvals or development tasks when evidence is missing or ratings fall below the expected level.
• Reporting becomes consistent: Power BI can show gaps by function, site, role family or manager without rebuilding the logic every reporting cycle.

For UK employers, this is also where compliance becomes easier to manage. If right to work checks, document retention periods and access to employee data all sit within the same Microsoft estate, you can connect them to role requirements and process ownership. That supports GDPR accountability and reduces the risk of critical checks being handled outside the system.

Keep the framework controlled

Digitisation helps only if the data model prevents avoidable mess.

If managers can keep adding near-duplicate competencies to role profiles, the framework expands until nobody can use it consistently. If review forms allow free-text substitutions for defined behaviours, reporting quality drops. If compliance steps rely on email reminders rather than system triggers, deadlines get missed and audit trails weaken.

The answer is configuration discipline. Set validation rules for role templates. Limit who can create or retire competencies. Use version control so historical assessments still make sense after the framework changes. Separate HR framework governance from manager input, so managers can submit evidence without rewriting the model.

For right to work and similar checks, link the workflow to the employee record and the role context, not to a manager's memory. In Dataverse, that usually means storing the check status, expiry or follow-up requirement as structured data, then using Power Automate to trigger the next step. It is a simple pattern, but it is one of the clearest ways to reduce admin delay and improve audit readiness.

Practical Microsoft patterns that work

The strongest implementations are usually quite plain technically. They focus on maintainable setup rather than clever architecture.

• Power Apps review forms: Managers complete structured assessments with preloaded competencies, behaviour indicators and evidence fields tied to the employee and role.
• Dataverse security model: HR owns the framework tables and approval rights, while managers can add assessment evidence only for their team.
• Recruitment matching: Candidate data can be mapped to defined competencies during hiring, provided the role and competency structure is already agreed and governed.
• Power BI dashboards: HR and leadership can track review completion, capability distribution, gaps by role family and repeated development needs.

There is a trade-off here. The more flexible the system is, the easier it is for local teams to adapt it. The harder it becomes to compare data across the business. Mid-market organisations usually benefit from tighter central control over the competency library, with limited local variation in behaviours or proficiency examples where a function needs it.

Generic guidance often stops at writing competency definitions. Implementation work starts after that. In Microsoft environments, key decisions are about table design, relationships, permissions, retention, workflow triggers and reporting logic. If you already own the stack, the challenge is rarely buying new software. It is modelling the framework in a way managers will effectively use and HR can govern.

Measuring Success and Avoiding Common Pitfalls

Six months after launch, HR often has the framework signed off, loaded into the system, and visible in review forms. Then the same problem appears. Managers still default to free-text comments, capability gaps remain hard to compare across teams, and leadership cannot see whether the framework is improving hiring, development, or risk control. That is the point to measure properly.

A competency framework earns its place when it changes decisions. In practice, that means checking whether managers use it consistently, whether employees understand what good looks like, and whether the data supports better judgement in recruitment, development, performance, and compliance activity.

Practice matters more than course completion

Training records matter, but they do not prove competence. Repeated performance in real work does. Investigations Quality's guidance on competency practice states that competence should be validated through practice, not just training, and recommends tracking the frequency, duration, depth, and accuracy of monthly professional challenges.

That principle applies well beyond regulated investigations work. If a manager marks someone as proficient in employee relations, case handling, or compliance checks, there should be evidence from actual work. In a Dynamics 365 and Dataverse setup, that usually means linking the rating to completed cases, review notes, observed behaviours, or other role-relevant records rather than accepting course attendance as proof.

If the framework only appears at annual review time, adoption is shallow.

What good measurement looks like

Start with measures that show whether the framework is being used properly and whether it is improving outcomes. UK mid-market firms do not need a large KPI library. They need a small set of indicators that HR can defend and managers can influence.

Useful measures include:

• Manager adoption: completion rates for competency-based reviews, evidence quality, and calibration attendance
• Employee clarity: whether people can see the competencies, behaviours, and proficiency expectations for their current role and likely next role
• Development follow-through: whether identified gaps lead to targeted learning, coaching, or stretch assignments within a defined period
• Decision quality: whether hiring, promotion, and performance discussions rely on the agreed framework rather than manager preference
• Control and compliance support: whether the framework improves consistency in activities with regulatory impact, such as onboarding checks, document handling, or Right to Work processes

In Microsoft environments, these measures should be visible in reporting, not buried in spreadsheets. Power BI can show review completion, overdue assessments, recurring skill gaps by role family, and patterns by business unit. Dataverse audit history also helps HR spot whether ratings are being updated with evidence or changed without explanation. That matters for governance and for GDPR accountability if competency data influences employment decisions.

Common Competency Framework Pitfalls and Solutions

The trade-offs to manage

There is always a balance between precision and usability. A detailed framework can capture genuine differences between specialist roles, but it also increases manager effort, training needs, and reporting complexity. A lighter model is easier to roll out and maintain, but it can flatten important distinctions.

For most UK mid-market organisations using the Microsoft stack, the safer choice is to start with tighter standards. Keep one governed competency library, a controlled set of proficiency levels, and clear evidence rules. Add complexity only where it improves decision quality. That approach usually gives HR better data, cleaner reporting in Power BI, and fewer arguments about what a rating means.

The avoidable failure is not technical. It is letting the framework become optional in day-to-day management. Once that happens, the system still exists, but the credibility goes.

Conclusion Your Strategic Talent Advantage

A competency framework is one of the few HR tools that can improve hiring quality, strengthen development, support fairer performance decisions and reinforce compliance discipline at the same time. Its real value comes from precision. Clear competencies, observable behaviours, sensible proficiency levels and disciplined application across the employee lifecycle.

For Microsoft-centric organisations, the bigger opportunity is digitisation. When the framework sits inside Dynamics 365 and Dataverse, it stops being a reference document and starts becoming part of how your business operates. Reviews become structured. Role requirements become reusable. Workflow and reporting become far more useful.

That's the difference between having a framework and running one.

We are DynamicsHub.co.uk. Experience HR transformation built around your business. Hubdrive's HR Management for Microsoft Dynamics 365 is the premier hire‑to‑retire solution, more powerful, more flexible, and more future‑ready than Microsoft Dynamics 365 HR.

DynamicsHub helps UK organisations turn competency frameworks into working HR systems on Microsoft technology. If you want a practical approach to HR transformation, built around your business, call 01522 508096 today or send us a message through DynamicsHub.

Chris Pickles Director / Dynamics 365 and Power Platform Architect & Consultant

Chris Pickles is a Dynamics 365 specialist and digital transformation leader with a passion for turning complex business challenges into practical, high-impact solutions. As Founder of F1Group and DynamicsHub, he works with organisations across the UK and internationally to unlock the full potential of Dynamics 365 Customer Engagement, HR solutions, and the Microsoft Power Platform. With decades of experience in Microsoft technologies, Chris combines strategic thinking with hands-on delivery. He designs and implements systems that don’t just function well technically — they empower people, streamline processes, and drive measurable performance improvements. Known for his straightforward, people-first approach, Chris challenges conventional thinking and focuses on outcomes over features. Whether modernising customer engagement, transforming HR operations, or automating processes with Power Platform, his goal is simple: build solutions that create clarity, capability, and competitive advantage.

See Full Bio

Dynamics 365 Customer Engagement (CE) Dynamics 365 Sales Dynamics 365 Customer Service Digital Transformation Microsoft Power Platform Power Apps Power Automate Power BI Dynamics 365 HR / HR Systems Hubdrive HR Business Process Automation