1. Plantation Management
  2. Features
  3. Fields and blocks
Feature · Fields and blocks

Fields and blocks

Keep each field's operating status and its planting blocks in one place.

OverviewPlantation Blocks Register
Plantation Management · Fields and blocks

Plantation Blocks Register

Plantation blocks

New
VarietyPlanting yearTree countFieldHarvest round countTotal weight KG
VRT-6488704FLD-609210430
VRT-2498301FLD-513724810
VRT-29777030FLD-520213300
VRT-93148016FLD-666639320
VRT-15061021FLD-94031760
6 of 6 records
VRT-648Plantation blocks · PB-50111
Planting year870
Tree count4
FieldFLD-6092
Harvest round count10
Total weight KG430
Example screen with sample data

What you can do

Begin with the ground the team manages

A field gives each piece of land a name, code, location, area and operating status. The plantation manager uses that record before assigning crop work or recording a harvest. Available, Planted, Fallow and Restricted are distinct decisions. A Restricted field prevents new block capture and field task execution until its status changes. The field area also gives yield review a consistent denominator.

A plantation block belongs to a field and carries its variety, planting year and tree count. The block record is the anchor for harvest rounds. A manager can see how many blocks belong to a field, while the block shows its round count and total weight. These values help identify which planting contributed to a harvest without treating the whole field as one undifferentiated crop.

How the work is organized

  • Field identity. Plantation Manager agrees the code, name, area and location before the first linked cycle or block is recorded.
  • Planting detail. A block connects variety, planting year and tree count to the parent field; Agronomy Reviewer can inspect those details before the record is used.
  • Operating status. The field status directs attention when work is planned or a harvest round is reviewed.

What to agree during setup

Decide how field codes correspond to the estate’s existing maps. Agree whether a physical subdivision is a separate field or a block within a field, and who may change that boundary after cycles and harvests refer to it. Establish the source of area measurements and the way corrections are recorded. Select who reviews a Restricted field and what evidence is needed before operational work proceeds. Confirm that planting years and tree counts are maintained by someone who knows the estate, rather than inferred from a harvest record.

Check the handoff on an actual case

Take a field called North Ridge with two varieties planted in different years. Register the field once, give each planting its own block, and compare the block details with the physical map. A Field Operator then selects the right block for a round and names the Crew Lead. The round’s weight contributes to that block’s total, while a crop cycle can still refer to the wider field. If the field is marked Restricted between planning and capture, the team must resolve the restriction before executing the task or capturing the round. This case tests the link from field to block to round without mixing block weight with whole-field yield.

What your team sees

  • Plantation Blocks Register — Review variety, planting year, tree count and each block’s linked field.
  • Fields Overview — Check field code, area, location and status before scheduling work.
  • Field Status Board — Scan fields by operating status for the next review.

What it keeps track of

Data model
Fields
Registered plantation fields with area, location and operational status.
Plantation blocks
Plantation blocks within a field, with variety, planting year and tree count.
Harvest rounds
Block-level harvest rounds with weight, grade and crew lead.

Who uses it

Permissions
Plantation Manager
, Agronomy Reviewer, Crew Lead and Admin.

Set up Plantation Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started