What changes about performance reviews when you hit 100–250 employees?

Three things change: (1) You have enough managers that a single calibration session stops working—you need department-level sessions feeding into an executive calibration. (2) Generic templates break down—Engineering reviews and Sales reviews need fundamentally different competencies. (3) Promotion decisions become harder to explain, so your rating criteria need to link to a leveling guide. Most companies at this size still run one generic review and suffer for it.

Should 100-250 employee companies do 360-degree feedback?

Selectively. Full 360s for every employee create admin overhead that HR teams at this size can't absorb. Better approach: upward feedback (reports rate managers) for all people managers, plus peer input for senior ICs being considered for promotion. This gives you the signal you actually need—whether managers are effective and whether promotion candidates have cross-functional credibility—without drowning HR in survey data.

How do you run calibration for 100–250 employees?

Two-layer structure works best: department heads run their own calibration session first (30–60 minutes per function), then an executive calibration reconciles across departments (90 minutes max). The exec session should only see the edge cases—Exceeds ratings and promotion recommendations. Middle ratings are resolved at the department level and don't need executive time.

How do you connect performance reviews to promotions at this size?

Build a simple leveling guide first—3–5 levels per function with behavioral descriptions of what each level looks like. Then tie Exceeds ratings to 'operating at the next level' in specific competencies. This makes promotion decisions defensible and reduces the bias toward louder employees who advocate for themselves in the room. Confirm's ONA data helps here—it shows who's actually influencing across the org, not just who's visible.

What's the most common calibration failure at 100–250 employees?

Skipping department-level calibration and going straight to an executive session. By the time the exec team sees ratings, there are 15 managers' worth of inconsistency baked in. The session blows up trying to reconcile everything. Fix: require department heads to run their own calibrations first and come to the exec session with settled ratings. Exceptions only.

Performance Review Template for 100–250 Employee Companies

Name: Performance Review Template for 100–250 Employee Companies
Brand: Confirm
Price: 8.00 USD
Availability: InStock

You've outgrown the one-size-fits-all template. At this size, IC and manager reviews need different tracks, calibration needs department-level structure, and promotions need a leveling guide behind them.

See how Confirm handles this →

What changes when you hit 100–250 employees

🏗️

One calibration session won't cut it

At 100+ employees, a single all-hands calibration session becomes a 5-hour disaster. You need department sessions feeding into an executive calibration—two layers instead of one.

🔀

IC and manager tracks need to split

A great engineer and a great engineering manager get evaluated on fundamentally different things. A shared template produces reviews that don't capture either one accurately.

📐

Promotions need a leveling guide

At 50 people, promotions happen through conversation. At 200 people, they need documented criteria—otherwise you promote whoever advocates loudest, not whoever performs best.

🔍

Upward feedback becomes critical

Your managers have 5–10 direct reports now. Poor management is driving churn you can't see. Structured upward feedback exposes manager effectiveness before you're writing departure offers.

IC Track (Individual Contributors)

Individual Contributor Template

Use for all ICs across departments. Customize competency names per function—"Technical Execution" for Engineering, "Pipeline Management" for Sales, "Content Output" for Marketing—while keeping the rating structure consistent.

1. Core Role Performance

Quality and scope of work delivered. Reliability on commitments. Output consistency over the review period.

Exceeds Delivered at a scope beyond their current level. Quality is consistently high. Drove outcomes that required others to raise their game.

Meets Delivered core responsibilities reliably. Output quality is consistent. Committed work landed on time with acceptable quality.

Below Missed key commitments or required significant rework. Quality is inconsistent. Manager intervention was needed to keep work on track.

Example phrases:

"Took on the highest-complexity project in the roadmap without prompting and delivered it ahead of schedule."
"Hit every sprint commitment this cycle. Code quality is clean, reviews are thorough, and incidents in her area are rare."
"Two major deliverables required manager re-scoping mid-cycle. Execution is inconsistent when work is ambiguous."

2. Cross-Functional Impact

Influence and collaboration beyond immediate team. Who comes to them for help? What cross-team work did they drive or enable?

Exceeds Recognized go-to resource across multiple teams. Drives cross-functional projects proactively. Influence extends well beyond job scope.

Meets Collaborates well outside the immediate team. Shows up reliably for cross-team asks. No friction in cross-functional work.

Below Work is siloed. Cross-functional asks create friction or fall through. Other teams route around them when possible.

Example phrases:

"Three different teams listed him as critical to their roadmap this cycle—engineering, product, and customer success."
"Reliable cross-team collaborator. Shows up when asked, follows through on commitments to adjacent teams."
"Tends to scope work narrowly. Missed a dependency that affected two other teams because she didn't loop them in early."

3. Leveling & Promotion Readiness

Is this person operating at, below, or above their current level? What evidence supports a level change?

Operating above level Consistently performs at the competencies of the next level. Ready for promotion conversation based on sustained performance, not one strong quarter.

At level Performing solidly at current level. Not yet demonstrating next-level competencies consistently.

Below level Not fully meeting current-level expectations. Needs a clear development plan before promotion is on the table.

Example phrases:

"Operating as a Staff engineer in scope and influence. Promotion to Staff is warranted—she's been at this level for 6 months."
"Solid L3 IC. Will be ready for L4 discussion in 6–12 months if he continues developing his cross-team influence."
"Not yet at full L2 expectations. Needs 2 more cycles of consistent delivery before we can discuss L3 readiness."

Manager Track (People Managers)

Manager Template

Use for all people managers. The key shift: a manager's performance is their team's performance. Avoid evaluating managers on individual IC contributions—that defeats the purpose of the separate track.

1. Team Delivery

Did the team hit commitments? Is the manager accountable for team output? Did they protect their team's capacity and prioritize effectively?

Exceeds Team consistently exceeds output expectations. Manager is the reason, not coincidence. Navigates blockers and priority changes without delivery failures.

Meets Team hits core commitments. Manager is accountable for results and doesn't deflect. Prioritization decisions are sound.

Below Team repeatedly misses commitments. Manager is unclear on team capacity or fails to escalate priority conflicts early. Delivery failures are a pattern.

Example phrases:

"Team shipped every roadmap commitment this cycle and absorbed two unplanned projects without missing deadlines on the core work."
"Hit the key metrics. A few minor slips, but overall delivery was reliable and the manager was accountable for the ones that missed."
"Team missed three major milestones. Post-mortems consistently attribute failures to resourcing or requirements—not to execution choices."

2. People Development

Is the team getting better? Are reports growing their skills? Is manager developing people or just deploying them?

Exceeds Visible talent growth across the team. Reports regularly promoted or expanded in scope. Manager is a talent multiplier the company relies on.

Meets Reports grow at expected pace. Development conversations happen regularly. No concerning attrition from the team.

Below Team growth is stalled. Attrition in the team is above average. Development conversations don't happen or lack follow-through.

Example phrases:

"Two direct reports promoted this cycle. A third is ready for promotion in the next one. This team is the talent pipeline for the whole function."
"Regular 1:1s, clear development goals, and consistent follow-through. Team retention is strong and morale is high."
"Two of three team members are actively interviewing elsewhere. Exit interviews cite 'no growth opportunity'—this manager hasn't had a development conversation in two cycles."

3. Upward Feedback Summary

What do direct reports say about this manager? This section synthesizes anonymous upward feedback scores into a qualitative summary.

Strong Upward scores significantly above average. Reports describe clear communication, strong support, and development focus. No recurring themes of concern.

Adequate Scores near average. Some positive feedback on specific areas, some development themes. Nothing alarming.

Concern Multiple reports cite recurring problems—unclear direction, unavailability, favoritism, or poor development support. Warrants a structured development plan.

Example phrases:

"Highest upward scores on the team: reports consistently cite clarity of direction, availability, and career investment."
"Solid scores on clarity and delivery support. Development area: reports want more career development conversations."
"Recurring theme across 4 of 5 reports: 'I don't know how decisions get made.' This manager needs to work on transparency and inclusion."

Two-layer calibration structure

One session no longer covers 100–250 employees. Here's how to structure calibration at this size.

Layer 1

Department Calibration (Per Function)

Each department head runs a 45–90 minute calibration with their managers. Focus: rating consistency within the department, surface any Exceeds or Below edge cases, and agree on promotion nominations. Output: settled ratings for all employees in the function, plus a short list of cross-cutting cases to escalate.

↓

Layer 2

Executive Calibration

Department heads present their settled ratings and promotion nominations to the exec team (60–90 minutes). The only items in scope: promotion decisions, cross-department outliers (e.g., one department's Exceeds looks like another department's Meets), and high flight-risk individuals. Middle ratings are not relitigated.

Tool requirements at this size

Breaks here

Spreadsheets

Stops working at 100+ employees. You'll spend a week aggregating data across 8–12 department sheets, lose version control, and make calibration nearly impossible to run systematically. Most companies learn this the hard way at cycle two or three.

Functional

Basic PM platforms

Handles forms and reminders well. Struggles with cross-department calibration workflow, multi-track templates, and leveling tie-ins. Gets you through cycles but adds friction at calibration time.

Purpose-built

Confirm

Two-layer calibration built in. ONA data shows cross-functional impact so IC reviews go beyond manager observations. Upward feedback built into the manager track. Promotion readiness flags surface automatically. Scales from this size to 5,000 without rebuilding your process.

See a demo →

This is where calibration either becomes a system or a crisis.

At 100–250 employees, you're building the review infrastructure your company will run for the next 10 years. Get it right now and it scales cleanly. Cut corners and you'll rebuild it under pressure at 500 people. Confirm was built for exactly this inflection point.

80%

time saved on performance reviews

40%

reduction in rating bias

98%

review completion rate

See a demo →