Articles

•

November 16, 2026

How to Tie Performance Reviews to Role Responsibilities

Sign up for our newsletter
Read for free. Unsubscribe anytime.
SHARE IT!

To tie reviews to each role's responsibilities at 130 people, write three to seven outcome-based responsibilities for every role, attach the SOPs and goals that go with them, and build each review from that list, so people are measured on what their role owns rather than on a manager's memory. Trainual is Business Operations & SOP Software that turns company knowledge into employee performance, with Training, Operations, and Performance in one place, so the role, the training, and the review all live in one place.

The calibration meeting is going sideways. Two support reps, same role, different managers. One got a 4 for "handling tough customers well." The other got a 3 for "not hitting response-time targets," a target the first manager never mentioned. Both reviews are reasonable on their own terms. Side by side, they measure two different jobs.

That's the problem at around 130 people: enough managers that each one carries their own picture of every role, and not enough written down to keep those pictures the same. The fix is to make the role, not the manager, the source of truth.

Updated November 2026.

Key takeaways

  • The role is the standard. Write what each role owns, and build every review from it.
  • Phrase responsibilities as outcomes, so they can be checked instead of debated.
  • Review responsibilities and goals separately, so one-off goals don't replace the core of the job.
  • Calibrate across managers before reviews go out, using the same role descriptions.

Why responsibility-based reviews matter at 130 people

At 30 people, the founder knows every role and every review is consistent by default. At 130, three things change:

  1. More managers, more interpretations. Every manager has a slightly different idea of what each role is for.
  2. Same role, different teams. People in the same role report to different managers, which makes fairness visible and inconsistency costly.
  3. Higher stakes. Raises, promotions, and exits depend on reviews, and people compare notes.

Reviews tied to written responsibilities fix all three, because everyone is reviewed against the same description of the job. For more on why written roles matter, see roles vs. responsibilities.

How to write responsibilities you can review

The difference between a responsibility you can review and one you can't is usually wording. Activities describe what someone does; outcomes describe what should be true when they do it well.

Activity (hard to review)
Outcome (easy to review)
Support lead
Answers customer tickets
Support lead
Keeps first-response time under four working hours for the team's queue
Account manager
Manages client relationships
Account manager
Renews at least 90% of assigned accounts each year
Operations coordinator
Handles scheduling
Operations coordinator
Publishes a complete crew schedule by Thursday at noon for the next week
Office manager
Takes care of the office
Office manager
Keeps supplies, vendors, and facilities running with no unplanned downtime
Sales rep
Does outreach
Sales rep
Books enough qualified first meetings to hit the monthly pipeline target
  1. Start from the work, not the job title. List what the role is accountable for each week, month, and quarter.
  2. Rewrite each item as an outcome. "Publishes the crew schedule by Thursday at noon" beats "handles scheduling."
  3. Keep it to three to seven. That's enough to cover the job and few enough to remember.
  4. Attach the how. Link the SOPs that explain how each responsibility gets done.
  5. Name the owner of the role description. Usually the department lead, who updates it when the job changes.

Where two roles seem to own the same thing, settle it before review season; how to define ownership across overlapping roles walks through it.

How to build a review from the role

Once each role has written responsibilities, the review almost writes its outline itself:

Review section Comes from Example: support lead
Responsibilities The role's written responsibilities First-response time, queue health, escalation handling
Goals Goals the person owned this period Cut average resolution time by 15%
How the work is done The SOPs attached to the role Follows the escalation and refund processes
Training and growth Training completed and open growth areas Finished the new refund-policy training; growth area: coaching new reps
Feedback Praise and course-corrections recorded during the period Two customer shout-outs; one note on handoff timing
  1. Responsibilities: how well the person delivered on each outcome the role owns.
  2. Goals: progress on the goals they owned this period.
  3. How the work is done: whether they follow the SOPs attached to the role.
  4. Training and growth: what they've completed, and which growth areas are open.
  5. Feedback: the praise and course-corrections recorded during the period.

Ask each person to complete a self-review against the same sections first. When both reviews use the same structure, the conversation focuses on differences, not on what the job is.

Example: a role written for reviews

Here's what a review-ready role looks like for a support lead:

Role: Support lead. Reports to: head of customer experience. Owner of this description: head of customer experience. Last updated: October 2026.

Responsibilities:

  1. Keeps first-response time under four working hours for the team's queue.
  2. Resolves or correctly escalates every ticket older than two days.
  3. Keeps customer satisfaction for the team at or above the company target.
  4. Trains and coaches new support reps through their first 60 days.
  5. Updates the support SOPs within a week whenever a process changes.

Attached SOPs: ticket triage, escalation, refunds, and new-rep onboarding.

Goals this period: cut average resolution time by 15%.

Every line can be checked, every line points to how the work is done, and every manager reviewing a support lead starts from the same page.

How to roll this out before your next review cycle

Give yourself about six weeks:

  1. Weeks 1 to 2: department leads write or update responsibilities for every role, starting with roles that have several managers.
  2. Week 3: attach SOPs and confirm each role has an owner.
  3. Week 4: share the role descriptions with the people in each role and invite corrections.
  4. Week 5: brief managers on the rating scale and the review structure.
  5. Week 6: open self-reviews, followed by manager reviews and calibration.

How to calibrate reviews across managers

At 130 people, calibration is what keeps ratings meaningful:

  1. Use one rating scale with a short definition for each level.
  2. Group reviews by role, not by manager, before they go out.
  3. Hold a 60-minute calibration meeting where managers compare ratings for the same roles and explain outliers.
  4. Adjust where the evidence doesn't support the rating, and note why.
  5. Share the role descriptions with employees before reviews, so nobody is surprised by the standard.

Keep roles current, or reviews drift

A review tied to an outdated role is worse than no role at all. Build a habit of updating roles when the work changes:

  • When a role changes, update the responsibilities first, then the next review reflects them.
  • Review every role description once a year, ideally a month before review season.
  • Track the changes, so it's clear which version applied during which review period.
  • Tell the people in the role when their responsibilities change, and why.

Connect reviews to growth

A review that ends in a score tells someone where they stand. A review that ends in a growth area tells them where to go:

  • Pick one or two growth areas per person, tied to a specific responsibility.
  • Link each growth area to training that builds that skill.
  • Check progress in monthly one-on-ones, not just at the next review.
  • Close the growth area when the responsibility is consistently met.

For more on the review conversation itself, see how to give and receive a performance review.

Common mistakes

  • Activity-based responsibilities. "Manages clients" can't be reviewed; "renews 90% of accounts" can.
  • Too many responsibilities. Fifteen bullet points means nothing is the core of the job.
  • Reviewing only goals. People get rated on this quarter's project and not on the job they do every day.
  • Skipping calibration. Ratings drift by manager, and employees notice.
  • Stale role descriptions. If the role changed in March, the review in June should reflect it.

How to tie reviews to roles in Trainual

Trainual keeps roles, responsibilities, SOPs, training, and reviews in one system, so a review starts from what the role owns.

Training: build the skills each role needs.

  • Training by role. Role-based training paths teach each role's responsibilities and SOPs, with completion tracked by person.
  • The how behind each responsibility. Process documentation links the SOPs that explain how each outcome gets done.

Operations: one written standard for every role.

Performance: reviews measured against the role.

  • Reviews built from the role. In Performance, review cycles draw on each role's responsibilities, goals, and completed training, with self and manager reviews.
  • Feedback captured all year. Public praise and private course-corrections are recorded as they happen.
  • Growth areas tied to training. Growth areas link to the exact training that closes a gap.

Together, that's the loop:

  • Train: so everyone knows how work should be done.
  • Operate: so everyone knows what needs to happen today.
  • Perform: so everyone knows what's expected and how knowledge turns into better work.

For the full picture, see How Work Is Won, and if you're building the system without an HR team, performance management for a 75-person company without HR.

Quick wins to start this week

Quick win #1: Pick one role with several managers

Compare how each manager describes it.

Quick win #2: Rewrite its responsibilities as outcomes

Three to seven, each one checkable.

Quick win #3: Attach the SOPs to each responsibility

So the role shows how, not just what.

Quick win #4: Draft one rating scale with definitions

Share it with every manager before the next cycle.

Quick win #5: Book a calibration meeting

Sixty minutes, the week before reviews go out.

Ready to see how Trainual works?

👉 Book a demo and see how Trainual ties every review to the responsibilities, goals, and training each role already has.

Want a sneak peek?

👉 Read customer stories from growing teams who made roles clear and reviews fair.

Frequently asked questions

How do you tie performance reviews to each role's responsibilities?

Write three to seven outcome-based responsibilities for every role, attach the SOPs and goals that go with each one, and build every review from that list. People are then measured on what their role owns, not on each manager's idea of the job.

What performance review software ties reviews to role responsibilities?

Look for software where roles, responsibilities, and reviews live in the same system, so a review starts from what the role owns. Trainual's Performance builds reviews from each role's responsibilities, goals, and completed training.

How do you write responsibilities that can be reviewed?

Phrase each one as an outcome someone could check without asking anyone's opinion, such as "publishes the crew schedule by Thursday at noon," rather than an activity like "handles scheduling." Keep it to three to seven per role.

How do you keep reviews consistent across managers at a 130-person company?

Give every manager the same written responsibilities for each role, use the same rating scale, and hold a short calibration meeting before reviews go out, where managers compare ratings for the same roles.

What happens to reviews when a role changes?

Update the role's responsibilities first, then let the next review reflect the new version. Reviewing someone against an outdated role description is unfair to them and confusing for the manager.

How many responsibilities should a role have?

Three to seven. Fewer and the review misses important parts of the job; more and nothing stands out as the core of the role.

Should goals and responsibilities be reviewed separately?

Yes. Responsibilities are what the role always owns; goals are what the person is pushing on this period. A good review covers both, so someone isn't rated only on one-off goals.

How do reviews connect to training?

When a review shows a gap in a responsibility, set a growth area and link it to the training that covers that skill. In Trainual, growth areas link directly to the training that closes the gap.

📰

Become a better business
leader in 5 minutes or less.

Join over 50K readers who get The Manual in their inbox each month.
Practical, tactical insights you can use right away.
Join our 50k+ readers

Smarter than your smartest employee. Faster than your shared drive.

The know-it-all tool every employee uses to understand what to do, how to do it, and who’s doing what. Purpose-built to make your team instantly more productive, consistent, and aligned from day one to day 1,000.