Guides & resources
The employee handbook nobody opens: writing one frontline teams actually use
What belongs in an employee handbook for frontline and deskless teams, how to keep one version current across sites, and how to tell whether anyone finds the answer.
Quarter past eight on a Thursday. A guest asks about returning something bought three weeks ago. The person serving them started eleven days ago. She knows the answer exists — it came up in her induction, and she is fairly sure it is in the handbook. What she does not know is whether the handbook is in the welcome email, in the binder in the back office, or on an intranet she has never signed into. So she guesses.
Most writing about employee handbooks stops at the table of contents. This one covers that too, because you need it, but spends as much time on the question that decides whether the work was worth doing: does anyone find the answer when it matters?
What a handbook is for, and what it is not
A handbook collects what applies at work: terms, routines, expectations and practical answers. It is not the employment contract and it does not replace one. Where a union agreement or a collective agreement applies, the handbook explains it in plain language rather than restating it — restating it means maintaining the same fact in two places, and the two will drift.
It is also not a set of SOPs. An SOP describes how one task is performed, step by step, and belongs where the work happens. The handbook describes everything around the work: calling in sick, breaks, uniform, who to go to. Merge the two and the handbook becomes a document nobody finishes.
Legal requirements vary by country and, in the United States, by state — what has to be written down, what has to be acknowledged, and what has to be posted are all local questions. Check yours with someone qualified. What is consistent everywhere is the underlying point: certain things have to exist in writing, be known, and be findable. A handbook is the tidiest way to satisfy all three at once.
What belongs in it
Content varies by industry and size, but most of it falls into six groups.
About the company
What you do, who you serve, what you expect of each other. Keep it short. This part is read once, at induction, and never again.
Employment and terms
- contract types and probation
- pay, pay dates and how to query a payslip
- holiday entitlement, the holiday year and carry-over
- overtime and unsocial hours
- pension and insurance
- notice periods
Point at the agreement where one applies rather than copying it out. Otherwise the same fact lives in two places, and the two will drift.
Absence and leave
- calling in sick: who to tell, how, and by when
- sick pay and when a sick note is needed
- time off for dependants
- parental leave and unpaid leave
- booking holiday: how and how far ahead
- compassionate leave
This is the section people actually look up, usually on a phone and usually while ill. Write it simpler than you think you need to.
Health, safety and conduct
- your health and safety policy
- who the safety representative is and how to reach them
- how to report an incident, an accident or a near miss
- what to do about threats or violence
- guidelines on harassment, sexual harassment and retaliation
- evacuation, assembly point and first aid
- lone working, where it happens
Evacuation and first aid have to be site-specific. A handbook that says “the assembly point is signposted” helps nobody.
The practical stuff on the floor
- uniform, protective equipment and hygiene rules
- staff meals and staff discount
- phone use on shift
- smoking
- keys, alarm codes and what to do if the alarm goes
- alcohol, on shift and at staff events
- parking, changing rooms and lockers
This is what new starters ask about most, and what handbooks most often leave out entirely.
Compliance
- confidentiality
- data protection and how you handle personal data
- social media guidelines
- second jobs
- whistleblowing
- gifts, hospitality and conflicts of interest
In food service, food safety and HACCP sit here or in a handbook of their own, depending on how much of it there is.
Two things that are easy to forget, and that belong to no section: who owns each part, and when it was last reviewed. Without those, a handbook goes stale without anyone noticing.
The part nobody writes about
Think about who actually needs the handbook. Rarely head office. It is the person on shift — the new starter in week three, the agency cover, the summer hire in July. They have no time to hunt, they are not at a desk, and they would rather ask a colleague than open a document. The colleague’s answer is roughly right, roughly as often.
Three things decide whether a handbook gets used:
- It is on the phone. Not in the welcome email. Not behind an intranet login only the office has. In the same app as the rest of the work.
- It is searchable. Nobody reads a handbook. People look things up in it, using their own words — “sick”, not “absence procedure, section 4”.
- The answer is trustworthy. If two versions say two things, people stop asking the handbook and go back to asking each other.
One version, everywhere
The most common reason a handbook falls out of use is not that it is badly written. It is that nobody is sure which version is current any more.
It starts innocently. Someone exports a PDF and emails it round. A site prints its own and puts it in the binder. A section gets updated, but only in the original. Six months later the handbook exists in four versions and three of them are wrong.
The fix is dull and it works: one handbook, one place, one current version. Updates happen there and land everywhere at once. Every section has an owner and a date for its next review. Do that review twice a year, and any time a law or an agreement changes.
The right handbook for the role
A group running restaurants, hotels or stores rarely has one handbook. It has a shared layer that applies to everyone, then parts that apply to some: the kitchen’s routines, the front desk’s routines, the bits only site managers should see.
Solve that with one long handbook and you make everyone read past what does not concern them, which is a reliable way to stop them reading at all. Solve it with seven separate documents and you get seven version problems instead of one.
What works is one body of content with permissions over the top: the same handbook, where each person sees their part, driven by site and role.
How to tell whether it is working
This is where most teams stop. The handbook is published, everyone gets an email, and then there is no signal at all about whether it is used until something goes wrong.
There is a better measure: what people ask about. If the same question comes up every week, either the answer is missing from the handbook or it cannot be found. Both are worth knowing, and both can be fixed in an afternoon.
In Todolo the handbook lives in the Knowledge module. Existing material is imported as PDF or Word and structured into chapters and sections with one clearly current version. Permissions are set per site, site group and role, so the right handbook reaches the right person. It is published in the web and mobile apps, and it is searchable.
On top of that sits TOD, which answers questions from your own material and points at where the answer came from, so whoever asked can read the full section themselves. The question gets asked mid-shift, on a phone, instead of someone digging through a document library. And TOD’s analytics show what the team actually asks about, which handbooks get used — and which questions got no answer at all. That last list is the most useful one you will have, because it is the gaps in your handbook, written down.
Common questions
Is an employee handbook a legal requirement?
That depends on where you operate, and in the US on the state. Some policies have to exist in writing whatever you call the document that holds them. Check the specifics locally; the handbook itself is a format, not the obligation.
How often should a handbook be updated?
Review it twice a year, and whenever a law, an agreement or an internal routine changes. Give every section an owner and a review date, or it will go stale quietly.
What is the difference between a handbook and an SOP?
The handbook says what applies: terms, routines and expectations. An SOP says how one task is done, step by step. Keep them apart, or the handbook gets too heavy to read and the routines too hard to follow.
How do we get people to actually read it?
Assume they will not. They look things up instead. Put it on the phone, make it searchable in everyday words, and keep it to one version. Then measure what people ask about, and fill the gaps.
Can Todolo write our handbook for us?
No. The content is yours, and you are the ones who know what applies where you work. Todolo takes the material you already have, as PDF or Word, and turns it into a structured handbook with version control and permissions that your team can search and ask TOD about.
Our handbook is on the intranet. Is that not enough?
It depends who is on shift. If the intranet works on a phone, with no desk and no hunting, it may well be. If the honest answer is that most of your frontline has never logged into it, the handbook is invisible to the people who need it most.
Start with the question that gets asked most
You do not have to rebuild the whole handbook to make progress. Find out which question your team asks their manager most often, and make sure it has an answer that can be found in ten seconds on a phone. Do the same with the next question the following week.
In thirty minutes we will walk through what your current handbook would look like in Todolo, using your own material. There is no long contract to sign, and there is a 30-day money-back guarantee.