Engagement Signals
Engagement Signals turns submitted iMatter scorecards into evidence-led snapshots, comparisons, and natural-language insight that help leaders understand organisational engagement more clearly.
Overview
Engagement Signals is the first Signals dashboard in WeMatter. It turns submitted iMatter scorecards into a defined snapshot, then combines the structured scores and written feedback into a report that is easier to read, discuss, and act on.
What makes the dashboard compelling is the way it moves beyond averages. The headline score matters, but so do the strongest and weakest areas, the way the signal is distributed across different groups, and the narrative evidence that helps explain what may sit behind the numbers. Used well, Engagement Signals gives leaders a clearer view of both the engagement position and the shape of the conversation they may need to have next.
Snapshot-led
Work from a saved reporting view rather than a constantly shifting live state.
Evidence-led
Read scores and written comments together rather than in isolation.
Discussion-ready
Use the report to guide leadership conversations, not just inspect charts.
What makes Engagement Signals different
Engagement Signals combines score trends, breakdown comparisons, and narrative analysis of written comments so leaders can understand both what is changing and why it may be changing.
What an Engagement Signals snapshot gives you
An Engagement Signals snapshot is a saved reporting view rather than a live, always-changing dashboard state. That matters because it gives teams a stable artefact to discuss, share, and revisit later.
Inside a snapshot you can expect to see a defined current reporting period, an optional comparison period, a saved cohort definition for region, department, and manager filters, and a report that combines headline engagement scores with group comparisons, area-level analysis, and narrative sections such as key themes, risks, opportunities, and strategy. The underlying scorecards and comments remain visible so the report can still be checked against its source material.
At a glance, a strong snapshot gives you:
- a fixed reporting window
- a saved cohort boundary
- a readable engagement summary
- narrative sections that interpret the evidence
- access back to the underlying source material
Where to find Engagement Signals
In the main dashboard, go to Organisation, then Signals, then Engagement. From there you can generate new snapshots, review recent ones, refresh status, and open completed reports.
Who Engagement Signals is for
Engagement Signals is primarily designed for organisation admins, RPO users, and client stakeholders who need to review engagement at organisation or cohort level. In the current product, the workspace is restricted to users with the required organisation access and the correct role permissions.
How to use this documentation
The guides below follow the journey most teams take in practice: first creating the snapshot, then reading and interpreting it, and finally deciding how to share or operationally manage it.
Methodology
Understand how Engagement Signals processes scores and anecdotal feedback into narrative insight.
Create a Snapshot
Choose a period, refine the cohort, and generate a saved engagement report.
Read a Snapshot
Understand what each report section means and how to interpret it.
Share and Export
Manage public links, anonymous sharing, and CSV export.
Manager/Admin Guide
Run the reporting workflow, manage snapshots, and govern access.
The role of narrative insight
One of the most valuable parts of Engagement Signals is the narrative layer. WeMatter does not simply summarise every comment in one pass. Instead, the dashboard uses an evidence-led pipeline to prepare and quality-check written comments, group related anecdotes into themes, balance qualitative feedback with score movement and cohort structure, and generate board-ready narrative cards grounded in the strongest evidence.
If you want to understand how that process works in more depth, the Engagement Signals Methodology guide explains the approach.
Last updated on