Planning reference

Days to Maturity vs Harvest Window

Use days to maturity as a crop-screening number, then test the expected harvest window against frost runway, soil temperature, start method, crop tolerance, and harvest quality limits.

What each signal means

Days to maturity
Use the catalog or packet maturity estimate as a planning input, not a promised calendar date. Germination, transplant timing, weather, and harvest quality can move the real result.
Harvest window
Use the harvest window as the realistic period when the crop can be harvested at useful quality after maturity, before heat, frost, short days, or overmaturity narrow the window.
Frost runway
Use local last-frost and first-frost dates to decide whether enough days remain for establishment, maturity, and harvest before likely cold injury.
Start method
Check whether the maturity estimate is being used from outdoor sowing, indoor sowing, or transplanting. Do not mix direct-sow and transplant timing without checking the crop source.

Decision workflow

Start with the maturity estimate
Sort crops by days to maturity, then add germination time, transplant recovery, and expected harvest duration before assigning bed space.
Add frost and soil checks
Pair the maturity estimate with explicit local frost dates and soil-temperature readiness so the crop is not planted into cold soil or counted past first frost.
Separate spring from fall
Fall windows need extra caution because shortening days, cooling soil, and early freezes can slow or end harvest before the catalog number is reached.
Use succession timing
For repeated sowing, stop the next batch when the maturity estimate plus harvest window would land in heat, short days, or frost risk.
Do not promise a date
Do not treat days to maturity as a guaranteed harvest date. Use it as one signal alongside start method, frost runway, soil temperature, and crop tolerance.

Use these paths

Source basis