These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Farm Management System
- Features
- Crop cycles
Crop cycles
Follow each crop and variety from plan through harvest and close.
OverviewPlanned Crop Cycles×
Farm Management System · Crop cycles
New
Planned Crop Cycles
Approval conditions
| Crop name | Variety | Field | Expected harvest | Status | |
|---|---|---|---|---|---|
| Crop 852 | VRT-962 | FLD-2503 | 09 Oct | Planned | |
| Crop 522 | VRT-685 | FLD-6866 | 03 Oct | Planned | |
| Crop 525 | VRT-312 | FLD-8069 | 16 Oct | Planned | |
| Crop 105 | VRT-467 | FLD-8103 | 18 Oct | Planned | |
| Crop 875 | VRT-734 | FLD-8059 | 19 Oct | Planned |
6 of 6 records
Crop 852Crop cycles · CC-77802
PlannedVarietyVRT-962
FieldFLD-2503
Expected harvest09 Oct
What you can do
Work from the field record
A cycle belongs to a field. Give the crop and variety clear names, record the expected harvest date and move the cycle through planned, planted, growing, harvesting and closed as work occurs. The Crop Cycles screen presents stage and field filters alongside a chronological list and harvest evidence.
How the work is organized
- Identify the work. Link the crop and variety to the correct field before setting its expected harvest.
- Record the event. Record planting and actual harvest dates when those events occur.
- Review the result. Farm Manager changes the cycle stage as planting, growing and harvest work progresses.
Agree when a planting date is recorded, who changes the stage, and how an actual harvest date is distinguished from the expected date. These choices make the board useful during a busy season. A closed cycle should have its harvest work reviewed before the next plan relies on it.
What to agree during setup
Agree who records the planted and actual harvest dates and when Farm Manager moves a cycle to Harvesting or Closed. Keep the linked People and Users records current so the named operator or reviewer can be found during the rehearsal.
Check the handoff on an actual case
Take a growing crop whose expected harvest has moved. Check the field, planting date and current stage; compare due field work with the expected harvest. When harvest starts, follow the linked harvest record and its reviewed quantity instead of substituting a scouting estimate.
Ask Field Operator to compare the current stage with due tasks. Harvest Reviewer then checks the separate harvest quantity and its unit before Farm Manager closes the cycle. Open the live record again after a deliberate change and agree who corrects it before the next step.
Use the board to find the cycle for a particular field and stage, then open its dated record before changing the plan. Expected harvest belongs to the plan; harvested quantity belongs to the harvest record. Keeping those separate lets Harvest Reviewer inspect the measured result after the field work changes.
What your team sees
- Crop Cycle Board — Shows crop stages by field and current cycle.
- Active Crop Cycles — Lists planted, growing and harvesting cycles with their dates.
Follow the work through
See the field-to-harvest flow and the data model. The implementation guide gives a small rehearsal scope before a wider operating cycle.
What it keeps track of
Data model- Crop cycles
- Crop cycles per field from planned planting through growing, harvesting and close
- Fields
- Farm fields and plots with area, location and availability status
- Harvests
- Harvested quantities with unit and grade, accepted by a reviewer
Who uses it
Permissions- Farm Manager
- , Field Operator, Harvest Reviewer.
- Farm Manager
- Owns the stage; Field Operator follows work; Harvest Reviewer checks the linked harvest.
Set up Farm Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.