The 11pm phone call
It's a Wednesday evening. Your sous chef pulls you over and says, "I want to do a new starter for Saturday — burrata with peach and basil oil. Trying it on the prix fixe?"
You say yes. Then you start thinking about everything that has to happen between now and Saturday lunch.
You need to write down the recipe properly. Cost it. Decide a price. Check which of the 14 allergens it contains. Update the printed menu. Make sure the till has the right description. Brief the front-of-house team on ingredients and substitutions. Update the website. Email the wholesaler for anything that needs to be in by Friday.
In a paper-and-Word-document kitchen, that's six to eight hours of work spread across two days. Realistically, half of it doesn't get done. The dish goes on the menu, three things slip through the cracks, and a server gets caught off-guard mid-service by a customer asking "is the basil oil dairy-free?"
This article shows a different way. Fifteen minutes from "I want to add this dish" to "the new menu is live, the allergens are correct, and the team has been told." No exaggeration — we time-tested it on real recipes.
Why menus stay frozen longer than they should
Most independent restaurants change their menu less often than they want to. Talk to any chef-owner and they'll tell you they have ideas — seasonal dishes, regional specials, the thing they saw at a competitor — that never get on the board.
The reason isn't creativity. It's friction. Every menu change creates a long tail of administrative work:
- Recipe documentation — someone has to type up ingredients and method in a format other cooks can follow. The hour everyone hates.
- Allergen analysis — 14 EU allergens to check, and the answer changes with every supplier swap. Get this wrong and you have a Natasha's Law problem.
- Dietary labelling — is it vegetarian? Vegan-adaptable? Gluten-free if you swap the croutons? These need to be on your menu and your customer-facing answers need to be consistent.
- Cost and price — somebody has to add up ingredient cost and decide gross margin.
- Reprinting and republishing — physical menus, website, delivery platforms, table cards, the chalkboard outside.
- Staff briefing — kitchen needs to see the new method. Front-of-house needs to taste it, learn the description and the allergens before service.
- Compliance records — your HACCP folder needs the new recipe added, especially if it changes a cooking method or chilling step.
If any of those steps gets skipped, the consequences range from "small typo on a printed menu" to "ambulance and lawsuit". So owners do the safe thing: they don't change the menu, or they change it twice a year, and they put up a "specials" board where the rules feel more relaxed.
That's the wrong fix. The right fix is to remove the friction.
The 15-minute workflow
Here's the sequence we use ourselves and that our customers use. Times are wall-clock, on an iPhone or laptop, with no preparation other than having the recipe written down somewhere. A napkin works.
Minutes 0–3 — Capture the recipe
You have three options for getting the recipe into Blueroll:
- Photo — take a picture of a handwritten card, a printed recipe, a page from a book. AI Recipe Import reads it.
- PDF — drag a recipe PDF onto the import screen. Same result.
- Text — paste plain text. Useful when the recipe was emailed.
Behind the scenes, AI Recipe Import reads the input and extracts a structured recipe: name, description, category, ingredients with quantities and units, cooking method and temperature, reheating, chilling, freezing and defrosting instructions, plus extra-care flags for eggs, rice, pulses, and shellfish.
Time: about 30 seconds for the import, plus the time to take the photo. Total around two to three minutes.
Minutes 3–6 — Check allergens
This is where the time savings really start.
Every ingredient the AI extracted is matched against your ingredient database. If you've used tuna before, the system already knows tuna contains fish. Same with mozzarella (milk), wheat flour (gluten), and so on for all 14 EU allergens.
The recipe page now shows you a clean summary at the top — "Contains: milk, gluten, sulphites" — and dietary labels — "Vegetarian: yes, Vegan: no, Gluten-free: no, Dairy-free: no." All calculated automatically from the ingredients.
If a new ingredient appears that the system has never seen, you tag its allergens once. Next time you use it, the tag is permanent.
This is the step that pays for the whole tool. Manual allergen checking on a recipe with 12 ingredients takes 20 minutes if you're careful. Auto-tagging takes 20 seconds and is more accurate.
Time: two to three minutes for review. Less if all ingredients are already in your database.
Minutes 6–9 — Activate and categorise
The recipe is now in your library but not yet on the menu. To put it on the menu, you toggle Active and choose a category — starter, main, dessert, side, drink, cocktail, beverage.
The category is important: it determines where the dish appears in your menu and your allergen matrix, both of which your front-of-house team consults during service.
Add a price. Done.
Time: one minute.
Minutes 9–12 — Export the menu
Your menu is automatically the list of all active recipes, grouped by category, with dietary labels and optional allergen columns.
To print or share it, hit Export. You get:
- PDF in A4 portrait, ready to print, with optional allergen columns for staff use.
- CSV for delivery platforms or POS systems.
- A public read-only link to share with delivery aggregators or embed on your website.
Time: one minute, including the print job kicking off.
Minutes 12–15 — Brief the team
The kitchen needs to know there's a new dish. Front-of-house needs to know its allergens and dietary status.
You don't need to call a team huddle. You add a single line to the Diary — "New dish added: burrata with peach and basil oil. Vegetarian, contains milk and sulphites. See recipe for method." Everyone who logs in tonight will see it on the dashboard.
For larger changes, you can send a checklist task — "Try the new burrata before Saturday service" — to every chef.
For front-of-house, the allergen matrix is on their phone. They can look up "burrata" in two taps mid-service.
Time: three minutes for the diary entry plus task creation.
Total: fifteen minutes. From "Sous chef wants to add a dish" to "It's on the menu, the allergens are correct, the team knows, and a delivery platform can pull the latest version." The first time you do this you'll be slower — maybe 20 minutes. By the fifth menu change it feels automatic.
What you actually save
Let's do the maths on a typical independent restaurant that updates the menu monthly. Twelve changes a year, each averaging six hours the old way:
| Approach | Per change | Per year |
|---|---|---|
| Paper + Word + memory | ~6 hours | 72 hours |
| Blueroll workflow | 15 minutes | 3 hours |
| Time saved | 5h 45m | 69 hours |
If the manager's hour costs £20 fully loaded, that's £1,380 a year of recovered time, conservatively. For restaurants that change menus weekly — gastropubs, dessert cafés, specialty coffee places — multiply by four to get to £5,500.
The bigger upside, though, is the things you do because you can:
- Try a seasonal special on a Tuesday without the dread of paperwork.
- Run a one-night-only collaboration with a guest chef.
- Test three variants of a dish over two weeks before committing.
- Swap out an underperforming item the day the supplier delivery is rubbish, not three weeks later.
Restaurants that experiment more tend to win more. The friction of menu changes is one of the silent killers of innovation in independents. Remove it and the menu becomes alive.
The hidden upside: allergen accuracy
The number-one cause of an allergen incident isn't carelessness — it's outdated information. A dish was tweaked, a supplier was changed, but the allergen card on the wall wasn't updated. With auto-calculated allergens linked to your live ingredient database, that drift doesn't happen.
This is also why the workflow above puts allergen review before menu activation, not after. By the time the dish is "live" it has already been allergen-checked. There's no follow-up step that can be skipped.
Common objections
"AI can't read my chef's handwriting."
It can, actually. We've tested with handwriting from chefs across five kitchens — including some that the chefs themselves couldn't read three months later. The model is trained on millions of varied handwriting samples and is more reliable than the manager who'd otherwise have to decipher it. Edge cases — blurry photos, unusual abbreviations — you correct in the editable fields after import.
"It doesn't know our cooking techniques."
It doesn't need to. The technique stays in the head and hands of the chef who developed it. The AI extracts the basic structure — ingredients, method outline, temperatures, times — and you fill in the specifics. The point is to remove the typing, not the cooking.
"Sounds expensive."
The whole tool is £14.99 a month. There's no per-recipe cost, no usage limit on AI imports, no add-on for the import feature. If you change one menu a year and save four hours of manager time, it has already paid for itself.
"I have a POS that does menus."
POS systems are great at processing orders. They are not built for recipe documentation, allergen tracking, dietary labels, or staff onboarding. The two systems coexist: your POS handles transactions, your operations app handles operational knowledge.
"Can I do this on my phone or do I need a laptop?"
Both work. The AI Recipe Import flow is genuinely mobile-first — most owners do it from their phone, in the kitchen, with the recipe card in their other hand. The export step (printing a menu) is usually easier on a laptop, but you can email the PDF from your phone too.
Free download: the printable checklist
The whole 15-minute workflow on one page, with timings, the things to check at each step, and the common mistakes to avoid. Print it out and stick it in your kitchen office.
What to do today
If you want to see this in action without committing anything:
- Open your phone camera.
- Take a picture of any recipe — a printed page, a handwritten card, a screenshot from your phone notes.
- Sign up for the free trial at app.blueroll.app.
- On the AI Import screen, upload the photo.
- Watch the recipe extract in 30 seconds.
If after that you don't think you can run your next menu change in 15 minutes, reply to hello@blueroll.app and tell us what we missed. The team reads everything.