How to Build a Role Profile: Required Skills and Minimum Proficiency
Why Every Gap Analysis Starts with a Role Profile
Picture this: a manager stops by HR on a Tuesday afternoon and asks which members of the operations team could step into a project-coordinator role if one opened up next month. It's a reasonable question — and it should be answerable in minutes.
Instead, you open the shared drive. There's a job description from three years ago and a job-posting template. Neither one says anything useful about how good at Excel someone needs to be, or whether stakeholder communication is a must-have at an intermediate level or a nice-to-have at a basic level. So you make some calls, wait for replies, and piece together an answer by end of week.
The problem isn't that you lack data about your people. The problem is that you have no standard to measure them against. You know — roughly — what your employees can do. You don't have a written, agreed-upon definition of what each role requires.
That definition is a role profile: a structured document that lists the specific skills a job needs and the minimum proficiency level each skill must reach for someone to perform effectively in that role. Without it, a skills gap analysis is just guesswork. With it, you can compare any employee's actual skill level to a clear target and see exactly where the gap is.
This article walks you through building a role profile from scratch — from choosing your skills to setting defensible proficiency thresholds — so that your next gap analysis has a solid foundation to stand on.
What a Role Profile Actually Contains
A role profile is not a job description, though the two overlap. A job description is written for candidates: it describes responsibilities, reporting lines, and working conditions. A role profile is written for workforce planning: it answers the question, "What must someone know and be able to do to perform this job well?"
A complete role profile contains four elements:
Role title and scope — the job title, team, and a one-line description of the role's primary function. This anchors the profile to a real position in your org chart.
Required skills list — the specific skills the role depends on, drawn from a consistent taxonomy so that skills mean the same thing across every role in your organization. (More on building this list in the next section.)
Minimum proficiency level per skill — a numeric rating on a defined scale (typically 1–5) representing the floor an employee needs to reach, not an aspirational ceiling. This is the number that makes gap analysis possible. Understanding what each level on the scale actually means — the difference between a 2 and a 3 for a given skill — is worth working through before you start rating; the proficiency scale guide covers how to define each level in plain terms your managers will apply consistently.
Skill type classification (optional but useful) — flagging each skill as technical/hard, transferable/soft, or domain-specific helps you separate gaps that training can close from gaps that require hiring.
Keep the profile focused. Fifteen to twenty-five skills is typically enough for most roles. A profile with fifty line items tends to blur the signal — everything looks like a gap.
How to Build Your Required Skills List
Start with an occupation template, not a blank page
The most common mistake when building a first role profile is starting from a blank document. Someone has to decide which skills matter, that person's judgment varies by day and by role, and the result is a collection of profiles that don't share a common vocabulary.
A better starting point is an occupation template from O*NET (the Occupational Information Network), maintained by the US Department of Labor's Employment and Training Administration. O*NET organizes work-relevant knowledge and skills across Basic Skills, Cross-Functional Skills, and Knowledge domains, mapped to more than 900 occupations.
Skills Inventory Manager uses O*NET-derived data to seed the taxonomy available in the platform, used and adapted under CC BY 4.0. O*NET data is sourced from the O*NET Resource Center at onetcenter.org. Verify the current O*NET release at the O*NET Resource Center before citing a specific release number; requirements and descriptions are updated periodically.
What this means practically: when you open a "Project Coordinator" or "Quality Control Technician" template in a tool that uses O*NET occupation data, you get a pre-populated list of relevant skills — not your finished role profile, but a credible first draft built on data from thousands of actual job incumbents. That's a far better starting point than a blank spreadsheet or a recycled job posting.
See the O*NET occupation templates guide for a walkthrough of how to read an occupation template and which fields to pull into a role profile.
Edit the template for your context
O*NET describes what the typical job looks like across the economy. Your role operates in your specific industry, team structure, and set of tools. After pulling the occupation template, do three things:
Remove skills the role genuinely doesn't use. If the template includes a skill your team has outsourced entirely, cut it. Carrying irrelevant skills in a profile creates noise in your gap reports.
Add skills specific to your environment. Tools, systems, and domain knowledge that don't appear in a general taxonomy belong here — your ERP system, your industry's regulatory framework, the specific certifications your team carries. These custom skills sit alongside the O*NET-derived ones in your profile.
Confirm the list with the hiring manager or team lead. The role profile lives in HR, but the skills that matter most in day-to-day work are visible to the people doing and supervising that work. A 30-minute conversation with the team lead will surface the two or three skills that make or break performance in this specific role — and that conversation builds the credibility your gap analysis will need when it produces results.
A consistent skills taxonomy across all your role profiles is what makes cross-role comparisons possible — finding who's closest to ready for a new role, spotting department-wide gaps, or planning training that benefits multiple teams. The competency framework guide explains how to build that shared taxonomy for your organization.
How to Set Minimum Proficiency Levels
Use a 1–5 scale with written definitions
Proficiency ratings only work if everyone applying them means the same thing by "3." A numeric scale without definitions produces inconsistent ratings; a 3 from one manager is a 4 from another, and your gap analysis becomes unreliable.
A common approach uses a five-point scale:
| Level | Label | What it means (example definition) |
|---|---|---|
| 1 | Awareness | Knows the concept; cannot apply it independently |
| 2 | Basic | Can perform simple tasks with guidance |
| 3 | Proficient | Works independently on routine tasks; handles most situations |
| 4 | Advanced | Handles complex situations; can guide others |
| 5 | Expert | Recognized authority; drives standard-setting |
The exact wording matters less than consistency — the definitions need to be specific enough that two different managers applying them to the same employee land within one point of each other. Anchor each level to observable behavior where possible, not to adjectives alone.
Set the floor, not the ideal
The minimum proficiency in a role profile is the level below which someone cannot perform the job safely and effectively. It is not the level you'd want in a perfect world.
This distinction matters for two reasons. First, if every skill has a minimum of 4 or 5, almost everyone in your organization will show a gap — which makes the gap report useless for prioritization. Second, it's more honest: a level 3 in data analysis may be genuinely sufficient for an office coordinator, even if you'd prefer a 4.
A useful calibration question: "At what proficiency level would this person just barely be doing this part of the job well enough that we'd keep them in the role?" That's your minimum.
Set the minimum through conversation, not guesswork. The hiring manager knows which skills are hard constraints (below this level, the role fails) and which are soft targets (we'd invest in training to get here over time).
Distinguish must-have from nice-to-have
Not every skill on the profile carries the same weight. Some skills are threshold requirements — a payroll coordinator must have the system-access and compliance-documentation skills before they touch a single run. Others are developmental targets — skills the organization expects someone to grow into over their first year.
A practical approach: mark skills as either required at hire or expected within 12 months. This tells you which gaps are blocking-today problems and which are growth-plan items, and it stops your gap analysis from treating every shortfall with the same urgency.
Common Mistakes to Avoid
Copying the job posting directly. Job postings are written to attract candidates; they often omit the unglamorous skills that actually matter (attention to detail in data entry, comfort with repetitive compliance tasks, tolerance for interruption) and over-emphasize aspirational ones. A role profile needs to reflect the real job.
Setting identical proficiency minimums for every skill. If everything requires a 4, nothing is prioritized. Differentiate your minimums to reflect the actual structure of the role — a handful of critical skills with high minimums, a broader set with moderate ones, and a few developmental items at the lower end.
Building profiles in isolation. A role profile that only one person has reviewed is a role profile that one person will argue with when the gap results land. Get at least one manager and one current incumbent to sanity-check the skills list and minimums before you lock them.
Letting profiles go stale. A role profile built in 2022 may not reflect a role that now includes a new tool, a regulatory change, or a restructured set of responsibilities. Treat your profiles as living documents with an annual review cadence — or trigger a review whenever a role changes materially.
Connecting Your Role Profile to a Gap Analysis
Once you have a role profile with defined skills and minimum proficiency levels, a gap analysis is arithmetic: compare each employee's actual proficiency rating (from a self-assessment, manager rating, or both) to the minimum in the profile. Where the actual falls below the minimum, there is a gap. Where it meets or exceeds the minimum, the requirement is satisfied.
The output — a skills matrix showing each employee against each required skill, colored by gap status — is what lets you answer the questions that matter: Who on the team is ready for this role today? Which skill gaps affect the most people? Where should training spend go first? What does our bench strength look like if two senior people left?
The skills gap analysis guide walks through that full process, including how to run the analysis, read the results, and turn them into a training plan.
A role profile is also the foundation of your broader skills inventory: without defined role requirements, you have a list of skills and levels but no way to interpret what they mean for organizational readiness.
Start with One Role, Then Scale
The most common reason role profiles don't get built is that the whole project feels too large. Fifteen roles, each with twenty-five skills, each needing manager sign-off — it adds up fast.
A more useful approach: pick one role where the question "who is ready?" comes up most often, or where you've had the most difficult time explaining decisions to the team. Build that profile carefully, run the gap analysis against it, and share the results. One concrete example — "here's who's at a 3 or above on all five critical skills, and here's the two-person gap we need to close before Q3" — does more to build credibility for the broader skills-management program than any slide deck about the process.
Skills Inventory Manager gives you a role profile builder pre-loaded with O*NET-derived skills (used and adapted under CC BY 4.0 from onetcenter.org), so your first profile starts from a credible draft rather than a blank page. Set your minimum proficiency levels, run the gap analysis against your team's current ratings, and have the results ready for the conversation that matters next week.
See what the role profile builder does → or start a 14-day free trial and build your first role profile today.