How to delegate a restaurant without losing control

In the morning, the owner hands the restaurant keys to the manager

To delegate a restaurant without losing control, write down the delegation level for each type of decision (the manager decides alone, decides and informs, proposes, or asks), set the cases that trigger escalation, and review dated facts together rather than impressions. Control does not come from being present: it comes from a framework both of you know.

Friday's replacement

On a Friday at 4pm, the evening cook is absent. The second location's manager calls the owner: can they bring in a temp, or should two dishes come off the menu? The owner, in a meeting, replies late and in a bad mood. The manager concludes they should have decided alone, and also that they will get corrected if they do.

The following week, the same manager decides a scheduling matter alone. The owner disapproves on seeing the result. The manager concludes there is no rule: sometimes they must ask, sometimes they must not. So they call about everything.

Why delegation backfires on the owner

The boundary is blurry. Nobody wrote down what belongs to the manager. Each case is settled by guesswork, and the mood of the day becomes the rule.

Feedback has not been planned. The owner does not know what was decided. They discover the consequences, hence the reflex to approve everything.

Trust is tested by mistakes. A failed decision is reversed in public, which teaches managers to stop deciding.

Facts are missing to judge by. With no trace of what was done and why, the discussion rests on feelings.

The four levels of delegation

Level	The manager	The owner	Examples
1. Decides alone	Acts, does not inform	Does not see it	Adjust the prep order, reorganize a station during the day
2. Decides and informs	Acts, reports back	Reads afterward	Call in a temp, pull a dish that is out of stock
3. Proposes	Prepares an option	Approves	Change a supplier, modify opening hours
4. Asks	Lays out the situation	Decides	Hiring for a key role, works, a financial commitment

Filling in this table together in an hour is worth more than one more rule. It is completed by the cases where the level changes: a food safety issue moves to level 4 as soon as it touches guests' health.

The method in five steps

1. List the twenty decisions that come up most

Take the calls and messages from the last month. For each decision: who made it, who should have. Format: a spreadsheet or a sheet of paper.

2. Place each decision in a level

With the manager, not for them. You will often find that they would gladly take on more decisions than you thought.

3. Write the exception thresholds

A level 1 can become level 4 based on an observable criterion: a repeated incident, a cost above an amount you will set, a food safety risk. Write the criterion, not "if it's serious."

4. Agree on how to report back

Level 2 assumes a format: a short note, signed, dated, read at a known frequency. Not an extra phone call.

5. Review on a fixed date

After a few weeks, go back over the decisions made: which worked well, which lacked information or framework. You adjust the level, not the person.

A concrete case of a threshold

A fictional example: the manager can hire a temp alone for a service (level 2), provided they log it that same evening. If the same need recurs three weeks in a row, the topic moves up to level 3: it is no longer a stopgap, it is a scheduling or hiring problem that deserves a proposal. The threshold is not an arbitrary amount, it is repetition.

Common mistakes

Saying "you're autonomous" without writing down how far that goes.
Overturning in public a decision that belonged to the manager.
Demanding permanent approval to reassure yourself, which makes delegation fictional.
Confusing follow-up on commitments with monitoring people.
Delegating without giving the manager access to the facts they need.

What to measure

The number of decision calls received per week, by type of topic: if it does not fall, the boundary is still blurry.
Commitments made by the manager and their status on the planned date.
Decisions overturned by the owner, with the reason noted each time.

Where Tsuno comes in

Tsuno keeps decisions, commitments and actions dated, with their provenance, so the discussion rests on facts. The owner can ask "What have my managers not dealt with?" without going through a call, and the manager sees the same information. Tsuno prepares an action and summarizes its effect, a person confirms, and everything is traced: nothing runs on its own. It does not grade managers or predict their departure: the software recalls, people decide. See trust.

Key takeaways

Delegating means writing down decision levels, exception thresholds and a way to report back. Control becomes the review of facts shared with the manager, not permanent approval.

Frequently asked questions

How do you delegate running a restaurant without approving everything yourself?

For each type of decision, write down its level: the manager decides alone, decides and informs, proposes, or asks. Anything left unclassified ends up escalating to the owner by default.

Which decisions should an owner keep?

Generally strategy, key hires, investments and anything that commits the group over the long term. The rest depends on your organization, but it must be written down and known to the managers.

How do you follow a manager without monitoring them?

By looking at dated commitments and their results, shared with the manager, rather than signals collected without their knowledge. Follow-up is useful when the manager sees what you see.

What if a delegated decision goes wrong?

Go back over the facts with the manager, look for what was missing (information, framework, training) before looking for fault, then adjust the level of delegation if needed.

How long does it take for delegation to work?

It depends on the manager and the subject. Go in stages: give a limited scope, review the results on an agreed date, then widen or clarify.