Photo by Amar Preciado on Pexels
Order the same dish on a Tuesday and a Saturday at most restaurants and you'll get two different plates. Same menu, same price, different amount of protein, different sauce, different garnish. Nobody did anything wrong. The recipe just lives in three cooks' hands, and every pair of hands has an opinion.
That's the gap a recipe sheet template closes. One page per dish, weighed rather than guessed, with the yield, the portion, the method, and the plate cost on it, so the version that goes out the window is the version you signed off on rather than the version the cook remembers.
Below is what belongs on the sheet, how to build one in about 15 minutes a dish, and the two mistakes that make kitchens abandon them. There's a free fillable version at the bottom you can complete on this page and save as a PDF, plus a CSV if you'd rather keep them in a spreadsheet.
What a Recipe Sheet Is (and Isn't)
A recipe sheet, also called a standardized recipe or a spec sheet, is the single written version of a dish that every cook works from. It's not a cookbook recipe. A cookbook recipe teaches somebody to cook a dish once, and it's allowed to say "season to taste." A recipe sheet has to produce the same plate 400 times in a row across three cooks who have never met.
The practical difference shows up in the language. A cookbook says "a splash of cream." A recipe sheet says "2 oz heavy cream, weighed." A cookbook says "cook until done." A recipe sheet says what done looks like, in a way a cook on their second week can verify without calling anyone over.
Recipe sheet language
- "6 oz protein, weighed, portioned at prep"
- "2 oz sauce, ladled with the 2 oz black ladle"
- "Sear 3 minutes per side, no movement in the pan"
- "Yield 4 qt / 32 portions at 4 oz"
- "Rests 5 minutes on the rack before plating"
Cookbook language
- "A generous portion of protein"
- "Sauce to taste"
- "Sear until nicely browned"
- "Serves 4 to 6"
- "Let rest a bit"
Everything on the right is fine at home and useless on a line. Every vague word is a decision you've handed to whoever is on the station tonight, and the whole point of a spec is that those decisions get made once, by you, in daylight.
The 9 Fields Every Recipe Sheet Needs
Nine fields cover a full spec. Anything past these starts costing you the thing that matters most, which is whether a cook will actually read the page mid-service.
| Field | What goes in it | Why it earns the space |
|---|---|---|
| 1. Dish & section | Menu name, section, station that owns it, version date | Tells you instantly whether this is the current sheet or a ghost from two menus ago. |
| 2. Yield & portion | Total batch yield, portion size, number of portions | The number every other line depends on. Without it the cost is fiction. |
| 3. Ingredients | Each item with quantity by weight, plus unit cost and extended cost | The heart of the sheet. Weight, not "a handful." |
| 4. Method | Numbered steps, one action per step, times and visual cues | Numbered so a cook can find their place after getting pulled away. |
| 5. Equipment | Pan sizes, hotel pans, ladle and scoop sizes by color or number | "The 2 oz black ladle" removes a whole category of drift. |
| 6. Plating | Plate or bowl, build order, garnish, and a photo | The photo does more work than the paragraph. Always include one. |
| 7. Allergens | Allergens present, and which ones are hidden in a sub-recipe | The hidden ones are what get missed: fish sauce, butter in a stock, nuts in an oil. |
| 8. Storage | Container, labeling, shelf life, and how it's reheated or held | A dish made perfectly and stored badly is still a dish you're throwing out. |
| 9. Cost | Plate cost, menu price, food-cost percentage | Turns the sheet from a training doc into a margin tool. |
Field 6 is the one people skip and the one that pays for the whole exercise. A photo of the finished plate, taken on your actual plateware under your actual lights, settles more arguments than any written description will. If you're building sheets digitally, the photo is free. If you're printing, print it in color anyway.
How to Write One in 15 Minutes
The mistake almost every kitchen makes is writing recipe sheets at a desk. You sit down with a legal pad, write out the dish from memory, and produce a document that describes a version of the dish nobody actually cooks. Then you wonder why nobody follows it.
Write it while you cook it, at full batch size, and record what happens rather than what's supposed to happen. That means a scale on the bench and a pen in your apron.
- Weigh everything as it goes in. Including the oil, the salt, and the acid at the end. The seasoning is usually where the plate-to-plate variance lives.
- Weigh the finished yield. Not the raw total. Cooking loss is real, and yield after cooking is the only number that makes portioning honest.
- Divide yield by portions to get the true portion size, then write the tool that delivers it. A number is good, a number plus a named ladle is better.
- Number the method, one action per step. Short lines. A cook reads this standing up with wet hands.
- Photograph the finished plate on your plateware.
- Hand it to a cook who has never made the dish and watch them build it without answering questions.
That last step is the whole test, and it's the one everybody skips. Every question the cook asks is a missing line on your sheet. Write it down, fix the sheet, and move on. Two rounds of that and the document is finished for years.
Worked example: braised short rib, spec vs. reality
- Written from memory: "8 lb short rib, braise until tender, portion 4 per pan." Cost line assumes 8 lb yields 16 portions.
- Written while cooking: 8 lb raw trims to 6.4 lb, braises down to 4.9 lb finished. At a 5 oz portion that's 15 portions, not 16.
- What it changes: Plate cost was calculated on a yield that never existed, so every short rib sold has been carrying a hidden cost gap all year.
- The fix: One line on the sheet, "raw 8 lb / trimmed 6.4 lb / cooked 4.9 lb / 15 portions at 5 oz," and the number is true forever.
Why the Cost Line Belongs on the Sheet
Plenty of kitchens keep recipes in one place and costs in another. That split is why food cost meetings feel like archaeology. The spec and the cost are the same document, because the cost is only accurate if the spec is being followed.
Plate cost ÷ menu price = food-cost percentage for that dish
Put the three numbers at the bottom of every sheet: plate cost, menu price, and the resulting percentage. Now the sheet answers two questions at once. A cook uses the top of the page and you use the bottom of it, and when a supplier raises a price you know exactly which dishes just moved.
Reprice quarterly at minimum. A cost line from two years ago isn't a number, it's a memory. If you want the full method behind that math, we walk through it in why recipe costing is the habit profitable kitchens never skip, and the pricing side lives in the menu pricing formula most restaurants get wrong.
There's a waste angle too. Most over-portioning is invisible because it happens a couple of ounces at a time across hundreds of covers. A spec with a named portioning tool is the cheapest control you have on it, which is why specs show up so heavily in our breakdown of restaurant food waste.
Getting Cooks to Actually Use Them
Two things kill recipe sheets. The first is location: sheets in a binder in the office are sheets nobody reads. Put them at the station, in a sleeve, one page per dish, and the friction disappears.
The second is authorship. A sheet that arrives laminated from management gets worked around. A sheet your cooks helped write gets defended, because now it's their spec and they'll tell the new guy he's doing it wrong. Build the first drafts with the person who cooks the dish most, and let them argue about the method before you sign it.
After that, three habits keep them alive. Train new hires directly from the sheets rather than by shadowing, which is the fastest path to a productive cook and the core of good restaurant staff training. Spec-check plates during service, quietly and often, comparing what's on the pass to the photo. And keep exactly one master version, edited in one place, with a version date on it. Two versions of the same dish floating around a kitchen is worse than none.
This is the same discipline that turns any repeated task into a system rather than a habit, which is what standard operating procedures are for. And once you have 40 sheets, paper starts working against you, which is the argument for a digital recipe book your whole kitchen can pull up in a second. For broader operational and menu resources, the National Restaurant Association is a reasonable place to start.
The Free Recipe Sheet Template
Here's the full spec sheet. Fill it in on this page and hit Save as PDF and your browser exports just the sheet, ready to slide into a station sleeve. Or print blanks and build your specs by hand as you cook them.
Standardized Recipe Sheet
This is a blank template to standardize your own recipes, not a complete or compliance document. You are responsible for the accuracy of what you enter, including allergen and storage information. Confirm allergen handling and any food-safety requirements for your operation with your local health department.
1. Dish & section
2. Yield & portion
3. Ingredients
| Ingredient | Qty (weight) | Unit cost | Ext. cost |
|---|---|---|---|
4. Method (numbered, one action per step)
5. Equipment
6. Plating & garnish
7. Allergens
8. Storage & holding
9. Cost
Prefer a spreadsheet? Download the recipe sheet template as a CSV. It opens in Excel, Numbers, or Google Sheets, comes pre-filled with a worked example, and has the cost formulas noted in the file so you can build your whole spec book in one place.
If you want your specs on the station instead of in a binder, with the current version, the plate photo, and a cost line that updates when your prices move, that's what we build. Let's talk about what that would look like in your kitchen.
Frequently Asked Questions
What is a recipe sheet?
A recipe sheet, sometimes called a standardized recipe or a spec sheet, is the single written version of a dish that every cook on every shift works from. It records the exact ingredients and quantities, the yield and portion size, the method in numbered steps, the plating and garnish, the allergens, and the plate cost. It is not a cookbook recipe. A cookbook recipe teaches someone how to cook a dish once. A recipe sheet makes the same dish come out the same way 400 times in a row, no matter who is on the station.
What should be included in a recipe sheet template?
Nine fields cover it: dish name and menu section, yield and portion size, an ingredient table with quantities by weight, prep method in numbered steps, equipment and pan sizes, plating and garnish specs, allergens, storage and shelf life, and the plate cost with its target food-cost percentage. Add a photo of the finished plate and a version date. If a field will not change how the dish comes out or what it costs, leave it off. Every extra line is a line a cook has to read at 7:30 on a Friday.
How do you write a standardized recipe for a restaurant?
Make the dish once, at full batch size, and write down what actually happens rather than what you think happens. Weigh every ingredient as it goes in, including the oil and the salt. Weigh the finished yield, then divide by portions to get true portion size. Photograph the plate. Then hand the sheet to a cook who has never made the dish and watch them build it without asking a question. Every question they ask is a missing line on the sheet. Fifteen minutes per dish, done properly, and it holds for years.
Why should recipes be standardized in a restaurant?
Three reasons, and only one of them is consistency. First, the guest gets the same dish every visit, which is the entire basis of a repeat customer. Second, your food cost becomes knowable, because a plate cost calculated from a spec is meaningless if the cook is pouring by feel. Third, standardized recipes are the fastest training tool in the building. A new cook with good sheets is productive in days rather than weeks, and your best cook stops being the only person who knows how anything is made.
Should recipe sheets use weight or volume?
Weight, for anything that matters. Volume measurements drift because a packed cup and a loose cup are not the same cup, and two cooks scooping flour will give you two different doughs. Weight is repeatable, faster to scale up or down, and it is the only way a plate cost stays honest. Keep volume for liquids where a measured pour is genuinely quicker, and note the unit clearly on the sheet so nobody has to guess whether ounces means fluid or weight.
How often should recipe sheets be updated?
Update the method whenever the dish changes, and reprice the cost line every quarter at minimum. Ingredient prices move constantly, and a recipe sheet with a two-year-old cost line is telling you a comfortable story rather than the truth. Put a version date on every sheet, keep one master copy that gets edited, and pull the old printouts out of the binder the day the new one goes in. Two versions of the same dish floating around a kitchen is worse than none.
How do you get cooks to actually use recipe sheets?
Make them faster to use than to ignore. Sheets belong at the station in a sleeve, not in a binder in the office. One page per dish, a photo of the finished plate, and the ingredient table where the eye lands first. Then train with them, spec-check plates against them during service, and involve your cooks in writing them. A cook who helped write the sheet defends it. A cook who was handed a laminated page by management works around it.