Crop Season Planning and Scheduling
Season Plan holds the crop schedule by week and compares it with execution on each logical land. It provides the baseline for discussions between farming and operations: what was due, what was completed and why an activity moved.
Before you begin
Select the crop and confirm the season. The approved master plan is described as fixed in this solution; actual weeks and delay reasons explain departures from it.
Navigation: Top-right screen dropdown → Season Plan.
Procedure
- Select the crop in the toolbar. The worked example uses Potato.
- Review the weekly master schedule and the On plan, Late and Upcoming totals.
- Start with the exceptions in the logical-land register, which is ordered by the worst state.
- Select the land and compare plan week, actual week, responsible team, status and reason for each activity.
- For a delay, retain the baseline and review the actual timing and reason through the configured operational process.
- Open Field Job Board for the associated request, execution and inspection history.
Responsibilities and follow-up
Agree the recovery action with operations against the specific activity and logical land. A crop-level status is useful for prioritisation, but the activity record is what explains the delay.
Example: a two-week delay
| Logical land | Activity | Plan | Actual | Reason |
|---|---|---|---|---|
| P061-26 | Land preparation | Week 24 | Week 26 | Heavy rain |
The example has six potato activities. Irrigation, planting and fertilisation show completed actual weeks, while chemical spraying and mechanical harvesting remain upcoming. Use the activity-level evidence to decide the next operational conversation; the overall “Late” status alone does not explain every step.
Important notes
Upcoming and overdue are different states. The Potato example has 60 upcoming steps and no overdue steps; the Wheat parcel example contains overdue work. Do not combine the two totals without aligning crop and period.