Using SowWindow
Create and edit sowing batches
The succession planner turns a start date, an end date, and a whole-day interval into a list of sowing tasks. It counts dates, not harvests. Use a crop reference or your own clearly stated assumption to decide whether the sequence makes sense for the crop and season.
Reviewed Oct 28, 2026
Set the three scheduling inputs
Choose the crop and the intended harvest stage when the preset distinguishes one. Enter the full first-sowing date, last allowed date, and a positive interval in days. The last allowed date must not precede the first date.
A source-suggested interval remains editable. If you change it, treat the new number as your own assumption. Check whether the source has a separate later-season cutoff; an interval alone does not decide how late planting can continue.
Understand the inclusive cutoff
The first date is always a batch when the inputs form a valid sequence. The planner then adds the interval repeatedly. A date on the cutoff is included; a date after it is not.
| First date | Last allowed date | Interval | Generated dates |
|---|---|---|---|
| April 1, 2027 | May 1, 2027 | 14 days | April 1, April 15, April 29 |
| April 1, 2027 | May 1, 2027 | 10 days | April 1, April 11, April 21, May 1 |
Check the generated list before adding it
Inspect the batch count and the first and last dates. Read the cutoff explanation if the next interval would fall outside the plan. Confirm that each row says what you intend to do, and that a growing-condition note has not been mistaken for an automatic weather check.
- Generate the dates.
- Review the source or custom-interval label.
- Check whether the last batch still has a suitable season and a place to grow.
- Add the batches to the plan and give useful notes to each one.
Use full years for a cross-year plan
Enter the next year on the ending date when the sequence crosses December. For example, December 20, 2027 to January 20, 2028 at a 14-day interval gives December 20, January 3, and January 17. These dates demonstrate ordering only; they are not a recommendation for a particular climate.
Do not infer a planting season from a month name alone. Keep the location-specific reasoning in your own notes and the crop reference conditions alongside the schedule.
Edit without losing work
Once added, batches can carry their own dates, notes, and completion status. Before changing the interval or rebuilding a sequence, decide which individual changes need to remain. A revised generated sequence is not automatically the same record as every task you have already edited.
Keep a JSON backup before replacing a complex schedule. If an input is invalid, correct the field while retaining the other values. Export CSV for a simple dated list or JSON when you need to keep the editable plan and its assumptions.