# How to track employee policy sign-off (not just click-through)

*Collection: Managing Documents · Category: Versions & Lifecycle · Availability: FileDeck AI · Canonical URL: https://www.getfiledeck.com/docs/policy-acknowledgment-process/*

Getting a policy *published* is easy. Getting people to genuinely read it — and being able to prove they did, a year later, to an auditor or a tribunal — is the hard part. A blanket "reply to confirm you've read this" email produces a folder of replies that proves almost nothing: no one knows who was actually asked, who ignored it, or which version they saw.

This is a workflow problem before it's a software problem. Below is a process that holds up, and where a document library like FileDeck removes the manual steps. The process matters whether or not you use FileDeck; the tool just stops you doing it by hand.

> **FileDeck AI tier** — the FileDeck feature this process uses,
> [acknowledgment tracking](https://www.getfiledeck.com/docs/acknowledgment-tracking/), is part of the AI
> tier (from $119/year), which sits above Free and Pro; it is **not** included
> in Pro. No AI provider key is needed for it — it runs entirely on your own
> site. [See pricing](https://www.getfiledeck.com/pricing/)

## Why checkbox-only acknowledgment fails

A single "I agree" checkbox at the bottom of a wiki page fails for predictable reasons:

- **Habituation.** People learn that clicking makes the box go away, so they click without reading. The checkbox measures compliance-with-the-checkbox, not comprehension.
- **No accountability.** If confirmation lives in someone's inbox or a spreadsheet, there is no single answer to "who still hasn't done it?" — so no one chases, and it quietly decays.
- **No version pinning.** When the policy changes, last year's confirmations silently become meaningless. Nobody re-confirms because nobody is told to.
- **No audit trail.** "We emailed everyone" is not evidence. Evidence is a dated record of *who was asked, who confirmed, when, and against which version* — including the people who never responded.

You can't fully defeat habituation with software. What you *can* do is make the record trustworthy and the follow-up automatic, so the acknowledgment means something and the gaps are visible.

## Step 1 — Segment who needs to read what

Don't blast every policy at every employee. Over-asking is the fastest way to train people to rubber-stamp. Map each document to the group that actually needs it: safeguarding to staff who work with children, a clinical protocol to clinicians, the finance manual to finance.

In practice that means assigning by **role** rather than emailing named individuals — roles survive staff turnover, so a new hire is covered automatically instead of being forgotten. If you need a small named group, create a role for it.

In FileDeck this is a per-document setting: edit the document, tick the roles that must read it under **Read & confirm (FileDeck AI)**, and optionally set a **Confirm by** date. Everyone in those roles who can open the document — including accounts created later — is now on the hook. See [acknowledgment tracking](https://www.getfiledeck.com/docs/acknowledgment-tracking/) for the full walkthrough.

## Step 2 — Make the confirmation mean something

This is where teams over-reach and buy comprehension quizzes nobody finishes. Be realistic about what actually moves the needle:

- **Put the confirmation on the document itself**, not in a separate survey tool, so reading and confirming are one flow rather than two disconnected tasks.
- **Pin every confirmation to a version**, so "I read it" always means "I read *this* revision" — the single most important property, because it's what makes re-reading enforceable later.
- **Keep the action honest.** A one-click "I confirm I have read and understood this document" that is dated and version-stamped is worth far more than an elaborate quiz that people share answers to.

FileDeck records exactly that: a one-click confirmation on the document's own page, stamped with the document's version at the moment of confirming. It deliberately does **not** fake rigour with a scroll-lock or a quiz — the accountability comes from the dated, version-pinned record and the re-acknowledgment cycle in Step 4, not from trapping someone on the page. If your compliance regime genuinely requires a comprehension test, run that in dedicated training software and use the document library for the attestation record.

## Step 3 — Chase non-responders automatically, not manually

Manual chasing is where policy attestation dies. Someone has to notice who's outstanding, email them, remember to follow up, and do it again next week — and they don't. The fix is to make the chase automatic and the outstanding list a live view, not a spreadsheet you rebuild by hand.

FileDeck emails each person their own outstanding list once a week — one email per person, everything they owe, with links and confirm-by dates — and stops emailing them the moment they're done. You can also click **Send reminders** to nudge a single document's stragglers on demand. Nobody gets double-chased, and people who are up to date are left alone (which keeps the reminders from becoming noise people filter).

## Step 4 — Keep an audit-ready record, and re-ask when the policy changes

The output an auditor actually wants is a table: every assigned person, their status, the timestamp, and which version they confirmed — with the non-responders included, not filtered out. A pile of "confirmed!" emails isn't that.

Two things make the record durable:

- **Export dated evidence.** FileDeck exports a CSV per document or for the whole library: document, user, email, status (`confirmed` / `outstanding` / `superseded` / `confirmed (no longer assigned)`), the confirmation timestamp, and the version they read. Outstanding people appear as rows too, so it answers "who was asked and who didn't respond," not just "who succeeded."
- **Re-ask on meaningful updates.** When a policy materially changes, old confirmations shouldn't silently carry over. Click **Require re-acknowledgment**: everyone shows as outstanding again, but the previous confirmations are kept and marked `superseded` — so you can still prove staff confirmed the earlier version too. Pair this with [document expiry](https://www.getfiledeck.com/docs/document-expiry/) or [review cycles](https://www.getfiledeck.com/docs/review-cycles/) so policies get revisited on a schedule instead of drifting.

## Common mistakes to avoid

- **One blanket email to all-staff.** It trains people to ignore acknowledgments and gives you no per-person status.
- **No owner for follow-up.** If chasing depends on a person remembering, it won't happen — automate it.
- **No version control on the policy.** If you can't say which version someone confirmed, the confirmation is worthless the moment you edit the document.
- **Deleting old confirmations when you update.** Keep them, marked superseded — you may need to prove what people confirmed last year.
- **Treating "we sent it" as evidence.** Evidence is the dated, per-person record including the people who didn't respond.

## How FileDeck handles each step

FileDeck's [acknowledgment tracking](https://www.getfiledeck.com/docs/acknowledgment-tracking/) is part of the **AI plan** (from $119/year — [see pricing](https://www.getfiledeck.com/pricing/)), and it runs entirely on your own site with no AI provider key needed. It covers Steps 1, 3 and 4 directly: role-based assignment, weekly automatic reminders, a live per-person status view under **Documents → Compliance → Acknowledgments**, version-pinned confirmations, one-click re-acknowledgment, and CSV evidence export. Step 2's "make it meaningful" is a one-click, version-stamped confirmation on the document page — honest accountability rather than a scroll-lock. The Free and Pro plans do not include acknowledgment tracking; if you only need to publish and access-control documents, [see what's in each tier](https://www.getfiledeck.com/docs/free-vs-pro/).
