Insights, Alignment, and Outputs

Overview

Scorecards do not end at submission. Once a scorecard stage is submitted, WeMatter can generate a set of follow-on outputs that help people interpret the review, compare perspectives, export the result, and move into development work.

Those outputs are part of the live product workflow, not just background data. They help turn a completed scorecard into something easier to discuss and easier to use afterwards.

---

What gets generated, and when

The exact output depends on which part of the scorecard has just been submitted.

After iMatter submission

WeMatter can generate:

• written scorecard insights for the participant's self-reflection
• visual summaries such as engagement and performance charts

If both iMatter and uMatter are now submitted, WeMatter can also generate the alignment output used for workshop preparation.

After uMatter submission

WeMatter can generate:

• written scorecard insights for the reviewer response
• visual summaries for that submitted response

Again, if both earlier stages are now submitted, WeMatter can generate the alignment output as well.

After WeMatter submission

WeMatter can generate or trigger:

• written workshop insights for the final agreed scorecard
• the completed scorecard PDF
• the prompt to create a follow-on development goal

This is why the completed workshop is a transition point, not only a closed conversation.

---

What the insights output contains

The exact wording changes by scorecard, but the live product structures insights into consistent sections.

For iMatter, uMatter, and WeMatter, the insight output typically includes:

• a summary of the overall picture
• motivators or positives worth protecting
• blockers or risks that are getting in the way
• opportunities for development or support

From the scorecard page, look for the Scorecard insights action card. If insights already exist, selecting it opens the insights sheet. If they have not been created yet, use Generate scorecard insights first and then reopen the same action.

Once open, the insights sheet is designed to move from interpretation into evidence.

For the completed WeMatter stage, the generated insight can also include a separate section on how major misalignments were resolved during the workshop.

That extra section matters because the final workshop record is not only showing where the scorecard ended. It is also showing how it got there.

---

What the alignment output contains

Alignment is its own output rather than just another paragraph inside insights.

Once both iMatter and uMatter have been submitted, the alignment view can summarise:

• the overall pattern of agreement and disagreement
• the areas of strongest alignment
• the areas of strongest misalignment
• the suggested workshop focus
• a short set of key questions for the conversation

From the scorecard page, open the Rating alignment action card. If the sheet has already been generated, it opens directly. If not, use Generate rating alignment first.

The sheet itself is simple: Summary gives the narrative alignment view, and Performance lets you inspect the detailed rating comparison. Within Performance, a second tab row switches between Skills and Behaviours.

This makes the alignment output especially useful before or during the workshop. It helps people see where the real discussion points are likely to sit before they get pulled into the detail of every competency.

---

Charts, comparisons, and evidence views

The generated outputs are not only narrative. Depending on the stage and the view you open, scorecards can also surface supporting visual summaries such as:

• engagement charts
• performance charts
• comparison tables across Human Performance Indicator areas
• alignment step comparisons between iMatter and uMatter

These are useful because they help people move between two levels of reading: the overall pattern and the specific evidence underneath it.

---

Automatic generation versus manual generation

In the live workflow, these outputs are designed to generate as part of the submission flow.

That means the normal experience is not to finish a scorecard and then manually start all the downstream steps one by one. Submission itself is what opens the next layer.

Even so, it is still useful to think of the outputs separately:

• insights help interpret the submitted response
• alignment helps frame the workshop conversation
• PDF preserves the completed scorecard as an exportable artefact
• goal generation turns the completed review into the next development step

---

PDF output and export

When the WeMatter stage is submitted, WeMatter can build the completed scorecard PDF.

That PDF is more than a temporary download. It is a stored scorecard artefact that can be used later for sharing, record-keeping, and reference.

In practical terms, this gives the review cycle a durable end product:

• the workshop has been completed
• the final agreed scorecard has been captured
• the output can be revisited without reopening the live editing workflow

---

Post-scorecard goal generation

After the WeMatter stage is submitted, WeMatter can prompt the next step of the development flow by opening goal creation.

That is a strong product moment because the scorecard has just moved through reflection, reviewer input, and agreement. The platform now has a clearer basis for deciding what kind of development goal would be most useful.

This does not mean AI must always be used. Manual goal creation still has a clear role. But the post-scorecard prompt is deliberate: it keeps review and development connected instead of leaving the scorecard as a closed historical record.

If you want the fuller goals-side explanation of that flow, read:

• AI and Advanced Workflows

---

Trend and comparison context

Over time, completed scorecards can also contribute to wider comparison and trend-reading.

For example, a later scorecard may show movement relative to the previous completed cycle, and organisation-wide analysis can later use calibrated results to compare relative score positions across different reviewing styles.

That broader analysis sits outside the single scorecard page, but it is one of the reasons the generated outputs matter. They help carry the scorecard forward into later reporting and development work.

---

What resets if a scorecard is reopened

Generated outputs depend on the submitted state of the scorecard. If a stage is later unsubmitted, those outputs may no longer match the live data.

That is why reopening a scorecard can clear or invalidate things such as:

• generated insights
• generated alignment output
• the submitted WeMatter state
• the completed PDF artefact for that version of the scorecard

This is especially important when reopening iMatter or uMatter. If one of those upstream inputs changes, the workshop and its outputs can no longer be treated as final.

---

A good way to read generated outputs

The outputs are designed to make the scorecard easier to use, not to replace judgement.

Read them as structured interpretation:

• use insights to understand the main picture
• use alignment to focus the workshop on the most important gaps
• use the PDF as the durable record of the completed review
• use the goal prompt to move from agreement into action whilst the context is still fresh

That usually produces a much stronger development flow than treating the scorecard as something that simply gets filed away once submitted.

---

Read this alongside

• WeMatter Workshop and Alignment
• Manager/Admin Guide
• User Guide