Overview

Overview

Scorecards are WeMatter's structured review cycle for a person in your organisation. They bring together self-reflection, reviewer feedback, and a shared workshop so performance conversations have more shape, more evidence, and more chance of leading somewhere useful.

Without that structure, performance discussions often go wrong in predictable ways. They stay vague. They rely too much on memory. Or they jump too quickly from feeling to action without building a shared picture first. Scorecards give that picture a clearer form.

---

Where scorecards fit in WeMatter

Scorecards sit between understanding and action. Foundation gives context around the person. Competency frameworks describe the capability standard their role or context is being reviewed against. Scorecards then gather the evidence, tension, and alignment needed for a meaningful conversation.

After that, Goals can turn the outcome into focused development work.

So scorecards are not the start of the story and they are not the end of it. They are the point where context and expectations are tested against lived experience.

---

The three parts of a scorecard

Every scorecard is built around three connected responses. They are linked, but they do different jobs.

Together, those stages create a sequence: reflection first, review second, alignment third.

If you want the operational detail behind the workshop itself, read WeMatter Workshop and Alignment.

---

Where people find scorecards

People meet scorecards in a few different ways across the product. A participant may open one from their dashboard, a task, or their profile. Managers and leads often open them from the main Scorecards area or from a person's profile. Users with broader permissions may also launch scorecards directly from people and profile actions.

Admins and RPO users can go further still, including accessing the Scoring Analysis dashboard in Signals for organisation-wide reviewer scoring comparison.

---

How the cycle moves forward

At the workflow level, scorecards move through a set of familiar stages:

• No responses
• Self-Reflection
• Manager Review
• Feedback Workshop
• Completed
• Archived

Those labels describe where the scorecard is in the review cycle itself. In list views, you may also see simpler progress labels such as Submitted, In Progress, and Overdue. Those are based on deadlines and submission state rather than the richer workflow stage.

That distinction matters because two scorecards can be in different operational states even if they look similar at first glance in a list.

---

Why frameworks matter before launch

Scorecards do not launch from nothing. Before launch, WeMatter checks that the organisation has engagement areas and Human Performance Indicators configured, that the participant has a framework assigned, and that the framework is ready for live use.

Operationally, the assigned framework must be published, must contain competencies, and must cover all of the organisation's Human Performance Indicators. If it does not, the scorecard cannot launch cleanly.

This is one of the strongest links between the frameworks area and the scorecards area. The framework provides the performance structure the scorecard will later use.

---

Why scorecard groups matter

Each scorecard also stores its reporting context at launch, including the saved region, department, and manager group values used at that point in time.

That may sound administrative, but it matters. People move teams. Reporting lines change. Departments are renamed. The scorecard still needs a stable record of where that review belonged when it happened. Those saved group values protect the quality of later reporting in Signals, including Engagement and Scoring Analysis.

So although the conversation inside the scorecard is the visible part, the saved group structure is doing quieter work in the background to keep analysis more trustworthy later.

---

What happens after submission

Submitting a scorecard stage does not only close that response. It can also open the scorecard's next outputs.

• submitted responses can generate written insights and visual summaries
• once both iMatter and uMatter are submitted, WeMatter can generate the alignment view for workshop preparation
• when WeMatter is submitted, WeMatter can build the PDF and open the follow-on goal flow

That makes scorecards more than a review form. They are part of a connected workflow that moves from reflection into alignment and then into development.

For the full operational detail, read Insights, Alignment, and Outputs.

---

Ratings and scoring

Scorecards use two rating languages.

Engagement uses a 1-10 scale from Unacceptable to Industry Leading. Performance uses the organisation's configured performance scale, which may be a 4-point model or a 5-point model depending on setup.

For organisation-wide comparison, completed scorecards can also be calibrated to reduce the effect of different reviewer scoring styles.

Engagement rating cards

Performance rating cards

Your organisation will use either the 4-point scale or the 5-point scale.

4-point scale

5-point scale

---

Guides