Read and understood record template for Confluence
At an ISO 9001 or ISO 13485 audit, the auditor picks one person and one procedure and asks: did they read the version in force, and when? This template keeps that answer on one page: who must read, which version, by when, and the proof.
Read and understood record: [document title]
Document: [link] · Version in force: [2.0, effective date] · Owner: [name] · Deadline to read: [date]
1. Who must read it
[People and groups. Include people who join these groups later.]
2. Check of understanding (optional)
[Two or three questions on the key points, with the expected answer.]
3. Confirmations
| Person | Version read | Confirmed on | Check passed | Late? |
|---|---|---|---|---|
| [name] | [2.0] | [date] | [yes / no / not required] | [yes / no] |
| [name] | [2.0] | [date] | [yes / no / not required] | [yes / no] |
4. When the document changes
A change to the content starts a new round for version [next]. A typo fix keeps the confirmations, with the reason written here: [reason].
5. Follow-up
Reminders: [one per day at most]. Escalation after the deadline: [manager, date].
How to use it in Confluence
- Click Copy the template, open a new Confluence page and paste: headings, lists and tables stay as they are.
- Replace the parts in [brackets] and delete what does not apply to you.
- To reuse it, save it as a space template: Space settings › Templates › Create template, then paste.
Why a list of names is not enough
A spreadsheet of names goes out of date the day the procedure changes. What holds up is one confirmation per person and per version, with a date. ISO 9001 (clause 7.2) and ISO 13485 (clause 6.2) both expect evidence that people are competent for their work, which is why auditors look for training records tied to the procedure actually in force.
Related: how to prove people read the current version in Confluence.