Plan style
Choose balanced everyday, higher protein, vegetable-forward or active lifestyle.
7-Day Plan
A good week starts here.
The 7-day plan page turns the food guides into a request. It takes the food ideas from the Top 10, the menu examples from the weekly preview and the ingredient logic from the standards page, then asks for the details that make a week workable.
The form is intentionally practical: menu type, meals per day, number of people, ingredient preferences, allergens, name, phone, email, city, address and preferred start date. The review step then summarises the plan before submission.
Built from the Top 10London request flowClear review step
The week strip
Pick a date and the week stops feeling abstract.
The strip updates visually when the preferred start date changes. That small interaction turns the 07 motif into actual calendar days.
Day 1OatsChoose start date
Day 2EggsChoose start date
Day 3LentilsChoose start date
Day 4SalmonChoose start date
Day 5YoghurtChoose start date
Day 6GreensChoose start date
Day 7SeedsChoose start date
Order request
A good week starts here.
Share the practical details, check the estimate and send a request that lands on a real confirmation page. The big 07 is the hand-off from idea to week.
Step 1: planStep 2: deliveryStep 3: review
What makes a request clear
A useful request is specific without becoming fussy. Menu style tells the team what kind of week the visitor wants. Meals per day and household size explain the scale. Ingredient preferences show which foods should appear more often, while the avoid list prevents awkward surprises. The start date turns the idea into a calendar rhythm, and the review step catches details before submission.
The form also keeps the editorial concept intact. The Top 10 foods remain the base, the weekly menu preview shows possible combinations, and the ingredient standards explain why variety, freshness and practical storage matter. The request is therefore not a separate checkout-style object. It is the final step of the magazine journey.
How the seven days are shaped
The week does not need seven completely different ideas. It needs enough variation to feel fresh and enough repetition to stay manageable. Oats can return with different fruits, yoghurt can become breakfast or dressing, lentils can become salad or supper, and seeds can finish several plates without drawing attention to themselves.
That is why the plan builder asks for preferences instead of forcing a fixed menu. A visitor can ask for vegetable-forward lunches, active-day snacks, lighter evening plates, familiar breakfasts or extra variety in textures. The confirmation page then records the submitted details so the request has a clear reference.
Using the journal before the form
The best route is simple: read the food atlas, skim the theme that matches the week, preview the menu, then return here with a clearer sense of what to ask for. That sequence keeps the form from feeling empty. Instead of guessing, the visitor can borrow language from the article pages and turn it into practical notes.
For example, a reader might ask for yoghurt breakfasts, lentil lunches that travel well, two fish-led suppers, extra greens, or snacks that work around long workdays. Those details are small, but they make the request easier to understand and easier to review before it lands on the thank-you page. They also make the request feel personal without asking the visitor to write a long brief from scratch.
Delivery area and contact note
The request flow is written for London delivery details. The address, city, phone and email fields help the team understand the practical shape of the request before follow-up. Business hours are Monday to Friday, 09:00-18:00, and the contact page remains the best place for questions that do not fit the form.
If you are unsure whether to start with the menu preview or the request form, read the preview first. It shows how breakfast, lunch, dinner and snacks can repeat the ten foods without making the week feel narrow.
Plan FAQ
Before you submit
Yes. The first step asks for menu type and meals per day so the request can reflect your rhythm.
Yes. The form uses method post and action thank-you.php, so the physical confirmation page remains the destination.
Yes. The weekly menu preview shows seven days with breakfast, lunch, dinner and snack examples.
The ingredient standards page explains variety, produce, proteins, pantry logic and freshness rhythm.
Ready