Define the measure and its base
A pulse result should state what was asked, which scale was used and who was eligible to respond. Participation matters: a result among respondents should not be presented as the opinion of the entire workforce.
Keep counts of comments distinct from counts of people. One respondent may mention several themes or submit more than one contribution depending on the collection design.
How different instruments support a common comparison
Start with a question the participating teams genuinely share. For each required field, define the unit, eligible population, period, response options, missing states and calculation. Record how each local field maps to that definition, who reviewed the mapping and which version applies.
Departments may need different questions about their work. A shared pulse question, reporting period and sufficiently broad department category can support an approved comparison. An anonymous pulse must not gain a person identifier to make linkage easier.
For example, a department’s priority clarity question can map to the shared measure only when wording, scale, period and eligible group support that interpretation. A general engagement question is not a substitute. Keep different measures separate and preserve anonymous group analysis; do not add individual identifiers to manufacture matched responses.
Before combining anonymous returns, check definitions, group coverage and the collection design. State which teams supplied usable evidence and which are pending. Use only the duplicate-submission checks allowed by the original design; do not try to identify respondents to match them across sources. If repeated submissions cannot be distinguished, describe that uncertainty. Keep separate results when populations, methods or collection promises make combination inappropriate.
In a Sopact workflow, the shared definitions provide context for analysis while the connected record retains local responses, files and history. Your team can review a source-to-field mapping instead of redesigning every local survey. Test that configuration with sample records before relying on a combined result; a data dictionary cannot supply missing evidence or make incompatible measures equivalent.
Review the whole release, not only one chart
The organization should define appropriate small-group reporting and quotation rules with its responsible people and privacy teams. A group size alone does not prevent identification when details are distinctive.
Two separate breakdowns can reveal more when combined. Review the report, exports, drill-downs and source links as a connected release. An omitted cell may still be inferred from totals.
Give team leaders useful action guidance without unnecessary individual detail. A more aggregated view can be preferable to a precise-looking breakdown that undermines the collection promise.
Keep interpretation proportional
A low score identifies a topic to understand, not an automatic conclusion about managerial competence. Group differences may reflect roles, timing, response coverage or other factors.
Write the comparison rule before choosing the most striking chart. Preserve definition changes and the reasons for withholding a detail from a particular audience.
The dictionary helps collection, analysis and review use the same terms. It must be tested against real reporting situations and actual configured controls; it is not a privacy certification.
Work through the Linden example
This is a fictional teaching example. Adapt the fields and rules to the question your own workflow needs to answer.
| Definition | Specify | Review question |
|---|---|---|
| Measure | Question, scale and period | What does the result mean? |
| Base | Eligible and responding population | Who is represented? |
| Group | Reporting boundary | Could the detail identify someone? |
| Release | Allowed views, exports and quotations | What can the combined output reveal? |
Build this part of your plan in more detail
These lessons address the next practical questions in this module. Choose the detail your workflow needs, then return to complete the exercise.
- How to Connect Quantitative and Qualitative Survey Data
Read aggregate scores and comments without overriding the privacy promise.
- How Do You Analyze Survey Results by Demographic Subgroup?
Compare relevant groups while checking coverage, changing profiles, uncertainty and disclosure.
Add this part to your plan
On workbook page 5, define one pulse measure and the reporting rules for two audiences. Include a quote and small-group review. Map one local field to a common definition. Give one example that must remain separate.
Download workbook (fillable PDF)Compare with a suggested answer
The dictionary names the response base and reporting scope. A distinctive quote is removed or appropriately paraphrased after review. The team checks the combined release rather than relying on a threshold alone.
Self-check: Can the audience use the finding while the listening promise remains credible?
Questions you may have
Is one minimum group size enough?
No universal size guarantees anonymity. The context, other outputs and distinctive details also matter.
Can leaders see all raw responses?
Access should follow the stated purpose and policy, not automatically expand because someone manages the team.
Apply the method to your work
Use the five-part plan to assess the sources, analysis and permissions your team needs. The solution page shows where a connected platform can support that workflow.
Explore the employee experience solution →