Teamwork Performance Review: The Nine Things Actually Being Scored

A teamwork performance review rates specific behaviors, not one overall impression: whether you keep commitments, share what you know, put the shared goal ahead of your own, disagree without damaging trust, and back decisions that went against you. Each has evidence behind it, and evidence is what you bring.

If you came here for phrases to drop into a self-assessment, the instinct makes sense — there are thousands online. But a phrase describes a rating; it doesn’t earn one. What follows is the other half: the nine things a teamwork rating is usually assembled from, and what counts as proof for each.

Why the phrase lists leave you stuck

Appraisal wording for this topic tends to come as lists of 115 teamwork phrases, 100, 50, 40, 20 — sheer volume, not explanation of criteria. Appraisal wording is a deadline-driven need that recurs every cycle, so the emphasis lands on quantity of sentences rather than what the sentences are meant to demonstrate.

Two things follow. Almost all of it is written for the manager filling in the form — third-person sentences about someone else, which is why they never quite fit when you lift them into your own words. More importantly, they assume the criteria without naming them, leaving you able to describe good teamwork without being able to demonstrate your own.

There’s a timing problem underneath that, too. Manager-facing guidance, including Exec’s teamwork review guide and CMOE’s evaluation walkthrough, says to gather peer feedback and cross-functional input before the review meeting. By the time you sit down, much of the rating has been assembled from impressions colleagues formed months ago. Wording written the night before can’t reach those. Behavior over the preceding months can.

What a teamwork performance review actually measures

No single authority defines the criteria, but they converge. Across independent sources — CMOE, Effy, Suptask, ClearCompany — the same short list reappears: collaborating actively, sharing knowledge and expertise, resolving conflict, contributing to shared goals, listening actively, and staying flexible when things change.

The pattern holds where collaboration has been measured rigorously. The Interprofessional Collaborator Assessment Rubric, used in healthcare education, splits collaboration into six named domains — communication; collaboration; roles and responsibilities; a patient-family-centered approach; conflict management and resolution; and team functioning — and reported high internal consistency in multi-source feedback with medical residents. That’s a clinical training setting, so its numbers say nothing about your appraisal form. What it shows is structural: even a validated instrument refuses to treat collaboration as a single score. Your form does the same, less openly. Here are nine components it is likely built from.

1. Doing what you said you would do, when you said it

Reliability is the criterion colleagues track whether or not the form asks them to, because a missed handover costs them their own time. It’s also the most documentable item here: commitments made and commitments met leave a trail in tickets, chat threads, notes and calendar invitations. The evidence already exists; you only have to collect it before you write anything. And if a deadline moved, the useful detail isn’t that it moved — it’s whether you flagged it early enough for someone else to replan around.

2. Sharing what you know instead of holding on to it

“Willingly shares knowledge and expertise” appears near-verbatim across independent sources, which makes it one of the more predictably scored behaviors. The evidence is unusually concrete: documentation you wrote that someone else now uses, a colleague you onboarded, a process you explained rather than performed on their behalf. That last distinction carries weight. Doing the task for a teammate reads as helpfulness; teaching them to do it reads as knowledge sharing, and only the second compounds. If you can’t name an instance, that’s a real gap rather than a wording problem.

3. Putting the shared goal ahead of your own scorecard

Reviews score contribution to team goals and help given to colleagues, which in practice often means work that never appears on your own objective sheet. Hence a tension nobody warns you about: the most collaborative work is frequently the least visible. You cover a gap while someone is out, you take the unglamorous half of a project, you coordinate instead of build. None of it lands as your output. The answer isn’t to stop — it’s to record it in a line or two as it happens, so it exists somewhere other than your memory.

4. Disagreeing without damaging the relationship

Conflict resolution and handling tension are named explicitly as evaluation areas across the corporate sources, and conflict management is one of the six domains in the rubric above. Both directions of failure are penalized, which is what makes this hard. Staying quiet through a decision you think is wrong reads as passivity; pressing the point personally reads as friction. What scores well is engaging the disagreement while keeping it on the topic rather than the person. The evidence is specific: an occasion you objected, and how the conversation ended.

5. Backing a decision you argued against

It’s rarely written into review forms and almost absent from the phrase libraries, yet it weighs heavily in the impressions colleagues form — it’s what lets a team move after a debate. Arguing your case and then implementing the decision loyally is one behavior, not two contradictory ones. Relitigating a settled decision, or complying while making sure everyone remembers you disagreed, both register. Usually not in the words a reviewer uses, but in the rating.

6. Being excellent in your own role, and staying out of everyone else’s

“Roles and responsibilities” is a standalone domain in that rubric and recurs in workplace criteria as role clarity. The failure mode is symmetrical, which is what catches people out. Under-delivering on your own part reads as unreliable. Over-reaching into someone else’s — redoing their work, answering for them, taking a decision that was theirs — reads as not trusting the team, even when it produces a better result. The question before stepping in is whether the team needs you there, or whether you’ve just noticed something you’d have done differently.

7. Listening in a way that visibly changed something

A rubric question recurs almost verbatim in the ranking material: “Does the employee actively listen to and value the opinions of others?” It’s a yes-or-no judgment with no evidence standard attached, which is the whole problem in one line — it asks a reviewer to form an impression rather than check a record. The only usable proof runs the other way: an occasion where someone else’s input demonstrably changed what you did. Naming the person, the input and the change beats any claim about being a good listener, because it can be checked.

8. Holding teammates to their commitments, respectfully

The counterpart to your own reliability, and the criterion most often left to the manager by default. Saying something when a colleague misses what they agreed to feels like overstepping, so most people say nothing. Done well it has a shape: early rather than after it has compounded, specific about what was agreed rather than general about the person, and directly rather than routed upward. That combination is often what a reviewer means by taking ownership of team outcomes. Complaining afterwards is the version that scores badly.

9. Giving the credit outward

Distinct from putting the shared goal first: this is attribution once the work is done, and colleagues remember it. It matters mechanically as well as decently, because peer input gets collected before the review meeting — so credit you gave in March shapes the rating in November, while credit given during the review itself arrives too late to move anything. Naming who did what, in the room where the work is discussed, costs nothing and registers with several people at once.

Nine criteria is a lot to assess honestly about yourself, and the one you’re weakest on is usually the one you notice least — which is what makes a teamwork rating feel arbitrary when it lands. Working through them cold is one option; finding out which criteria you’re weakest on before the meeting is a quicker one, and it means nothing in the room arrives as a surprise.

The part of this you can practice before next time

Read back over the nine and something is hard to miss: almost none of them is about the review. They’re things you either did or didn’t do over the preceding year, plus a conversation you either prepared for or didn’t. Most of the rating sits inside behaviors you can practice.

Working with Your Manager is what turns the review from a verdict into a conversation you’re half of. It covers making your results visible before they get rated rather than after, preparing properly for the meeting, staying future-focused when a score disappoints, and asking directly for what you want next period. Given how much of a teamwork rating is assembled before you walk in, that preparation is most of the leverage you actually have.

Teamwork is the thing being scored, and the nine components above are largely its anatomy: being excellent in your own role while respecting others’, putting the common purpose ahead of your own agenda, building trust by being reliable and meaning what you say, disagreeing without making it personal, committing to decisions once they’re made, and holding each other to what was agreed. Named that way, it stops being a verdict on your personality and becomes a handful of things you can work on separately.

Building Self-Awareness carries the receiving half. Teamwork is the competency most likely to surface something you can’t see — colleagues experience your collaboration from a vantage point you don’t have, and their input often feeds the rating. The skill is understanding feedback fully before reacting to it, adding your own view rather than either swallowing it or fighting it, then asking for advice specific enough to act on: not “be more collaborative,” but which behavior, in which situation.

None of that is fixed, and the free Job Skills Test exists to tell you which parts of it you already have. It reads across the twelve work skills the framework treats as buildable — teamwork and the two above among them — so if a past review left you unsure where the real gap sat, it’s worth getting the full twelve-skill picture rather than guessing from one competency score.

Where this leaves you before the next cycle

Some of this probably already describes how you work — the instinct to flag a slipping deadline early, or to say who actually did the thing when a project gets praised. None of it asks you to become a different person at work; these are behaviors people add to how they already operate. And they count for more, not less, as you take on more, because the further along you go the more of your work runs through other people — which is a reason to know where you stand now, while it’s cheap to find out. Worth noticing what you’re doing right now, too: reading about how a teamwork rating gets built, rather than arguing with one after it’s written.

Find out where your teamwork actually stands

What a review form can’t give you is an honest picture of your own starting point — it gives you someone else’s. The free Job Skills Test is a short self-assessment of the workplace skills this article has been circling, teamwork among them. It takes about seven minutes in one sitting, and it shows you where you stand across all twelve of them, plus which one or two would change the most about how your next review reads. If it’s the only thing you do about this today, it’s enough to work from.

Get my skills profile

Free, seven minutes, and your results appear as soon as you finish.