From an updated policy to a record of who has read it.
- Step 01
Policy published
An editor marks a Notion policy page as a new version, with a short note on what changed.
- Step 02
Readers chosen
Work out who the policy applies to from the roles or teams set on the page.
- Step 03
Staff asked
Message each person in Microsoft Teams with the summary, a link and a button to confirm they have read it.
- Step 04
Confirmation recorded
Log each confirmation in a Notion database, with the person, the version and the time.
- Step 05
Reminders sent
Remind anyone who hasn’t confirmed after a few days, and give the manager a list of who is outstanding.
The result
A clear record of who has read what, ready when it’s asked for.
Only pages an editor marks as a new version send requests, so fixing a typo doesn’t message everyone. Each person is asked once per version, and confirmations are never edited after they are recorded.