Knowledge base & SOPs
Restaurant Menu Documentation for Staff
Menu documentation should answer the questions staff actually get under pressure. For servers and bartenders: what is this dish in one sentence, what are prestige ingredients, what pairs or upsells fit naturally, how do you pronounce it, what are the top three allergy questions, and what do you do when the kitchen 86s it.
For cooks: builds, hold times, finish cues, plateware, and batch links. For bartenders: spec, ice, glassware, garnish, and prep ties. Clutter happens when you force FOH storytelling and BOH weights on the same page.
Define the update ritual. When culinary changes a build, the spec updates first, then the menu doc, then the floor huddle talking points, then the LMS micro lesson if needed. Stale menu docs erode trust faster than a blank page.
Allergen questions deserve approved language, not improvisation. Scripts reduce liability and speed up accurate answers.
Restaurant Codex Knowledge Base plus Codex Bot lets teams search approved content on the line. Grounded answers beat group chat folklore when the dining room is loud.
Related question
How do you keep allergen information accurate in recipes?Tag at the ingredient, govern supplier changes, document cross contact, train approved FOH scripts, and close the loop when specs move.