Skip to main content

Development trial ยท sample information only

Respond to a framework mandate as a member

For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.

What you will achieve

Acknowledge a group mandate, accept and link it to framework adoption or reject it with a reason, while deciding information sharing separately.

Before you start

Select the member organisation and open its company-group membership. Confirm you are authorised to respond on its behalf.

Read the framework version, threshold, due date and context. Identify any existing adoption so that you understand whether the response will reuse it or create a new one.

Acknowledge and decide

  1. Open the membership's Mandates page.
  2. Find the intended current-cycle assignment and read its response and disclosure states.
  3. Use Acknowledge when you have received and understood the request.
  4. In the resulting choice, select Accept and link only when the organisation agrees to the framework requirement.
  5. Review the result and use Open adoption to inspect the linked framework adoption. The card distinguishes an existing adoption from one created for the mandate.
  6. If the organisation cannot accept, choose the rejection action, provide a meaningful Reason and confirm Reject requirement.
  7. Read back the saved response.

Acknowledgement is receipt, not acceptance. Acceptance links adoption work; it does not mean the coverage threshold has already been met.

Choose sharing deliberately

For an accepted assignment, use Manage framework sharing where authorised. Review the supported levels, from adoption summary through certificates, controls and answers, to authorised evidence lists.

Select only the information the organisation intends to share. Organisation and adoption limits remain the ceiling; a mandate does not override them.

If disclosure is queued or withheld, follow the displayed state and the membership's disclosure-review process. Do not assume that accepting again or restoring eligibility automatically publishes every queued record.

Check it worked

The response and reason, where applicable, belong to the correct member organisation and mandate. The linked adoption is correct, and the sharing state reflects the chosen level. Inspect actual adoption coverage separately.

If something goes wrong

Problem Next action
Response controls are absent Confirm member context and authority rather than acting from the group-owner view
The linked adoption is unexpected Stop further sharing and ask the framework owner to investigate
Rejection is blocked Supply a substantive reason and check the current response state
The group cannot see the result Inspect disclosure eligibility and release state separately

Human judgement matters

You are making an organisational response. Do not accept simply to improve a network dashboard or share evidence that the organisation has not authorised.

What next?

For the wider context, see Manage clients and company groups. Maintain the linked adoption and track the work needed to meet or explain the mandate's threshold.

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.

Was this article helpful?