Delegating as a new restaurant owner: a delegation ladder

Most new owners don't decide not to delegate. It happens by default. You opened the place, you know how everything works, and doing it yourself is faster than explaining it. Six months in, you're still the only person who can place the produce order, count the safe, fix the printer and answer "are we out of oat milk?"

That's not sustainable, and it's not good for your team either. People who are never handed anything don't grow, and the good ones notice.

This is the first post in our series on leading your first team. It covers how to find what to hand off, which tasks to start with, and a simple ladder for handing them over without losing control. The rest of the series covers check-ins, raises, recognition, fair schedules, conflict between staff, and letting someone go.

Start with a one-week time audit

Before you hand anything off, find out where your week goes. For one ordinary week, keep a list on your phone. Every time you switch tasks, write down what it was and roughly how long it took. Don't clean it up: "answered three texts about the schedule, 15 min" counts.

At the end of the week, sort every line into one of four groups:

Group	What it means	Examples
Only you	It needs your authority or your money	Hiring and firing, pay rates, signing contracts, the bank
You, for now	Someone could learn it, but it isn't written down	The vendor order, the weekly schedule, the closing count
Anyone trained	There's already a way to do it, you're just the one doing it	Restocking, temperature checks, opening tasks
Nobody	It doesn't need doing at all	A report nobody reads, a second check of a checked task

The "anyone trained" and "nobody" groups are your quick wins. The "you, for now" group is where delegation really happens, one task at a time.

What to hand off first

Not every task is a good first handoff. The best first ones share four traits:

They repeat. Daily or weekly, so the person gets practice fast and you see the result often.
"Done" is easy to see. The walk-in is organized or it isn't. The order arrived or it didn't.
A mistake is cheap and fixable. A short order on paper towels is a bad day, not a disaster.
They take your time, not your judgment. Counting, checking, restocking and setting up.

That usually points to a list like this:

Hand off early	Hand off once someone is ready	Keep for now
Opening or closing checklist	Ordering from one vendor, using a par sheet	Hiring, firing and discipline
Temperature and food-safety logs	Drafting next week's schedule for you to approve	Pay rates and raises
Restocking and the cleaning schedule	Finding cover for a call-out	Final say on the published schedule
Prep list for one station	Training a new hire on one station	Bank deposits, safe combination, vendor accounts
The handoff note at the end of a shift	Handling a complaint within a set limit	POS settings and anything that edits pay or punches

The right-hand column isn't about trust. Keeping hiring, pay and the money in your hands (or a manager's) separates duties so nobody can, for example, edit their own hours. Our post on promoting your first shift lead explains why that protects your lead as much as you, and goes deeper on cash and keys.

The delegation ladder

Handing something over isn't a single moment. It's a few steps, and skipping steps is where most delegation goes wrong: the owner says "you're doing the order now," the order comes in short, and the owner takes it back for good.

Use five rungs instead:

Rung	What it sounds like	Who decides	How you check
1. Watch me	"Stand with me while I do the order and ask anything."	You	Nothing to check yet
2. Do it with me	"You do it, I'm right here."	You, after they suggest	You watch the whole thing
3. Do it, I'll check	"Do the order, then show me before you send it."	They propose, you approve	Every time, before it goes out
4. Do it, tell me after	"Send it, and tell me what you ordered."	They do, within limits	After the fact, then less often
5. Own it	"The order is yours. Tell me if something changes."	They do	Spot checks, and the numbers

Three rules make the ladder work:

Say which rung you're on. "This week you're on rung 3 for the order" removes the guessing about whether they're allowed to send it.
Move up on evidence, not on time. Three orders in a row that you didn't need to change is a reason to move to rung 4. Two weeks passing isn't.
Moving down isn't a punishment. If something goes wrong, drop one rung for a few cycles, say why, and say what it takes to move back up.

The same ladder works for most of the "you, for now" tasks. Our one-week training plan uses a similar watch, do and sign-off pattern for teaching stations, and our shift lead hiring guide turns it into promotion criteria.

Write the standard before you hand it over

Most "they did it wrong" moments come from a standard that only existed in the owner's head. Before a task leaves your hands, write down four things:

What done looks like. "Walk-in: everything on its labeled shelf, raw below ready-to-eat, nothing on the floor, door shut."
The steps, in the order you actually do them. A checklist beats a paragraph.
What they decide alone, with numbers: "Order up to the par sheet. Anything over $50 above the usual, ask me."
When to call you, for the few things that are truly yours: a vendor price jump, a recall notice, anything to do with safety.

Then let them change the steps once they're on rung 4 or 5. A person who owns a task usually improves it, and that's the point.

Check without taking it back

Owners who stop delegating usually stop because checking feels like doing it twice. Make the checking smaller as the person moves up:

Rungs 2 and 3: check every time, and give feedback the same day. Name what was right, not just what was wrong.
Rung 4: check the result, not the method. Did the order arrive complete? Did the closing checklist get done, with the photos?
Rung 5: check a sample. Read one closing in five, or look at the weekly food cost instead of every invoice.

Watch for the task drifting back to you. When someone brings you a problem with a task they own, ask "what do you think we should do?" before you answer. If their answer is reasonable, say yes. If it isn't, tell them why, and let them decide the next one.

When delegation stalls

"It's faster if I do it." It is, this week. Count how many weeks you'll keep doing it.
"Nobody does it like me." Write down what "like me" means. If you can't, it isn't a standard yet.
"They'll make mistakes." They will, on rungs 2 and 3, where you're checking. That's what the rungs are for.
"I don't have time to train." Start with the task that eats the most of your time, and train for one week only on that.
"They don't want more work." Ask. Some people do, some don't. Delegated work that grows a role is a good reason for a raise or a title later on, which is the subject of a later post in this series.

A one-month delegation plan

Week 1: keep the time audit. Sort it into the four groups.
Week 2: pick two "anyone trained" tasks and hand them off outright. Pick one "you, for now" task and do rung 1 with someone.
Week 3: that task moves to rungs 2 and 3. Write the standard as you go.
Week 4: rung 4 if the evidence is there. Look at what you did with the time you got back.

Then pick the next task. Over a few months, the "you, for now" list gets shorter, and you start working on the business instead of in every shift.

Where Mays fits

Give each task an owner. On a checklist template, Who does it? can be A role or department or Specific people; with Specific people, each person gets their own copy, so the closing checklist can belong to the person you're handing it to. A single task in a template can go to one person with Assign to person. For something one-off, Tasks → Tasks → Create Task on the web assigns it to one person or to the location (Location Task (any staff)), and the person gets a notification.
Check the work at the rung you're on. Tasks → Tasks on the web shows each completed task with the photo, number or note that was submitted, and Team Stats shows each person's completed and open tasks. If something isn't right, Reject Task sends it back with your reason, and the person gets a Task Rejected notification. That's rung 3 without standing over anyone.
Access that matches the job. Mays has three built-in roles: Employee, Manager and Admin. Under Locations & Users → Roles → Add Role, an admin can build a role with only the permissions a task needs, for example Create custom tasks, reject submissions for someone who checks the closing list. People on a custom role use the employee screens in the app, so they review work on the web.
The handoff note. The manager Logbook is a daily journal for each location, with categories and a Needs follow-up flag. Managers and admins read and write it; a custom role can be given View log book and Manage log book.

Mays doesn't record which rung someone is on or run the time audit for you, so keep both in your own notes.

Your delegation checklist

A one-week time audit, sorted into only you, you for now, anyone trained and nobody
Two easy handoffs this week, and one task started on the ladder
The rung said out loud for every handed-off task
A written standard: what done looks like, the steps, the limits, when to call you
Checks that get smaller as the person moves up
Hiring, pay and the money kept separate from the person who counts it

Hand off the first task with Mays

Give each task an owner, see that it got done, and keep the decisions that are yours.

Start your free trial: 30 days, every module, no card needed. Still building the team you'll delegate to? Start with hiring your first restaurant team.