AI in a Restaurant Kitchen and Office

This is how I’d set up an AI assistant for an independent restaurant, the kind where the owner works the line on busy nights and does the paperwork after close.

Nobody in a kitchen has time to learn a new system. So I wouldn’t start with anything fancy. I’d start with the writing and arithmetic that already happens every week and usually happens at midnight.

Get the recipes written down

Most restaurants run on recipes that live in the chef’s head or on a stained sheet taped inside a cabinet. That’s the first thing I’d fix, because everything else depends on it.

The chef talks through a dish, or hands over a rough card, and the assistant turns it into a standard recipe format: yield, ingredients by weight, method, plating, holding time, and the station it belongs to. The chef corrects it. Once it’s right, it goes into the restaurant’s reference file.

With standard recipes in place, scaling stops being a mental math exercise during a rush. “Scale the braised short rib to 40 portions and give me the order quantities by case size” becomes a quick request. The assistant does the arithmetic; the chef looks it over before anyone orders.

Prep lists and ordering notes

A prep list is just par levels minus what’s on hand, sorted by station and priority. That’s a good job for an assistant.

At the end of the night, a cook does a quick count and types or dictates what’s left. The assistant compares it to pars and produces tomorrow’s prep list, grouped by station, with the long-lead items first. I’d write a short instruction for it:

Use the par sheet. List items below par with the quantity needed. Put anything that takes more than two hours, like stocks, braises, and doughs, at the top. Don’t invent items that aren’t on the par sheet.

Ordering notes work the same way. The assistant can turn a count into a draft order for each vendor, organized the way that vendor’s sheet is organized. The owner still places the order, because the owner knows the fish delivery is short this week and the produce price jumped.

Training cards for new cooks

Line cooks come and go. Every new one needs to learn the same things: station setup, the plates they’ll make, what “86” means in this kitchen, and who to ask.

From the standard recipes, the assistant can produce a one-page card for each station. Mise en place list, the four or five plates that station owns with a photo spot and key steps, and the two mistakes the chef sees most often. Laminated and hung at the station, it’s faster than asking the sous chef the same question for the tenth time.

It can also draft short quizzes for the front of house: what’s in the dishes, which items can be made gluten-free, how to describe the special. Servers who know the menu sell more of it and make fewer mistakes at the table.

Menu descriptions and review replies

Writing menu copy is a chore most owners put off. An assistant can draft descriptions from the recipe in the restaurant’s own tone, short and specific, with the main ingredients and the cooking method. The owner picks and edits.

For reviews, I’d give it the same rules I’d give a new manager. Thank the guest. Respond to the specific thing they mentioned. Don’t argue. Don’t offer comps in public. And if a review mentions illness, an allergic reaction, or an injury, don’t reply at all; send it to the owner.

Where to be careful

This is the section that matters most in a restaurant.

Allergens are not a writing task. An assistant can format an allergen chart, but it can’t know that the fryer oil is shared or that a sauce base changed suppliers. Every allergen statement on a menu, a training card, or a server’s answer has to be verified by someone who knows what’s actually in the food. I’d put that rule at the top of the assistant’s instructions and on the wall.

Food safety stays with people and the code. Holding temperatures, cooling times, date labeling, and sanitizing procedures come from the health code and the restaurant’s own food safety plan. The assistant can help format a cooling log or a cleaning checklist from that plan. It should never be the source of a temperature or a time.

A few more lines I’d hold:

• Recipes, costs, and vendor pricing are business information. Decide which tool is approved and keep those files there.
• Staff schedules involve personal details and availability. Draft the schedule structure, but keep names and phone numbers out of tools that aren’t approved for them.
• Scaled recipes and order quantities get a human check before anyone cooks or buys.

Where I’d start

If I were sitting down with a restaurant owner, I’d start with two things: writing down the recipes the kitchen depends on, and building the nightly prep list routine. The first protects the restaurant if the chef leaves. The second saves time every single day. Training cards and menu copy follow naturally once the recipes are in good shape.