Twenty-something. Summer job. I worked a real kitchen for about ten weeks. I thought the chef was the impressive one. Calling tickets. Plating the protein. Running the line. Watching him work felt like watching someone conduct.
By August the person who had impressed me was the sous chef.
She was not in the spotlight. She was not plating. She was at the prep table at two in the afternoon, six hours before service, looking at the next three days of reservations and saying out loud. “We will need fifty pounds of onions diced by Thursday, twenty caramelized by Friday, the demi started Wednesday afternoon.”
None of that sounded like leadership. It sounded like inventory.
But every time service started smooth, it was because she had made those calls two days earlier. And every time service started in chaos, it was because she had missed one.
She was not routing tickets. She was not translating direction. She was forecasting. That was the move.
If your Pass is running on adrenaline, you don’t have a Pass. You have an air-traffic controller in the wrong job.
The station you forgot to design
Quick context. We have been talking about the Station Plan. It is the architecture of a business as a working kitchen. Chef at the Hub making the calls. Agents on the Line doing the labor. The Pass in between, routing work from one station to the next.
A few weeks back there was a piece called The Pass. All about the four jobs that station does. Routes work between agents. Translates direction from the Chef down. Translates status from agents back up. Sequences dependencies during service. Four functions. The orchestrator is the reason the Chef has any leverage at all.
Here’s the thing. There is a fifth function hiding inside the fourth one, and almost nobody has named it.
Sequencing dependencies during the rush is air traffic control. You react to what is already on the line. You shuffle. You catch.
Forecasting dependencies before the rush is a different job entirely. That is the prep call. It is the difference between an orchestrator who keeps the kitchen from crashing and an orchestrator who keeps the kitchen from ever needing to be saved.
Most small-business orchestrators are stuck in the first job. They are routing live. They are putting out fires. They are making the schedule work in the moment. They are never up two days. The kitchen survives every shift, and nobody is asking why every shift feels like survival.
Right? Same problem the sous chef would have if she only showed up at six. Different category of work entirely.
What forecasting actually sounds like
I keep thinking about what a prep call sounds like in an actual operating business right now, with AI in the mix. It does not sound technical. It sounds like inventory talk for a kitchen that has not been built yet.
It sounds like “we need this customer dataset cleaned by Tuesday because Thursday’s new agent run depends on it.”
It sounds like “we need to start collecting three good examples of this output by Friday, because by month-end we are going to hit volume and the model will need them.”
It sounds like “the renewal-season prompt has to be rewritten and tested this week, because in three weeks every producer is going to be running it twenty times a day and the version we have now produces generic.”
That is the prep call. Calling for ingredients the kitchen does not even know it is going to need yet.
Most ops managers are not making it. Most ops managers are too busy answering the question what is broken right now to answer the question what is going to be broken in three weeks if nobody starts cooking the prep today.
That is the fifth function. That is the leadership move. And it does not happen in the rush. It happens at two in the afternoon at a prep table, six hours before the rush, with a calendar open and a piece of paper.
Why yours is missing
Two reasons. Both are design problems, not effort problems.
One. The Pass was never designed. That is the diagnosis we ran in the original Pass episode. If the orchestrator is reacting full-time, she has no oxygen for forecasting. She is too busy translating today’s edge case to look at next week’s volume curve. The Pass does not get to forecast until the routine routing is documented enough that someone else can run it. This part is on the Pass and on whoever built the Pass.
Two. The Chef has not given the Pass a far-enough horizon. This part is on the Chef.
Most operators tell their orchestrator what is broken this week. They are not telling the orchestrator what we are going to be cooking in four weeks. When the Chef will not look forward, the Pass cannot either. The Pass can only forecast against a menu. If the Chef has not named the menu past Friday, the Pass is going to live in this Friday’s tickets. That is not the Pass’s failure. That is a Chef who never delivered the four weeks out conversation.
Yeah. The Pass that is on adrenaline is usually downstream of a Chef who is also on adrenaline. The whole system is reacting.
It is not a personality problem. It is not a I’m just not that kind of person problem. It is a calendared conversation that literally did not exist last month and literally exists this month. Once it exists, the Pass has a forward horizon. Before it exists, she does not. Does that make sense?
The dish that gives this away
Here’s the thing. If you want to know whether you have a Pass or an air-traffic controller, do not look at the org chart. Look at the last three weeks of unplanned chaos in your business.
The hire that took three weeks longer than it should have, because nobody started writing the JD until the resignation hit. The new agent that shipped late, because nobody started gathering training examples until the launch was already on the calendar. The renewal season that started rough, because the agency’s intake prompt had not been touched since last year and nobody noticed until the volume actually hit.
Every one of those is a missed prep call. Not a missed routing decision. Not a missed translation. Not a missed sequence. A missed prep call. The thing the Pass should have seen four weeks earlier and called for.
When you see that pattern stacking up across the last three months, you do not have a hiring problem or an AI problem or an intake problem. You have a Pass that is not making the call, because nobody ever gave her the horizon to make it from.
The conversation that changes it
The fix is one conversation, named, on the calendar, every week.
It is not a status meeting. It is not a stand-up. It is not a quarterly review.
It is a thirty-minute conversation between the Chef and whoever is playing the Pass. One agenda item. What is coming in the next four weeks, and what prep has to start now to be ready for it.
Not what shipped last week. Not what is broken today. What is coming, and what we would need to chop now to be ready.
End the meeting with three named prep items. Each one has an owner. Each one has a deadline. Each one is in the Pass’s hand on the way out the door.
Run it again the next week. Pick up the three from last week. Add three more.
By week four you have something most operating businesses in your market do not have. You have an orchestration function that is ahead of the line instead of behind it. Right? Almost nobody around you is running this. The Pass that calls for prep two weeks out is not a common asset. It is a competitive one.
The Monday Move
Open the calendar. Put a thirty-minute meeting on it. Title it Prep Call. Invite you and whoever is playing the Pass in your business. Weekly. Same time. Protected.
One agenda item. What is on the menu in the next four weeks, and what prep has to start now to be ready for it.
Bring a piece of paper. End the meeting with three named prep items. Each one has an owner. Each one has a deadline. Hand them off and go run service.
Do not skip it next week. Do not move it. Do not turn it into a status meeting. Twelve minutes in, when one of you starts saying “and we should also talk about the thing that broke yesterday,” one of you has to say, out loud, “no. That goes somewhere else. This call is about what is coming.”
That single discipline, held for four weeks, is the difference between a Pass that is keeping the kitchen alive and a Pass that is making the kitchen impossible to surprise.
So.
The chef gets the credit. The sous chef makes the credit possible.
You have already promoted someone into the Pass seat. Almost every operator has. The question is whether you have given the Pass the forty-eight-hour horizon she needs, or whether you have left her routing tickets in the moment and called it orchestration.
If your Pass is running on adrenaline, you don’t have a Pass. You have an air-traffic controller in the wrong job. And you are going to lose her by Q4, because adrenaline does not scale and nobody can live there forever.
Put the Prep Call on the calendar this week. Then watch what happens.
Original framework. Distilled from client work.
Framework spine: The Station Plan. The Pass as a designed station with a forward horizon. Read the full framework. Companion piece: The Pass.
~ source material · Original framework. Distilled from client work.
