Decide who needs to understand what.
A partner may need an activity summary, while a researcher needs subgroup detail. Choose the findings and access level around that purpose. Keep raw data access separate from a public report.
Give the survey question, collection period, recruitment method and response base. Explain the scale and the denominator of each percentage. A chart title should say what is being shown, not merely repeat a variable code.
Bring studies together without disguising their differences.
In the report designer, a component can use a selected study and question. This lets a project report include needs assessment, event feedback and a test result in one place.
A main-study filter does not change a component from another study. Precomputed model results are not recalculated either. Keep those bases visible and do not imply that people’s records have been merged.
Add the researcher’s explanation.
Record or upload audio commentary for a component. Explain how the chart should be read, what it suggests and where the method limits the conclusion. Preview the audio before publication.
Keep essential explanations in text too. A reader who cannot or does not listen should still understand the finding and its caveats.
Let a finding travel with its source.
When sharing is enabled for the reader, a selected chart can become an image. A chart with researcher audio can also become an animated MP4 in square or vertical format. The reader downloads it and adds it to a social post.
The file is a snapshot. A report link or embedded chart can continue to update. State the source and relevant date so an old downloaded image is not mistaken for the latest result.
Check publication before opening access.
- Read the report on a phone and a desktop.
- Review small groups, open quotations and audio for identifying information.
- Test the completed/partial setting and permitted filters.
- Inspect a shared chart outside the full report.
- Confirm access, password and embedding settings.