Crop Cycles

A field can support different crop cycles over time. Farm Manager identifies the crop and variety for the current cycle and links it to the correct field. Planned, Planted, Growing, Harvesting and Closed describe the cycle’s progress. Planting, expected harvest and actual harvest dates give the team a chronological view of the work.

Crop Cycles brings a stage board together with a chronological list and crop-delivery evidence. The team can narrow the review by field, stage and intake period. Use that view to find the cycle under discussion before checking its assigned work or accepted harvest quantities.

• Cycle identity. Keep the crop, variety and field together. Similar crop names on neighboring fields should remain separate cycles so that tasks and deliveries point to the intended work.
• Progress dates. Record planting when it happens and maintain the expected harvest date as the planning outlook changes. The actual harvest date supports the later review of what occurred during the cycle.
• Operating evidence. Field tasks reference the cycle directly. Accepted deliveries also carry that reference, allowing Farm Manager to review work and harvest evidence before closing the cycle.

Agree who creates a crop cycle and who changes its stage. Define what the farm means by the move from Growing to Harvesting, especially where harvesting takes place over several visits. Decide how the actual harvest date should represent that work and apply the convention consistently.

Set the field identity before importing cycle records. Ask the team how it will distinguish successive cycles for the same crop on the same plot. The field and cycle references must remain clear when an operator selects work or Harvest Reviewer accepts a delivery. Agree a regular review of expected harvest dates so the outlook remains useful to the crew.

Take a tomato cycle on a named field. Farm Manager begins with a planting plan and records the crop variety. After planting, the cycle moves to Planted and then Growing as the work progresses. The field’s availability record is reviewed alongside that change so the operating plan describes the same situation.

As harvest approaches, the manager checks the expected date and the assigned harvest work. A delivery should reference this cycle rather than an earlier tomato cycle on the same field. Review the accepted quantity with its unit and grade before considering the cycle complete.

Rehearse an early or delayed harvest by changing the expected date while keeping the recorded planting date intact. The team should still be able to explain the chronology. At close, review outstanding tasks and the actual harvest date with the accepted delivery evidence rather than using the stage label alone to settle the discussion.

• Crop Cycles — The cycle list and crop-delivery evidence support a field-specific progress review.
• Crop Stage Board — Active cycles are grouped by stage for the operating discussion.
• Harvest Outlook — Open cycles with harvest expected within a week or overdue stay visible for follow-up.

Use field and cycle preparation and harvest acceptance and close.