The record is isolated from production
- the plan and actual application must be compared manually;
- it may be unclear which crop cycle the treatment belongs to;
- the result has to be found in observations and messages.
Crop protection application log
Plan crop protection treatments and record what was actually applied
Keep the farm, crop, target pest or disease, product, rate, area, timing, and responsible team in one record. Each treatment stays in the crop history instead of disappearing into a separate spreadsheet.
- Treatment plan and actual application
- Product, rate, and quantity used
- History by location and crop
Before the workTreatment plan
After the workActual application data
Farm and crop
Target pest or disease
Product and rate
Area and quantity used
Date and time
Applicator
Do not fill out the log after the fact
A treatment starts with a plan and ends with a recorded application
When the agronomist plans in one place, the worker receives the task somewhere else, and the log is completed later, important context gets lost. In Gros.farm, it is one connected workflow.
The treatment stays connected to the crop
- the location, crop, and growth stage are already linked to the record;
- planned values are updated with actual application data;
- observations and crop status remain visible after the treatment.
One connected workflow
From the agronomic decision to treatment history
Every step keeps its context. There is no need to reconstruct the record from the calendar, team tasks, and a separate application log.
- 01
Make the agronomic decision
The agronomist defines the objective, product, application rate, and suitable treatment window.
- 02
Plan the treatment
Set the location, crop, area, date, time, and responsible team.
- 03
Perform the work
The worker receives a clear task in the context of the production area.
- 04
Record the actual application
Actual area, quantity used, timing, and notes become part of the history.
Treatment record
All application details in one record
The fields follow the work itself: location and timing first, then the treatment target, crop protection product, and actual application.
Location and crop
Farm, facility, production area, crop, and growth stage.
Area and timing
Planned and actual area, date, start time, and finish time.
Treatment target
Pest, disease, weed, or another reason for the application.
Crop protection product
Product type, trade name, active ingredient, and registration number.
Rate and quantity used
The planned application rate beside the actual product quantity used.
Team and conditions
Applicator, equipment, weather conditions, checks, and notes.
Important for agronomists
Gros.farm structures the record but does not choose the product or application rate for the specialist. Product selection, label compliance, and authorization to perform the work remain the responsibility of the farm’s qualified staff.
Before and after the treatment
See each application next to the crop’s response
The treatment appears on the monitoring timeline. The growth stage, weather, observations, photos, and environmental metrics stay beside it, so you can reconstruct what happened before the application and how conditions changed afterward.
- 01Before the application
Observations, photos, crop status, and the weather window.
- 02Treatment
Product, rate, area, timing, and applicator.
- 03After the application
New observations and metric trends for the same crop cycle.
One log, several working views
Review treatments as a list, by date, or in the crop cycle history
There is no need to maintain duplicate records. The view changes, but the treatment and its actual application values stay the same.
Treatment list
Filter records by location and crop, then open application details quickly.
Calendar
See treatments by day and compare them with other work across the farm.
Crop cycle history
Return to a treatment together with growth stages, observations, and metrics.
Context for the AI workspace
Treatment history becomes structured data for reviewing the season
A connected model can work with periods, locations, crops, observations, and actual application data instead of a scattered list of product names.
“Show treatments for this location during the selected period.”
“Find records where the actual area or product quantity is missing.”
“Compare treatments with the crop observations that followed.”
AI can help find relationships and prepare data selections, but it cannot confirm treatment efficacy or replace the agronomist’s decision.
The essentials
Crop protection application log FAQ
What is an electronic crop protection application log?
It is a working area for planning and recording crop protection treatments. Each record is connected to the farm location, crop, production area, date, product, application rate, and actual application details.
Can I plan a treatment first and record the actual application afterward?
Yes. Enter the planned values before the work. After the treatment, add the actual area, quantity used, timing, applicator, and notes.
What information can be stored in a treatment record?
Location and production area, crop, treatment target, product, product type, active ingredient, registration number, application rate, quantity used, area, date and time, equipment, conditions, applicator, and checks.
Can one treatment include several products or targets?
Yes. One treatment can include several products and several target pests, diseases, or weeds when that matches the agronomic decision made by the farm.
Where can a completed treatment be reviewed?
The record stays in the application log, calendar, and crop cycle history. It can also appear in the monitoring table beside growth stages, weather, and observations.
Does Gros.farm replace legally required pesticide reporting systems?
No. Gros.farm helps organize internal production records and prepare data for reporting, but it does not replace legally required government systems, label requirements, or local regulations.
Can AI choose a product or confirm treatment efficacy?
No. AI can prepare data selections, find incomplete records, and help explore treatment history. A qualified specialist remains responsible for the product, application rate, and evaluation of the result.
No separate spreadsheet
Build crop protection applications into production history
See how Gros.farm connects treatment planning, field work, actual application data, and the observations that follow.