Manager/Admin Guide

Who this is for

This guide is for managers, WeMatter leads, admins, and RPO users who need to launch or manage scorecards for other people.

What you can actually do depends on your role. Some parts of the scorecard flow are widely visible to reviewing users. Others, such as reviewer management, Scoring Analysis, and broader administrative controls, are more restricted.

---

Why scorecards matter operationally

Scorecards help turn performance conversations into something more deliberate. They give you a shared structure for participant reflection, reviewer input, and later alignment. That structure makes it easier to see where views already match, where they do not, and what kind of support or development is likely to matter most afterwards.

In practice, scorecards are doing two jobs at once. They support a live review conversation, and they create a useful record that can later feed reporting, insights, and development planning.

---

Finding scorecards in the product

You can usually reach scorecards through the main Scorecards area, from a person's profile, or from tasks that point to a response you need to complete.

Launching often begins from profile or people actions. Organisation-wide views, including Scoring Analysis in Signals, are mainly relevant to admins and RPO users.

---

Launching a scorecard well

You can launch a scorecard for one person or run a grouped launch for several people together. In both cases, WeMatter sets the scorecard up with the core data it needs to support the whole cycle.

Before launch, WeMatter checks that the organisation has engagement areas and Human Performance Indicators configured, that the participant has a framework, and that the framework is genuinely usable for live review. In practical terms, it must be published, not deleted, contain competencies, and cover all of the organisation's Human Performance Indicators.

If those conditions are not met, launch is blocked for a reason. It is a sign that the review would otherwise be structurally weak.

What launch creates

When launch succeeds, WeMatter creates the scorecard record itself, the blank competency rating rows, the Human Performance Indicator comment rows, the engagement area rows, and the deadlines for the three response stages.

Current WeMatter leads are also added as reviewers when the scorecard is launched.

---

Understanding the live workflow

At the workflow level, scorecards move through No responses, Self-Reflection, Manager Review, Feedback Workshop, Completed, and Archived.

Those labels tell you where the scorecard sits in the review sequence. List views also use simpler progress states such as Submitted, In Progress, and Overdue. Those are useful, but they are not the same thing.

If you are managing the process at scale, it helps to read both layers together: workflow stage tells you what kind of work is waiting, while progress state tells you whether timing is becoming a problem.

---

Completing uMatter

uMatter is the reviewer response stage. In the current product, it focuses on the performance side of the scorecard rather than duplicating the participant's engagement section.

To reach 100% and submit uMatter, you need the manager comment, a rating for each competency, and comments across the Human Performance Indicator structure.

When you submit uMatter, you also decide when the participant can access it. That access can open immediately, after they have submitted iMatter, or only after the WeMatter workshop is complete. This is one of the most important timing controls in the scorecard cycle, because it shapes the context in which feedback is first read.

---

Reading participant access carefully

You may not be able to read a participant's iMatter the moment a scorecard is launched. Access depends on whether they have submitted it and which visibility setting they chose at submission.

If they chose to wait until the reviewer response is submitted, your access only opens after uMatter has been sent. That behaviour is deliberate. It lets the timing of the exchange be managed more intentionally.

---

Running WeMatter

WeMatter becomes available once both iMatter and uMatter are submitted.

Its role is to help people align, not to start from zero. Matching ratings are already effectively agreed. The workshop focuses on the competencies where there is still something to resolve.

As a result, WeMatter can sometimes feel surprisingly light. If very few ratings need agreement, progress may already be near completion. If there is a lot of difference, the workshop becomes the place where that difference is worked through.

When WeMatter is submitted, WeMatter can generate insights, build the PDF, and open the post-scorecard goal flow.

For the operational workshop detail, including auto-carried agreements, facilitated workshop access, and why some WeMatter scorecards already sit at 100%, read WeMatter Workshop and Alignment.

---

Search, filtering, and list management

The scorecards list is designed for active management as well as record-keeping. You can search by participant name or status text, and filter by workflow status, participant, reviewing manager, and launch date range.

Sorting is available by participant name, nearest deadline, and list-level progress state. The list is paginated, and opening a scorecard card gives you a navigation dialog with response links, dates, actions, and saved group context.

---

Managing active scorecards

Depending on your role, you may be able to manage deadlines, visibility, or the submission state of active scorecards directly from the response page or the navigation dialog.

Deadlines

Deadlines can be updated while the relevant stage is still active. iMatter and uMatter deadlines cannot be pushed beyond the WeMatter deadline, and the WeMatter deadline cannot be moved earlier than those earlier stages.

Visibility

Visibility can be updated on iMatter and uMatter while the scorecard is still in active use. This is useful when the intended timing of access changes and the review needs a different disclosure sequence.

Reviewers

Reviewer management is more restricted than some other scorecard controls. Admins and RPO users can update the assigned reviewers for a scorecard. That is useful when the original reviewer set no longer matches the reality of who needs to take part.

Stamped reporting groups

The navigation dialog also shows the saved region, department, and manager group values attached to that scorecard.

These stamped values matter because they preserve the reporting context of the review at the time it was launched. If the participant later moves team or the live structure changes, the scorecard still keeps the original grouping used for that review cycle.

Admins and RPO users can review and update those group values where needed.

---

Unsubmit, archive, and delete

If a submitted stage needs to be reopened, it can be unsubmitted. This makes that part of the scorecard editable again and clears the generated insight or alignment outputs that no longer match the reopened state.

Unsubmitting iMatter or uMatter also clears WeMatter submission, because the shared workshop can no longer be treated as final if one of its inputs has been reopened.

Archive is different. Archiving makes the scorecard read-only in the active workflow and allows a new scorecard to be launched for that participant.

Delete is the stronger action. It should be used when the scorecard should no longer exist as part of the active record, for example because it was launched in error.

---

Insights and reporting

Completed scorecards can generate engagement charts, performance charts, written insights, and alignment views for WeMatter. Over time, they can also show trend signals by comparing against the previous completed scorecard.

For broader organisational comparison, scorecard results can then be calibrated. That work sits in Scoring Analysis under Signals and is mainly for admin and RPO users.

For the full downstream output flow, including generated insight sections, alignment summaries, PDF creation, and post-scorecard goal prompts, read Insights, Alignment, and Outputs.

---

A good operating mindset

Good scorecard management is intentional rather than mechanical. Set deadlines that make the cycle feel predictable. Use visibility settings with care. Treat WeMatter as a real alignment conversation, not a final box to tick.

And when you are reading trends or insights later, use scorecards to spot patterns over time rather than trying to extract too much certainty from a single review in isolation.