Garden Calendar Planner

{{ cropCount }} crop{{ cropCount === 1 ? '' : 's' }} {{ bedCount }} bed note{{ bedCount === 1 ? '' : 's' }} {{ seasonLabel }} {{ planHorizonLabel }} {{ frostModeLabel }} {{ successionWaveLabel }}

Climate zone:

Use a zone or region label that will make sense in your garden notes.

Season:

Pick the planting season that anchors the task windows.

Start date:

Use the week you want to begin prep, sowing, or transplanting work.

Last spring frost date:

Use your local average last frost date, then adjust the output for microclimates and current weather.

First fall frost date:

Use your local average first fall frost date to bound late sowings and harvest windows.

Frost planning behavior:

Choose which frost-aware artifact should get the strongest planning emphasis.

Planning horizon:

Short plans stay focused; longer plans include more follow-up reminders.

weeks

Succession interval:

Short intervals smooth harvests; longer intervals reduce weekly workload.

days

Succession wave count:

Use fewer waves for long-season crops and more for quick greens, roots, and herbs.

waves

Crops:

One crop per line keeps the calendar and bed assignment tables readable.

Bed notes:

Use bed names, sun limits, irrigation notes, or rotation constraints.

Calendar inputs need attention

{{ warning }}

Window	Crop	Task	Target date	Bed note	Copy
{{ row.window }}	{{ row.crop }}	{{ row.task }}	{{ row.date }}	{{ row.bedNote }}
No calendar rows yet Add at least one crop and a valid start date to build seasonal tasks.

Crop	Start method	Indoor sow/start	Harden-off starts	Transplant/direct-sow	Last feasible sow	Planning note	Copy
{{ row.crop }}	{{ row.method }}	{{ row.indoorStart }}	{{ row.hardenOff }}	{{ row.transplantOrDirect }}	{{ row.lastFeasibleSow }}	{{ row.note }}
No seed-starting rows yet Add crops and a valid last spring frost date to build indoor start, harden-off, and transplant dates.

Crop	Wave	Sow/start date	Plant/transplant date	Harvest window	Last feasible sow	Feasibility note	Copy
{{ row.crop }}	{{ row.wave }}	{{ row.sowDate }}	{{ row.plantDate }}	{{ row.harvestWindow }}	{{ row.lastFeasibleSow }}	{{ row.note }}
No succession waves yet Add crops and valid frost dates to calculate repeated sowings, harvest windows, and fall cutoffs.

Add at least one crop and a valid start date to render the workload heatmap.

Crop	Bed slot	Calendar window	Prep and rotation note	Copy
{{ row.crop }}	{{ row.bed }}	{{ row.window }}	{{ row.note }}
No bed assignments yet Add crops and bed notes to map the rotation plan.

Due date	Focus	Cadence	Action	Copy
{{ row.date }}	{{ row.focus }}	{{ row.cadence }}	{{ row.action }}
No follow-ups yet Add crops and a start date to generate follow-up reminders.

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Vegetable garden calendars translate crop biology into dated work: seed starting, bed preparation, planting, follow-up checks, and harvest windows. Lettuce, basil, tomatoes, peppers, beans, roots, and greens all respond differently to cold soil, frost risk, heat, day length, transplant shock, and the number of days they need before harvest. A useful plan keeps those differences visible before seed trays, beds, and weekend chores start competing for the same few days.

Frost dates are the most common anchors because they describe the normal edges of an outdoor growing season. The average last spring frost helps decide when tender crops can move outside and how far back indoor seed starting should begin. The average first fall frost helps decide whether a late sowing has enough time to mature. These dates are planning estimates, not promises. A low yard, windy balcony, raised bed, protected tunnel, or unusually warm spring can shift the real planting window.

Planning anchor	Question it answers	Common mistake
Hardiness zone or region	Which broad climate label belongs in the garden notes.	Treating a zone as a complete vegetable schedule. Hardiness zones describe winter cold better than spring soil warmth or fall timing.
Last spring frost	When frost-sensitive crops can usually move outdoors and when indoor starts should begin.	Transplanting tender plants on the calendar date without checking the short-term forecast and soil conditions.
First fall frost	Whether a late sowing has enough days to mature before cold weather closes the season.	Counting only the seed packet maturity days and forgetting a frost buffer, harvest window, or transplant lead time.
Succession interval	How far apart repeated sowings should be so harvests are spread out.	Repeating every crop even when a long-season crop is better handled as one main planting plus replacement starts.
Bed note	Which growing space, sun condition, irrigation setup, or rotation constraint should travel with each crop.	Scheduling dates first and discovering later that the trellis, shade, water, or crop-family rotation does not fit.

Vegetable garden timeline showing seed starts before last frost, planting waves, and fall harvest runway — Frost dates, repeated sowings, and harvest windows pull the calendar in different directions.

Succession planting solves a different problem from first planting dates. Instead of sowing all of a fast crop at once, repeated smaller sowings can keep lettuce, radishes, beans, herbs, greens, and roots coming in manageable amounts. The interval matters. A seven day interval can create a steady stream for quick greens, while a two or three week interval often makes more sense when each crop needs more space or harvest labor.

A good calendar also protects workload and bed logic. A date can be horticulturally reasonable and still be impractical if it puts bed prep, transplanting, thinning, trellising, watering checks, and harvest all into one crowded week. Crop timing is strongest when it is checked against the actual spaces available, the seed packet or cultivar days to maturity, the local extension calendar, and the weather that is happening now.

How to Use This Tool:

Start with the garden facts that decide the season, then use the result tabs to compare calendar dates, frost-aware seed starts, repeated sowings, bed assignments, and weekly workload.

Enter a Climate zone or region label that will make sense in your garden notes. Use a hardiness zone, frost band, city region, or another local label you normally use for planting decisions.
Choose the Season and set the Start date. The seasonal choice changes the general wording for prep, planting, follow-up, and harvest tasks, while the start date anchors the visible calendar rows.
Add the Last spring frost date and First fall frost date. If either date is missing or the fall frost is not after the spring frost, the warning area explains what needs attention before seed-starting and cutoff dates are useful.
Select Frost planning behavior. Use Calendar + starts + waves for a balanced plan, Seed-starting emphasis when indoor sowing and transplant timing are the main concern, or Succession emphasis when repeated sowings and fall cutoffs matter most.
Set the Planning horizon, Succession interval, and Succession wave count. Shorter horizons keep the calendar focused, shorter intervals pack repeated sowings closer together, and more waves produce more rows per crop.
List one crop per line in Crops. Add one bed, container, sun, irrigation, or rotation note per line in Bed notes so the Bed Assignments result has real planning context.
Read Seasonal Calendar first, then compare Seed-starting Schedule, Succession Waves, Garden Workload Heatmap, Bed Assignments, and Follow-up Checklist. Use the warnings and any "past the last feasible sow date" notes as prompts to revise dates, intervals, crop choices, or bed notes.

Interpreting Results:

The Seasonal Calendar is the high-level work plan. Each crop receives prep, planting, and follow-up rows shifted through the selected horizon so every crop does not start on the same week. The task wording follows the selected season, so a summer plan emphasizes shade, irrigation, heat stress, and frequent harvest while a fall plan emphasizes clearing beds, cold snaps, and harvest before frost.

The Seed-starting Schedule should be checked against the crop row, not just the date. Some crops are treated as indoor starts, some as direct-sown, and some can use either path. An unknown crop uses a generic vegetable default and says so in the planning note, which is a sign to check the seed packet or local extension calendar before sowing.

The Succession Waves table is most useful for fast or repeatable crops. A wave marked feasible is still an estimate, because real maturity depends on cultivar, soil temperature, light, and stress. A wave marked past the last feasible sow date should not be treated as impossible, but it needs a corrective choice such as season protection, transplants, a shorter-maturity cultivar, or skipping that wave.

Garden Workload Heatmap: look for weeks where several crops show planting or follow-up work at once, then move lower-priority tasks before the week becomes unrealistic.
Bed Assignments: use the rows as a draft. Crop-family rotation, trellis height, irrigation, and spacing can override a simple rotating bed note.
Follow-up Checklist: use these reminders for germination, transplant recovery, thinning, irrigation, pests, yield timing, and gaps in the next succession sowing.

The strongest false-confidence risk is trusting a date because it looks exact. Treat the result as a structured draft, then verify the frost dates, seed packet days to maturity, current forecast, soil temperature, and any crop-specific local advice before planting.

Technical Details:

Garden calendar math combines three timing systems. Calendar spacing distributes visible prep, planting, and follow-up tasks across the selected horizon. Frost math works in both directions: indoor seed starts count backward from the average last spring frost, while late sowing cutoffs count backward from the average first fall frost. Succession math repeats sowing or start dates by a fixed interval and checks whether each repeated wave still has enough days before fall frost.

The crop defaults are deterministic. Recognized vegetables such as tomato, basil, lettuce, broccoli, cabbage, kale, spinach, beans, cucurbits, peppers, eggplant, onions, corn, roots, and greens receive built-in method, lead-time, maturity, harvest-window, succession, and frost-buffer values. Unrecognized crop names receive a generic vegetable plan, which keeps the calendar filled while clearly signaling that crop-specific timing should be verified.

Formula Core:

Rule	Formula or boundary	Meaning
Horizon days	$H_{days} = 7 H_{weeks}$	The planning horizon is converted from weeks to days.
Crop spacing	$S_{days} = \max (7, ⌊ \frac{H_{days}}{\max} ⌋)$	Crop starts are spaced at least seven days apart, with wider spacing when the horizon allows.
Calendar offset	$O_{i} = i S_{days}$	Crop index i determines how far from the start date that crop begins.
Visible task dates	Prep = start date + offset; plant = prep + 7 days; follow-up = prep + 21 days.	Every listed crop receives the same three visible calendar checkpoints, shifted by crop order.
Indoor start	$D_{start} = D_{last frost} - 7 W_{indoor}$	Indoor seed-start timing counts back from the last spring frost by the crop default number of weeks.
Fall cutoff	$D_{last sow} = D_{first frost} - (M + B + L)$	Days to maturity M, frost buffer B, and indoor lead time L are subtracted from the first fall frost.
Succession wave	$D_{wave j} = \max (D_{spring sow}, D_{start}) + j I$	Each wave starts from the later of the crop's spring sowing date and the plan start date, then adds the selected interval I.

With a 12 week horizon and three crops, the spacing formula uses 84 days divided by five, rounded down to 16 days. The first, second, and third crop therefore begin at offsets of 0, 16, and 32 days. If the start date is May 15, 2026, the prep rows fall on May 15, May 31, and June 16 before each crop receives planting and follow-up rows one and three weeks after its own prep date.

Rules and Boundaries:

Area	Applied rule	Planning effect
Planning horizon	Accepted values are clamped from 4 to 24 weeks.	Very short plans stay focused; longer plans spread crop rows and follow-up reminders farther out.
Succession interval	Accepted values are clamped from 7 to 45 days.	Short intervals create denser repeated sowings; long intervals reduce weekly workload.
Succession wave count	Accepted values are clamped from 1 to 8 waves.	Each additional wave adds another sowing, planting, harvest-window, and feasibility check per crop.
Crop matching	Crop names are matched against common aliases. Unknown names use the generic vegetable default.	Common crops get more specific lead times, while unusual crops still appear in the plan with a verification note.
Feasibility note	A wave is late when its sow or start date is after the calculated last feasible sow date.	Late rows call for protection, nursery starts, a faster cultivar, or skipping the wave.
Bed assignment	Bed notes rotate through the crop list when the counts differ.	The rows stay filled, but rotation, spacing, irrigation, and support needs still need gardener judgment.

Accuracy and Privacy Notes:

The calendar is a planning model, not a local horticulture forecast. It does not measure soil temperature, check current weather, know your cultivar, inspect a microclimate, or confirm crop-family rotation. After the browser loads the planner, calculations run in the browser; copying, downloading, or sharing any generated text is controlled by the person using it.

Use average frost dates as planning anchors, then check current forecasts before transplanting tender crops.
Confirm crop-specific seed-start and days-to-maturity values on the seed packet or a local extension calendar.
Adjust the result for protected culture, raised beds, containers, wind exposure, slope, shade, irrigation, and pest pressure.
Move tasks manually when the workload heatmap shows too many planting or follow-up jobs in the same week.

Worked Examples:

A spring plan for tomato, basil, and lettuce with a May 15, 2026 start date, an April 15 last spring frost, an October 15 first fall frost, a 12 week horizon, four waves, and a 14 day interval spreads the Seasonal Calendar prep rows across May 15, May 31, and June 16. The Seed-starting Schedule puts tomato indoor sowing on February 25, hardening-off on April 18, and transplanting on April 25. That gives the tomato row a precise date set, but the gardener should still wait if nights are cold or the transplant space is not ready.

The same spring plan treats basil as a repeatable tender herb. In Succession Waves, basil waves starting May 15, May 29, June 12, and June 26 stay before the August 7 last feasible sow date and show harvest windows into late summer or early fall. Tomato waves using the same 14 day interval become less reliable after the second wave because later indoor-start timing pushes harvest into the fall frost window.

A troubleshooting case starts with an empty Crops field or a first fall frost date that comes before the last spring frost date. The warning area reports the missing crop list or reversed frost dates, and the affected tables stay empty or less useful. Adding one crop per line and fixing the frost order restores the calendar rows, seed-start rows, succession waves, and follow-up checklist.

FAQ:

Can this give the exact best planting date for my garden?

No. It builds dated rows from the season, start date, frost dates, crop defaults, and succession settings you enter. Use the result as a planning draft, then confirm soil temperature, forecast, seed packet guidance, and local extension advice.

Why does a crop show "Generic crop default"?

The crop name did not match a built-in common vegetable alias. The row still receives conservative timing so the plan stays usable, but the planning note is a reminder to verify that crop's real seed-start, transplant, and maturity needs.

Why are some succession waves marked late?

A wave is marked late when its sow or start date comes after the calculated last feasible sow date before first fall frost. A late wave may still work with protection or transplants, but it should not be treated as a normal-risk sowing.

What should I do when the workload heatmap looks crowded?

Move lower-priority sowings, reduce the succession wave count, lengthen the succession interval, or split prep and planting across more days. The heatmap is meant to expose calendar pressure before the work becomes hard to finish.

Do bed notes replace crop rotation planning?

No. Bed notes rotate through the crop list so every row has a space or constraint attached. Check the Bed Assignments rows against crop family rotation, spacing, supports, shade, and irrigation before planting.

Glossary:

Hardiness zone: A broad climate label based on average extreme winter cold, useful for garden notes but not a complete vegetable planting schedule.
Last spring frost: The average final spring frost date used to time tender transplants and indoor seed starts.
First fall frost: The average first autumn frost date used to estimate late sowing cutoffs and harvest runway.
Days to maturity: The estimated number of days a crop needs from sowing, transplanting, or outdoor establishment to harvest.
Succession planting: Repeated sowing or planting at set intervals so harvest is spread across more of the season.
Frost buffer: Extra days reserved before the first fall frost to reduce the risk that a crop runs out of warm enough growing time.
Harvest window: The estimated period when a crop is likely to be picked after it reaches maturity.
Bed assignment: The growing space, container, sun note, irrigation note, or rotation constraint attached to a crop row.

References:

USDA Plant Hardiness Zone Map, USDA Agricultural Research Service, 2023.
Planting the Vegetable Garden, University of Minnesota Extension.
Growing Vegetables: When to Plant Your Vegetable Garden, University of New Hampshire Extension.
Succession Planting, Oregon State University Extension Service.
Vegetable Planting Calendar for Central Maryland, University of Maryland Extension, March 2026.
When to Plant, Illinois Extension.