How to Rotate Crops in a Vegetable Garden (and Why It Is Harder Than You Are Told)

Crop rotation is one of the few pieces of gardening advice that appears in every single manual, and one of the most poorly applied. Not out of laziness, but because the simplified version in circulation — "alternate leaf, fruit, root" — is both easy to remember and largely beside the point.

Why rotation works

Two distinct mechanisms hide behind the same word, and it pays not to confuse them.

The first is about disease. A good share of vegetable garden problems are caused by fungi, bacteria or nematodes that live in the soil and that attack only a narrow set of related species. As long as those organisms find a host plant in the same spot every year, their population rebuilds and accumulates. If the host disappears for several seasons, the inoculum declines: some of the resting structures germinate without finding a root to colonise, others are broken down by soil life. Rotation sterilises nothing and cures nothing; it lowers a pressure. The same logic applies to specialised pests that spend part of their cycle in the soil, such as carrot rust fly, whose pupae overwinter where the crop grew — with the caveat that an insect that flies will eventually find your carrots again, and that shifting a row three feet over has never been a control measure on its own.

The second mechanism is about fertility. Species do not take up the same quantities or the same elements, and they do not explore the soil to the same depth: a carrot and a lettuce simply do not occupy the same root volume. Legumes, in symbiosis with nitrogen-fixing bacteria, generally leave the soil better supplied, provided their residues go back into that bed. Alternating demands stops you from draining the same reserve in the same spot year after year.

Botanical family, not the part you eat

The "leaf, fruit, root" grouping has one merit: it is memorable. It has one fatal flaw: it corresponds to nothing biological. A soil fungus takes no interest in which organ you harvest; it takes an interest in which plants it can colonise, and that ability follows botanical kinship.

The clearest example is the potato. Filed under "root" or "tuber" in most rotation charts, it in fact belongs to the same family as the tomato, the aubergine or eggplant, and the pepper. Following tomatoes with potatoes looks like a rotation while handing the same pathogens perfect continuity. Another classic: beetroot and spinach, one eaten as a root and the other as a leaf, sit in the same botanical group, as does chard.

So learn the families rather than the organs. In a home garden, five of them cover most of what you grow: nightshades (tomato, potato, aubergine, pepper, chilli), brassicas (cabbage, kale, broccoli, turnip, radish, rocket or arugula, mustard), umbellifers (carrot, parsnip, celery, parsley, fennel), legumes (bean, pea, broad bean) and cucurbits (squash, courgette or zucchini, cucumber, melon). The onion family (onion, garlic, leek, shallot) forms a sixth group worth watching too.

The nightshade problem

If you only keep one rotation, keep this one. Nightshades combine three features that make them the pressure point of a home garden: they are almost always the crops you care most about, they occupy a large area for a long stretch of the season, and several of the problems that affect them persist in soil from one year to the next — fungal wilts, root-knot nematodes, various cankers.

One honest qualification belongs here, because it is nearly always left out. Late blight of tomato and potato, by far the most feared disease on these crops, does not mainly overwinter in bare soil: it survives above all on living plant material, particularly tubers missed at harvest or kept in storage. Against blight, rotation helps little; lifting every tuber, pulling volunteers, and watching the forecast help a great deal more. Rotating nightshades is still fully justified, but for reasons other than the one most often given.

Return intervals: an order of magnitude, not a rule

The figure you will meet everywhere is three to four years before the same family returns to the same ground, sometimes stretched to four or five for nightshades and brassicas. Take it for what it is: a convention that comes out of agronomic practice, not a measured constant.

How long an organism actually persists in a given soil depends on the species, on the nature of its resting structures, on climate, on soil texture and on biological activity. Some pathogens fade in a season or two; others — clubroot in brassicas is the textbook case — persist far longer than any home rotation can outlast. Three or four years is therefore a reasonable compromise, not a guarantee.

On two hundred square feet, perfect rotation does not exist

Here is the point most articles avoid. A four-year rotation assumes you can divide your garden into four beds of comparable size and grow a different family in each one every year. It works beautifully on paper and badly in a real garden, for a simple reason: nobody grows four families in equal quantities. If tomatoes take up half your space because tomatoes are what you want to eat, no arrangement of beds will let you rotate them on a four-year cycle.

Add the physical constraints — the one bed that actually gets full sun, the sheltered corner, the trellis that stays where it is — and those of the calendar, since a winter crop and a summer crop sometimes share the same ground. A small plot drifts naturally towards local monoculture.

Better to admit it than to deny it. An imperfect rotation you actually follow is worth infinitely more than a theoretical plan abandoned in May. The realistic goal is not the ideal cycle: it is to avoid putting the same family straight back in the same place, and to hold the longest intervals where the stakes are highest.

A workable method for a small plot

Start with the opposite of what the charts do: do not plan, record. Write down each year what actually grew in each bed, with the botanical family next to the variety name. Without that history you are planning from memory, and memory reliably confuses last year with three years ago.

Then set priorities. Spend your rotation effort on the high-risk, high-occupancy families: nightshades first, brassicas next, umbellifers if you grow a lot of them. Salads, radishes and annual herbs can serve as your adjustment variable — short cycles and shallow roots make them gap-fillers you can slot wherever the plan leaves a hole.

Finally, accept the compromises, but choose them. If you have to put tomatoes back in the same bed after only two years, do it knowingly and compensate where you can: organic matter, a cover crop between seasons, watering at the base rather than overhead, generous spacing, prompt removal of diseased material. A shortcut you have decided on and hedged is nothing like a shortcut you have drifted into.

Keeping track of what actually grew

This is exactly why Marmanda keeps a log of what was sown and planted in each spot, season after season, and shows the source of every recommendation along with its limits. The tool does not calculate your rotation for you — that capability does not exist today, and it would be dishonest to imply otherwise. It does something more modest and more useful: it holds an accurate memory of your past crops, which is the raw material without which no rotation, however rough, can be decided at all.

A useful rotation comes down to three things: knowing what grew there, knowing the families, and making honest trade-offs when space runs short. The rest is the intellectual comfort of a four-box chart.