Updated:
Short answer
Choose next season's vegetables by plant family and the bed's history, rather than by the name of the last vegetable alone. Replacing tomatoes with peppers repeats the nightshade family. With one or two beds, record the conflicts first, then decide which crops you can move, reduce or skip. A perfect-looking rotation chart cannot create planting space you do not have.
This guide helps you make that decision at season's end. It is an extension-informed planning method, not a garden trial, a disease diagnosis or a promise of better yields. A notebook or a copy of the worksheet below is enough; no special bed, fertilizer or irrigation purchase is needed to make the plan.
What rotation can do in a small garden
Wisconsin Extension's home-garden rotation guide recommends changing families and keeping a map. Its general target is a three- to four-year interval before returning the same family to an area, including cover crops. It also recognizes that small gardens may manage only a year-to-year family change. That is a planning recommendation, not a guaranteed waiting period that clears every pathogen.
Scale matters. University of Maryland Extension describes rotation as beneficial in home gardens but only marginally helpful against insects and disease at that small scale. Moving a tomato to the neighboring bed is therefore not a reason to label it protected. Rotation belongs alongside crop-specific care and investigation of actual problems; it does not certify that a bed is disease-free.
There is also no required sequence of “fruit, root, leaf, bean” that solves every garden. Those harvest categories can hide family repeats. Use them as a meal-planning preference if helpful, but make the family history visible before assigning the space.
Group crops by family
Use this compact selection of examples from the Wisconsin and Minnesota Extension family lists. It is not a complete botanical catalog. Check unfamiliar vegetables and every species in a seed mixture separately.
| Family group | Familiar examples | An easy repeat to miss |
|---|---|---|
| Nightshade | Tomato, pepper, eggplant, potato | Pepper after tomato changes the crop, but keeps the family |
| Cabbage or mustard | Broccoli, cabbage, kale, radish, turnip | A radish root crop and leafy kale share a family |
| Legume | Bean, pea | Peas followed by beans are still a family repeat |
| Gourd | Cucumber, squash, melon, pumpkin | A cucumber-to-squash swap keeps the family |
| Carrot | Carrot, celery, parsley, parsnip | Parsley also belongs in a carrot-family history |
| Sunflower | Lettuce, endive, sunflower | Lettuce is not in the cabbage family simply because both are leafy |
A mixed bed needs more than one family label. If tomatoes occupied one end and beans the other, mark both on the map. Record where the crops actually grew, not just the seed packet you considered buying. If the boundary is uncertain, write “mixed or uncertain” instead of drawing a precise clean area from memory.
Cover crops belong in the record too. Minnesota's cover-crop selection guidance flags brassica mixtures before susceptible brassica vegetables and peas before another pea crop. Its planting windows and winter behavior are Minnesota guidance, not instructions for every region. Use our cover-crop planning guide for establishment and termination questions; here, record the species and family so a winter planting does not disappear from next year's history.
Make a bed-history record before cleanup
Give each growing area a durable name such as “A, fence side” or “B, patio side.” Keep the names when you redraw the plan. A north arrow, a fixed path or a photograph can help you recognize the same area later. Numbering beds again every spring can make an apparent rotation that exists only on paper.
Copy these fields for each bed or clearly mapped section. This is a written planning worksheet, not an interactive form. Unknown entries are useful: they show which decisions still need evidence.
| Record field | What to write | Why it changes the next step |
|---|---|---|
| Fixed area ID and sketch | Bed A, fence end; mark its actual boundaries | Keeps this year's crop attached to the same place next year |
| Crop sequence and year | Every spring, summer and fall crop, not just the main harvest | Shows a family that returned within the same year |
| Family for each crop | Names from a checked family list | Reveals tomato/pepper or kale/radish repeats |
| Cover crop or mixed planting | Named species; mark uncertain mixtures | Prevents treating a living cover as an empty interval |
| Problem observations | Crop, date, affected part and any diagnosis; keep a photograph | Separates a recorded symptom from an assumed disease |
| Proposed crop and constraints | Family, usable sun, planting season, support and access | Avoids moving a crop into a place that cannot accommodate it |
| Decision and review point | Accept, change or leave unresolved; say what would change the choice | Makes the next action explicit before ordering seeds |
Keep soil condition in a separate column or note. A family map does not tell you whether to add compost, correct pH or replace lost soil volume. Use the established-bed soil maintenance guide to distinguish those decisions rather than adding an amendment as a substitute for rotation.
Work through a two-bed conflict
Consider a hypothetical garden, not a performed trial. The gardener has two established beds, can grow only in those beds, and wants tomatoes every year. The recorded crops are:
| Growing year | Bed A | Bed B | What the history shows |
|---|---|---|---|
| 2025 | Tomatoes | Beans | A had nightshades; B had legumes |
| 2026 | Peppers | Tomatoes | Both beds had nightshades; A repeated the family |
| Proposed 2027 | Tomatoes | Beans | Tomatoes repeat nightshades in A again; B changes family from its 2026 crop |
Moving the proposed tomatoes to B does not remove the immediate conflict: B also held nightshades in 2026. Replacing them with eggplant does not remove it either. Calling the pepper year a “break from tomatoes” obscures the decision.
The next question is a preference question: must this garden produce a nightshade crop in 2027, or can that family pause? There is no chart that satisfies both “nightshades every year in these two beds” and “each bed gets several years without nightshades” indefinitely. That is a space constraint, not evidence that the gardener needs a particular new product.
One possible 2027 proposal is beans in A and lettuce in B, assuming the local season, crop needs and the fuller history permit them. Both differ from the 2026 family. This proposal does not establish a complete three- or four-year rotation: only two past growing years are recorded, and it says nothing about the cause of any observed plant problem. Write those limits beside the proposal.
If keeping tomatoes is the priority, record which area will repeat nightshades and ask for crop-specific advice if there was a serious or diagnosed problem. The honest result may be “repeat accepted with unresolved risk,” not “rotation completed.” An additional planting location is an option only if the household wants and can manage it; buying a container does not by itself establish disease control, appropriate growing conditions or separation from the original problem.
Choose a plan when space is limited
Start with the situation you actually have. These are planning choices, not rankings of treatments or promises of pest reduction.
| Situation | A practical planning choice | What remains unresolved |
|---|---|---|
| One bed, no known diagnosis | Record all families and consider a different family next season | A switch alone does not identify or prevent every disease |
| Two beds, one held the desired family last year | Check the other bed's longer history and whether the crop can grow there | “Not last year” is less information than a multi-year record |
| Both beds held the desired family | Reduce or pause that family, find another suitable location, or explicitly accept the repeat | There is no unused-family bed to discover by relabeling it |
| Many families grew together in both beds | Map what you can, retain uncertainty and diversify the next plan | Mixed planting is not proof of a family-free interval |
| A crop had serious unexplained symptoms | Preserve observations and seek local diagnostic guidance before repeating susceptible crops | A generic family chart is not a diagnosis or a treatment plan |
Minnesota Extension suggests combining different families for crop diversity when space will not permit rotation. This is a workable planning alternative, not a claim that diversity provides the same disease break as separated fields. Record the mixed planting so next year's map stays useful.
Check physical feasibility before finalizing a moved crop. A different bed may have different seasonal light, room for supports or access for harvest. The raised-bed layout worksheet helps check those constraints. Do not sacrifice the crop's basic growing requirements solely to make an arrow on a rotation diagram.
Finally, separate next year's plan from what to do with the bed now. Choosing a different family for spring does not tell you that there is time to start it this fall. Use the fall raised-bed decision guide to decide whether to continue a crop, harvest or close the bed using local conditions. Keep next season's family plan with that record so the same decision does not have to be reconstructed from memory.
Questions gardeners ask
What can I plant after tomatoes in a raised bed?
Choose a suitable crop from a different family after checking that area's fuller history and growing conditions. Beans or lettuce are examples of different families, not universal prescriptions. Peppers, eggplant and potatoes share the tomato family.
Do I need four raised beds to rotate crops?
No fixed bed count is required to keep a useful history or change families. The available area, crop mix and desired return interval determine what is possible. One or two beds may not accommodate the same favorite family every year with several years between repeats.
Does a winter cover crop reset the rotation?
No. Record its species and family as another crop in the sequence. A cover crop can share a family with a later vegetable, and its local establishment and termination requirements still matter.
Is moving tomatoes to the neighboring bed enough to prevent disease?
It does not establish disease prevention. Maryland Extension says rotation's effect on insect and disease pressure is limited at home-garden scale. Use the history alongside crop-specific care and diagnosis of actual symptoms.
Should I replace all the soil if I cannot rotate?
An inability to rotate is not a diagnosis or evidence that all soil needs replacing. Record the problem and seek advice appropriate to the crop, suspected cause and bed before choosing a treatment or buying replacement material.
Sources and scope
Sources read October 23, 2026. The family-history record, conflict example and decision tables are editorial planning aids created for this guide. They are not extension-prescribed crop schedules or evidence from a trial on these beds. No yield, disease-control percentage, regional planting date or product-performance claim is made.
- Wisconsin Extension: Using Crop Rotation in the Home Vegetable Garden — family grouping, general return interval and garden records; the page states a 2012 revision date.
- University of Maryland Extension: Vegetable Succession and Companion Planting — succession versus rotation and the limits of pest and disease effects in small gardens.
- University of Minnesota Extension: Promote healthy soil in your garden — family-based rotation and diversity when space is limited; reviewed in 2024.
- University of Minnesota Extension: Cover crop selection for vegetable growers — crop-family conflicts in cover crops; regional management advice must be checked locally.