Track Whether Your Team Read the Handbook or Training PDF

You can measure your own handbook the same way this week: create a free tracked link, send it to the team in place of the attachment, and read the page-by-page numbers afterwards — 50 files, 50 links, 12 months of history, no card.

What you actually need to know

The reason this question gets asked is almost never legal. The legal record is the acknowledgement form, and HR guidance is unusually direct about what it is worth: companies are not required by law to collect signatures, it is good practice to do so, and a court will generally side with the employer even where the employee says they signed without reading.

So the signature already does its job. What it cannot do is tell you whether the new expenses policy on page 34 has been seen by anybody, which is the question that actually matters the week before it takes effect. Two things are worth knowing, and they are different measurements: coverage — how much of the team opened it at all — and depth — how far into the document the ones who opened it got.

Depth is the one that changes decisions. If nobody reaches section nine, the fix is not a reminder email; it is moving section nine, or sending it on its own.

The workflow, step by step

1. Upload the PDF and create a link, one per group. A link per department, site or intake gives you a comparison rather than a single number, and it costs nothing on a free plan that carries 50 links.

2. Turn the email gate on if you need names. The gate asks for an address before the document opens. Internally that is a reasonable ask, and it is what turns “41 sessions” into a list you can follow up. It records an address somebody typed rather than a verified identity, so where it has to be exact, one link per person is the more reliable shape.

3. Send the link, not the file. An attachment is a copy: it lands on someone's laptop and reports nothing back. Everything on this page depends on the document being served as pages.

4. Keep your acknowledgement form exactly as it is. The reading data is a management instrument, not a compliance record, and swapping one for the other is the mistake this page exists to prevent.

5. Read the numbers a week later, then change the document. Reading data on a policy nobody rewrites is a report; reading data that moves a section to the front is a process.

What to measure, and what the numbers mean

Reach per page is the headline. It answers “how far did people get” directly, and on a long document the answer is usually humbling — in our own corpus, on documents of 20 pages or more, 10.7% of recorded sessions reached the last page.

Time per page separates reading from scrolling. A page that everyone reaches and nobody dwells on has been passed through, not read, and on a handbook that is often the table of contents doing its job.

Return visits are the quiet compliment. Somebody coming back to the leave policy in March is the document being used as a reference, which is what a handbook is for and is invisible to every distribution report.

Coverage against headcount is the one to handle carefully. Sessions are not people: the same person on a phone and a laptop is two sessions, and automated opens from mail-security scanners are excluded from our counts rather than inflating them. Compare a link's reach against its own audience, not against a payroll number. How duration itself is measured, and where it is unreliable, is set out in how to see how long someone spent reading your document.

The methods compared

Five ways an internal document gets sent, and what each leaves on the record. The last column is the one HR usually needs and the tracking column is the one nobody has.

The Google row deserves its own sentence, because it is the method most teams reach for first and its limits are documented rather than inferred.

“If the file isn't owned by a Google Account through work or school, no one can see the view history.”— Google Docs Editors Help, “See file activity”, fetched 2026-08-14

The second limit sits in the same document: a viewer can turn their own view history off, and Google notes that doing so does not affect view logs outside the Activity dashboard. Where the dashboard applies, what a Drive link gives you is access rather than depth: Activity dashboard covers only work/school-owned files, and any viewer can hide their own view history. For a handbook it does not apply at all — Google documents the Activity dashboard for Docs, Sheets and Slides, not for a PDF stored in Drive, so a Drive link to a PDF has no view history to read on any account type.

What this cannot do

It is not an LMS and it does not record completion. There is no course, no quiz, no pass mark and no completion certificate. If your obligation is to evidence that people completed training, a learning system is the right tool and this is not a substitute for it.

It does not capture a signed acknowledgement. We have no e-signature at any tier and are not building one. Reading data does not replace the form; it tells you something the form was never able to.

It does not prove comprehension, and nothing on the market does. Reaching the last page of the code of conduct is not the same as understanding it, and a page that claimed otherwise would be selling you a number.

And it stops at the download. Once someone saves a copy, the reading that happens afterwards is invisible — to us and to every method in the table. Keeping downloads switched off is the honest way to get a complete reading record, at the cost of the offline copy some staff genuinely need.

Where the other options win

The acknowledgement form wins where it counts legally. It is the record that a dispute turns on, and no amount of reading data replaces a signature and a date. Keep it.

A learning system wins on the audit trail. Enrolment, completion, expiry, re-certification and the reporting that goes with them are its whole purpose. If the handbook is one item inside a mandatory training programme, that programme is where it belongs.

Google Drive wins on reach and on file types. 15 GB free with every Google account, everyone in the organisation already has an account, and it takes every format your team works in where we take PDFs and nothing else.

Peony wins when the acknowledgement has to happen in the same place as the reading — 3 e-signatures per month, free on its free tier, against none from us at any price. Where we come back in is narrow and it is the point of the page: which pages of a long internal document actually got read, on a free plan that keeps the answer for twelve months. The wider how-to for measuring a PDF at all is how to track PDF files.

When Pro becomes the right choice

Free is the whole job for one handbook and one rollout. Page-by-page reading, the email gate, the download switch and 12 months of history are all on it — free is not a preview of the data — and 50 links is more than enough for a link per department.

Pro becomes the right choice at the point where you are doing this for a headcount rather than a team. Once every joiner needs their own link so that “who has not read it” is a list of names instead of a guess, bulk personalised links build one labelled link per person in a single pass. Two more things change at that scale: when the policy is revised you replace the file behind the live link, so the URL you circulated six months ago keeps working and the reading history stays attached to the document; and 24 months of history covers an annual review cycle rather than a single year. At $9/mo that is the trade — the afternoon you stop spending on link admin every intake. Full limits are on the pricing page, and the live demo shows the readout on sample data.

Keep reading: how far people get through a long document, how to track PDF files, and how free PDF tracking works.