How to Run Your First Evaluation Cycle in 30 Minutes

The promotion conversation that stopped you cold

Picture this: a manager pulls you aside on a Tuesday afternoon and says she wants to promote one of her engineers. You ask the natural follow-up questions. What are the criteria for the next level? Has the engineer been evaluated against those criteria? Is there any documentation you could show the employee — or, if anyone ever pushed back, show a lawyer?

Silence.

It is not a lack of caring. It is a lack of infrastructure. Most HR teams at growing companies reach the 40- or 60-employee mark still running reviews out of a shared Google Doc that changes without a version log, scoring employees on a gut-feel scale that means something different to every manager, and producing no output that an employee can actually use to develop.

The good news: you do not need a six-month implementation project to fix this. A structured first evaluation cycle — a real competency framework, a consistent 1–5 scoring form, and an output that tells each employee exactly where they stand — can be up and running in about thirty minutes. This guide walks you through it, step by step.

---

What "evaluation cycle" means before you start

A career framework is the skeleton: job families (e.g., Engineering, Sales, Operations), career levels within each family (e.g., Associate → Mid → Senior → Staff), and the competency statements that define what good looks like at each level.

An evaluation cycle is the living process that runs on top of that skeleton: a defined window of time in which managers score each employee against the competency statements, submit evidence notes, receive Admin approval, and produce a per-employee skill-gap report that becomes the input to a development conversation.

If you have never built either, start here. You do not need both to be perfect before you run the first cycle — you need them to be good enough to produce a consistent, documented result.

---

Step 1 — Seed your framework from an O*NET template (10 minutes)

The fastest way to avoid starting from a blank page is to use an occupational competency template drawn from ONET, the U.S. Department of Labor's continuously updated database of nearly 1,000 occupations. ONET's Content Model organizes each occupation into skills, knowledge areas, work activities, and abilities — exactly the raw material a career-level competency statement is built from.

In Career Ladder Builder, every plan includes access to O*NET-seeded templates covering 20+ job families. When you create a new career framework, you select the job family most relevant to the team you want to evaluate first, and the platform pre-populates a set of competency statements you can edit, remove, or add to.

For your first cycle, resist the urge to customize everything. Pick the job family. Accept the default competencies with light edits. Add your career levels (most HR teams start with three to five). Assign competencies to levels. That is it.

A practical constraint to hold in mind: ONET provides occupational and competency content — it does not supply career levels or company-specific leveling rubrics. Those are yours to define inside the platform. The ONET templates give you the competency vocabulary; your business context determines what "Senior" means vs. "Mid."

For a deeper look at how O*NET content maps to a company-specific framework, see our guide to building a competency framework from O*NET content.

This article references occupational content from ONET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). ONET data is used under CC BY 4.0.

---

Step 2 — Configure your evaluation form (8 minutes)

With a framework in place, the next step is confirming how managers will score employees. Career Ladder Builder uses a 1–5 scale by default:

Score	Meaning
1	Not yet demonstrated
2	Developing
3	Meets expectations for the level
4	Exceeds expectations for the level
5	Role model — consistently demonstrates at the level above

This scale matters more than it looks. When every manager uses the same five points with the same anchored definitions, scores become comparable across teams — which is what makes the eventual skill-gap report meaningful and what makes a promotion decision documentable. Without anchored definitions, a "4" from one manager and a "4" from another may describe completely different employees.

For each competency on the form, managers enter a score and a brief evidence note: one or two sentences describing a specific, observable behavior. The evidence note is what transforms a number into a record that can support a promotion decision, a development conversation, or, if ever needed, a documented basis for an employment action. For a detailed explanation of how to apply the scale consistently across managers, see how the 1–5 evaluation scoring scale works.

Before you launch, confirm two configuration details:

1. Who is the Admin approver? In Career Ladder Builder, manager submissions route to an Admin for review before they are finalized. Decide now whether that is you, a People Operations lead, or a senior HR business partner — and make sure that person has Admin access.
2. What is the cycle window? For a first cycle, a two-week submission window is generous. Set a hard deadline, not a soft suggestion. Cycles that lack a deadline tend to drift indefinitely.

---

Step 3 — Add employees and assign managers (5 minutes)

Navigate to your employee roster and confirm that each person who will be evaluated in this cycle is listed and assigned to the correct manager. For your first cycle, it is fine to scope this to one team or one job family rather than the whole company. Starting narrow lets you pressure-test the process — the scoring form, the Admin approval flow, the gap report output — before rolling it out to every department.

Double-check that manager accounts are active and that each manager can see only the employees they are responsible for evaluating. This is a basic data hygiene step that prevents a manager from inadvertently viewing another team's in-progress scores.

---

Step 4 — Launch the cycle and brief your managers (5 minutes)

Once the framework, form, and roster are in place, launch the cycle. Career Ladder Builder sends automated notifications to managers when a cycle opens.

Your job in the next five minutes is a brief manager communication — a short email or Slack message — that covers three things:

1. What they are being asked to do. Score each of their direct reports against the competency statements on the evaluation form. Add an evidence note for each score. Submit before the deadline.
2. How the scale works. Paste the five-point anchor definitions from Step 2. Remind managers that a 3 means "meets expectations for this level" — it is not a bad score. Many managers inflate to 4 by default because 3 feels like a slight; anchored language corrects that drift.
3. What happens after they submit. Remind them that submissions go to Admin for review before anything is finalized, so employees will not see scores until the Admin has approved the cycle output.

Brevity here is a feature, not a corner cut. If the brief takes more than five minutes to write and a manager more than five minutes to read, the instructions are too complicated for a first cycle.

---

Step 5 — Review, approve, and release the skill-gap report (2 minutes of setup; async review)

When manager submissions come in, the Admin approval workflow surfaces them for your review. You are looking for two things:

• Score distribution. Are all of one manager's reports clustered at 4 or 5? That is a calibration flag, not necessarily a problem — but it is worth a quick conversation before you approve.
• Evidence note quality. A score with no evidence note is a score with no defensible basis. Send back any submission missing notes and ask for a one-sentence behavioral observation.

Once you approve a manager's submissions, the platform auto-generates a per-employee skill-gap report. The report shows each competency, the score the employee received, and a delta that identifies the gap between current performance and the target for the next career level. That delta — the difference between where the employee is now and where the next level requires them to be — is the input to every development conversation that follows. For a full explanation of how to read and act on the output, see how to interpret a skill-gap report.

The most important thing to know about the first cycle: the gap report does not need to be perfect. It needs to be honest, consistent, and documented. Those three properties are what distinguish a first cycle from an ad-hoc conversation.

---

What to do with the output

The skill-gap report is not the end of the process — it is the beginning of the development loop. After the first cycle closes:

• Share each employee's report with their manager before the manager has a development conversation. The report gives the manager specific competencies to discuss, not a vague sense of performance.
• Set one to three development action items per employee based on the largest gaps. These should be specific, time-bound, and tied to a named competency: "Complete two peer code reviews per sprint to develop the Technical Review competency from a 2 to a 3 by the next cycle."
• Schedule the next cycle. A single evaluation is a data point. Two evaluations, separated by a quarter or a half-year, are a trend. For guidance on cadence and structure, see review cycle best practices and how to evaluate employee career readiness.

The employees who are most likely to stay and grow are the ones who can see a clear path — who know not just what their score is, but what closing a specific gap looks like in practice. That visibility is what a structured first evaluation cycle creates, and it is something no amount of informal feedback can reliably replicate.

---

A note on the manager's workload

One objection HR teams hear when introducing structured evaluation: "This will take managers hours they don't have." For a first cycle scoped to one team of eight to twelve people, a well-configured form with clear anchored definitions and brief evidence-note prompts should take a manager forty-five minutes to an hour — total, for the whole team. That is one regular meeting replaced.

The tool that can help managers do that work efficiently before your platform cycle is live, or alongside it for teams that need an offline-first option, is our Career Evaluation Scorecard — Manager's Edition. It is a structured standalone scorecard that uses the same 1–5 anchored scale, organized by competency and career level, so managers can gather their observations before entering them into the platform.

---

Your first evaluation cycle starts now

The thirty-minute path described here — seed a framework, configure the form, assign employees, brief managers, approve, release — is not a shortcut. It is the minimum viable structure that produces a documented, consistent, defensible result. Everything that makes a career framework valuable at scale — calibration across managers, promotion criteria that hold up to scrutiny, development conversations with a factual basis — begins with the first cycle.

Explore the full feature set to see how the framework, evaluation, gap report, and action-item tracking work together. When you are ready to run it yourself, start a 14-day free trial — no per-user fees, no implementation contract, and no blank page to start from.