For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Define the reporting period for group work and create reusable member cohorts for a phased issue of requirements or mandates.
Before you start
Select the group-owner organisation and the correct group. Agree the period, intended member population and who may activate or close it. Check existing cycles before creating a new one.
A cycle is a period for issued work. A cohort is a reusable selection of members. Neither is proof that a requirement has been issued or answered.
Create and activate a cycle
- Open the group's assessment-cycle page and review Reporting periods.
- Use the new-cycle action.
- Enter Name, Starts, Ends and a description that makes the purpose clear.
- Save the draft and inspect its dates.
- When the period is ready to receive work, use Activate cycle and review the confirmation.
- Refresh the page and verify the intended active cycle.
Only active cycles can receive new requirements or mandates through this journey. At the agreed end, inspect outstanding work before using Close cycle. Closing the period does not mean all member responses were satisfactory.
Create and maintain a cohort
Open Rollout cohorts and choose New cohort. Give it a meaningful name and description, select the intended members through the offered selector, then save.
Check the saved membership and compare the Outside cohorts and In multiple cohorts context. Overlapping cohorts can be intentional, but they should not be a surprise when selecting an issue population.
Use Edit cohort for an authorised membership change. Use Archive cohort only after reviewing the confirmation and programme impact.
Check issued scope separately
When issuing work, inspect its target summary and future-allocation explanation. A later cohort change should not be assumed to rewrite an already-issued requirement or its historical population.
Current-cycle progress reports against assignments actually issued. Do not treat a cohort's current headcount as interchangeable with the denominator of every historical metric.
Check it worked
The correct cycle is active with the agreed dates. The cohort contains the intended members, and the next issue form offers the expected selection. Outstanding work and closed-period outcomes remain distinguishable.
If something goes wrong
| Problem | Next action |
|---|---|
| No cycle is available for issue | Check draft, active and closed states |
| Cohort count is surprising | Review membership, overlap and filtering |
| A member is outside the intended phase | Correct the cohort before issuing work |
| Closing returns an uncertain result | Refresh the current cycle before repeating the action |
Human judgement matters
Choose reporting periods and populations to reflect the programme, not to improve a completion percentage.
What next?
For the wider context, see Manage clients and company groups. Issue the approved requirement or mandate and verify its actual member assignments.
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.