

A well-written recipe has seven parts: a specific title, a short headnote, a yield and time, an ingredient list in the order of use, numbered steps that start with verbs, doneness cues you can see or measure, and storage notes. Add credit for wherever the dish came from. This guide covers each part in order, with examples you can copy.
The standard format is not fussy tradition. It exists so that a stranger, in a kitchen you have never seen, can get the result you got.
RecipeforkHelp Your Recipes Travel FurtherShare recipe adaptations on RecipeFork, where cooks can add their own twists while crediting the original source.Explore RecipeForkMost bad recipes are not bad dishes. The cook who wrote them just knew things the page never said. “Cook until done” means something to the person who has made the dish fifty times. It means nothing to someone making it for the first time.
That gap is the whole job. Professional kitchens solved it with what they call a standardized recipe. Nevada’s university extension describes it as a tool for consistency across different cooks and environments, controlling quality, yield and cost. A New York State education department guide says these recipes have been tested, modified and retested several times so they produce the same results and yield every time.
You don’t need a commercial kitchen to borrow the idea. You need to write as if someone else will cook your dish without you in the room, because someone will.
Here is the order most readers expect. Break it, and people hunt for the part they need with flour on their hands.
| Part | What it does | Typical length |
|---|---|---|
| Title | Names the dish and the one thing that makes it distinct | 3 to 8 words |
| Headnote | Tells the cook why this version, and what to expect | 1 to 3 sentences |
| Yield and time | Sets expectations before shopping | One line each |
| Ingredients | Everything needed, in order of use | One line per item |
| Steps | The method, numbered | 4 to 12 steps |
| Notes | Substitutions, storage, make-ahead | 2 to 5 lines |
A textbook chapter on standardized recipes lists nearly the same core elements: the name, total yield, portion size, ingredient quantities and preparation procedures. Home recipes can be lighter, but the skeleton is the same.
Name the dish plainly and add the hook. “Harissa-Roasted Cauliflower with White Bean Cream” tells you the main ingredient, the flavor and the texture in one line. You can see it written out in full on this harissa cauliflower recipe. “Grandma’s Special” tells a stranger nothing.
Two or three sentences. Say what the dish tastes like, when you make it, and what could go wrong. Do not write a memoir. If the story is good, it can sit below the recipe, where the cook can skip it with a messy thumb.
Give the yield as a number plus a unit: “Serves 4” or “Makes 12 muffins.” Then give prep time and cook time separately. Be honest. If dicing three onions takes you 15 minutes, don’t write “5 minutes prep” because it looks better.
Yield also matters for anyone who wants to scale the recipe. The textbook chapter above explains that adjusting a recipe starts by noting the original yield, so your number is the starting point for every conversion.
The ingredient list does more work than any other part. Get it right and half your clarity problems vanish.
List ingredients in the order the steps use them. A cook reading down the list should meet them in the same sequence as the method. Group them if the dish has parts: “For the sauce,” “For the chicken.”
Put the amount first, then the unit, then the ingredient, then the prep. The placement of the comma changes the meaning:
Those are different amounts of walnuts. Pick one and mean it.
A few more habits that save cooks:
Cooking oil for the pan, water for boiling, ice for the bath, the pan size. If it needs to be bought, found or washed, it belongs on the list or in the headnote.
The method is where recipe writing becomes real writing. The rules are simple and strict.
Begin each step with an action: “Heat,” “Whisk,” “Fold.” Readers scan recipes mid-task, and a verb at the front lets them find their place again.
Write “Combine the flour and sugar,” not “Combine the first three ingredients.” Lists get reordered, edited and adapted. Counting breaks the moment anyone changes them.
A numbered step should hold one stage of work, not a dense paragraph with three jobs in it. Short steps also let a cook put the phone down and pick it up again without losing track.
Times vary with stoves, pans and altitude. A cue does not. Compare:
The second version gives a heat level, a range, a motion and an end state. A first-time cook can succeed without guessing.
Heat level (low, medium, medium-high), pan type and size, oven rack position and preheat temperature belong in the steps. “Bake at 400°F on the middle rack in a 9-by-13-inch pan” leaves nothing to chance.
If an ingredient needs prep, make it its own instruction or put it in the ingredient line. “1 cup finely diced carrots” quietly assigns work. Writing “1 cup carrots, finely diced” makes the action clear and visible.
If your recipe involves meat, poultry, eggs, dairy or rice, safety numbers are part of the method, not a footnote.
The U.S. Department of Agriculture’s Food Safety and Inspection Service says bacteria grow rapidly between 40°F and 140°F, and that perishable foods left in that range for more than 2 hours (1 hour above 90°F) should be discarded. Its guidance on cooked leftovers is to refrigerate or freeze them in shallow containers so they cool quickly.
So in a recipe for a casserole or a braise, the last steps should say something like: “Refrigerate leftovers within 2 hours in shallow containers.”
For doneness, give a thermometer number instead of “cook until no longer pink.” The USDA’s safe minimum internal temperature chart lists these, among others:
| Food | Minimum internal temperature |
|---|---|
| Beef, pork, veal and lamb steaks, chops, roasts | 145°F, then rest at least 3 minutes |
| Ground meats | 160°F |
| All poultry, including ground | 165°F |
| Casseroles | 165°F |
If you are publishing a recipe for others, check these numbers against the chart itself, since guidance can be updated. If someone cooking your recipe has a health condition, is pregnant, or is cooking for very young children or older adults, the USDA’s pages are the place to check, and a doctor or dietitian is the person to ask about specific risks.
Here is a typical family-recipe note:
Chicken soup: chicken, veggies, broth, noodles. Simmer until done. Season.
And here is the same dish in standard format.
Weeknight Chicken Noodle Soup
A light, clear soup that comes together in about 45 minutes. Bone-in thighs give the broth body without a long simmer.

Serves: 6 | Prep: 15 minutes | Cook: 30 minutes
Ingredients
Steps
Notes: Refrigerate leftovers within 2 hours in shallow containers, for up to 4 days. The noodles will absorb broth, so add a splash of water when reheating.
The second version is longer, but a stranger can make it. That is the test.
A recipe is not finished when you finish writing it. It is finished when someone else cooks it.
Most recipes are adapted from someone else’s. That’s normal, and cooking has always worked that way. The question is how to handle it fairly.
On the legal side, the U.S. Copyright Office’s circular on works not protected by copyright says that a mere list of ingredients is not protected, though substantial literary expression in a recipe’s text can be. In practice, your own wording, headnotes and photos are yours, and the basic ingredients-and-method of a dish are shared. This is general information, not legal advice. If you are publishing a cookbook commercially or someone is disputing use of their text, a lawyer who handles intellectual property is the right person to ask.
Law is the floor. Credit is the courtesy that makes a recipe community work. If you adapted a dish, say so: “Adapted from my aunt Rosa’s lasagna, with less ricotta and a bechamel layer.” That one line tells the next cook where the dish came from, what you changed and why.

We built RecipeFork around a simple observation: nobody cooks a recipe exactly as written, and the page rarely says what changed. A cook swaps the herbs, halves the sugar, cooks it in a different pan, and the knowledge disappears into a scribble in a margin.
That is why we think about recipes the way developers think about code. A good recipe is a clear starting point. When someone adapts it, the adaptation should be visible, the original should stay credited, and the next cook should be able to see both. We call that forking.
It also changes how we think about writing. If you know your recipe may be adapted, you write the base version more carefully: exact amounts, clear cues, notes on what is flexible and what isn’t. A recipe that explains why you brown the onions first is easier to adapt well than one that only says to do it.
We also think recipe pages should be about the cooking. That is why we have no traditional ads, and why we put the cook’s credit and the recipe’s source in plain view.
— David
If you want a place to put the recipes you’ve written, RecipeFork lets you share them, fork recipes from other cooks with credit to the original, and collect favorites into personal cookbooks. You can browse public cookbooks to see how other home cooks organize and format their recipes, or look at the recipes from the RecipeFork team for examples of the format in this guide.
A well-written recipe has a title, a short headnote, yield and time, an ingredient list in order of use, numbered steps and notes. Each step starts with a verb and includes a cue such as color, texture or temperature. Credit for the source belongs near the top or bottom.
Use the same layout for every recipe: title, headnote, yield, ingredients, steps, notes. Keep units and abbreviations consistent across the book, and add the name of the person each recipe came from. A consistent format makes a collection easier to cook from and easier to keep.
Measure anything that affects structure or safety: flour, leavening, salt in baking, meat weights and cooking temperatures. Seasonings and aromatics can be given as a range or “to taste,” as long as you say how to judge. When you cook by feel, measure once and write down what you actually used.
Copying someone’s exact text and photos is a different matter from sharing a dish. The U.S. Copyright Office says a list of ingredients is not protected by copyright, but creative writing around it can be. If you adapt a recipe, rewrite the method in your own words and credit the original. For a specific legal question, ask an intellectual property lawyer.
Most home recipes need between 4 and 12 steps. If a step contains more than one stage of work, split it. If you have more than 12, consider grouping the recipe into parts, such as sauce and main, with a short set of steps for each.