The reusable recipe library: the asset that gives back the most time

Of everything you can systematise in a nutrition practice, the recipe library has the best ratio of effort invested to time recovered. A well-built recipe gets used dozens of times; one improvised for a single plan is used once and disappears.

How many recipes you need

Fewer than you think. Intuition says variety demands a huge catalogue, but in practice a clinic runs on a fairly small core, because recipes combine with each other and adapt by portions.

What earns a place

The criterion is not that the recipe is good but that it is reusable. A recipe gets in if it meets most of these:

• Uses ingredients found in any supermarket at any time of year.
• Scales well: doubling it does not break the preparation.
• Allows obvious substitutions for the most common restrictions.
• Takes an amount of time compatible with a working day.
• Needs no equipment most people lack.
• Holds up well when prepared in advance.

How to structure each recipe

The difference between a library that gets used and one that gets abandoned lies in the fields you choose to store. The essentials:

• Ingredients with quantity per portion, not total quantity.
• The base number of portions, so scaling is correct.
• Nutritional values per portion.
• Real preparation time, not the optimistic one.
• Restriction tags: gluten-free, lactose-free, vegetarian, vegan.
• Planned substitutions for the most problematic ingredients.
• The time of day it fits.

Tags are what turn a list into something usable. Without them you end up reading forty recipes to find the dairy-free one; with them, you filter.

The mistake of personalising too early

It is tempting to create a bespoke recipe for every client. Six months later the result is a catalogue of two hundred recipes each used once, impossible to maintain or filter. The alternative that works: one base recipe in the library, with adaptation as a one-off variation inside that specific plan.

How to start without stalling

1. Review the last ten plans you delivered and note which recipes repeat.
2. Formalise those first: you already know they work and that you use them.
3. Fill the obvious gaps by time of day.
4. Add restriction tags to everything you have.
5. From then on, add a new recipe only once you have used it two or three times.

With this method a usable library comes together in two or three afternoons, and from the second week it is already giving time back on every plan you prepare.

Maintenance

One review a year is enough: delete what you have never used, correct the preparation times you know were optimistic, and add what has settled in. A library ages badly not because its recipes are old but because nobody has cleaned it.