Keeping dates useful
Update a plan when your dates change
A planting plan should be easy to revise. The difficult part is deciding which dates should follow a new assumption and which dates represent a choice you made on purpose. Treat that review as part of the change, rather than replacing every date in one step.
Reviewed Oct 27, 2026
Make a backup when the current plan matters
Before a substantial change, download the plan as JSON or duplicate it. This gives you a version to compare with the revised schedule. A printed list is helpful for comparison, but it does not preserve the complete editable settings.
Check the saved-state message as well. If the current browser has not saved your changes, keep the page open and download a backup. Changing dates in an unsaved plan is still possible, but closing the page can remove the only current copy.
Change the anchor, then inspect what depends on it
Update the full frost date, including the year. Tasks generated from that anchor can be recalculated using their recorded timing rules. Other tasks may have a different basis, such as a user-entered batch start or a selected transplant date.
Read the proposed results before accepting them. A source-based window and a manual date should remain distinguishable. If you intentionally moved a task, keep that edit unless you explicitly decide to return it to the calculated timing.
Keep source updates separate from date changes
Changing your frost date does not mean you have chosen to replace every crop parameter with a new data version. Saved plans retain their recorded assumptions so that an earlier plan remains explainable. Review any proposed data update before applying it.
If you switch to a different guide or growing method, add a note about that choice. A new source can describe a different scope rather than a simple correction to the old value. Do not silently average conflicting guidance.
Refresh the copies you work from
After reviewing the tasks, save the plan and produce new exports as needed. Old PDFs and CSVs remain old snapshots. Calendar applications also have their own import behavior, so inspect an updated calendar import for duplicates rather than assuming that every application will replace existing events.
Keep one current working copy clearly named. If you retain the old version, make the season or revision obvious enough that you will not accidentally print it when you are heading outside.