Location, crop, and result live in separate records
- the team cannot see what is currently growing in each zone;
- areas and quantities have to be reconciled by hand;
- after harvest, the actual production history is difficult to reconstruct.
Farm production records
Farm registry: know what is growing, where, and in which cycle
Map a greenhouse, field, orchard, grow room, or indoor farm into working zones. For every zone, keep the crop, occupied area, plan, actual result, and responsible person together in the context of the current growing cycle.
- A structure that matches your operation
- Plan and actuals for every production zone
- Read-only history of completed cycles
One rowZone · crop · area
One cyclePlan · actual · owner
Facilities and production zones
Crops and active cycles
Area, quantity, and yield
People, data sources, and tasks
Completed-cycle history
The foundation of production records
Place, crop, and growing cycle in one registry
See which crop occupies each row, block, room, or plot, how much capacity it uses, who owns the work, and what result the current cycle is expected to deliver.
One row represents one production zone in an active cycle
- the zone is tied to the crop and its production data;
- area, quantity, and yield totals stay visible in the table;
- completed-cycle records remain available as read-only history.
In practical terms: open a row and see what is growing there, how much space it occupies, the planned result, and the person responsible.
Production structure
Build the registry around the way your operation actually works
Start with facilities such as greenhouses, fields, orchards, rooms, or indoor farms. Then divide each facility into the units your team already uses: rows, blocks, compartments, plots, racks, bays, or another familiar production zone.
Use the level of detail that supports real decisions.
Create only the zones for which the team will regularly maintain data.
- 01OrganizationFarm or production company
A shared workspace for the operation and its team.
- 02FacilityGreenhouse, field, orchard, room, or farm
A physical production site with its own cycles and data.
- 03Zone within a facilityRow, block, plot, bay, or rack
A practical production unit represented by a registry row.
- 04Growing contextCrop and active cycle
Plan and actual production data for this zone.
Configuration without development
Select a production type and start with relevant fields
A greenhouse, orchard, mushroom room, nursery, and vertical farm need different records. Gros.farm provides a suitable starting set, and you keep only the columns your team will use.
Use the names your team already knows
Define what a zone is called and how many there are, such as 50 rows or 12 grow rooms.
Start with fields suited to your production type
Selecting a production type provides relevant fields for area, planting, quantity, and output.
Remove columns that do not support the workflow
Keep the parameters your team will actually maintain and add custom fields where needed.
Greenhouses and vegetablesBerriesOrchards and vineyardsMushroom productionFlowersNurseriesVertical farmsField crops
Current-cycle data
Keep plan and actuals side by side for every zone and facility
Each row describes what is happening in a specific production zone now. The team enters actual data, Gros.farm calculates the values it can derive, and the registry rolls up totals for the facility.
Actual production data
A row keeps the crop or variety, occupied area, quantity, timing, and current result.
Calculated fields
When source data is available, Gros.farm derives occupancy, density, and other totals.
Facility totals
The summary row brings together area, quantity, and other values that can be aggregated.
Initial-data import
Import an existing table to get started, then maintain the record directly in the registry.
PlanWhat the cycle is expected to deliver
→Planned occupied area, quantity, timing, and output.
ActualWhat is happening and what was achieved
Actual occupancy, recorded quantity, timing, quality, and output.
Every activity has a location
Connect each zone with people, data sources, and work
Tie a production zone to a responsible person, available sensors, and tasks. The team can then see who owns the area, where a reading came from, and exactly where work needs to happen.
Responsible person
Who owns the zone and keeps its record current.
Data sources
Which production zone a sensor or measurement belongs to.
Tasks
What needs to be done, where, by whom, and by when.
Growing history
The cycle ends, but its production record remains
Review actual values before closing the cycle. Once confirmed, populated rows move into read-only history and the active table is ready for the next cycle.
- 01Run the active cycle
Update registry rows as production progresses.
- 02Review actuals
Confirm areas, quantities, dates, and the production result.
- 03Close the cycle
Populated rows move into read-only cycle history.
- 04Start the next cycle
The active table is ready for the next crop or batch.
Cycle historyCompleted-cycle data becomes read-only
Closing a cycle cannot be undone.
An empty registry does not create a history record. Review the actual data before confirming completion.
Connected production context
The registry gives every record a place and a growing cycle
A tech card describes how the cycle should run. Monitoring records what is happening. Tasks organize the team’s response. The registry connects all of it to a facility, production zone, crop, and active cycle.
Farm registryFacility · zone · crop · cycle
Tech cards
Define the stages, targets, and work for a growing cycle.
Monitoring table
Keeps crop observations and conditions in a daily and weekly context.
Tasks and team
Connect work with its location, owner, status, and due date.
AI workspace
A model receives a value together with its facility, zone, crop, and cycle context.
Context helps investigate relationships; it does not prove causation.
AI can help examine a hypothesis, while the final decision remains with the responsible specialist.
One model, different production systems
Use the zones and fields that make sense for your operation
A greenhouse may use compartments and rows, an orchard uses blocks and plots, and a mushroom operation uses grow rooms. Name production zones in familiar terms and collect only the data your team needs.
Greenhouse
Compartments, bays, blocks, or rows.
Area · crop · plant quantity · planned yieldField, orchard, or vineyard
Fields, plots, orchard blocks, or rows.
Area · variety · planting · expected and actual outputMushroom room or vertical farm
Rooms, racks, levels, or production zones.
Batch · quantity · production area · cycle resultPlot or production line
Rows, benches, trays, blocks, or sections.
Crop · variety · density · quantity · marketable outputFarm registry questions
What to decide before configuration
How is the farm registry different from a spreadsheet?
A spreadsheet row is usually an isolated record. In Gros.farm, a registry row belongs to a facility, production zone, crop, and active growing cycle. It can also carry plan and actual values, a responsible person, data sources, and related work. Completed-cycle data remains available as read-only history.
What is a production zone or sub-object?
It is a part of a facility that makes sense to manage separately: a row, compartment, room, block, plot, rack, level, bay, or another working unit. Your operation chooses the name and number of zones.
Which fields can the registry hold?
The starting set depends on the production type. Typical fields include crop and variety, production and occupied area, plant or substrate quantity, density, dates, planned and actual yield or output, equipment, and responsible people. Keep only the fields relevant to your workflow and add custom fields when needed.
Do I need sensors to start?
No. The registry can be configured and maintained manually. If sensors or integrations are available, connect their data to the relevant production zone and crop.
What happens when a growing cycle is completed?
Populated rows move into read-only history and the active table becomes available for the next cycle. An empty registry does not create a history record. Cycle completion cannot be undone, so actual data should be reviewed first.
How detailed should the facility structure be?
Use the level at which decisions are made and responsibility is assigned. Zones that are too large hide differences; zones that are too small create unnecessary maintenance. A useful rule is that each row should describe one clear production unit the team can keep current.
Can one zone contain more than one crop?
It can if that reflects your real record-keeping. However, plan-versus-actual review is clearer when each row has one production meaning, so different crops are usually easier to manage as separate zones or rows.
Start with your real production structure
Build a working registry for your farm
We will help map facilities into practical production zones, choose the right fields, and connect the registry with active growing cycles.