What you'll achieve
You will create a reusable assurance survey, publish a controlled version, issue it to a supported relationship, answer an assignment and review the response with evidence boundaries intact.
Who this is for
This guide is for an Organisation Collaborator with the permission or assigned action described below. If the navigation or action is missing, check the selected organisation, effective account level, feature state and role before assuming the product is unavailable.
Before you start
Check that you have:
- The assurance purpose and consumer.
- Question owners and expected evidence.
- Permission to author, issue or answer the relevant work.
1. Create or import a draft survey
Open Assurance and choose New survey. Start manually or import a supported document. Review every generated question; an import is a draft, not a validated assessment.
2. Define answer and evidence expectations
Use sections, help text and assessment settings to tell respondents what is being asked. Avoid questions that demand unnecessary personal, confidential or secret information.
3. Publish and issue deliberately
Publish a reviewed version, then choose Issue survey and the supported assurance consumer. Confirm relationship, assignee, dates and assessment mode before issuing.
4. Complete received assignments
Open Assurance > Assignments. Answer each question from current evidence, add a useful narrative, and disclose only the evidence fields intended for that consumer.
5. Submit and review
Submit only when the response is complete. Reviewers should assess the answer and disclosed evidence, record findings or requests for change, and preserve question numbering and version context.
Check it worked
- The survey version is identifiable and immutable after publication.
- The issue target and assignee are correct.
- Each answer distinguishes evidence, narrative and unavailable information.
- The review outcome is attributable and visible in the work queue.
If something goes wrong
| What you see | What to do |
|---|---|
| Import created weak questions | Keep the survey in draft and edit before publishing. |
| Evidence contains more than the recipient needs | Reduce disclosure; do not submit the attachment as-is. |
| An answer is reused | Revalidate it against this question, period and consumer before applying. |
| The assignment is for the wrong relationship | Do not answer. Ask the issuer to correct or withdraw it. |
Human judgement, security and privacy
Assurance is a claim supported by scoped evidence. A confident narrative does not compensate for missing, stale or undisclosed evidence.
What's next
Track follow-up obligations and schedule revalidation when the evidence or relationship changes.
Need help?
Use your organisation's approved Backstory support route. Include the organisation, page and action that failed, but do not include passwords, invitation links, secret keys or unnecessary personal or confidential content.