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 survey requirement to the intended group members and track actual response and review states without treating issue as completion.
Before you start
Confirm the group-owner organisation, an active assessment cycle and a suitable published survey. Review the survey's questions and version before choosing it.
Agree the due date, assessment approach and member population. Issuing a requirement creates work for other organisations, so obtain the appropriate programme authority.
Issue the requirement
- Open the group's Requirements page and inspect existing issued work to avoid duplicates.
- Open the survey-issue action.
- Select the intended assessment cycle and survey.
- Set the due date and review the assessment mode offered by the form. Do not assume an automatic assessment is a human acceptance decision.
- Choose All active members, Selected members or Named cohort.
- For a selection or cohort, verify the exact organisations represented.
- Read the recipient summary and future-allocation explanation. Record any important scope assumptions in your programme record.
- Submit the issue action once and wait for the resulting requirement and assignments.
- Refresh the Requirements page and check that the correct survey, cycle and target population were issued.
Track response and review
Use the Portfolio, Geography and Actions views as appropriate. Keep states such as not started, in progress, in review, returned, accepted, rejected, withheld and overdue distinct.
Open the relevant requirement or member assignment to understand the source behind a summary. A response can exist without being released or accepted. An unavailable outcome should not be translated into a pass or failure.
Review overdue or returned work with the member's responsible contact. Do not complete the member's answers on their behalf merely to clear programme attention.
Check it worked
The issued requirement belongs to the intended cycle and the actual assignment count and members match your decision. Track the issued population rather than assuming it always equals today's group membership.
If something goes wrong
| Problem | Next action |
|---|---|
| Issue is disabled | Check active cycle, survey eligibility, recipients and permissions |
| Creation succeeds but issue appears to fail | Inspect the existing request before creating another |
| A cohort contains unexpected members | Resolve scope before issuing; inspect existing assignments if already issued |
| A response is withheld | Follow the disclosure process instead of treating it as an empty answer |
Human judgement matters
A requirement coordinates evidence collection. It does not transfer accountability for the member's facts or authorise unrestricted access to its internal records.
What next?
For the wider context, see Manage clients and company groups. Review released responses through the assurance workflow and maintain clear, owned follow-up actions.
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. Never share passwords, session details or confidential evidence in an open support request.