Skip to main content

Review answers and share feedback

Purpose​

Work through the submissions you have been assigned, record a verdict on each answer, and send the parts you want the assessee to see.

Who this is for​

Auditors, and the managers who oversee them.

Getting in​

Auditor Workspace in the sidebar. The entry only appears if you either hold a manager permission or have at least one auditor assignment. If you open it without either, the page says "You do not have auditor workspace access in this account."

If you expect assignments and see none, ask a campaign manager to assign you — see Add people to a campaign.

Find the work​

My assignments lists what you are responsible for: the target (a participant or an assessment), the campaign, the scope, and when you were assigned. Search across them, filter by scope, and sort by assigned date, scope type, campaign or target.

Choosing an assignment loads Assignment review context on the right: campaign, target, scope, a Review progress meter, and a table of that assignment's submissions. Choose a submission to open the answer-by-answer panel.

Review an answer​

Each answer in the Answer review panel gets its own block: the question key, the submitted value, and controls.

For each answer, set:

  • Verification — Unverified, Verified, or Modified.
  • Corrected answer — appears when you choose modified. The original value is not overwritten; your correction sits alongside it. The control is the question's own: a list of the answers that question offers, one selector per row on a matrix, a text box only where the question itself is free text. On a maturity item a correction has to be a point on the item's own scale, and the panel says which. On a qualifier — a province, an employment band, a sector, a discipline, a job title — you are choosing between the answers the question offers, because a qualifier records what the respondent is and segments the cohort rather than scoring it. Choosing modified and leaving the corrected answer empty records the verdict and nothing else: the respondent's own answer stands, in the scorecards, the maturity profile, the published results and every export. Picking the blank option clears a correction you had saved earlier.
  • Review level — your own account's list, if it has one (a select beside Verification). This is not a computed score: an account adds, renames and reorders its own levels from Labels in the dashboard sidebar, under a group named Review level. If the account has not defined any yet, the row says so and links there. Choosing the blank option clears a level you set earlier.
  • #hashtags — space-separated, for grouping findings across submissions.
  • A note — free text about this specific answer.
  • Include in export — on by default. Turn it off and your note and hashtags on that answer stay inside the tenant: they appear in no export, in any format. The answer itself, and your verdict on it, still export — a file that presented your correction as the respondent's own answer would be worse than one carrying no review at all — and each row reports how many notes were withheld, so the file says what it is not carrying.
  • Share with participant — see below.

Choose Save on the block. Each answer is saved on its own; there is no save-all.

Attachments on an answer​

Where a question asked for an uploaded artefact — a policy document, a scan, a screenshot — the answer block lists each attachment by name with a Download button beside it, instead of printing the stored value.

You can download an attachment because you are assigned to review this submission, not because you hold a file permission: any auditor or campaign manager who may read this submission's review may download the evidence that submission cites. The grant is exactly that narrow — it reaches the artefacts cited by the answers you are reviewing and nothing else in the account, and a file that this submission does not cite is not found from here even if it exists elsewhere.

Downloads are recorded. Each one writes an entry to the account's activity log and a file.downloaded event, identical to a download taken from the files browser.

An attachment added before the platform stored evidence files separately shows its name with no downloadable copy beside it. There is no stored artefact to fetch; the respondent's answer recorded only the file's name.

Analytics at the top of the panel overlays each answer with how everyone else answered that question — a distribution with counts and percentages. Useful for judging whether an answer is unusual.

Locking (managers only)​

A manager can tick Locked on an answer review. Once locked, other auditors see the block greyed out and its Save button disabled, explaining itself on hover — A manager has locked this answer. Managers can still edit it. Use this to freeze a moderated verdict.

Reopen a submission​

Reopen at the top of the panel puts a completed submission back into an answerable state so the participant can add or correct answers. It asks What needs correcting? first, and at least five characters are required — that sentence is not a note to yourself, it is the whole of what the respondent receives, which is why the dialog says so. Reopen and notify commits it.

If the respondent has no address, or no link can be minted for them, the server refuses rather than reopening silently, and offers a second dialog — Nobody can be notified → Reopen for in-workspace correction — so you can still reopen it knowing nobody was told. Either way the submission's status badge changes to reopened, and it cannot be undone from here.

Share feedback with the assessee​

Tick Share with participant on an answer and save. That answer's verification status, your corrected value (if any) and your note become visible to the person who submitted it. Answers you do not tick stay internal.

What the assessee sees, and where:

  • On the assessment's completion page, under Reviewer feedback, with the question's own text rather than its internal key. Statuses are shown to them as Reviewed, Verified or Adjusted.
  • An email, sent once per submission — when the submission goes from "nothing shared" to "something shared". Sharing more answers afterwards does not send another email; nor does re-saving an already-shared answer. Un-sharing everything and sharing again does.

Tell people this: the link in that email only works in the browser the assessment was completed in. The submission is recognised by a key stored in that browser, not by a sign-in. The email says so, but it is worth repeating in your own message. If the assessee has changed device, they cannot reach the feedback and you will need to relay it another way.

Notes about the assignment as a whole​

Below the answer panel, Create auditor note records a note against the assignment rather than a single answer. Choose its visibility:

  • Private — only you.
  • Shared — also visible to managers in the Shared notes feed tab.

Only the auditor an assignment belongs to can write one. A manager opening the same assignment sees no composer at all, and the panel says why: "Managers observe auditor notes rather than author them. Note creation is reserved for the auditor an assignment belongs to." If you are a manager who needs something on the record here, ask the assignment's auditor to write it.

You can link a note to a specific submission, and edit or delete your own notes. Note that assignment-level notes marked shared go to managers, not to the participant — sharing with the assessee is the per-answer checkbox described above.

Managers: the shared feed​

Managers get a second tab, Shared notes feed, listing every shared note across the account with campaign, scope, text, author and time, plus a search and a Reload button.

Export your caseload​

Top-right of the workspace: pick XLSX, CSV or JSON and choose Export caseload. The file downloads immediately and covers every submission assigned to you.

It carries your review, not just the raw answers:

  • the answer column holds your corrected value where you set modified — the same value the scorecards use — and ans:<question>::original holds what the respondent actually wrote, but only where your correction changed it;
  • rev:<question>::status, ::modifiedApplied, ::locked, ::reviewedAtIso, ::reviewerKey, ::reviewLevel and ::reviewLevelLabel describe each review, and a question nobody reviewed gets no such columns at all; ::reviewLevel is your account's own label id, ::reviewLevelLabel its current display text;
  • each row counts its reviews, including how many notes were withheld by include in export;
  • a Notes table (a sheet in XLSX, a notes section in JSON, a notes field on the CSV payload) carries the notes and hashtags you did permit.

Reviewers are identified by a stable key, never by email address.

Limits and gotchas​

  • Answers are keyed by their internal question key in this panel, not by question text.
  • Include in export governs the export only. It hides your note and your hashtags on that answer, and nothing else. It does not remove an answer from scoring: a response you excluded still counts towards every scorecard, the maturity profile and the published results, and the answer, your verdict and any correction still export.
  • A modified verdict with no corrected value changes no number. rev:<question>::modifiedApplied in an export reads 1 only where a corrected value was actually substituted.
  • The review level never changes a number either — it does not touch scoring, the maturity profile or any published result, the same as Include in export.
  • Reviewing does not change the participant's stored answers; a modified verdict adds a correction next to the original.
  • Sharing is per answer and irreversible in the sense that the assessee may already have read it before you un-share.
  • An attachment download needs a storage backend configured for the deployment. Where there is none, the button reports that there is nothing to download rather than claiming a download happened.
  • The download link is short-lived by design (about two minutes). It is minted when you press the button and cannot be copied out and kept.