slim.to / Blog

The onboarding doc nobody reads (and how you'd find out)

You wrote the handbook. You linked it in the welcome email. Whether anyone got past page two is the one thing you've never been able to check — here's the version where you can.

The slim.to team · · 4 min read

Every company has a document that everyone agrees is important and nobody has finished. The onboarding handbook. The security policy. The new expenses process. The 40-slide deck from the all-hands.

You can tell it isn't landing because the same questions keep arriving in Slack — questions the document answers, on page six. But you can't tell why. Is it that people never open it? That they open it and bounce? That they read the first third and stop at the wall of text on page four?

Those need three different fixes, and without data you'll guess.

Put the document behind one internal link — on your own domain, so it looks like a company resource rather than a random URL:

docs.yourcompany.com/onboarding

Send that. Put it in the welcome email, the Slack channel topic, the offer pack. One address, forever, which is worth something on its own: internal documents that live at a stable URL get linked to, and documents that get linked to get read.

If the doc lives as a page rather than a PDF, an assistant can publish and update it directly — the whole flow is in "Make me a newspaper".

What the read profile tells you

After a dozen new starters, the shape of the problem stops being a mystery.

Everyone opens it, nobody finishes. Median read: 90 seconds on a document that takes 20 minutes. That's not a readership problem, it's a length problem. The fix is not a reminder email; it's cutting the document or splitting it into the four things people actually need in week one.

A cliff at one page. Steady reading, then a sharp drop at the same point every time. Something on that page is doing the damage — usually a dense table, a wall of policy text, or the section written by legal. That page is now the highest-leverage thing you can rewrite, and you'd never have found it by guessing.

Opened once on day one, never again. The document is being treated as a formality, not a reference. That's usually a structure problem — nothing is findable, so nobody comes back. Headings and a table of contents will do more than any amount of chasing.

Half of them never open it at all. Now it's a delivery problem, not a content problem. The link is buried in an email nobody reads on their first morning, and it needs to move somewhere it'll be seen.

Each of those is a specific, actionable finding. All four look identical from the outside — "people don't read the handbook".

The compliance version

For documents where "did they read it?" is a question you may one day have to answer — a security policy, a code of conduct, a policy update — the same setup plus an email gate gives you a per-person record: who opened it, when, and how long they spent.

Two honest caveats before anyone builds a process on this:

Used to improve a document, this is good practice. Used to check up on individuals, it's the kind of thing that gets a tool banned internally — and deserves to be.

The habit that makes it work

Update the document in place, at the same URL, forever.

Onboarding docs rot faster than anything else in a company, and the reason is almost always distribution: someone fixes the doc, but the version circulating is a PDF attached to a template email nobody has edited in two years. Replacing the file behind a stable link means fixing the doc actually fixes what people see.

That single property — the link is always current — is what turns a handbook from an artefact into a living document.

Where to go next

Keep reading