For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Configure and launch a policy check-in, then monitor the resulting attestation requirements. The interface uses “check-in” for this campaign flow.
Before you start
Have an approved live policy version, a reviewed Knowledge Check question bank and an agreed audience. Confirm the policy's Informed RACI assignments: these resolve to the people receiving the check-in.
An audience record alone does not issue work. A preview alone does not contact recipients.
Configure and preview
- Open the policy's Testing configuration.
- Select Configure testing. Review the major/minor cadence, response window, question rules and pass threshold shown in the testing contract.
- Check the questions in Knowledge Check against the live policy. Correct ambiguous or outdated questions before launching.
- Select Preview audience. Check the resolved RACI-I population, including people included through groups. Fix the source assignments if the population is wrong.
- Select Run a check-in and choose the requested type.
- Select Preview check-in. Review the policy version, response deadline, recipient count and actual major/minor split.
A requested minor check-in can become a major one for a recipient without a successful major acknowledgement for the current live version. Read the preview instead of assuming everyone receives the same short exercise.
Launch and follow up
After the owner approves the preview, select Launch check-in once. Reopen the resulting event and inspect its audience and history. The audience is resolved at launch and retained as a cycle snapshot; later RACI changes are not a rewrite of that snapshot.
Use Policy Acknowledgements to filter and inspect required, pending, completed and overdue records. Check the policy version as well as the person's name. People in multiple teams can contribute to more than one team comparison.
Check it worked
Ask an intended recipient to open their assigned policy in their own session. Confirm the requirement is for the intended version and that completion appears against the correct record.
If something goes wrong
| Problem | Next action |
|---|---|
| No recipients appear | Review Informed assignments and organisation membership |
| Launch is unavailable | Check permission, live content and question-bank readiness |
| Result is uncertain after launch | Reload the event history before trying again to avoid duplicate work |
| A person has difficulty completing | Check access, wording and understanding before treating it as refusal |
Human judgement matters
Acknowledgement and a passed knowledge check provide evidence of a response. They do not prove that every real-world action follows the policy. Never complete someone else's attestation for them.
What next?
For the wider context, see Manage policies, controls and frameworks.
Share the Participant policy-attestation guide and arrange appropriate support for unresolved responses.
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.