How to Write Behavioral Competency Statements That You Can Evaluate
By Career Ladder Builder
When the review form says "communicates well" and every manager means something different
Picture a mid-year review season at your company. Twelve managers open the same evaluation form. The first competency on the list reads: "Demonstrates strong communication skills."
Manager A rates her direct report a 4 out of 5 because he speaks clearly in team meetings. Manager B gives a 2 to someone who writes beautifully but dislikes all-hands presentations. Manager C gives 5s across the board because he wants to avoid difficult conversations. Three managers. Three mental models. One meaningless score.
When a high performer later asks why she wasn't considered for a promotion to Senior Designer, there's no clean answer — because the criteria that produced her score were never the same criteria twice.
This is the core problem with vague competency statements. It isn't that managers are careless; it's that the statement itself provided no shared definition of what good looks like. Fixing that starts at the point of authorship, before any evaluation cycle runs.
This article gives you a practical method for writing behavioral competency statements that are specific enough for consistent scoring, observable enough for a manager to point to real evidence, and differentiated enough to mean something different at each career level. By the end, you'll have a reusable framework you can apply to every competency in your career ladder.
What makes a competency statement "behavioral"
A competency is a cluster of knowledge, skills, and behaviors required to perform a role effectively. A behavioral competency statement is the written description of what that competency looks like in action — observable, specific, and tied to the level of the role.
The distinction matters because "behaviors" are things a manager can actually witness or gather evidence for. You cannot watch someone "have strategic thinking." You can watch someone "identify two or more second-order effects of a proposed solution before the team commits to an approach."
A well-formed behavioral competency statement has three properties:
- Observable. A third party could confirm whether the behavior occurred, using notes from a meeting, a document artifact, a peer's account, or a direct observation.
- Specific. It describes what the person does, not a trait they possess. Traits (collaborative, proactive, strategic) are adjectives. Behaviors are verbs operating in a context.
- Level-differentiated. The same competency — say, "Stakeholder Communication" — should read differently for an Associate than for a Senior or a Lead. The behavior that earns a 3 at the Associate level should be what earns a 1 at the Senior level. Without level differentiation, your scoring scale has no consistent anchor.
If you're still deciding whether a competency statement belongs inside a broader career framework or a standalone competency model, the distinction between those two structures is worth understanding before you write — competency model vs. career framework covers that decision in detail.
The anatomy of a strong behavioral competency statement
A reliable structure for a behavioral competency statement has four components. You don't need all four in a single sentence — they can span a short statement of two or three sentences — but all four should be answerable from the text.
1. The action verb (observable behavior)
Start with a strong, specific action verb. Words like facilitates, synthesizes, escalates, documents, negotiates, and identifies are evaluable. Words like understands, appreciates, supports, or demonstrates are not — they describe a state of mind or a disposition, which a manager cannot score without a further definition of what "understanding" looks like externally.
Weak: Demonstrates an understanding of project risks. Strong: Identifies and documents risks before project kick-off, including likelihood and potential impact, so the project lead can make an informed go/no-go decision.
2. The context or condition
State where or when the behavior occurs. This grounds the statement in the work the person actually does and prevents managers from reaching for anecdotes from a completely different domain.
"...in cross-functional planning meetings" is more useful than "...when communicating," because it tells the manager which situations to look for and which evidence to collect.
3. The quality marker or standard
What does "good" look like? Quality markers anchor the scoring rubric. They might reference completeness ("without prompting"), consistency ("across all assigned accounts"), scope ("for decisions affecting two or more teams"), or outcome ("in a way that reduces clarifying follow-up questions from stakeholders").
Avoid relative quality words like effectively, appropriately, or well — they reintroduce ambiguity by deferring the definition back to the individual manager.
4. The level signal
The level signal is what makes the same competency mean something different on an Associate career level versus a Senior or Lead. It controls scope, autonomy, and complexity:
- Scope: Individual contribution → Team → Department → Organization
- Autonomy: With guidance → Independently → Setting the standard for others
- Complexity: Routine situations → Ambiguous or novel situations → Systemic or structural problems
Changing one of these three dials shifts the statement from one career level to the next without rewriting the underlying competency from scratch.
A worked example: "Communication" across three career levels
Here is how one competency — Stakeholder Communication — might be written across three levels of an IC track. Observe how the action verb, context, quality marker, and level signal each shift.
Level 1 — Associate: "Communicates project status updates in writing (via team channel or email) at least weekly, with enough context that a colleague unfamiliar with the project can understand the current state, next step, and any blockers, with guidance from a senior team member on format when needed."
Level 2 — Mid-Level: "Independently prepares and delivers project status communications to internal stakeholders at a cadence appropriate to project risk, calibrates the level of detail to the audience, and surfaces blockers early enough to allow for resolution before they affect the timeline."
Level 3 — Senior: "Structures communication strategies for complex or multi-stakeholder projects, including deciding what to communicate, to whom, and at what cadence; coaches less senior team members on how to prepare effective status updates; and identifies when a communication breakdown is structural and proposes a fix."
Notice what has changed across levels: the scope (one project → multi-stakeholder → organizational patterns), the autonomy (guided → independent → setting the standard), and the complexity (status updates → calibrated audience management → structural problem-solving). The underlying competency — Stakeholder Communication — is the same; the bar is not.
This leveling logic is also what makes your evaluation scoring scale defensible. A manager giving a 3 out of 5 on "Stakeholder Communication" can point to which level's description the employee currently meets and which one they're not yet meeting. That's the conversation that produces development plans rather than shrugs.
Five common writing mistakes — and how to fix them
1. Trait statements disguised as behaviors
The mistake: "Is proactive in identifying problems." Why it fails: "Is proactive" is a trait assessment. A manager cannot consistently score it because "proactive" means different things to different people. The fix: Replace the trait with the behavior that demonstrates the trait. "Flags risks and potential blockers before they become issues, typically before being asked, and brings at least a preliminary mitigation option to the conversation."
2. The double (or triple) barrel
The mistake: "Communicates clearly, builds relationships with stakeholders, and manages up effectively." Why it fails: Three behaviors in one statement make it impossible to score. Does a 3 mean the employee met two of three? All partially? The manager has to decide privately, which reintroduces inconsistency. The fix: One behavior per statement. If a competency cluster has three components, write three separate statements and score them separately, or explicitly define the cluster and make clear that all components must be met for a given score.
3. The unmeasurable quality marker
The mistake: "Communicates complex ideas in a clear and effective way." Why it fails: "Clear and effective" is the quality marker, but it delegates the definition of quality to each manager individually. The fix: Anchor the quality marker to an observable outcome or a concrete standard. "Communicates complex technical concepts in writing so that a non-technical stakeholder can restate the key decision or risk without referring back to the original document."
4. Level-agnostic statements
The mistake: Using the same competency statement across all levels, then relying on the scoring rubric (1–5) to carry all the differentiation. Why it fails: If the statement doesn't change, a 3 at the Associate level and a 3 at the Senior level mean different things only in the scorer's head — and different scorers carry different heads. The fix: Write level-specific statements for each competency, or write a single statement with an explicit progression table showing how scope, autonomy, and complexity shift at each level.
5. The invisible evidence requirement
The mistake: Writing statements that are evaluable in theory but for which no evidence actually exists in your work environment. Why it fails: A manager might know intuitively whether an employee meets the bar, but without a documented artifact — a document, a meeting record, a peer account, a project output — the score is unchallengeable and the feedback conversation has no substance. The fix: As you draft each statement, ask: "Where would a manager find evidence that this behavior occurred?" If the honest answer is "I'd just know," rewrite the statement to name an output, venue, or artifact type.
Connecting behavioral competency statements to your evaluation cycle
Writing strong statements is the first step. The second is connecting them to an evaluation workflow that actually uses them.
In practice, that means three things:
Scoring anchors for each level. Attach a brief description to each score point (1–5) that translates the level-specific behavioral statement into a rating. A score of 3 should mean "meets the statement for this level consistently." A 4 should mean "meets it with notable depth or scope expansion." A 2 should mean "meets it in some situations but not consistently or without significant guidance." Without this, managers will fill the scale with their own private anchors — and your scoring data will be noisy.
Evidence collection built into the cycle. Reviewers should enter evidence notes — a concrete example, a document reference, an observed interaction — alongside every score. A behavioral competency statement is only as useful as the evidence it invites. If your current process doesn't capture evidence, the statements will improve consistency only partially.
A calibration step before scores are final. Even with excellent statements, managers will interpret the edges differently. A brief calibration meeting — where two or three managers compare scores on shared cases — catches outliers before they become official record and before employees see them. This is also where an Admin approval workflow earns its keep: a second set of eyes on scores before they're locked creates a natural checkpoint for outliers.
If you're building out a full evaluation cycle from scratch, how to evaluate employee career readiness walks through the process end to end, including how to sequence reviews and structure the approval step.
Using an O*NET-based competency library as a starting point
Writing competency statements from a blank page is time-consuming and inconsistent. A well-maintained competency library — organized by job family — gives your managers a consistent vocabulary and lets you spend your effort on level differentiation and context-setting rather than generating competency clusters from scratch.
Career Ladder Builder's template library is seeded from ONET, the U.S. Department of Labor's occupational information database, which covers nearly 1,000 occupations and is updated continuously through tens of thousands of surveys. ONET's work activity and skill descriptors provide a strong, standardized starting vocabulary that you then adapt to your company's context and level structure.
For a deeper look at how O*NET's competency content maps to the job families most relevant to mid-size companies, see O*NET competency frameworks explained.
If you want to start with a ready-made library rather than building from O*NET scratch, the Competency Library Starter Kit gives you 50 drafted competency statements across 5 job families — a practical shortcut for getting a first draft of your competency framework into review without spending weeks in authorship.
This article references occupational content from O*NET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). O*NET data is used under CC BY 4.0.
Putting it together: a one-page authorship checklist
Before any competency statement goes into your framework, run it through these five questions:
- Does it start with a specific action verb? If the verb is understands, appreciates, supports, or demonstrates, rewrite it.
- Can a manager find evidence for it in real work? If not, either add an artifact or output reference, or rewrite the statement.
- Does it have a quality marker that doesn't delegate the definition back to the scorer? If the only quality words are effectively or well, anchor them to an outcome or standard.
- Is it scoped to a single behavior? If it contains and more than once, consider splitting it.
- Is it level-differentiated from the adjacent levels? Compare it to the statement immediately above and below in the leveling table. If they look almost identical, revisit the scope, autonomy, or complexity dial.
Your next step
If you're starting or rebuilding a career ladder, competency statement quality is the linchpin. Strong statements make your evaluation scores defensible, your feedback conversations substantive, and your promotion decisions easier to explain to the employee and to the rest of the team.
For a full picture of how competency statements fit inside a career ladder structure — job families, career levels, IC and Manager dual tracks — how to build a career ladder is the logical next read. Or, if you'd like a ready-made set of drafted statements to react to rather than starting from a blank page, download the Competency Library Starter Kit.
When you're ready to move from a document library to a live evaluation cycle — with structured scoring, evidence notes, an Admin approval workflow, and automated gap reports — start a 14-day free trial of Career Ladder Builder and bring your competency statements into a system built to use them.
Enjoying this? Get more HR development guides in your inbox.
