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.
- Plantation Management
- Features
- Harvest records
Harvest records
Capture crop quantities and block rounds with the right field context.
OverviewHarvest Rounds Log×
Plantation Management · Harvest records
New
Harvest Rounds Log
Harvest rounds
| Block | Harvested at | Weight KG | Grade | Crew lead | |
|---|---|---|---|---|---|
| PB-9260 | 07 Oct | 530 | GRD-708 | ||
| PB-4524 | 13 Oct | 130 | GRD-475 | ||
| PB-8238 | 15 Oct | 70 | GRD-600 | ||
| PB-2497 | 07 Oct | 500 | GRD-802 | ||
| PB-7828 | 05 Oct | 960 | GRD-785 |
6 of 6 records
GRD-708Harvest rounds · HR-90724
BlockPB-9260
Harvested at07 Oct
Weight KG530
What you can do
Keep crop harvest and block round distinct
A crop harvest records date, quantity, unit and grade against a crop cycle. It also points to the person who accepts it. The cycle gathers harvest count and accepted harvest quantity for yield review. A block harvest round records a different perspective: its block, date, weight in kilograms, grade and crew lead. Its block carries variety and planting year, and the accumulated round weight belongs to that block.
These records help answer different questions. A plantation manager can ask how much of a cycle’s crop has been accepted and compare yield against the field area. A crew lead can ask how much a particular block contributed across rounds. When both records describe the same physical harvest, agree how the team reconciles them. Do not add the block weight to crop quantity unless units and scope are aligned.
How the work is organized
- Block capture. Field Operator chooses the planted block, records the harvest date, measured weight and grade, and names the Crew Lead.
- Cycle capture. Field Operator enters a crop harvest with its cycle, quantity, unit and grade.
- Review. Harvest Reviewer checks the crop harvest against its cycle and records the accepting person; Plantation Manager uses the result in cycle closure.
What to agree during setup
Agree grade names and measuring practices before comparing rounds. Define the relationship between block round weights and crop harvest quantities, including whether a round can span several crop cycles. Identify the reviewer who accepts crop harvest quantities and the checks required before that person is named. Decide how a mistaken weight or grade is corrected after the team has used it in a report. Confirm that the crew lead directory includes active People records linked to users.
Check the handoff on an actual case
Harvest one block of North Ridge in a morning round. Select the block and crew lead, record the date, measured kilograms and grade, then check that the round contributes to the intended block. Create the crop harvest against the current cycle with its own quantity and unit. The reviewer checks the values, the linked field and the person responsible for acceptance. Compare the cycle’s accepted quantity with the block’s accumulated weight only after confirming the same period and units. A Restricted field or future harvest date prevents round capture until the source details are corrected. Close the crop cycle only after the remaining field tasks and actual harvest date have been checked.
What your team sees
- Harvest Rounds Log — Review block, date, weight, grade and crew lead for each round.
- Harvests Log — Check cycle quantities and the person recorded for acceptance.
- Crop Harvest Calendar — Compare expected and actual dates for active cycles.
Follow the work through
What it keeps track of
Data model- Harvest rounds
- Block-level harvest rounds with weight, grade and crew lead.
- Harvests
- Harvest quantities recorded against a crop cycle and accepted by a reviewer.
- Plantation blocks
- Plantation blocks within a field, with variety, planting year and tree count.
- Crop cycles
- Crop cycles planted on a field, from planning through harvest closure.
- People
- Plantation staff and crew members referenced by operational records.
- Fields
- Registered plantation fields with area, location and operational status.
Who uses it
Permissions- Crew Lead
- , Harvest Reviewer, Plantation Manager and Field Operator.
Set up Plantation Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.