Attestation blocks
An attestation block presents policy content and requires the learner to explicitly acknowledge it before moving on. It's a first-class block type, so you can drop it into any course exactly where the policy belongs.
- Explicit acknowledgement, not a passive page view
- Placed inside the relevant course or program
- Pairs with checklists and quizzes to confirm understanding
- Recorded as part of the learner's completion
The audit trail
Acknowledgements are backed by completion records with timestamps, and administrative actions are captured in an audit log. Together they answer the questions a reviewer asks: what was acknowledged, who acknowledged it, and when.
Reporting and renewal
You can report on completion to see who has and hasn't acknowledged a policy, and export the results to CSV. When policies change or need periodic re-acknowledgement, recurring assignment rules can require people to attest again on a schedule.
Frequently asked questions
How does a learner acknowledge a policy?
Through an attestation block inside a course. The learner reads the policy and explicitly attests to it, and that acknowledgement is recorded as part of their completion.
What proof is kept?
Completion records with timestamps capture the acknowledgement, and an audit log records administrative actions, so you can show what was acknowledged, by whom, and when.
Can I confirm understanding, not just agreement?
Yes. Attestation blocks sit alongside checklists and quizzes in the same course, so you can require a policy sign-off and verify comprehension together.
Can I make people re-acknowledge a policy periodically?
Yes. Recurring assignment rules can require re-acknowledgement on a schedule — from custom day intervals through yearly — which is useful when policies are updated.
Can I see who hasn't acknowledged a policy yet?
Yes. Completion and overdue reporting show who has and hasn't attested, and you can filter the results and export them to CSV.