Guide

How to write a recipe someone else can actually cook

How to write a recipe that works without you in the room: ingredients in order of use, steps with cues you can see, and swap and make-ahead notes. With examples to copy.

By Crumb EditorsUpdated 7 min read

You know this dish by heart. You know "a glug of oil" means about two tablespoons, that the potatoes are ready when the skins start to split, and that the sauce goes on at the very end. The person reading your recipe knows none of that. Learning how to write a recipe is mostly learning to get what's in your head onto the page, so a stranger can cook it without texting you.

What a well-written recipe looks like

Read this once as a cook, then we'll take it apart.

Crispy smashed potatoes with lemon-herb yogurt

Serves 4 as a side. Hands-on time: 20 minutes. Total time: about 1 hour 15 minutes.

For the yogurt

  • 150 g (2/3 cup) plain Greek yogurt
  • 1 small garlic clove, finely grated
  • 1 tablespoon lemon juice
  • 2 tablespoons chopped fresh dill or parsley
  • 1/4 teaspoon fine salt

For the potatoes

  • 1 kg (2.2 lb) small waxy potatoes, about the size of a golf ball

  • 1 tablespoon fine salt, for the cooking water

  • 4 tablespoons olive oil, divided

  • Flaky salt, to finish

  1. Heat the oven to 220°C (425°F) with a rack in the upper third.
  2. Make the yogurt: Stir together the yogurt, garlic, lemon juice, herbs and 1/4 teaspoon salt. Cover and refrigerate until serving.
  3. Boil the potatoes: Put the potatoes in a large pot, cover with cold water by about 2 cm (1 inch) and add 1 tablespoon salt. Bring to a boil, then lower the heat so the water bubbles steadily. Cook for 15 to 20 minutes, until a knife slides into the biggest potato with no resistance.
  4. Drain the potatoes and leave them in the colander for 5 minutes, until the skins look dry and dull instead of wet.
  5. Smash and roast: Pour 2 tablespoons of the oil onto a large rimmed baking sheet. Add the potatoes and press each one with the bottom of a glass until it's about 1.5 cm (1/2 inch) thick and the edges crack. Drizzle with the remaining 2 tablespoons oil.
  6. Roast for 30 to 40 minutes, until the edges are deep golden brown and the potatoes release easily from the pan.
  7. Sprinkle with flaky salt and serve with the yogurt spooned over or alongside.

What's doing the work: the yogurt is made first, so it's listed first, as Virginia Cooperative Extension's recipe-writing guide recommends. "Divided" adds up (2 tablespoons, then "the remaining 2"). Every judgment call has a cue: a knife sliding in, dull skins, cracked edges. And the total time counts heating the oven and boiling, not just the roast.

How to write a recipe ingredient list

The ingredient list is where people shop and measure, so be specific about anything that changes what they buy. Greek or regular yogurt. Small waxy potatoes with a size, because "1 kg potatoes" could be three big bakers that take twice as long to boil.

Watch the comma. "1 cup walnuts, chopped" means measure whole walnuts, then chop. "1 cup chopped walnuts" means chop first, then measure, which gives you more nuts. Write the one you actually did.

Weights are more reliable than cups. If you write in cups, add grams alongside; our cups to grams guide has the numbers for the usual staples.

Write steps the cook can see

Leslie Jeon's tips for writing better recipes put it neatly: compare "Cook until done" with "Cook until browned and a fork can easily be inserted." The second gives the cook a picture to match.

  • Warn early. If the oven needs to be hot or the dough chills for three hours, say so in step 1, in the timing up top and in the headnote. Plenty of people skip the headnote.
  • Say what kind of heat. As JJ Goode argues in "The Case for Very Long Recipes", a simmer can be bare, gentle or nearly a boil, and that changes how fast things cook. "Bubbles steadily" costs two words.
  • Spend words where a wrong guess would ruin the dish, not on how to chop an onion. When a stage is hard to describe, add a photo beside that step (recipe photos covers which moments to shoot) and keep the words too.

Yield and time should be what you actually got ("about 24 cookies"), with every rest, chill and rise in the total. Adapted someone else's recipe? Credit and link the original; recipe copyright covers what you can reuse.

Recipe variations: a note or a whole new recipe?

Here's the test: after reading the note, does the cook have to keep remembering exceptions? If they don't, a note is enough:

Lemon-chili version: Add the finely grated zest of 1 lemon and 1/2 teaspoon red pepper flakes with the last 2 tablespoons of oil in step 5. Everything else stays the same.

If the version changes the heat, the timing and the doneness cues (an air-fryer version of these potatoes, say), write it out as its own complete recipe. Five "same as above, except…" notes make the cook assemble the recipe for you.

Substitution notes that say what you know

Mike Johnson's recipe development guide recommends offering substitutions only when you've tested them, with exact amounts. In practice you'll have three kinds of note. Here's each one for the potatoes, written from your test log:

Yukon Gold potatoes: I made this with 1 kg small Yukon Golds instead of waxy potatoes, everything else the same. The edges got extra crisp, but a few potatoes fell apart when I smashed them.

Sour cream instead of yogurt: A reader made the sauce with sour cream and loved it. They didn't say how much they used, and I haven't tried it myself.

Dairy-free yogurt: I haven't tested this, so I can't tell you how it'll turn out.

"I haven't tested this" is useful information. It saves the reader from guessing whether you forgot to mention it or never tried.

Two traps. Don't merge notes into a combination you never made; "use Yukon Golds and sour cream" is a new claim. And skip the bare "1:1." Equal weight and equal volume can be very different amounts, so write "150 g sour cream instead of the yogurt."

To promote a swap from "a reader tried it" to "this works," cook it. Our guide on how to test a recipe shows how to change one thing at a time.

Make-ahead notes: where to stop and how to restart

A good make-ahead note says where to stop, how to store it, what to do first on the way back, and where to rejoin:

Make ahead: Boil and drain the potatoes (steps 3 and 4) up to 1 day ahead. Let them cool, then refrigerate in a covered container within 2 hours of cooking. When you're ready, heat the oven as in step 1, then pick up at step 5. Cold potatoes may need 5 extra minutes in the oven. Make the yogurt the morning you serve it.

Use your own tested times, and match the storage line to the FDA's safe food handling guidance: refrigerate perishables within 2 hours of cooking, at 40°F (4°C) or below.

Watch the restart. "Refrigerate, then continue at step 5" sounds precise, but the oven gets heated in step 1. Jump straight there and you're smashing potatoes with a cold oven. Write the first action after the pause, then where the cook rejoins. And add a pointer in the method ("To make ahead, see the note"), so the cook sees the option before passing it.

Writing a recipe with more than one part

Keep component names identical everywhere: if it's "the yogurt" in the list, don't call it "the sauce" in step 7.

When a component makes more than the dish needs, give the amount at the step where it's used: "Toss with 1/3 cup of the dressing (you'll have about 1/3 cup left over)." Otherwise people pour in the lot.

If a component lives on its own page, name it at the top of the recipe with how much to make and when to start, so nobody discovers a linked sauce recipe mid-assembly. Changing a component's batch size? The recipe scaler does the arithmetic.

Read it like a stranger before you publish

Open the recipe on your phone and follow it from shopping list to plate without filling any gaps from memory. Does every listed ingredient get used? Do divided amounts add up? Does any instruction arrive late, like a chill you only learn about in step 6? Does each variation, swap and make-ahead note work if you follow only that route?

Anything you can't answer from your notes goes back to the kitchen. Once it passes, give it a page that's easy to cook from: our guide to setting up a recipe page covers the layout, and building a useful recipe archive helps readers find it again next week.

recipe writingrecipe developmentrecipe notes
← Back to the blog