The Café Staff Handbook Nobody Writes Until They Need It
9 October 2026 · MidaOne
Most small cafés run perfectly well on verbal understanding. Everyone knows roughly what time to arrive, roughly what counts as a reasonable staff drink, roughly what happens if you can't make a shift. It works until the first real disagreement — and then it turns out two people remembered the rule differently, both of them honestly, and there is nothing written down to settle it. That is the moment owners decide to write a handbook, which is the worst possible moment to write one, because now it reads as a response to a person rather than a description of a café.
This post is about the document: what belongs in it, what doesn't, how long it should be, and how to introduce it without the team hearing a threat. It is not about entitlements. Leave, notice, gratuity and the rest sit in the employment contract and in UAE labour law, not in a handbook, and we cover them separately in staff contracts and visas and leave entitlements. Nothing here states a figure or an entitlement, and your handbook shouldn't either.
A handbook is not a contract, and the difference matters
The contract defines the legal relationship between you and one employee: the role, the pay, the hours, the terms on which it ends. It is individual, it is binding, and the terms in it are governed by law. If you find yourself drafting a handbook clause about notice periods or annual leave days, stop — you are writing the contract again, badly, and if the two documents ever disagree you have created a problem rather than solved one.
The handbook covers something the contract is silent on: how this particular café runs. Not what someone is owed, but what they do on a Tuesday morning, who they tell when the milk delivery is short, whether they can answer their phone behind the bar. It applies to everybody rather than to one person, it is yours to change, and it is the document that stops a shift running on folklore.
| Belongs in the contract | Belongs in the handbook |
|---|---|
| Role, pay, agreed hours and place of work | What the opener actually does in the first twenty minutes |
| Leave, notice and end-of-service terms as they apply to that employee | How you request leave: who you ask, how far ahead, and how you'll hear back |
| Probation and the grounds on which employment ends | What counts as a lateness problem, and at what point it becomes a conversation |
| Anything the law requires of the employment relationship | Phones, uniform, staff drinks, till rules, and who to tell when something goes wrong |
What actually goes in it
Write the things that have caused, or could cause, an argument. For a café that is a short and fairly predictable list.
- Shifts and attendance. How the rota is published and how far ahead, how swaps work and who approves them, and — the important one — exactly what you do when you cannot make a shift. Who you call, not who you message, and by when.
- Breaks. When they happen, how long, where they are taken, and whether you leave the premises. This is a frequent source of quiet resentment precisely because it is usually unstated.
- Uniform and appearance. What is provided, what the team supplies, what the standard is and who launders it. Our guide to uniform and appearance standards is the long version; the handbook needs one paragraph.
- Phones. Say the actual rule rather than implying one. A blanket ban that nobody enforces is worse than a stated norm about not using a phone in front of a customer.
- Staff drinks and food. What is free, what is discounted, when, and how it is recorded. Vagueness here costs real money and real goodwill — the detail is in staff drinks and comps.
- Cash and the till. Who opens a drawer, what happens to a mistake, who can void or refund, and how a shortfall is handled. Not an accusation: a procedure, which is what cash handling and security exists to describe.
- Customers. What a barista is authorised to do on their own when a drink is wrong or a customer is unhappy, and when to fetch the manager. Giving the team a clear limit is what makes a refund and complaint policy usable at the counter.
- Raising a problem. Who you go to, and the second name for when the first person is the problem. A handbook without that second name is a handbook that only protects the manager.
Notice what is not on the list. No salary scales, no leave allowances, no notice periods, no disciplinary penalties expressed as amounts. Describe process — that an issue gets raised, in writing, early — and leave the entitlements where they legally live.
Write it in the languages your team reads
A UAE café floor is routinely three or four first languages. A handbook that exists only in English, handed to a team that works in Arabic, Urdu, Hindi or Tagalog, is a document written for your protection rather than for their understanding — and it will not do much protecting either, because "they signed it" is a thin argument when nobody can show the person could read it.
You do not need a professional translation of every page. Translate the operative parts: the rules someone could be held to. Then have the person acknowledge, in the language they actually read, that it was explained to them. If your team is largely Arabic-reading, that version is the real document and the English one is the copy — which is the same principle behind keeping the menu and receipts bilingual rather than treating Arabic as an afterthought.
Keep it short enough to actually be read
The common failure is not a missing handbook. It is a thirty-page document assembled from templates, full of clauses about company vehicles and share schemes, that nobody has opened since the day it was printed. A café handbook should be a few pages. Plain sentences, one subject per heading, no defined terms, nothing that needs a lawyer to parse at six in the morning.
Treat it as a living document rather than a monument. When you change a rule — new opening hours, a new rule about deliveries, a decision you made after something went wrong — change the handbook that week, note the date on it, and tell the team what changed. A handbook that is visibly maintained gets taken seriously. One that is three years stale teaches the team that written rules here are decorative.
Rolling it out without making it a threat
With a new hire this is easy: it is part of induction, you walk through it together, they sign, it goes in their file alongside everything else. Build it into barista training and it never has to be a separate event.
With an existing team it needs framing, because a document appearing after years of informality reads as distrust. The honest framing is usually the true one: this is writing down what we already do, so that a new person can learn it in a week and so that nobody has to guess. Ask them to read it and tell you what is wrong — half the corrections will be things you had genuinely misremembered about your own café, and a team that edited the handbook tends to follow it. It is a small thing, and it sits in the same place as everything else that quietly affects whether good staff stay.
Where MidaOne fits
A handbook is a document, not software, and no system writes it for you. But several of the promises a handbook makes only hold if the till backs them up — otherwise you have a rule in a folder and a different reality at the counter.
MidaOne has staff roles and permissions scoped by role and by branch, so "only a supervisor processes a refund" is enforced rather than trusted. Shift closes show expected against counted with the difference, which turns a shortfall into a number both of you can look at instead of an accusation. Sales by employee exists for the same reason. The point is not surveillance; it is that written rules and system permissions should say the same thing, so that the handbook describes the café rather than contradicting it. Where the two diverge, staff follow the system every time — see POS permissions and staff security for how to set them to match.
Give every role exactly the access it needs. Free for 14 days, no card required.
Start your free trialFrequently asked questions
Is a staff handbook legally required for a café in the UAE?
A handbook is not a substitute for the employment contract, which is the document the law is concerned with. Whether anything beyond the contract is required of your business is a question for MOHRE or an employment adviser rather than a blog. The practical reason to have a handbook is different anyway: it gives you a consistent, written answer when a dispute turns on what the rule was.
How long should a café staff handbook be?
A few pages. If it runs past about ten, it has almost certainly absorbed template material that has nothing to do with running a café. The test is whether a new barista could read it properly in one sitting on their first shift and remember most of it.
Should the handbook cover leave, notice periods and gratuity?
No. Those are governed by the employment contract and by UAE labour law, and a handbook clause that restates them will eventually contradict them. Cover the process instead — how you request leave, who approves it, how much notice of a request you expect — and point to the contract for the entitlement itself.
What language should a café staff handbook be in?
The languages your team actually reads, which in most UAE cafés means at least Arabic and English. Translate the operative rules rather than every page, and have each person acknowledge the version they can read. A rule somebody could not understand is difficult to rely on later, however clearly it was written in English.
Do staff need to sign the handbook?
Have them sign or otherwise acknowledge that they received it and that it was explained, and keep that acknowledgement in their file with the contract. It is not about building a case against anyone — it is how you establish, a year later, that the rule existed and was communicated rather than invented after the incident.
Write it on a quiet afternoon when nothing has gone wrong. It will take you two hours, most of which is realising how many rules your café runs on that have never been said out loud — and the version written in calm is the one that reads like a description of a workplace instead of a reaction to a person.