Team & operations

Staff policy acknowledgements with Notion and Teams

Policy acknowledgement automation asks the right staff to read a policy whenever a new version is published in Notion. It records who confirmed which version and when, and reminds anyone still outstanding.

An example of how the studio would build it. No live services are connected.

From an updated policy to a record of who has read it.

  1. Step 01

    Policy published

    An editor marks a Notion policy page as a new version, with a short note on what changed.

  2. Step 02

    Readers chosen

    Work out who the policy applies to from the roles or teams set on the page.

  3. Step 03

    Staff asked

    Message each person in Microsoft Teams with the summary, a link and a button to confirm they have read it.

  4. Step 04

    Confirmation recorded

    Log each confirmation in a Notion database, with the person, the version and the time.

  5. 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.

Before we connect it.

Where this is useful

Useful for nurseries, clinics, gyms and care providers, where inspectors or insurers may ask how staff learn about changes to safeguarding, health and safety or data policies. A sensible first version handles one handbook section and one team, with reminders going to the manager rather than straight to staff.

What we need to connect

  1. 01A Notion handbook with one page per policy, and properties for the version, the owner and who it applies to.
  2. 02A Microsoft Teams app or workflow that can message staff individually and receive their confirmation.
  3. 03Your list of roles and teams, how long staff have to confirm and who follows up with anyone who doesn’t.

What needs careful handling

Some staff, such as casual or agency workers, may not have Teams accounts, so they can confirm through an email link or on paper and be recorded by a manager. Confirming that something has been read is not the same as understanding it, so important changes can still be covered in a team meeting or training. People join between versions, so new starters are asked to read the current version of each policy that applies to them.

Questions people ask.

Will this satisfy an inspection?

It gives you a clear, dated record of who confirmed each version, which is often what is asked for. Inspectors also look at how policies are put into practice, so it supports your approach rather than replacing it.

Do we have to use Notion?

No. The same approach works with policies kept in SharePoint, Google Drive or another tool that records versions. Notion suits teams that already keep their handbook there.

All automation examples