Most farm software asks you to create a season, then asks you to file every record under one. Intecrop does not. A season here is a view over records that already carry a date, and it is derived, never stored.
That difference explains most of what is surprising about seasons in this app, so it is worth understanding once.
A season is twelve months, anchored to a month you choose
Each crop on each production unit carries a starting month. Together with a year, that names a window of exactly twelve months: from the first of the starting month in that year, up to but not including the first of the same month the following year.
A table grape crop with a starting month of July has these seasons:
| Season | Runs from | Up to (excluded) |
|---|---|---|
| 2024 | 1 July 2024 | 1 July 2025 |
| 2025 | 1 July 2025 | 1 July 2026 |
| 2026 | 1 July 2026 | 1 July 2027 |
The label is the opening year. The 2025 season runs into 2026, and an application dated March 2026 belongs to it.
The first of the starting month opens the new season
The boundary is half-open: the first of the starting month belongs to the season it opens, not the one it closes. So with a July starting month, 30 June 2026 falls in the 2025 season and 1 July 2026 falls in the 2026 season. There is no day that belongs to both, and no day that belongs to neither.
Different crops can be in different seasons on the same day
The starting month is set per crop per production unit, not per farm. A farm growing table grapes with a July start and citrus with a March start is, on any given day in May, in the 2025 grape season and the 2025 citrus season — but the grape season is ten months old and the citrus season is two.
This is deliberate. A season boundary should sit in the quiet part of that crop's year, and different crops are quiet at different times. It does mean that "the current season" is only a well-formed question once you have said which crop.
Nothing is filed into a season
Because the window is derived from a date, there is no season field on an application, a block, or a chemical record — and no way to file something into the wrong season. Change the date and the record moves. Change the starting month and every record on that crop is regrouped, historically as well as going forward.
The cost of that design is the one thing that catches people out: moving a starting month is not a small edit. It silently redraws every season boundary that crop has ever had, so a report you ran last week may not reproduce. Move it deliberately, and expect the history to shift with it.
What "this season" means when you have not chosen one
Reports default to the season containing today, resolved per crop against that crop's own starting month. When you pick a season explicitly, that label is used for every crop in the report — the same year, but each crop's own twelve-month window around it.