How chemical compliance checking works

Chemical compliance checking and harvest review are available to selected accounts. If you don't see these features, contact your FarmQA representative.

How chemical compliance checking works

FarmQA checks the chemical compliance of a field's application records against regulatory and contractual requirements via ExtendAg. This article explains what compliance checking covers, how the check works, and what the results mean — so you know how to read a field's compliance status and what to do when a field is non-compliant.

For step-by-step instructions, see Run a compliance check on a field.

What compliance checking covers

A compliance check validates the application records on a field against a set of requirements that include pre-harvest intervals (PHI), maximum residue limits (MRLs), and product label restrictions. The check is run by submitting field data to ExtendAg, which returns a result.

Compliance checking covers chemical application records tied to the field and crop year. It doesn't cover storage applications.

When a check runs

You initiate compliance checks manually by selecting one or more fields and running the check. Checks don't run automatically. The result of the most recent check is stored as the field's current compliance state — previous check results aren't retained.

Compliance states

Each field shows one of the following compliance states:

Compliance state is separate from the field's submission and approval status. A field can be compliant and not yet submitted, or submitted and non-compliant. The two states don't affect each other directly — compliance state informs your decisions; it doesn't automatically change what stage the field is in.

Non-compliant fields

When a field is non-compliant, you can see the failure detail: which product failed, why, and on which date. This detail comes from ExtendAg's response and reflects what the check found at the time it ran.

To resolve a non-compliance, correct the underlying application record — for example, if a PHI was violated, work with the grower to address it — then run the check again. Only a passing check result changes the compliance state to Compliant.

Required fields on application records

Application records must have the following fields complete before they can be saved:

• Applicator license number
• Weather information
• Temperature at time of application

Records missing any of these fields can't be saved. The system shows a validation error at save time indicating what's missing. This requirement applies to all application records regardless of whether a compliance check is planned.

Related articles

• Run a compliance check on a field
• Required data for compliance submission
• Review and approve fields for harvest
• Group and organize fields in the field list