Role expectation architecture
Connected expectations for purpose, behaviours, technical practice, scope and responsibility.
03Organisation Design and Change Management
Competency and Capabilities Framework
Turn broad competency language into role expectations that managers and employees can recognise, assess and develop.
Expectations illustrated through work
Behavioural and technical clarity
Profiles tested with their users
CCFCompetency and Capabilities Framework
Start with your situation
When this framework helps.
- Job profiles use broad phrases without observable examples.
- Different professions need a common language with distinct technical expectations.
- Assessment and development practices use inconsistent standards.
The decisions it supports
- What outcomes and behaviours does this role require?
- Which technical skills and level of independence matter?
- How will people demonstrate the expectations in everyday work?
The framework at a glance
Competency and Capabilities Framework
Make the behaviours, skills and capabilities needed for effective work clear.
Explore the complete model
The approach
Clear expectations begin with the work
Give people a clear understanding of the behaviours, specialist skills and contribution their work requires. HR Delivery helps organisations translate strategy and real work into practical role expectations that support recruitment, development, career conversations and performance dialogue.
The Competency and Capabilities Framework, or CCF, connects a common organisational language with the distinct demands of different professions. This consultancy model adapts HR Delivery’s competency-library approach into a role-design and governance method. Its structure is designed to be tailored and tested with the people who understand the work.
A long competency dictionary can leave managers uncertain about what matters most. Employees may recognise the words but struggle to connect them with a decision, work product or development opportunity.
CCF starts with the outcomes a role must achieve, then specifies the behaviour and technical practice that contribute to those outcomes. It makes differences in independence, complexity and responsibility visible without assuming that a job title tells the whole story.
For this framework, a competency is a defined area of knowledge, skill, judgement or behaviour used in work. Organisational capability is the wider ability to deliver an outcome through people, processes, information and resources. A skills gap therefore needs to be distinguished from a missing tool, unclear authority or poorly designed process.
What you can take forward
Useful work. Clear next steps.
Tested competency profiles
A focused selection from the libraries, tailored with observable examples and appropriate maturity expectations.
Integration and review guide
A practical way to use profiles in assessment and development, and keep them current as work changes.
CCF · In practice
The model connects four layers of expectation
Purpose and outcomes
What must this work deliver, for whom and under what conditions? Identify the role’s contribution, critical tasks, service expectations and important risks. Connect expectations to the organisation’s priorities while allowing for different operating environments.
The output is a concise account of why the role exists and what successful work produces. It becomes the reference point for deciding which competencies belong in the profile.
Behavioural expectations
How should people approach the work and interact with others? Translate relevant values and behavioural competencies into observable actions. Communication might involve explaining a recommendation, checking understanding or raising a concern at the right time.
Use examples that recognise different effective styles. Avoid personality ideals, vague cultural-fit language and unnecessary assumptions about confidence, visibility or social similarity. The aim is to describe conduct relevant to the work.
Technical and professional practice
What specialist knowledge, practical skill and professional judgement are required? Define the methods, decisions, work products and safeguards that distinguish competent practice in the role.
Technical expectations might cover analysing evidence, operating equipment, interpreting requirements or reviewing professional work. Separate capabilities needed on entry from those that can be developed with planned support. Record required qualifications or licences separately so that a competency profile does not imply professional authorisation.
Scope and responsibility
At what depth, complexity and independence must the contribution be made? Describe the decisions the role can take, the consequences it must manage and the support or assurance available.
A specialist can have substantial technical authority without managing employees. A people manager may need a different combination of professional depth and leadership capability. Scope descriptors make those differences explicit rather than treating every career as a single management ladder.
CCF · In practice
Use the libraries as building materials
HR Delivery’s related technical library, T8D100C, describes 100 technical areas across ten domains, with ten specialist skills in each area. Its five maturity labels are Foundation, Developing, Solid, Advanced and Mastery. These describe progressively more independent, complex and authoritative technical practice; they are not automatic job grades or rewards for time served.
CCF selects relevant content and checks it against the organisation’s work. It does not load every library entry into every role or assume that a library title is a complete job profile. Behavioural and technical content remain distinguishable, with clear definitions and source references.
A usable level descriptor names the kind of work and the judgement expected. In supplier evaluation, this could distinguish applying an agreed checklist with support from independently evaluating a complex supplier and explaining material risks. The indicators must be developed for the role and tested with specialists; a level label alone cannot show the difference.
The five technical levels are used where appropriate to that library. Existing organisational level structures can be retained when they are coherent and supported by observable work examples. Any mapping between local levels and library levels is documented and reviewed rather than assumed.
CCF · In practice
Six stages from business need to everyday use
Commission and focus
Agree the decisions the framework will support, the populations in scope and the owners. Identify existing role architecture, professional standards, employee input and systems that must connect. The first gate is an agreed purpose and manageable design boundary.
Understand the work
Review role documents, observe or discuss critical tasks and gather examples of effective practice from subject-matter experts and role holders. Test differences across locations, teams and delivery models. Job analysis provides the link between tasks and the competencies needed to perform them. OPM job analysis guidance
Build the architecture
Agree families, definitions, naming conventions and the relationship between shared and specialist expectations. Remove duplicate concepts and separate current requirements from future aspirations. Keep the number of requirements proportionate to the decisions they support.
Write and test profiles
Draft observable indicators and examples for the relevant levels. Ask managers and employees to apply them to realistic work situations. Where two assessors interpret a descriptor differently, improve the wording and examples before relying on it. Test whether role holders can name acceptable evidence and an attainable practice opportunity for each priority expectation.
Pilot and integrate
Test selected profiles in development conversations and other approved processes. Check usability, accessibility, assessment burden and unintended exclusion. Adapt integrations with recruitment, learning and performance systems only after confirming the intended use and required safeguards.
Govern and refresh
Assign content owners, approve changes and publish version-controlled profiles. Review the framework when work, technology, professional requirements or strategy change. Retire redundant expectations and explain revisions to the people affected.
From insight to action
What a consulting engagement can produce
The central output is a Role Expectation Record: role purpose, critical outcomes, selected competencies, required scope, observable indicators, acceptable evidence, entry requirements, development expectations and accountable owner.
Agreed outputs can include role-family profiles, a map relating competency levels to existing role requirements, and a register explaining definitions and sources. Manager guidance, pilot findings and an implementation plan help people use the profiles consistently. These materials are developed for the organisation rather than presented as a ready-made download library.
Keep the source references, approved version and review date with each profile so users can identify the expectations that apply. Explain material revisions and check their effect on connected assessment and development materials.
CCF · In practice
Keep the framework useful and accountable
Business leaders own work requirements. Professional specialists maintain technical accuracy. HR stewards consistency, employee participation and integration. Managers and employees test whether the expectations remain understandable in practice.
Monitor profile coverage, unresolved overlaps, user understanding, descriptor disagreements and the usefulness of development conversations. These are implementation indicators, not proof that the framework predicts performance. Any assessment used for consequential decisions requires its own evidence of suitability for that purpose.
CCF supplies expectations to the Capability Assessment Framework. Assessment then examines relevant evidence against those expectations. Career Planning and Career Paths uses the same architecture to explain options and transitions. Each has a distinct job to do.
Your questions, answered
Questions organisations ask
Do all employees need the same competencies?
Some expectations may be shared, but specialist requirements and contribution levels should reflect the work. A common architecture can accommodate meaningful differences.
Does completing a level mean promotion?
No. Capability descriptors inform development and readiness discussions. Appointment, grade and reward depend on the relevant role, organisational arrangements and decision process.
Can we use an existing framework?
Yes. The starting point can be a review of what is already useful, followed by targeted repair of unclear definitions, gaps, overlaps or weak implementation.
Is CCF a validated assessment?
CCF defines expectations. It does not itself establish the reliability, validity or fairness of an assessment instrument or decision rule.
An illustrative application
Replace vague requirements with observable expectations
This illustrative example shows the decisions and records the framework supports; it is not a reported client result.
The situation
A procurement job family uses broad expectations such as commercial judgement and effective communication. Managers disagree about readiness for more complex work, while employees cannot identify the evidence or learning needed.
Explore the evidence
Connect role outcomes to behavioural expectations, technical practice and scope. Review supplier-evaluation tasks with specialists and role holders. Separate applying an established method, recommending an option and approving a material exception, so that skill and decision authority are both clear.
Agree the next step
Create a Role Expectation Record with a focused set of indicators: assess relevant supplier evidence, identify uncertainty, explain a recommendation and escalate outside the role’s authority. Name suitable work evidence and supported practice. Use the technical-library levels where relevant, with any mapping to local levels documented.
Review what changes
Pilot the profile in development conversations. Check whether managers interpret indicators consistently and employees understand what to practise. Repair ambiguous or duplicated requirements before wider use. Keep competence evidence, grade, promotion and professional authorisation within their respective decision processes.
Put the framework to work
Build expectations people can use
Start with a priority job family, a changing professional discipline or a framework that has become difficult to apply. HR Delivery can help turn it into clearer role expectations, useful development conversations and a manageable system of ownership.