Controlled Environment Agriculture: Integrated pest management and how GLOBALG.A.P. IFA turns control into evidence

In the first article of our guest series on Controlled Environment Agriculture (CEA), Dr. Emilia Mikulewicz explores best practices in how to implement integrated pest management (IPM) as a closed control loop. 

In CEA, pests and diseases do not disappear. Risk accelerates, and audits reward producers who can prove control. Supported by an audit-defensible evidence chain linking monitoring, decisions, actions, and verification to a stable zone grid and harvest lot, the closed control loop keeps interventions traceable when auditing against the GLOBALG.A.P. Integrated Farm Assurance (IFA) standard.

Why evidence replaces assumption in CEA IPM

CEA does not eliminate pest and disease risk. Instead, short cycles, high crop density, and continuous production can compress the interval between detection, decision-making, and population growth.  

In CEA, stable setpoints – such as temperature, humidity, and nutrient levels – and repeated operations in the same zones can make outbreaks escalate faster once established. This compression makes response time and verification more critical, because small delays can turn routine pressure into a lot-level nonconformity or buyer dispute. 

In IFA audits, the question is not whether a problem occurred – but whether you can provide evidence of risk control from detection, through the decision, to a verified outcome. In an audit, evidence matters.  

If records are not consistent, repeatable, and traceable end-to-end, it becomes difficult to defend control for a specific zone and harvest lot. The record trail must therefore link observations, decisions, actions, and verification. The logic must be simple and closed: 

1. Threshold exceeded in Zone A 
2. Operational action 
3. Record in the register (zone, person, date, time, lot ID) 
4. Follow-up monitoring recorded using the same metric and the same zone grid, so the post-action status is documented.

What makes IPM defensible in IFA audits

Standard requirements do not replace IPM. They structure it by requiring systematic monitoring, defined control measures, and records that demonstrate implementation.  

In CEA, this is why monitoring and records must follow a defined method, a stable zone map (reporting unit), and a documented recording frequency. This is not a formality, but the condition for traceability and defensibility of decisions. Through its outcome-oriented approach, IFA does not prescribe numeric thresholds or response-time targets. Instead, it audits whether you defined risk-based rules, applied them consistently, and can prove outcomes with records. KPIs translate risk assessment and buyer requirements into measurable internal controls. 

A common defensibility gap in CEA appears when strong IPM is not supported by a stable reporting structure. Spreadsheets may look complete, but if records cannot be reconstructed by zone and harvest lot, the system breaks down in an audit. If the zone grid changes during the cycle, or harvest lots are re-aggregated without traceable links, comparability is lost and control can no longer be demonstrated – even if the agronomic actions were correct. 

In practice, this weakens harvest-lot identification and breaks the ability to reconstruct IPM actions across the full traceability chain:

1. Zone 
2. Lot 
3. Packing 
4. Customer 

In field production, weather variability and natural dispersion can sometimes slow outbreak development. In CEA, stability and repeatability can accelerate it: pressure can increase rapidly, infection-risk windows can repeat more often, and zoning or hygiene errors can transfer pressure between blocks. For this reason, the real audit question is not whether a problem occurred, but whether the producer can reconstruct the control logic by zone and lot, and demonstrate that the evidence chain remained intact.

The four elements that make CEA IPM audit-defensible

IPM in CEA is audit-ready when it functions as a closed control loop, supported by records that form a defensible evidence chain across four operational areas:

• Response time  
  Measured from signal or threshold exceedance to documented action in the same zone context. Example internal targets might be within 24 hours for higher risks, and within 72 hours for moderate risks, with escalation when targets are missed. 
• Microclimate management 
  Prevention driven by humidity, dew point, and airflow patterns, supported by documented operational adjustments. 
• Zoning and biosecurity 
  Movement rules, tool control, hygiene routines, and separation of risk levels between blocks. 
• Traceability 
  The ability to link IPM actions to a specific zone and a specific harvest lot. 

Each element must leave an evidence footprint that can be retrieved for the defined reporting unit. Minimum records include a monitoring register, decision and action log, and verification result. For IFA defensibility, records must also be attributable (who, when, where). 

Implementation starts with the reporting unit and records architecture. Define a fixed zone grid and a harvest-lot ID logic that stays consistent across cycles. Assign one owner, one KPI, and one review rhythm for each module, so signals trigger action by rule. If an item cannot be retrieved by reporting unit and harvest lot, it cannot be used as objective evidence in the audit. 

Operational example: How lot defense is built

Dew-point records show repeatable night-time risk windows in one zone, and scouting notes indicate early Botrytis cinerea pressure around senescing tissue.  

The response combines microclimate correction (dehumidification setpoint change, airflow redistribution, irrigation timing shift) with sanitation documented for that zone and linked to the harvest lot.  

Within the defined response time, the same monitoring method confirms a measurable change in the defined indicator and the confirmation is recorded. If a dispute later arises with a buyer, the defense is built by the evidence chain.

Six steps to evidence-based control

The indicators below are measured using defined sampling rules and the same monitoring method on the same zone grid, and recorded against the harvest lot.

1. Zoned pressure monitoring  
   Weekly trap counts and structured scouting recorded by zone. 
2. Decision thresholds by crop stage and market 
   Triggers aligned with plant stage, harvest rhythm, and buyer requirements. 
3. Microclimate risk indicator (internal KPI) 
   Minutes/hours within defined RH/VPD/dew-point risk ranges, linked to operational response. 
4. Response time (producer KPI) 
   Measured from threshold exceedance to documented action in that zone. Record target versus actual response time, and escalate when targets are not met. 
5. Effectiveness confirmation 
   Post-action verification that the KPI changed, using the same measurement rule, linked to the action, zone, and lot. 
6. Harvest-lot traceability 
   Including zone, date, person, lot ID, packing, shipment, and customer. 

Audit schemes and buyer requirements differ, but the evidence logic is constant.  

In CEA, predictability comes from control that can be proven. When a complaint, rejection, or withdrawal occurs, the advantage lies with the producer who can reconstruct the decision path and show that control was closed by zone and lot, and that the evidence chain supports it. 

In summary, control is not the differentiator. Retrievable proof of control is. Build IPM so any zone and any lot can be reconstructed on request. 

Related links 

• Explore the IFA for fruit and vegetables standard 
• Get expert support through the Registered Trainer program