The First Ninety Days of a Fractional COO in a Restaurant Group

A fractional COO in a restaurant group holds the chief operating officer’s role on a set cadence, accountable for the operation, in a group that cannot yet keep a full-time executive busy. That is the definition. It says nothing about what the work looks like on a Tuesday in week three, which is what a founder is asking when they ask what a fractional COO does. Here is the first term in order.

The call before day one

Every founder asks the same three questions on the first call, in some order, and the engagement is written to answer them before anyone meets the team.

• —Distance: how someone who is not in the restaurants every day leads the people who are.
• —Identity: who this person is to the team, and what the team calls them.
• —Control: how the founder knows the team will not be taken somewhere the founder did not send them.

The first is distance. How does someone who is not in the restaurants every day lead the people who are?

The answer is that presence is set in the scope rather than promised: time in the restaurants on a fixed monthly cadence, and between visits a weekly rhythm that runs whether the fractional COO is in the building or not. A fractional COO who is only present when physically present is not running anything.

The second is identity. Who is this person to my team, and what do I call them? The answer is that you introduce the role yourself, with the why, and the title is a real one: Fractional Chief Operating Officer, with access to the schedules, the numbers and the systems from day one. A role the team hears about second-hand never leads it.

The third is control, and it is usually asked last because it is the one that matters most.

How do I know this person will not take my team somewhere I did not send them? Groups ask this because many have lived the opposite: a senior hire who arrived with a direction of their own, gave it to the managers before the owner had agreed it, and was gone inside a quarter with the team split behind them.

The answer is written into the scope: every personnel decision stays with you, and nothing structural reaches the team until you and the fractional COO have built it together. Decision rights are set out before the work starts: where they decide, where they recommend, where the call stays with you. The first disagreement already has an answer.

Week one: read, and do not fix

The first week in the restaurants reads every unit in service, meets every manager, and reads the numbers. It comes back in writing: what was found and where the work starts. It does not come back with a fix.

That restraint is the point. A senior operator sees a dozen things in a first week that could be changed by Friday, and changing them would prove nothing except that the new person likes to change things.

The managers are watching for exactly that. A week that produces a written read and no orders tells them the role runs on evidence, and it gives you a document you can argue with, which is the first real conversation of the engagement.

What the read looks for is narrower than it sounds. Which unit is furthest behind its plan, and why. Where authority actually sits: whether the GMs are running restaurants or running shifts while the decisions are made one level up. Whether the schedule is written from the forecast or from habit. Who on the bench could hold the next job, and who is holding one now that they cannot.

Month one: every manager on one page

By the end of the first month every manager in the group is placed on one page by how they perform today and how far they can go, with you in the room. Not a ranking for its own sake: a read, made together, so that the decisions about roles that follow are made from it and not from a feeling in the moment someone resigns.

This is also where the group’s real org chart shows up. In a founder-led group the structure on paper rarely matches the structure in practice.

A director of operations may hold authority that belongs with the GMs, so the GMs run shifts instead of restaurants and the bench stops growing because nobody wants the next step. The page makes that visible without accusing anyone of it, which is why it is built with you and not handed to you.

Nothing structural moves yet. The read is the basis for what moves in the months that follow, in an order you have agreed to.

The cadence settles

Somewhere in the second month the rhythm stops being new. The flash P&L is read every Monday, food cost and labor line by line. The schedule is checked against the forecast before it posts.

You get a written note every week: what closed, what is still open, and the week ahead. Every GM gets a one-on-one every week. Each period the P&L review ends with every action given an owner and a date, and the next review opens by reading them.

Each piece exists because of what happens without it. A schedule posted before the forecast is read is a labor line decided by habit.

An action list with no owner and no date is a list of good intentions, and a review that does not open on last period’s actions teaches the managers that the actions were never real. A founder who gets no written note either asks for one every week or stops asking, and both are worse than the note.

This cadence is the one RANGE’s founder ran as chief operating officer of two multi-unit restaurant groups, across brands that did not share a kitchen, a guest or a price point. It does not move. The restaurants change; the rhythm is the thing that holds while they do.

The written material arrives in sequence

The role comes with the written material a growing group has usually never had time to write: the management and culinary leadership structures by position, bonus plans and the metrics they pay on, manager and owner P&L formats, job accountabilities, hiring and interview documents, service manuals and policies.

It is built from how well-run groups operate and fit to yours. It is never your own documents handed back.

The order matters more than the list. Structure comes before pay, because a bonus plan written against a position nobody has defined pays for the wrong thing.

Pay comes before accountabilities, because managers read a job description differently once they know what it earns. Manuals and policies come last, and each one goes out at a pace the team can absorb, which usually means one at a time.

Policies carry a lesson of their own. A standard that draws pushback, a dress code, a phone rule, a comp limit, only holds when the reason goes out with it, read at pre-shift before it takes effect. A policy that arrives as a memo is tested within the week. A policy that arrives with its why is kept by the managers who heard it, because now they can defend it to the next person who pushes.

What never changes

Three things hold for the whole term, and a founder should watch for the first time any of them slips.

• —Every personnel decision stays with you. The fractional COO reads the bench and recommends; the hire, the promotion and the exit are yours.
• —Nothing structural reaches the team before you and the fractional COO have built it together. The weekly call is where direction is agreed before anyone else hears it.
• —The rhythm runs between visits exactly as it runs during them. If the Monday read waits for the next trip, the role has become a visit, and a visit is not a role.

The second of the three is the one that protects you from the senior-hire failure most groups have already paid for once. A leader who gives the team a direction you did not set divides it, however good the direction. The call is where it is agreed; the team hears one voice.

Day ninety

By day ninety a founder should be able to see four things without being told. The weekly note has got shorter, because fewer things are open.

Last period’s actions closed, and the ones that did not have a reason written next to them. At least one GM is running a restaurant who was running shifts in week one. And the decisions that used to route to your phone are routing to the call, where they are decided once.

What a founder should not expect by day ninety is a finished group. The first term runs about six months, and the renewal is judged on the period reviews: every unit against its plan, whether the actions closed, and management resignations against the six months before. Ninety days is where the direction becomes visible. The rest of the term is where it becomes the managers’.

Which is the question the term ends on, and the question to ask on the first call before any of this starts: when I step back from the role, who holds it?

If the answer by the end of the first term is a name on your bench, or a search written against a working system instead of a job description written under pressure, the role did what it was for. The fractional COO page sets out the engagement itself; this is what it looks like from inside the first ninety days.