Keeps the production plan separate from daily work
- targets have to be found and copied manually;
- tasks, measurements, and control systems live apart;
- it is difficult to trace which revision produced the result.
A repeatable crop production standard
Digital crop plans that guide every growing cycle
Define stages, target ranges, tasks, recipes, and photoperiod. Gros.farm applies the relevant part of the plan to the current stage and connects it with actual data, team workflows, and available control integrations.
- Templates and farm-specific revisions
- For plant and mushroom production
- History for every growing cycle
Current stageFruiting · day 12This stage’s targets and work are active
Crop stages and biology
Target production metrics
Tasks and recipes
Photoperiod and control targets
Cycle history and revisions
Not a static document
A crop plan defines both what to do and what should be happening now
A conventional SOP describes the technology in general. A Gros.farm tech card understands the current stage of a specific cycle and gives every connected workflow the same production context.
Works inside each growing cycle
- the current stage determines active targets and processes;
- the team and connected modules use one stage context;
- actuals remain beside the plan for the next revision.
In practical terms: a tech card turns production knowledge into clear rules for people, data, and connected equipment.
The stage is the management unit
When the stage changes, the working context changes with it
A stage is more than a date on a calendar. It represents the biological state of the crop and the production objective for that period.
Example
When greenhouse tomatoes move from establishment to vegetative growth, target ranges, observation priorities, work, and environment strategy all change.
Tomato · greenhouse 1Growing cycle
On plan- 01Establishmentcompleted
- 02Vegetative growthcurrent stage
- 03Floweringnext
- 04Fruitingplanned
Active now
- the target ranges for this stage;
- the relevant tasks and recipes;
- photoperiod and configured setpoints;
- the rules for comparing plan with actuals.
Stage structureDescription · duration · targets · actions
What each stage contains
A specific set of targets and actions for every stage
The production specialist defines the stage once. During the cycle, the team sees the part of the technology that is relevant now, without searching old files or revisions.
Metrics and targets
Target values and ranges for output, crop status, and growing conditions.
Tasks
Stage-specific work, timing, and instructions that can be assigned to the team.
Recipes
Production recipes and operating sequences that belong to the stage.
Photoperiod
The stage-specific light schedule and lighting strategy when used by the operation.
One production standard across the system
The current stage gives connected workflows a shared context
The tech card does not measure climate or switch equipment by itself. It defines what the cycle needs now, while each connected function performs its own role.
Digital crop planCurrent stageShared production context
Tasks and team
Relevant work, instructions, due dates, and responsibility for the current stage.
Monitoring
Actual observations, photos, and values viewed against the targets for this stage.
Metrics and analytics
Plan versus actual, deviations, and events in the chronology of the growing cycle.
Climate and irrigation
Configured control modules can use stage targets when a suitable integration is available.
AI workspace
Uses cycle structure to help investigate patterns and hypotheses in accumulated data.
You do not have to start from a blank page
Use a starting point, adapt it to the farm, and develop your own revision
Start with a public, expert, or internal template. Every crop plan must still be validated under the conditions of the specific facility and market.
- 01
Choose a starting point
Select a public, expert, or internal template for the relevant crop and production method.
- 02
Adapt it
Refine stages, targets, tasks, and operating modes for the facility and production objective.
- 03
Start a growing cycle
Apply that revision to a specific crop cycle at a selected facility or production zone.
- 04
Improve it with actuals
Compare the plan with the result and create the next revision of the production standard.
A template is a starting point, not a universal recipe.
Adapt it to the cultivar or strain, facility, season, equipment, market requirements, and production objective, then refine it with evidence from your own cycles.
The production plan becomes measurable
See when the actual cycle moves outside the intended technology
Define stage-specific target values or ranges. Gros.farm compares them with manual observations and data available from connected sources.
- comparison follows the context of the current stage;
- charts bring together targets, actuals, and cycle events;
- specialists can notice a deviation earlier and investigate the cause.
Connection with local control systems
The crop plan defines the target; the local control layer executes safely
With a configured integration, Gros.farm control modules can use targets from the current stage. Commands are passed to the local control layer, which remains responsible for safe, reliable equipment operation at the facility.
Tech card→Climate or irrigation→Setpoint→Local control→Equipment
Gros.farm does not replace SCADA, PLCs, or local controllers.
The platform adds crop-production context above the existing local automation layer.
Different crops, one management model
Stages and parameters change; the operating principle stays consistent
Digital crop plans support different growing technologies. Each plan contains only the stages, targets, and actions that the production system actually needs.
Plant crop
Greenhouse tomato
Establishment → vegetative growth → flowering → fruiting
- day and night temperature, humidity, and VPD;
- radiation, irrigation, and drainage;
- growth, flowering, harvest, and team activities.
Mushroom crop
Button mushroom in a grow room
Colonization → cooling → pinning → harvest flushes
- substrate and air temperature, humidity, and CO₂;
- ventilation and climate strategy;
- mycelium condition, harvest flushes, and team tasks.
Production knowledge stays with the company
Every completed cycle can strengthen the next revision
Tech-card revisions and actual cycle history remain available for comparison, rollout to new facilities, and onboarding of new team members.
Repeatability
Teams across facilities work from the same clear production structure.
Comparability
Past and current cycles can be compared at equivalent stages.
Continuity
Production knowledge does not disappear when a specialist or team changes.
Context for AI
Connected models receive a structured context: crop, facility, stage, targets, actuals, and events. This can help investigate patterns and formulate hypotheses, while production decisions remain with the responsible specialist.
Digital crop plan questions
What to know before you start
What is a digital crop plan or tech card in Gros.farm?
It is a working model of the production technology: a sequence of stages with duration, target metrics, tasks, recipes, and photoperiod. A selected revision is applied to a specific growing cycle and provides the context for its current stage.
How is it different from an Excel file, PDF, or SOP?
A file stores instructions separately from production. In Gros.farm, the current stage can be connected with tasks, monitoring, analytics, and, when configured, control modules. Actual cycle history remains beside the crop-plan revision.
Can we start without sensors or automation?
Yes. Start with stages, tasks, manual observations, and target values. Add sensors, data sources, and local automation later when they support a specific production requirement.
What happens when the stage changes?
The next stage’s targets, tasks, recipes, and settings become relevant for the cycle. Automatic application of parameters depends on the configured control module and connected equipment.
Can we use an existing template?
Yes. Start from a public, expert, or internal template and create your own revision. Validate and adapt it for the crop, cultivar or strain, facility, season, equipment, market requirements, and production objective.
Does it work for mushroom production?
Yes. Instead of plant-development phases, define the stages of a mushroom production cycle, such as colonization, cooling, pinning, and harvest flushes, together with their climate targets and team activities.
Is this mainly a costing tool?
The primary purpose of a Gros.farm tech card is to manage the growing process by connecting stages, targets, actions, and actual production data. It is not merely a cost-calculation form or a static SOP.
From SOP to daily production management
Make crop technology a working system for every cycle
See how to build a digital crop plan around your crop, team, available data, and existing automation.