For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Issue a published survey to a supported assurance relationship and monitor the resulting assignments.
Before you start
Confirm the published survey version, target relationship, recipient population, deadline and assessment owner. In the reviewed issue form, supported targets are supplier relationships and company groups.
Issuing is an external-facing work assignment. Obtain approval for the recipients and timing before confirming it.
Issue the request
- Open the Assurance survey catalogue or the survey's detail page.
- Review its published version and use eligibility. Draft and archived templates are not ready to issue.
- Select Issue survey.
- In Issue assurance survey, choose the consumer type and then the exact supplier relationship or company group.
- Set the due date and assessment mode. Understand whether the selected mode inherits the survey's settings.
- Recheck the survey, organisation and target. For a company group, confirm the intended member-firm population before proceeding.
- Select Issue survey once and wait for the result.
- Open the resulting request and inspect the assignments rather than assuming the expected population was created.
Track progress
Use the request view to inspect assignment state, due dates and responses. Acknowledgement, draft work, submission and review are different stages.
Open response review for a submitted assignment. Check the actual answer and disclosed evidence before recording any assessment conclusion. Refer missing or unclear material back through the supported review process.
Compare progress with the original recipient scope. Do not interpret a percentage without understanding its denominator.
Check it worked
Reload the request and confirm it is issued, with the correct pinned survey version and expected assignments. Ask an intended respondent to confirm they can open their assignment in their own organisation context.
If something goes wrong
| Problem | Next action |
|---|---|
| The target is missing | Check the relationship, membership, access and supported target type |
| The action times out | Inspect existing requests before repeating issuance |
| A duplicate-version warning appears | Review the existing request; the same survey version cannot simply be reissued to the same target |
| A respondent cannot open it | Check the assignment and organisation context before sending a new request |
| Questions need changing | Publish a reviewed new template version and decide deliberately whether new work is needed |
Human judgement matters
Creating a newer survey version to bypass duplicate protection without a real need can burden respondents and fragment the evidence. Keep the purpose and history clear.
What next?
For the wider context, see Create, issue and complete assurance work.
Track review outcomes and follow-up actions. Share the response guide with the licensed Collaborators preparing evidence.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message, not confidential evidence or session details.