{{ headline }}
| Milestone | Date | Copy |
|---|---|---|
| {{ milestone.label }} | {{ milestone.value }} | |
| No milestones yet. | ||
| Date | Phase | Batch | Notes | Copy |
|---|---|---|---|---|
| {{ item.date }} | {{ item.phase }} | {{ item.batch }} | {{ item.notes }} | |
| No schedule items yet. | ||||
No insights yet—enter frost dates and crop details to generate analysis.
Add your frost dates and crop choice to build a sowing and harvest calendar.
Vegetable timing is mostly a matter of counting backward from a safe outdoor planting date and forward to a likely harvest. This planner turns that chain into one working calendar by combining your average last spring frost, an optional first fall frost, crop timing, and a few decisions about how you want the season to run.
It is useful when you want a vegetable planting calendar based on frost dates and do not want to keep separate notes for seed trays, bed preparation, later sowings, and harvest timing. You enter the frost dates, pick a USDA zone from 3 through 11, choose tomato, pepper, lettuce, bush bean, kale, carrot, or a custom crop profile, and then decide whether the goal is steady kitchen picking, a bigger preserving wave, or a rolling succession.
The outputs are split on purpose. Summary badges surface the first dates and risk numbers worth checking. Season Milestones keeps only the main anchors. Planting Schedule expands the result into date-sorted tasks for the main crop and each later succession. Planting Insights condenses the same plan into short notes. Season Timeline charts the main crop phases only, from the earliest start step through the modeled harvest window. JSON and export actions let you hand the plan to someone else without rebuilding it manually.
The scheduling math, chart rendering, and file exports are produced in your browser after the page loads. That keeps the calculation local, but a saved CSV, DOCX, image, or JSON file can still reveal what you plan to grow and when each bed turns over.
USDA hardiness zones add climate context, not a full planting calendar. The USDA explains that the zone map is based on average annual extreme minimum winter temperatures over a 30-year period. In this planner, the frost dates you enter do most of the real scheduling work, while the chosen zone adds a label, a note, and a fall-side padding rule.
The model validates the two date anchors first. Last spring frost must be a real calendar date, and the optional first fall frost must be later than the spring date. Numeric inputs are then clamped to the built-in ranges: days to maturity from 25 to 180, transplant lead from 0 to 16 weeks, season extension from 0 to 6 weeks, hardening from 0 to 14 days, successions from 1 to 6, bed-prep lead from 0 to 21 days, and fixed succession override from 0 to 60 days.
Spring timing depends on crop sensitivity and planting method. Frost-sensitive presets use a 7-day spring buffer. The others use a 3-day buffer. For transplants, season extension can reduce that wait, but never below zero. For direct sowing, the planner uses a shorter default delay of 3 days after spring frost and lets extension remove up to those 3 days. Custom mode keeps your chosen maturity and lead values, but the rest of the model falls back to tool defaults: a 5-day spring buffer, a 21-day base succession gap, and a 45-day harvest window.
The date rules below describe the tool's main schedule model.
| Symbol | Meaning here | Practical reading |
|---|---|---|
Fspring |
Last spring frost date | The early-season anchor you enter. |
Ffall |
First fall frost date | The late-season cap, when provided. |
B |
Spring buffer in days | 7 days for frost-sensitive presets, 3 days for the others, 5 days in custom mode. |
E |
Season extension in days | Weeks entered by you, converted to days by the planner. |
L and H |
Lead weeks and hardening days | Used only when you keep a transplant workflow. |
M and W |
Maturity days and harvest window | These push the calendar forward from the main field date. |
Pzone |
Zone padding | A built-in number of days subtracted from the fall side of the season. |
I |
Succession interval | Comes from the preset, the harvest goal, or your fixed override. |
| Preset | Maturity | Lead | Base gap | Harvest window | Direct sow default |
|---|---|---|---|---|---|
| Tomato (indeterminate) | 75 d | 6 wk | 28 d | 70 d | No |
| Pepper (sweet) | 80 d | 8 wk | 32 d | 60 d | No |
| Lettuce (butterhead) | 55 d | 3 wk | 14 d | 28 d | No |
| Bush bean | 58 d | 0 wk | 18 d | 35 d | Yes |
| Kale | 60 d | 4 wk | 30 d | 90 d | No |
| Carrot | 70 d | 0 wk | 21 d | 45 d | Yes |
| Custom | You set it | You set it | 21 d | 45 d | You decide |
Fall logic is deliberately tighter than spring logic. If you enter a first fall frost date, the planner calculates a default harvest-close date from the preset window, then compares it with a frost-based cap. Extension can help on the fall side, but only up to 21 extra days before zone padding is subtracted. That means a large extension value does not turn a short autumn into an unlimited late-season window.
| Zone | USDA winter range | Fall padding in tool |
|---|---|---|
| 3 | -40 to -30 °F | 21 d |
| 4 | -30 to -20 °F | 18 d |
| 5 | -20 to -10 °F | 14 d |
| 6 | -10 to 0 °F | 10 d |
| 7 | 0 to 10 °F | 7 d |
| 8 | 10 to 20 °F | 5 d |
| 9 | 20 to 30 °F | 3 d |
| 10 | 30 to 40 °F | 2 d |
| 11 | 40 to 50 °F | 0 d |
Succession spacing is also rule based. Without an override, the planner starts with the preset gap, tightens it for Fresh table, widens it for Preserving batch, and keeps the preset rhythm for Succession harvest. Any later planting whose field date would fall after the modeled harvest end is dropped. The main milestones and the timeline stay focused on the main crop, while those later batches remain visible in the schedule and insights.
Start with local frost records before touching any of the other controls. Average frost dates are still estimates, but they are much closer to planting reality than a zone label alone. For tender crops such as tomatoes and peppers, it is usually smarter to enter a conservative spring date than to trust an optimistic guess and then lose the first planting to a late cold night.
Next, choose the preset that most closely matches the crop and growth habit you actually plan to grow. Days to maturity are guides, not guarantees. Extension guidance regularly points out that weather and day length can slow ripening, especially for warm-season crops in shorter seasons. If your seed packet or local experience differs from the built-in preset, switch to Custom instead of forcing the preset to do a job it was not built for.
The harvest goal changes cadence, not crop biology. Fresh table is for steadier picking. Preserving batch pushes the plantings farther apart so harvest arrives in larger waves. Succession harvest keeps the preset rhythm. If you already know the spacing you want, the fixed succession override is the cleanest control because it replaces the goal-based gap directly.
| If you need to decide... | Check this first | Why it matters most |
|---|---|---|
| Whether a transplant crop fits your spring start | Spring frost, season extension, and preset choice | Those values set the main field date and every backward-counted indoor task. |
| Whether harvest should be steady or concentrated | Harvest goal, successions, and any fixed gap | Those controls reshape the rhythm of later plantings without changing maturity days. |
| Whether indoor work should disappear from the plan | Direct sow | Turning it on removes seed-start and hardening phases and changes the main field-date path. |
| Whether soil work needs its own reminder | Bed prep lead | This adds separate bed-prep tasks before the main crop and every later succession. |
| Whether the advisory note should stay repeatable | Notes seed | It locks the wording choice for the note without changing any dates. |
Use the transplant and direct-sow paths honestly. Bush beans and carrots often make sense as direct-sown crops, while tomatoes and peppers usually need a longer indoor lead. The tool lets you override those defaults, but it does not know your soil temperature or how much protection you actually have. University guidance on seed starting and season extension still matters here: hardening off is gradual, row covers need venting on warm days, and direct seeding into cold soil can delay or weaken emergence.
Treat the plan as a baseline that you adjust with local notes. If a bed stays wet, a low spot frosts early, or one cultivar consistently ripens slower than the packet suggests, capture that in your own records and move the inputs next time. The planner is most valuable when it stays tied to what your site actually does.
The summary badges are the fastest reality check. Start, Transplant, and Harvest show the main path through the season. Successions tells you how many plantings actually fit, not just how many you requested. When a fall frost date is present, the planner also shows the frost-window length and harvest buffer. A positive buffer means harvest ends before the frost date. Zero means the plan runs right to the edge. A negative value means the model expects harvest to continue past frost and flags the plan as risky.
The detailed tabs each answer a different question. The trick is knowing what each view does not show.
| View | Best use | What it leaves out |
|---|---|---|
| Summary badges | Quick sense check before you read the full plan. | They do not list every later batch or every prep task. |
| Season Milestones | Main anchors such as seed start, hardening, field date, harvest open, and final harvest push. | Later successions are not listed here. |
| Planting Schedule | Complete chronological task list for the main crop and each later succession. | It is a work list, not a visual duration chart. |
| Planting Insights | Short interpretation bullets built from the same plan and any seeded note variation. | The note is guidance, not a weather forecast or disease model. |
| Season Timeline | Main crop phase durations from the first anchor to harvest, with PNG, WebP, JPEG, and CSV downloads. | Later successions are not drawn as separate bars. |
| JSON | Structured handoff that includes inputs, outputs, badges, metrics, insights, and errors. | It is detailed, but still only reflects the tool's current model. |
A reduced succession count is not a bug. It means the next planned field date would have landed after the modeled harvest end, so the planner refused to force it into a season that no longer supports it. The same logic explains the season risk note. If the harvest window overruns the fall frost or leaves only a narrow buffer, the note warns you to shorten maturity, tighten the plan, or prepare stronger protection.
When no first fall frost date is entered, the planner can still build a calendar, but it loses the most useful late-season checks. You still get dates, yet you do not get a frost window, a harvest buffer, or a fall-based cap. That makes the result easier to read, but less complete for crops that need to finish before a hard stop in autumn.
Using the shipped defaults, the planner starts with a last spring frost of 2025-04-20, a first fall frost of 2025-10-05, zone 6, the indeterminate tomato preset, 2 weeks of season extension, 7 hardening days, and 3 successions. Because tomatoes are treated as frost sensitive, the 7-day spring buffer is fully canceled by the 14 extension days, so the main transplant date lands on 2025-04-20.
The backward count sets seed starting on 2025-03-02 and hardening on 2025-04-13. The forward count opens harvest on 2025-07-04 and closes the default tomato window on 2025-09-12. The next two field dates fall on 2025-05-18 and 2025-06-15, so all 3 planned plantings fit. With the default fall frost, that leaves a 23-day harvest buffer.
Now switch to the bush bean preset, leave direct sow on, keep the same frost dates, and add a 5-day bed-prep lead. Bush beans skip indoor propagation here, so the main sowing date stays at 2025-04-20 and the separate prep task lands on 2025-04-15. With the preset gap of 18 days and 3 requested successions, the later sowings fall on 2025-05-08 and 2025-05-26.
Harvest opens on 2025-06-17 and closes on 2025-07-22. The milestone list stays short because there is no indoor phase, but the full schedule still records the extra prep and sowing dates. This is the kind of plan that benefits most from the schedule tab rather than the milestone tab.
Take the sweet pepper preset, keep the same frost dates and extension, change the goal to Preserving batch, and enter a fixed succession override of 35 days. The main transplant date still lands on 2025-04-20, but the longer preset lead pushes seed starting back to 2025-02-16, with hardening on 2025-04-13. Harvest opens on 2025-07-09 and the built-in 60-day harvest window ends on 2025-09-07.
The fixed 35-day spacing produces later field dates on 2025-05-25 and 2025-06-29. That creates wider harvest waves than the default cadence and is easier to match with canning or other preserving sessions. If you asked for more batches after that, the planner would keep adding them only until the next field date moved past the modeled harvest end.
No. The zone selector adds a climate label, a zone note, and the tool's fall-padding rule. The spring and fall frost dates you enter are still the main date anchors.
The planner still builds the schedule, but it stops using a frost-based cap for the harvest end. The result falls back to the preset or custom harvest window and does not show a frost buffer.
Later field dates are added only while they still fall on or before the modeled harvest end. Once the next planting would land outside that window, the planner trims it away.
That value is used only to stabilize the wording choice in the advisory note. The calendar itself is built from the date, crop, and timing inputs.
The chart is built from the main crop phases only: seed start, hardening, bed prep, field date, outdoor growth, and harvest window. Later successions are listed in the Planting Schedule instead.
This slug does not ship a separate server-side planning helper. The date math, charting, copy actions, and downloads are created in the browser after the page assets load.