Precision is the foundation of a repeatable recipe

A recipe is only as good as the results it produces in someone else's kitchen. The difference between a dish that works once and one that works every time usually comes down to how carefully you have measured, described and tested it. Your reader has not watched you cook, cannot see what your sauce looked like at the crucial moment, and cannot ask you a quick question halfway through. Everything they need must be on the page.

Start by weighing dry ingredients in grams rather than reaching for a cup. A digital scale costs very little and removes an entire category of failure, because flour, cocoa and grated cheese compress differently every time they are scooped. Use millilitres for liquids, and keep teaspoons and tablespoons for small quantities — a UK tablespoon is 15ml and a teaspoon is 5ml, so say whether a spoon is level or heaped. If you offer cup measures as a courtesy, treat them as a rough guide and say so.

Be equally exact about equipment and heat. Give oven temperatures in Celsius with the fan equivalent and the gas mark, and describe pans by diameter and depth in centimetres. "A medium oven" means something different in every home; "200°C fan, gas mark 7" does not.

Build an ingredient list that reads like a checklist

List ingredients in the order they are used, unless the dish has distinct components, in which case group them under small subheadings such as "For the filling" and "For the topping". This lets a reader scan down the list with a pen in hand and gather everything before they begin.

State the preparation in the list itself, so nobody is chopping an onion at the last second while the pan burns. Practical, specific wording helps:

• 1 large onion, finely chopped rather than "1 onion"
• 200g plain flour, plus extra for dusting
• 2 eggs, at room temperature — and a note explaining why it matters
• 400g tin of chopped tomatoes, drained

Before the ingredients, give the essentials in a short block: how many people it serves, the total time, the active time, and any equipment a typical kitchen might not have. A reader should know within ten seconds whether they can cook this tonight.

Write method steps someone can follow in real time

One main action per numbered step. If a step contains three instructions joined by commas, it will be skimmed and something will be missed. Keep sentences short and begin each with a verb: heat, stir, fold, pour, rest.

Pair every timing with a sensory cue, because ovens, hobs and pans all behave differently. "Fry for 6–8 minutes, until the onions are soft, translucent and smell sweet" tells the reader what to look for if their pan runs hot. Include the details that only experience teaches: when to start preheating, when to put the pasta water on, how the mixture should look at each stage, and what texture to expect before moving on.

Be honest about resting, chilling and cooling times. They are part of the recipe, not an afterthought, and hiding a 30-minute rest in the final line of a step is a common way to frustrate people. If a dish needs to sit overnight, put that in the headnote so nobody starts cooking at 7pm expecting to eat at 8.

Test it more than once, in a normal kitchen

Cook your recipe at least twice, on different days, before publishing it. Weigh every ingredient each time rather than trusting your hands — the point of testing is to confirm what the written amounts actually do, not to reproduce a dish you can already make by instinct.

Set a timer at each stage and write down the real numbers. If your onions took nine minutes but you had written six, change the recipe. Test the awkward moments deliberately: does the custard curdle if it goes in too hot, does the pastry shrink, does the sauce split when reheated? Note the causes and the fixes. Finally, hand the written recipe to someone who has never eaten the dish and watch them cook it without your help. Every question they ask is a gap you need to fill.

Add notes that answer the questions readers will ask

A short notes section at the end of a recipe does a great deal of work. Cover make-ahead instructions, storage, reheating and freezing, with timings and containers specified. Mention swaps and their consequences honestly — swaping double cream for single will give you a thinner sauce, and a reader deserves to know that before they try it.

Be cautious about scaling. Most soups, stews and traybakes double happily, but baking is less forgiving: leavening agents, salt, pan size and cooking time do not simply multiply. Tell readers which recipes scale well and which are best made as written. Add a line or two on troubleshooting common problems, and flag allergens clearly.

Polish the language until it disappears

Use plain, active, present-tense instructions. "Stir the mixture" is better than "the mixture should be stirred". Choose one word for each action and use it throughout — if you say fry, do not switch to sauté halfway down. Keep your spelling, units and capitalisation consistent, and use bold sparingly to highlight the cues that matter most.

Read the whole recipe aloud as though you were cooking from it, and give it to one more person for a final check. Clear formatting, generous whitespace and numbered steps do more for a home cook than any amount of elegant prose. Do this well and your recipe quietly disappears, leaving only the pleasure of a dish that turns out right.