Kitchen Operations
Kitchen Station Responsibility Matrix for Small Teams
Build a kitchen station responsibility matrix: who owns each station, opening and closing tasks, temperature checks and sign-offs, days off and cross-training.
The classic brigade has a name for everyone: saucier, poissonnier, garde manger, entremetier. Each one knows exactly what belongs to them. Very few kitchens work like that now. A typical independent restaurant or franchise unit runs with four to eight cooks, half of them part-time, most of them moving between two or three stations in a week.
That flexibility is useful, but it creates a gap. When the fryer oil was not changed, or the reach-in on the cold station sat at 46°F all afternoon, the honest answer to "whose job was that?" is often "everyone's", which means nobody's. A responsibility matrix closes that gap. It is one page that says, for every station and every recurring task, who owns it on each shift.
What "owning" a station means
Ownership is narrower than "works there." The owner of a station for a shift is the one person who:
- Sets it up to par before service
- Does its temperature checks and signs for them
- Keeps it clean and stocked during service
- Breaks it down, labels, stores and cleans at close
- Tells the manager when something on it is broken, short or out of temperature
Other people can help. Ownership does not move because someone else touched the station. If the grill cook leaves at 9 and the sauté cook covers the grill for the last hour, the closing tasks for the grill need a named owner on the matrix, not an assumption.
Start with a list of stations and fixed points
Write down every station, including the ones that are not cooking stations. In a mid-sized casual restaurant, the list might be:
- Grill
- Sauté or wok
- Fry
- Cold and salads (garde manger, if you like the old word)
- Pastry and dessert
- Prep
- Dish
- Walk-in and receiving
- Expo or pass
Then list the fixed points that are not stations but need an owner: the opening temperature round, receiving, the closing walk-through, the fryer oil change, the sanitizer bucket checks, the hood filter wash. These tend to fall through the cracks precisely because they are not attached to a place.
A sample matrix
Here is what a matrix looks like for a kitchen of six on a typical weekday. Names are placeholders. Use roles if names change often, but names are better, because a role does not answer a phone.
| Station or task | Opening owner (AM) | Closing owner (PM) | Temp checks | Signs off at close |
|---|---|---|---|---|
| Grill | Maria | Dev | Grill lowboy, twice per shift | Dev |
| Sauté | Maria | Sam | Sauté reach-in, twice per shift | Sam |
| Fry | Prep cook covers until 11 | Sam | Oil quality check at open | Sam |
| Cold station | Lee | Jo | Cold well and reach-in, every 4 hours | Jo |
| Pastry | Lee | Jo | Pastry fridge, at open and close | Jo |
| Prep | Prep cook | n/a | Cooling log for all batches | Prep cook (by 3 pm) |
| Walk-in and freezer | Opening manager | Closing manager | At open and close | Closing manager |
| Receiving | Opening manager, or prep cook if delegated | n/a | Probe each delivery | Whoever receives |
| Dish | Dishwasher | Dishwasher | Final rinse or sanitizer test each shift | Dishwasher |
| Hood filters | n/a | Dev (grill), Sam (fry) | n/a | Closing manager checks |
| Closing walk-through | n/a | Closing manager | n/a | Closing manager |
Some things to notice. Fry has no cook of its own in the morning, so the matrix says who covers it until the second cook arrives. Prep has no closing owner because prep finishes by 3 pm, but its cooling log has an end time. The walk-in belongs to managers, not cooks, because it is the one place everyone uses and nobody tidies.
Keep the matrix to one page. If it needs two, you are probably listing tasks that belong on the station checklists rather than ownership.
Temperature checks and sign-offs
The matrix says who checks; the station checklist says what and when. Splitting it this way keeps the matrix readable. A cook should be able to look at it and see "the cold well readings are mine today," then open the checklist to see which units and which times.
Signing off matters more than most teams think. A sign-off at close is the cook saying the station is broken down, food is labeled and stored, and temperatures are logged. If an inspector or a manager finds a problem the next morning, there is a name to talk to. That is not about blame. It is the only way to find out whether the problem was a skipped step, a misunderstood step, or a broken fridge.
The most common failure is the pre-signed log: all four temperature readings written at 10 pm in the same pen. If you see it, deal with the cause (often too many checks for one person at a busy time) rather than just the person. Our article on stopping pencil-whipped checklists goes into this, and the food temperature log template is a good base for the station sheets.
Shift overlaps
Overlaps are where ownership gets lost. The morning cook leaves at 3, the evening cook arrives at 2:30, and the station is "handed over" with a nod.
Make the handover a short, specific moment. The outgoing owner tells the incoming one what is prepped, what is low, anything 86'd, and any equipment issue. The incoming cook checks the reach-in temperature and initials the handover line. Then ownership has moved, on paper, at a known time. If something was wrong before 3, it was the morning cook's; after, the evening cook's. The shift handover template gives a format for this.
Without that, the evening cook inherits a fridge at 45°F and has no way of knowing if it has been like that for twenty minutes or four hours.
Days off, sick calls and the person who always closes
Two problems show up within a month of using a matrix.
The first is days off. If the matrix only has the "usual" names, it is wrong two days a week. Either make it weekly (built with the schedule, so Thursday's matrix reflects who is actually on Thursday) or add a "cover" column that names the default backup for each station. The weekly version is more work and more accurate. For most kitchens, building it alongside the schedule each week takes ten minutes once you have done it a few times.
The second is the person who always closes. Every kitchen has one: reliable, fast, and quietly doing the closing tasks for three stations because it is easier than chasing people. When they leave or go on vacation, nobody else knows how to close. The matrix makes that visible. If one name appears in the closing column more than twice as often as anyone else, you have a dependency, not a system.
Cross-training without losing ownership
Cross-training is the reason small kitchens survive sick calls. It also makes ownership fuzzy if you are not careful. The fix is to separate "can work this station" from "owns this station today."
Keep a simple skills grid alongside the matrix: names down the side, stations across the top, and a mark for each person who has been trained and signed off to run a station alone. Then, when you build the weekly matrix, you choose owners only from people marked as trained for that station. Someone learning the grill can work it, but the trained cook beside them owns it until they are signed off.
A reasonable target for a kitchen of six to eight is that every station has at least two people trained to own it, and every cook can own at least two stations. That is usually enough to cover one sick call and one day off on the same shift without the manager stepping onto the line.
Making it stick
Post the matrix where people actually look, next to the schedule or the pass. Review it when the menu changes, when equipment moves, or when someone leaves. Check the sign-offs at the end of the day for the first few weeks; once the team sees that missed sign-offs get noticed, they stop being missed. If you run several sites, a standard station list across them makes comparison possible, even if each site's names are different.
The matrix is not paperwork for its own sake. It is the answer to the question every manager asks at least once a week, and it is better to have answered it in advance.