Genres

Writing a cookbook: recipe testing, headnotes and structure

A cookbook is a promise that every recipe works in someone else’s kitchen. How to test recipes properly, write ingredient lists and methods people can follow, write headnotes worth reading, and shape the whole book.

By The IdeaToBook team7 min read

Many people have a cookbook in them. Family recipes, the dishes friends always ask for, the cooking you’ve learned from a particular place or diet or way of life. It’s one of the most natural first books to write, because the material already exists and you know it works.

Except that you know it works in your kitchen, with your oven, made by you. A cookbook makes a bigger promise: that the recipe works for a stranger, with a different oven, different flour and none of the knowledge you carry in your hands. Most of the work of writing a cookbook is closing that gap.

Start with the book’s idea, not the recipes

A pile of good recipes isn’t yet a book. The cookbooks people love have a clear idea that holds them together: a cuisine, a technique, a situation, a person, a place. “Weeknight vegetarian dinners in thirty minutes.” “Sourdough for small kitchens and busy weeks.” “My grandmother’s Sicilian Sunday cooking.”

The idea decides which recipes go in and which stay out. It tells readers why this book and not one of the many others on the shelf. And it gives you a voice for the headnotes and introductions, because you know what you’re trying to say.

Write the idea in one sentence before you choose a single recipe. Then list every recipe you might include and cut anything that doesn’t fit. It’s often harder than it sounds; favourite recipes that don’t belong are better saved for another book.

Test every recipe, then test it again

Recipe testing is what separates a reliable cookbook from a collection of good intentions. A thorough process looks something like this.

Write it down while you cook it. Not from memory. Measure everything, including the things you normally do by eye. Weigh the onion. Time each stage. Note the size of the pan. Write down what it looks like at each point.

Cook it again from the written version. Follow your own words exactly, as if you’d never made the dish. You’ll find the steps you skipped because they’re automatic to you.

Have someone else cook it. This is the most important stage, and the one most often skipped by first-time authors. Give the written recipe to a home cook at your reader’s level and ask them to make it without calling you. Ask them to note every point where they hesitated, guessed or got a different result. Professional cookbooks are usually tested by people other than the author; volunteer friends and family can do the same job for you, especially if they’re honest.

Test across kitchens. If you can, have the recipe tested on different ovens (fan and conventional), at different altitudes if your readers might live high up, and with ingredients from different shops. Flour, butter and even eggs vary more than people expect.

Keep a testing log. For each recipe, note who tested it, what went wrong and what you changed. It’s tedious, and it’s what makes the book trustworthy.

Writing the ingredient list

Readers use the ingredient list to shop and to prepare, so it needs to be precise and in a predictable order.

List ingredients in the order they’re used. This is a widely followed convention and readers rely on it. If an ingredient is used twice, list it once with the total and specify the split in the method (“the remaining butter”), or list it twice under sub-headings.

Be specific about quantities and forms. “1 onion” is vague; “1 large onion (about 250 g), finely chopped” is not. Say whether butter is salted or unsalted, whether flour is plain or self-raising (or all-purpose in the US), whether herbs are fresh or dried.

Put preparation in the list when it’s simple. “2 garlic cloves, crushed” saves a step in the method. Complicated preparation belongs in the method.

Decide on units and stick to them. British readers expect grams and millilitres; American readers often expect cups and ounces. Many books give both, with metric first or US first depending on the main market. Converting between them isn’t exact, especially by volume, so test the conversions rather than relying on a chart. For baking, weights are more reliable than cups and many bakers prefer them.

Give oven temperatures in every form your readers might need. For a British book, that often means Celsius, Celsius for fan ovens, Fahrenheit and gas mark. Say which you tested with.

Writing the method

The method should let someone cook the dish without stopping to think.

  • Number the steps. Each step should be a stage, not a single tiny action, but shouldn’t combine unrelated stages.
  • Start with anything that takes time and can happen in the background: “Heat the oven to…”, “Put a large pan of salted water on to boil.”
  • Give both a time and a sign. “Cook for 8–10 minutes, until the onions are soft and golden at the edges.” Times vary between kitchens; visual and physical signs don’t.
  • Say what to do at the critical moments. If the sauce might split, say how to tell and how to rescue it.
  • Say how to know it’s done. For meat, a safe internal temperature from a reliable food-safety source; for cakes, a skewer that comes out clean; for bread, a hollow sound when tapped underneath.

Every recipe should state the yield (serves 4, makes 12) and the time, ideally split into active time and total time. Readers choose recipes by these numbers.

Headnotes: why this recipe

The headnote is the short paragraph above the recipe. It’s the one part of the recipe where you speak directly to the reader, and it’s where your voice lives.

A good headnote does at least one of these things:

  • says where the recipe comes from (a person, a place, a memory)
  • tells the reader what to expect (“it looks plain, but the browned butter makes it”)
  • gives one useful tip that applies before they start (“make the dough the night before”)
  • suggests when to make it, or what to serve it with

What it shouldn’t do is fill space. Long, rambling introductions before recipes are a familiar complaint about recipe websites, and readers bring that impatience to books. Keep most headnotes to a short paragraph. Save longer stories for chapter introductions, where readers who want them will find them.

Structuring the book

Most cookbooks are organised in one of a few ways.

By course or type of dish: starters, mains, desserts, baking. Familiar and easy to use, but can feel generic.

By season: spring, summer, autumn, winter. Good for books built around fresh produce.

By situation: weeknights, weekends, feeding a crowd, cooking ahead. Good for books that solve a practical problem.

By technique or base recipe: for example a dough, then everything you can make from it. Good for teaching books, where skills build on each other.

Whatever structure you choose, put a basics chapter early if your recipes rely on stocks, doughs, sauces or techniques that recur. Then refer back to it rather than repeating the instructions.

Beyond the recipes, readers value a short introduction that explains the book’s idea, a section on equipment and store-cupboard ingredients if they’re unusual, and a good index. A cookbook index should list recipes by name and by main ingredient, because readers often arrive with something in the fridge and want to know what to make with it.

Recipes sit in an unusual place in copyright law, and it varies by country, so take advice for your own situation. In the United States, the Copyright Office says that a mere list of ingredients isn’t protected by copyright, but that substantial literary expression, such as explanatory text, and the selection and arrangement of a collection can be. Whatever the law where you live, the honest practice is the same: if a recipe is adapted from someone else’s, say so (“adapted from…”) in the headnote, and write the method and headnote in your own words.

Pictures

Cookbooks are usually expected to have photographs, though not of every recipe, and plenty of good cookbooks have few or none. If you’re self-publishing, photography is often the largest cost, and colour printing adds considerably to the cost of a paperback. Consider whether a few chapter-opening images, or illustrations, would serve the book as well. If you photograph the food yourself, natural daylight from one side and a plain background will do more than expensive equipment.

Before you publish

Read every recipe one last time against your testing log. Check that every ingredient in the list appears in the method and vice versa: it’s surprisingly easy for one to go missing in editing. Check that the yields, times and temperatures are consistent across the book. Then give the finished manuscript to one more tester who hasn’t seen it before.

IdeaToBook has a cookbook type with a recipe interior style, laid out with ingredient lists, numbered methods and tips. It’ll help you shape the book and write the headnotes in your voice from your interview answers; our guide to making a cookbook with recipes walks through it. What it can’t do is test your recipes, and it doesn’t pretend to: that part is yours, and it’s the part your readers will thank you for.

Sources

Help & feedback

Talk to the people who make IdeaToBook. A person reads every message.

Have an account? See your messages. Or email support@ideatobook.my.