Employee handbook acknowledgement form (template)

An employee handbook acknowledgement form is a short statement each employee signs to confirm they received the handbook, read it, and know where to find it. Below is a template you can copy, followed by notes on each line and on collecting it at scale.

It is a starting point, not legal advice. Employment law differs by country and by state, so have the wording checked for where your people work.

The template

Replace everything in square brackets.

EMPLOYEE HANDBOOK ACKNOWLEDGEMENT

Company: [Company name]
Handbook: [Handbook title], version [version or revision date]
Where to find it: [link or location]

I confirm that:

1. I have received the [Company name] employee handbook named above,
   or have been given access to it at the location above.

2. I have read it, and I understand that I can ask [name or role] about
   anything in it that is unclear.

3. I understand that the handbook may be updated, that I will be told
   when it changes, and that I may be asked to acknowledge the new
   version.

4. [Optional, have this line reviewed by a lawyer] I understand that
   the handbook [is / is not] part of my contract of employment, except
   where it says otherwise.

Employee name: ______________________________

Signature: __________________________________

Date: ______________________________________

For HR use
Received by: ________________  Date recorded: ________________

What each line is for

Company, handbook and version. The version is the line most often left out, and the one that matters most later. If the handbook changes in March, a signature from January covers the January text only. Use a version number or the revision date, whichever you already maintain.

Where to find it. Many handbooks now live in a wiki or a shared drive rather than on paper. Naming the location makes "received" mean something when nobody was handed a copy.

Item 1: received. This is the core of the form. In the UK, employers must give employees a written statement covering, among other things, disciplinary and grievance procedures within two months of the start of employment, and some day-one information can sit in a separate document the employee "has reasonable access to", such as an intranet page (GOV.UK). If your handbook carries any of that, a record that each person had access is worth keeping.

Item 2: read and can ask. Naming a person or role to ask turns the form from a box-tick into a route for questions.

Item 3: updates. GOV.UK also says employers must tell employees about any changes to the written statement within one month of making them (GOV.UK). Setting the expectation in the form makes re-acknowledgement routine rather than a surprise.

Item 4: contractual status. Whether a handbook, or parts of it, form part of the contract is a legal question that depends on your wording and jurisdiction. It is marked optional for that reason. Leave it out rather than guess.

Signature and date. The date should be the date the person signed, not the date HR filed it. The HR section records the second date separately.

If you have staff in California

California employers must distribute a written harassment, discrimination and retaliation prevention policy, often part of the handbook. The regulation's accepted distribution methods include giving each employee a copy "with an acknowledgment form for the employee to sign and return", or an intranet "with a tracking system ensuring all employees have read and acknowledged receipt of the policies" (2 CCR § 11023(c)). The same regulation requires the policy to be translated into every language spoken by at least 10 percent of the workforce at a facility (2 CCR § 11023(e)).

Collecting it

For a handful of people, a printed form or a PDF sent for e-signature is fine. The work grows with headcount and with every handbook update:

• New starters. Each one needs the form in their first days, so it has to be part of onboarding rather than a reminder someone remembers to send.
• Updates. Every material change means a new version, and a new round of signatures from everyone.
• Chasing. Someone has to see who has not signed and remind them.
• Filing. The signed forms have to end up somewhere you can find a specific person's form for a specific version, on request.

Doing it in Listor

Listor replaces the paper form with the same record, collected and chased automatically. The handbook stays where it already lives (a Notion page, a Google Drive PDF, an intranet page); Listor holds its title and link.

• Assign once. Target the handbook at the All Employees group. Everyone who joins the workspace is added to that group, so the handbook appears on each new starter's reading list as soon as they join.
• Acknowledge. Each person opens the handbook from their reading list and confirms "I've read this". The confirmation is dated server-side and stored with their IP address and user-agent, which stands in for the signature and date lines.
• Ask. "I need help" sends a question to the handbook's owner, which covers item 2 of the template.
• Update. When the handbook changes, declare a new revision label and force re-attestation. Everyone targeted is emailed, and earlier acknowledgements stay on the record against the earlier version, which covers item 3.
• Renew. Set a renewal interval, for example 12 months, and Listor emails anyone whose acknowledgement has lapsed.
• Produce the record. The audit log exports as CSV or JSON, one row per acknowledgement, with person, document, revision, IP address and user-agent.

Forced re-attestation, renewals and help requests are on the paid plan. Listor is free for up to 10 assigned people and five documents; see pricing and employee handbook attestation.