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 defined framework expectation to group members, track their responses and withdraw a mandate when that specific programme decision is authorised.
Before you start
Confirm the group owner, an active assessment cycle and the exact framework version. Agree the required coverage threshold, response date and member scope.
A mandate requests an organisational response and links to adoption work. It is not proof that members already comply with the framework or that the group can inspect their private evidence.
Issue the mandate
- Open the group's Mandates page and review existing issued mandates.
- Choose Issue framework mandate.
- Select the intended assessment cycle.
- Search for and select the exact Framework version. Read its identifier and version rather than relying only on a familiar name.
- Set Coverage threshold, Response due and useful Context.
- Choose the members in scope: all, a named cohort or the offered selected-member option.
- Read the current target count and future-allocation explanation. Confirm the actual firms represented.
- Select Issue mandate once and wait for the saved result.
- Reopen the mandate and verify its framework, cycle, threshold and assignments.
Monitor the response
Review response lifecycle separately from adoption position. A member acknowledging the request has not yet accepted it. An accepted mandate can still have coverage below the required threshold or be awaiting disclosure.
Use the portfolio, geography and action views to locate the relevant member assignments. Open the source before drawing conclusions from a count or colour. Review released information only within the member's authorised sharing level.
Withdraw an active mandate
Where the active mandate offers Withdraw, first agree why it should no longer apply and how members will be informed. Inspect the exact mandate and confirmation before submitting.
Read back the resulting mandate state. Do not assume withdrawal deletes a member's framework adoption, erases historical responses or recalls information already seen.
Check it worked
The mandate and its member assignments match the authorised issue decision. After withdrawal, its state is no longer active and the programme record explains the change. Member outcomes and history remain distinguishable from the current requirement.
If something goes wrong
| Problem | Next action |
|---|---|
| Issue is unavailable | Check cycle, framework selection, targets and permissions |
| A similar framework is already mandated | Compare versions and existing assignments before duplicating work |
| Member coverage is unavailable | Check disclosure and response state rather than assuming zero |
| Withdrawal times out | Refresh the existing mandate before repeating it |
Human judgement matters
A threshold is a programme requirement, not an independent assurance conclusion. Record what it measures and review the supporting evidence.
What next?
For the wider context, see Manage clients and company groups. Coordinate member responses and use the group review process for released evidence and follow-up.
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.