Releasing results to respondents
Purpose
Decide which reports respondents may see for their own organisation, and when.
Who this is for
Account administrators and campaign managers — anyone holding campaigns.modify on
the wave.
The short version
- Open the campaign's Reporting & Scorecards page.
- When respondents see their results — pick the timing and save.
- Respondent results visibility — tick the reports they may see, and save.
- Under When I say so, press Release results now when you are ready.
Both panels are at the foot of the page, below the reports. There is no longer any
need for a console PATCH: that was the interim while the controls were being built.
The two decisions are separate on purpose
Which reports a respondent may see is a list. When they may see them is a single choice about the whole wave. They have a Save each, so changing the timing does not wait on a checklist you did not touch, and vice versa.
Neither panel can affect the other: each sends only its own field, and the campaign's results settings are merged rather than replaced.
Release timing
| Option | What happens |
|---|---|
| As soon as they answer | Each organisation sees its own result the moment its answers are in. |
| When the wave closes | Nothing is shown until the closing date passes. This is the default. |
| When I say so | Nothing is shown until you press Release results now. |
An account-wide default can be set under the account's reporting settings; a campaign that sets its own overrides it. The panel always shows the timing that is actually in force for this wave.
Release results now
The button appears only when the saved timing is "When I say so". If you have just switched to it, save first — the panel says so.
Pressing it stamps the release with the current time and writes an audit entry naming you. It can be pressed again; re-releasing a wave harms nothing and re-stamps the date. The date cannot be set, backdated or cleared from an API body — only this action writes it.
Which reports respondents may see
Only reports that can compute something for a single organisation are offered, which today means a maturity profile carrying a profile configuration — including the built-in BIMmaas Maturity Profile.
Ticking one here opens it for this campaign only. It does not turn the report on for the rest of the account. A report that carries the account-wide "visible to respondents" flag shows ticked and locked, because unticking it here would do nothing.
The built-in profile is a platform-wide report, so the account-wide flag cannot be set on it at all. This checklist is the way to reach it.
The comparison floor
The panel prints the floor and the rule behind it; it is not editable here.
A respondent sees how they compare with everyone taking part only once at least that many organisations have answered, and only when they all answered the same version of the questionnaire. Below the floor, their page says so and says how many more are needed.
The floor is a platform disclosure rule. An account may raise it; it can never be lowered, and a campaign asking for a smaller number gets the platform's.
What a respondent actually sees
Their own organisation's result, and the average across everyone taking part. Never another organisation's result, never an individual's answers, and never a group too small to report on. The full reader's view is Your results.