Hiring a Café Manager: The Handover Most Owners Get Wrong

2 October 2026 · MidaOne

You hired a manager three months ago, and your phone still rings at twenty past nine about whether to accept a delivery that is two crates short. Nothing is wrong with the person you hired. The job you handed them was a senior barista's job with a manager's title on it — and the difference between the two is almost entirely about which decisions they are allowed to make without ringing you.

What a café manager is actually for

A manager absorbs decisions. That is the function. Not shifts, not opening the shutters, not standing on bar through the rush — a good shift leader does all of that, and costs you far less. What you are paying a manager for is the thing nobody else in the building can do: close a question without escalating it. If every question still reaches you, you have bought a supervisor at a manager's price and your own week has not changed.

This is why the handover, not the hire, is where it usually goes wrong. Owners interview carefully, pick someone capable, and then hand over tasks while quietly keeping every decision. The manager spends a month asking, learns that asking is the job, and settles into it. Six months later the owner concludes that managers are not worth it, when what actually happened is that nobody ever said out loud which calls were theirs to make.

Hand over decisions in this order

Do it in stages, and let each one bed in before the next. The order matters more than the speed — start with the decisions that are reversible within a day, and keep the ones that commit the business until last.

  1. The rota, inside rules you set. They write it, cover a sick barista and approve a swap. You set the ceiling on hours and the minimum cover per shift, and the structural questions behind it stay yours — see building a café staff rota for what those rules should actually say.
  2. The daily close. They count, record the variance and explain it in writing the same day. A manager who does not own the close cannot be held to the cash.
  3. Reordering up to par. From suppliers you already use, within a weekly value you name. Running out on a Friday costs more than a spare crate of milk.
  4. Service recovery. A remake, a refund or a comped drink up to a limit, decided at the counter and logged, not phoned through to you.
  5. Screening for hourly roles. They shortlist and trial. You still meet the person before an offer goes out.

Each stage needs the same two things: a written limit, and a record of what was decided. Without the limit it is not delegation, it is a gamble. Without the record you cannot review it, which means you will quietly take the authority back the first time something goes wrong.

What you should keep — and say so out loud

Keeping things is not a failure of delegation. Pricing, supplier contracts and payment terms, the bank, the licence and the tax filings, and the decision to let someone go all stay with the owner in almost every small café, and nobody is offended by that. What causes trouble is leaving it unsaid, so the manager finds the boundary by crossing it.

So write the list down, both halves of it, on one page, and go through it on day one. Then stop re-deciding the half you gave away. An owner who overrules a manager's call in front of staff has not corrected a decision — they have told the room whose authority is real, and no amount of job title fixes it afterwards.

The permissions question that decides whether the job is real

Here is the test that cuts through all of it: can your manager do, in the till, the things you just said they could decide? If they can authorise a refund on paper but the system makes them call you for the code, you have not delegated anything. The permissions in your POS are the honest version of your org chart, and staff work out which one is true within a week.

So set access to match the authority you described, not to match seniority in general. Role-based access is the practical way to do it — the manager role gets what a manager decides, and the barista role does not — and POS permissions and staff access covers how to think about the sensitive ones. The principle is narrow: enough access to do the job without asking, tightly enough scoped that every action is attributed to a name.

DecisionWho makes itWhy it sits there
Refund or remake for an unhappy customerManager, up to a limit you setA customer waiting while someone phones the owner has already had a bad visit
Reorder up to par from an existing supplierManager, within a weekly ceilingRunning out mid-weekend costs more than one spare crate
Menu prices and recipesOwnerIt changes the margin on every future sale, not one sale
Supplier contracts and payment termsOwnerIt commits the business well beyond this week
Hiring for hourly rolesManager screens, owner meetsKeeps the rota theirs without handing over who joins the team

How you will know in six weeks whether it worked

Do not judge it on whether the café feels calmer — that is too easy to imagine. Judge it on four things you can actually observe:

  • The questions change shape. Fewer "what should I do" messages, more "this happened, here is what I did". That shift is the whole point.
  • Problems arrive before you notice them. A manager who tells you the fridge is running warm on Tuesday is doing the job; one who tells you after you ask on Friday is not.
  • Variances get explained, not excused. Cash and stock differences come with a cause attached, even an uncomfortable one.
  • Your own week moves. If you are still on the floor every rush, nothing has been handed over — whatever the title says.

Six weeks is also long enough to see the retention effect, which owners usually underestimate. Capable staff leave cafés where nobody on the floor can decide anything, because every shift feels like being supervised rather than trusted; that is a bigger factor in why good café staff leave than most owners expect. A manager with real authority is also your first proper test of whether the place can run without you — the question that decides everything about opening a second branch.

Where MidaOne fits

MidaOne gives staff roles and permissions scoped by role and by branch, so the access a manager has can be made to match the authority you actually gave them — and a branch manager does not get the keys to another branch's settings. On the review side, sales by employee, shift closes showing expected against counted with the difference, and the receipt list a sale can be refunded from all mean a decision has a name on it afterwards. What the system will not do is decide the limits for you: the refund ceiling, the ordering ceiling and the conversation when a variance goes unexplained are yours. It records; you manage. It is all on the flat AED 200 a month, with unlimited devices, so adding a manager's login costs nothing.

Give your manager the access the job needs — scoped by role and by branch. Free for 14 days, no card.

Start your free trial

Frequently asked questions

When does a café actually need a manager?

Usually when the owner has become the only person who can answer anything, and that is costing more than a salary — missed orders, decisions waiting for a phone call, no cover for a day off. If you are mainly short of hands on the floor rather than short of decisions, a senior barista or shift leader is the cheaper and better answer.

What should I hand over to a new café manager first?

The rota inside limits you set, the daily cash close, reordering up to par within a weekly ceiling, and service recovery up to a stated amount. Each needs a written limit and a record of what was decided, so you can review it rather than take the authority back the first time something goes wrong.

What should an owner keep rather than delegate?

In most small cafés: menu pricing, supplier contracts and payment terms, the bank, the licence and tax filings, and the decision to let someone go. Keeping these is normal — the mistake is leaving the list unspoken, so the manager discovers the boundary by crossing it.

Should a café manager be able to issue refunds on the POS?

Yes, up to a limit you set, otherwise you have given them the responsibility without the means. The control that matters is not blocking the action but attributing it: every refund recorded against the name that made it, and reviewed often enough that the manager knows you look.

How do I stop a manager handover from quietly reversing?

Write both halves of the list down, review the records rather than the moments, and never overrule a delegated decision in front of staff. Raise it afterwards in private if it was wrong — the handover survives a bad call far better than it survives being publicly overridden.

The handover is a document, not a conversation. One page: what they decide, what you decide, what the limits are, and what gets written down. Spend an hour on it before the first shift and you will know within six weeks whether the hire worked. Skip it, and in six months you will be telling someone that managers are not worth it in this business — from behind your own till, on a Saturday.

Try MidaOne free for 14 days — no card needed.

Start free