The Rescue Job

The Fractional Operator Turnaround Engagement, End to End

What a good fractional turnaround engagement looks like, from the first phone call to the handoff. Discovery, scoping, diagnostic, execution, exit.

Kiyong (Eric) Lee·Operations Executive·August 2026·10 min read

The short version

Discovery is one 60-minute call. Its only job is to confirm the business is a real turnaround candidate and the founder is ready to give the operator authority.
Scoping fits on one page. Four phases, four phase-gate deliverables, four fees, two exit ramps.
The diagnostic phase is 30 days, billed as a fixed fee. It ends with a written diagnostic the founder can act on with or without you.
Execution runs 5 to 8 months. Every two weeks you deliver a written progress note against the diagnostic. No surprises at quarter end.
The handoff starts on day one and ends with the internal owner running the standing meeting while you sit silent in the room.

Most fractional engagements go wrong before the operator ever walks in the door. The scoping was fuzzy, the authority was never real, and the exit was never defined. Six months in, the operator is still there, the numbers have not moved, and both sides are quietly resenting each other.

A good fractional turnaround engagement is not a mystery. It has a shape. The shape is four phases, four deliverables, four fees, and two exit ramps. If you get the shape right in the first two weeks, the actual work is straightforward. If you get it wrong, no amount of talent on either side rescues it.

This is what a good one looks like, from the first phone call to the day I walk out. I run this model as Fractional Head of Operations and Turnaround Lead at a $30M Michelin-recognized Bay Area restaurant group, and the shape below is what I have settled on after enough attempts to know which pieces matter.

Phase zero: the discovery call

Before there is a scope, there is a phone call. One call. Sixty minutes. Its only job is to answer two questions plainly, and the founder and I both have veto rights.

Question one: is this actually a turnaround? A lot of what founders call a turnaround is really a coaching engagement, a strategy question, or a hiring problem in disguise. If the business is growing 20 percent year over year and margins are compressing 200 basis points, that is not a turnaround. That is a scaling problem. Different fix, different operator, different fee. If three units are losing money every month and the founder is personally covering payroll from the healthy units, that is a turnaround.

Question two: is the founder ready to give the operator authority? This is the harder question. Most founders say yes and mean no. What they mean is that they want the operator's judgment on tap but they want to keep making the calls themselves. That does not work in a turnaround. In the discovery call I ask directly: for the length of the engagement, will the general managers report operationally to me? Can I hire and fire at the manager level with your approval but not your permission? Can I change the standing agenda without a meeting about the standing agenda? If any of those get a soft yes, the engagement is not going to work and the honest thing is to say so on the call.

The fractional operator without authority is a consultant with a bad pricing model. The client pays for the operator's time and gets the consultant's output. Nobody is happy.

Discovery calls are not billed. If the answer is no on either question, the honest move is to say so and end the call warmly. I get to no on discovery calls about a third of the time. The engagements that survive the discovery call are the ones worth doing.

Phase one: written scope on one page

If discovery clears, the next step is a one-page scope document. Not a proposal deck. One page. If the scope does not fit on one page, the engagement is not defined tightly enough to succeed.

The one page has these things and nothing else:

The four phases and their durations. Diagnostic (30 days). Execution (5 to 8 months). Handoff (final 60 days, overlapping with execution). Post-exit checkpoint (one call at 90 days after exit).
The deliverable at each phase gate. Written diagnostic at day 30. Biweekly progress notes during execution. Handoff runbook at day 210. Sixty-day post-exit note.
The fee for each phase. Fixed for diagnostic. Monthly retainer for execution. Included in retainer for handoff. Flat fee for the post-exit checkpoint.
The two exit ramps. Either side can end the engagement at the day 30 gate for any reason with the diagnostic fee due. Either side can end at any subsequent monthly checkpoint with 30 days notice.

That is the whole scope. It gets signed before day one. It is boring by design. Every hour spent making the scope airtight in week zero saves a week of grief in month four.

Fig. 1 · Four phases, four gates, two clean exits.

Phase two: the diagnostic (days 1 to 30)

The diagnostic is the same 30 days I would run in any turnaround, whether I was a full-time hire or a fractional. It is billed separately as a fixed fee for one reason: the client should be able to end the engagement at day 30 with a diagnostic in hand and walk away without owing anything else. Structuring it that way keeps both parties honest.

During the diagnostic I walk every unit on a working shift, read 90 days of daily P&L line by line, and interview every general manager about the decision rights they actually hold versus the ones on paper. I do not change SOPs, menus, or people. I do not build dashboards. The output is a written diagnostic that lands in the founder's inbox on day 30, with three parts:

What the operating problem actually is, in plain language, one paragraph.
The recommended sequence of fixes, in order, with the expected margin impact of each. Usually 4 to 7 items.
The exit criteria, defined up front. What has to be true at the end of the engagement for both of us to agree the work is done.

The diagnostic is the most useful document in the whole engagement, because it is the artifact both sides can point at when the work gets messy in month four. If the founder ever asks in month five "why are we doing this instead of that," the answer is on page one of the diagnostic. If I ever quietly drift into scope creep, the diagnostic is where I catch myself.

Phase three: execution (days 31 to 210)

Execution is the working phase. This is where the fractional actually earns the retainer. The rhythm is simple and it does not change from month to month:

Onsite two days a week, in the same two days

Same days every week. Predictability matters more than volume. The general managers know that Tuesday and Thursday are the days the operator is in the building, and they schedule the work that needs my involvement around it. Fractional operators who float in on random days do a fraction of the work with twice the disruption.

Weekly standing agenda, weekly written note

Monday morning: 45-minute P&L review with each general manager. Wednesday afternoon: 60-minute regional operating review with all managers in the room. Friday: I send a written progress note to the founder, no longer than one page, covering what moved this week, what did not, and the one decision I need from them in the coming week. The Friday note is the single most important habit in the engagement.

Biweekly deliverable against the diagnostic

Every second Friday, the written note also includes a status against each item in the day 30 diagnostic. Green, yellow, red, with one line of commentary. This is the thing that keeps the engagement anchored. It is very hard to drift when there is a written scorecard against the original scope going into the founder's inbox 12 times a quarter.

The Friday note is not a status update. It is the artifact the engagement is built on. Skip it for two weeks and you will feel the founder start to lose confidence, even if the numbers are moving.

Two exit ramps, always visible

At every monthly checkpoint I remind the founder that the 30-day exit ramp is still open. Not because I want them to take it, but because they need to know they can. A fractional engagement where the client cannot leave becomes a hostage situation for both parties. Naming the exit every month keeps the relationship healthy.

Phase four: the handoff (days 150 to 240)

The handoff is the phase most fractionals fumble. They treat it as a sprint at the end. It is not a sprint. It is a slow, deliberate transfer that starts on day one and finishes on day 240.

Every dashboard, standing meeting, and SOP I build is named to a person on the client team from the moment it is created. Not "operations." A person. The dashboard has an owner. The Monday P&L review has an owner. The vendor scorecard has an owner. On day one nobody is running these things because they do not exist yet. As they get built, the internal owner is already listed on them.

The runbook

By day 210 there is a written runbook the internal owner can operate the business from. Not a strategy document. An instruction manual. Where the dashboards live, who has access to what, which vendors are on which cadence, what the Monday P&L review agenda looks like, what to do if a general manager quits, what to do if a location fails a health inspection. Boring and specific.

The silent seat

In the final 60 days I attend the standing meetings but I do not run them. The internal owner runs them. I sit in the room. If the meeting fails without me speaking, we are not ready to hand off. If it runs cleanly, we are. Most weeks it runs cleanly. Some weeks it does not, and we push the handoff out two weeks. That is a normal and healthy conversation.

The final review

The last day is a founder review. Numbers versus the diagnostic. What we did. What we did not do and why. What I would do differently. What I recommend for the next 12 months. Signed handoff to the internal owner. Then I leave clean.

The 90-day post-exit checkpoint

Ninety days after exit I do one 60-minute call with the founder and the internal owner. This is included in the original scope. Its job is to catch decay early. Most turnaround gains that unwind, unwind in the first 90 days after the operator leaves, and a single call at day 90 is enough to name the drift before it becomes irreversible.

Nine times out of ten this call is uneventful. The occasional tenth time it is where the operator earns their reputation, because I can say plainly "the Monday review has moved to a Tuesday and dropped to 30 minutes, and that is why the labor variance is back." Small signal, large consequence.

What good client behavior looks like

Fractional engagements are not one-sided. The best ones happen when the client shows up in specific ways. Three that matter most:

Real authority for the length of the engagement. Not just in the scope document. In the room. When a general manager tests the authority by escalating over the operator's head to the founder, the founder sends them back to the operator. Every time.
Attendance at the weekly standing meeting. Not to run it. To be seen. The founder in the room every week signals that the engagement is real. The founder skipping three weeks in a row signals the opposite, and the whole organization reads it.
No shadow decision process. The founder is not running a parallel operations discussion with someone else on the side. If they lose confidence, they say so directly and either recommit or use the exit ramp. What they do not do is quietly hedge.

Founders who show up this way get the full return on the engagement. Founders who do not, do not. Both sides usually know inside the first 60 days which one this is going to be.

Why any of this matters

The reason to structure a fractional turnaround this way is not process for its own sake. It is that turnarounds are the highest-stakes operating work a business does, and they are usually happening while the founder is exhausted and the balance sheet is thin. Ambiguity is not a luxury either side can afford. The one-page scope, the day 30 exit ramp, the Friday note, the named internal owner: these are not bureaucracy. They are the shape that lets the actual work of running the business proceed while both sides trust each other.

Do the boring things at the start. The interesting things become possible.

Considering a fractional turnaround?

I take on a small number of fractional turnaround engagements each year, typically restaurant and hospitality groups in the $10M to $60M revenue range. If the shape above looks like what you need, I am happy to book a 60-minute discovery call.

Get in touch

Questions people ask

What is a fractional operator turnaround engagement?

A fractional operator turnaround engagement is a fixed-scope, fixed-duration project where a senior operations executive works inside a business at part-time or interim depth to restore profitability. Typical duration is 6 to 12 months. The operator carries real authority during the engagement and hands the work back to a named internal owner at exit. It is distinct from advisory work because the operator actually runs pieces of the business, not just recommends changes.

How is a fractional turnaround different from a consulting engagement?

A consulting engagement produces recommendations. A fractional turnaround produces changed numbers. The consultant hands over a slide deck. The fractional operator holds the pen on the schedule, the P&L review, and the vendor conversation. The client is not paying for analysis. They are paying for someone who will sit in the seat, make the calls, and be accountable for the operating result at the end of the quarter.

How much does a fractional operator turnaround cost?

A fractional turnaround engagement for a $10M to $60M multi-unit operation typically ranges from $12K to $28K per month for 6 to 12 months, with a diagnostic phase billed as a fixed fee separately. The right way to price it is against the size of the operating result the engagement is expected to produce, not against hourly rate. A turnaround that recovers $3M of operating profit is not a $50K project even if it takes 200 hours of the operator's time.

What does a good client look like in a fractional engagement?

A good client gives the operator real authority for the length of the engagement, does not renegotiate the scope every two weeks, shows up to the standing weekly review, and does not run a shadow decision process behind the operator. Bad clients treat the fractional as an advisor they can override, which produces the worst of both worlds: the operator's time without the operator's authority.

How does a fractional operator hand off the work at the end?

The handoff starts on day one, not day 240. Every dashboard, standing meeting, and SOP the operator builds is named to a person on the client team from the moment it is created. The last 60 days of the engagement are a formal transfer: the internal owner runs the meeting, the operator sits in the room but does not speak. If the operator has to keep speaking, the handoff is not done.

How long should a fractional turnaround engagement run?

For a 3 to 5 unit restaurant or hospitality group, 9 months is the honest floor and 12 months is common. Anything shorter than 6 months is either not a turnaround or it is going to unwind within a quarter after the operator leaves. Anything longer than 15 months means the operator has quietly become a permanent hire, which is a different arrangement and should be renegotiated as such.

When should you bring in a fractional operator instead of hiring full-time?

Bring in a fractional operator when the work is bounded, the timeline is fixed, and the skill required for the fix is different from the skill required to run the business afterward. Most turnarounds fit that shape. A full-time hire makes sense when the operating problem is permanent, not situational. Hiring a permanent COO to fix a temporary problem creates a role you will not need in 18 months and a person you cannot easily part with.