Kitchen Garden

We plan the garden with the kitchen. What the chef wants to pick — the herbs, the leaves, the speciality vegetables — sets the crop plan, and the seasons set the rhythm of what is sown and when.

That productive core is laid out as an ornamental potager: clipped, geometric beds that stay handsome even when they are being harvested. Everything is grown organically, with compost-led soil and companion planting doing the work that chemicals otherwise would.

We maintain the garden on a rotation that keeps the soil alive and the beds full, so the kitchen has a steady, seasonal supply and guests have a garden worth wandering.

Most kitchen gardens at hotels are planted the way a domestic vegetable patch is planted — a little of everything, evenly spaced, harvested whenever it is ready. It looks handsome and it is almost useless to a kitchen, because a chef cannot build a dish around four tomatoes on an unpredictable Tuesday.

A kitchen garden that a kitchen actually uses is planned from the other end. We start with the menu: which dishes are on it year-round, which items the chef would genuinely rather pick than order, and what quantity per service. Only then do we work back to bed area, succession intervals and sowing dates.

In practice that usually narrows the list considerably, and it should. Twelve crops grown in quantity, in succession, so that the kitchen can rely on them, are worth more than forty grown once. The rest of the space goes to the things that are genuinely better picked minutes before service — herbs above all, salad leaves, and the edible flowers and micro-leaves that would otherwise be bought in poor condition at a high price.

The other half of the brief is the guest. On most properties the kitchen garden is also somewhere guests are walked through, which means it has to be presentable on a day when half the beds have just been cut. That is a layout question, and it is solved by zoning the productive beds away from the walked route rather than by trying to keep everything looking finished at once.

Rajasthan gives three distinct growing windows, and the whole plan hangs off them.

Rabi, sown October to November, harvested through winter and early spring. This is the productive season here and the one to build the kitchen's expectations around. Tomato, brinjal, chilli, cauliflower, cabbage, carrot, radish, beetroot, spinach, fenugreek, coriander, peas, onion and garlic all do well. Coriander and spinach want repeat sowing every two to three weeks rather than one large sowing, or the kitchen gets a glut and then nothing.

Kharif, sown with the monsoon in June and July. Okra, cluster bean, cowpea, bottle gourd, ridge gourd, bitter gourd, pumpkin and amaranth. The gourds want vertical support, which is worth designing in rather than improvising, and they will produce heavily for a short concentrated period.

Summer, February to March sowing, harvested before the worst heat. A shorter and harder window. Cucumber, watermelon, muskmelon, summer gourds and heat-tolerant amaranth. Anything still in the ground in late May needs shade netting and will need water it may not be worth giving.

Herbs run across all three with protection. Mint, lemongrass and curry leaf are effectively perennial here. Basil, coriander and dill are cool-season and want succession sowing. Rosemary, thyme and oregano will hold if they are given sharp drainage and are not overwatered — which is how they are usually lost.

On most of the properties we work on, the existing ground is not worth growing vegetables in — it is shallow, stony, alkaline and low in organic matter, and building it up to a productive standard in place takes years.

So we generally build raised beds, and the reason is control rather than appearance. A raised bed lets us specify the growing medium outright, drains sharply in the monsoon when in-ground beds waterlog, warms and works earlier in the season, and keeps the soil out of the compacted paths. It also puts the work at a height that makes daily picking pleasant rather than a chore, which matters more to whether a garden is actually used than anything else on this page.

Bed width is set by reach — no bed should be wider than a person can comfortably work from both sides without standing in it, because standing in a bed undoes the soil structure that makes it productive.

The medium is built rather than bought: good loam, generous well-rotted compost or farmyard manure, and enough coarse material to keep it open. Then it is fed back every season, because a productive bed is exporting nutrients in every crate that goes to the kitchen. Compost from the property's own green waste and kitchen returns closes that loop, and on hotel sites there is usually plenty of both.

Kitchen gardens are the highest and least forgiving water demand on a property. Vegetables have shallow roots and short tempers, and irregular water shows up immediately as split tomatoes, bitter cucumbers and bolted coriander.

We irrigate them separately from the ornamental garden, on their own zones, usually with micro-sprinkler or closely spaced inline drip — bed spacing is too tight for widely spaced emitters to cover evenly. Mulch goes on heavily, because bare soil between crops in May loses water faster than any system can replace it. The irrigation design is done as part of the garden rather than added afterwards.

Shade netting from April through June is the difference between a kitchen garden that produces into summer and one that stops in March. Thirty to fifty per cent shade over the beds that are still cropping drops leaf temperature enough to keep things setting fruit, and cuts water demand at the same time. It is a seasonal structure, put up and taken down, not a permanent roof.

This is where a kitchen garden is different from every other part of a landscape, and it is not a small difference. Produce going to a hotel kitchen must have nothing on it that a guest should not eat, and the residue interval on many conventional products is longer than the interval between picking and service.

So the regime is built to work without them. Crop rotation across the beds so that soil-borne problems do not accumulate. Companion and trap planting — marigold at bed ends against nematodes, basil among tomatoes, a sacrificial row where it earns its place. Neem-based preparations, which this region has used for generations and which have a short and well-understood interval. Physical exclusion — fine netting over brassicas is far more effective than anything sprayed onto them afterwards. And encouraging the predators that do the work for free, which means not spraying broadly enough to kill them.

Where something does need intervention, we use the softest effective option and we write down what was applied, where, and when, so the kitchen knows the interval rather than guessing. On properties with food safety audits that record is required, and on properties without one it is still the right way to run a garden that feeds people.