TotalApp Docs

Quality & Crop Health Operations

Soil and pest surveillance, chemical compliance with PHI/MRL enforcement, and the farm-to-fork digital product passport — the quality assurance backbone of a growing season.

What this group does

This is the most interconnected group in Agriculture & Agro-Tech Operations. Soil & Water Testing and Pest & Disease Alerts both feed pesticide/fertilizer applications logged in Agro-Chemical Analytics, which enforces a PHI (Pre-Harvest Interval) harvest lockout. Crop Health Checklist gates pre-harvest clearance. Farm-to-Fork Traceability compiles all of it — plus Crop Yield Dashboard's weighbridge data — into a per-lot digital product passport.

Soil & Water Testing
→
Crop Health Checklist
→
Pest & Disease Alerts
→
Agro-Chemical Analytics
→
Farm-to-Fork Traceability

All five screens share one underlying data service, and reach into the Agro-Tech Execution and Harvest & Supply Inventory screens' own services for field orders, harvest schedules, yield records, and the silo registry.

Screen preview

A quick look at the screen. Use the toggle in the corner to switch between the dark and light themes.

app.totalapp.app/agriculture/sops
Irrigation SOP
Published
Spraying & PPE SOP
Compliant
Harvest Handling SOP
Review Due
Pruning & Training SOP
Published
Food Safety (GAP) SOP
Compliant

Agronomic SOP library with compliance status

1. Soil & Water Testing

Purpose: Log lab results for soil and water samples — pH, EC salinity, macro/micronutrients, heavy metals — against SOP-defined bounds, and trigger remediation when a sample falls out of range.

Key features

  • Sample types — Topsoil Profile, Subsoil Profile, Irrigation Water, Hydroponic Runoff, each test coded SWT-2026-XXXX.
  • Status lifecycle — Sample Collected → In Lab Analysis → Report Published → Action Required.
  • Lab readings — pH level, EC salinity (mS/cm), nitrogen/phosphorus/potassium (ppm), organic matter (%), a list of micronutrient readings (ppm, deficiency flag) and heavy-metal flags (ppm, exceeds-safe-limit flag).
  • Soil Health Score — a dedicated calculation compares pH and EC against the crop recipe's target growth-stage thresholds.
  • SOP bounds check — a dedicated check flags a sample whose pH falls outside the recipe's min/max, or whose EC deviates >25% from target — the trigger condition for a remediation order.

Integration triggers

ActionWhat it does
Sync Soil Data to Field ProfileUpdates the master parcel's soil characteristics (last soil test date) directly on the matching record in Fields & Greenhouses.
Create Remediation Field OrderWhen pH or nutrient levels fall out of SOP bounds, creates a soil amendment/lime application field order (task type Fertigation, status Scheduled) directly in Field/Greenhouse Orders — see Agro-Tech Execution.
Sync Fertilizer RequirementsFeeds fertilizer adjustment requirements (derived from N/P/K deficits) into this same service's own Agro-Chemical Analytics ledger as a new fertilizer application record.

2. Crop Health Checklist

Purpose: Conduct field agronomic audits — routine, pre-harvest, or post-treatment — scoring crop condition on a set of 1-5 field ratings and percentage metrics, and gate harvest authorization.

Key features

  • Inspection types — Routine Agronomic, Pre-Harvest Audit, Post-Treatment Check, each checklist coded CHC-2026-XXXX.
  • Status lifecycle — Passed, Requires Attention, Quarantine Flagged.
  • 1-5 field rating scale — chlorophyll health, weed density, irrigation uniformity, insect pressure, plus percentage metrics for canopy density, foliage vigor, and root structure health.
  • Health Index Score — a dedicated calculation averages the normalized ratings and percentage metrics into a single 0-100 score.
  • Deficiency flags — a list of symptom/severity entries (e.g. "Nitrogen deficiency — yellowing lower leaves").
  • Pre-harvest linkage — a Pre-Harvest Audit checklist can be linked to a Season & Harvest Scheduling schedule.

Integration triggers

ActionWhat it does
Escalate Checklist to AlertWhen insect pressure pressure is assessed as critical (rating ≥ 4), generates an alert directly in this service's own Pest & Disease Alert ledger, severity derived from the rating (5→Critical Quarantine, 4→Moderate).
Approve Pre-Harvest ChecklistSets the pre-harvest clearance approval flag on the linked harvest schedule in Season & Harvest Scheduling, unlocking harvest authorization — see Agro-Tech Execution.
Request Soil TestingWhen a deficiency flag's symptom text matches a known nutrient-deficiency pattern, dispatches a sample-collection task directly into this service's own Soil & Water Testing ledger (status Sample Collected).

3. Pest & Disease Alerts

Purpose: Track active pest/disease outbreaks by field, assess spread risk, and dispatch an emergency pesticide response.

Key features

  • Outbreak severity — Low, Moderate, Critical Quarantine, each alert coded PDA-2026-XXXX.
  • Response status — Active Threat → Spray Scheduled → Contained → Resolved.
  • Spread Risk Score — a dedicated calculation blends a severity base score with a climate boost from ambient humidity (>70%) and temperature (22-32°C), pulled from IoT telemetry when available.
  • Diagnostic findings & target active ingredients — a list of lab-confirmable findings, and a list of target active ingredients each with a dosage rate limit and PHI days.
  • Source linkage — an alert can carry a reference to its originating checklist when escalated from a Crop Health Checklist audit, and a reference to a specific yield record for projecting yield loss onto it.

Integration triggers

ActionWhat it does
Dispatch Emergency Pesticide OrderCreates an urgent Pesticide Spraying field order directly in Field/Greenhouse Orders, noting the active ingredient in the operator observations — see Agro-Tech Execution.
Log Chemical Active IngredientRegisters the alert's target active ingredient, dosage limit, and PHI window directly into this service's own Agro-Chemical Analytics ledger, MRL status set to PHI Restricted.
Project Yield Loss PenaltySends the estimated crop loss percentage to discount the affected product's ML yield baseline via a shared calculation in the Target Harvests service, and reduces the linked Crop Yield record's target baseline proportionally.

4. Agro-Chemical Analytics

Purpose: Track every chemical application against its Pre-Harvest Interval (PHI) countdown and Maximum Residue Limit (MRL) compliance, enforcing a harvest lockout while restricted.

Key features

  • Record codes — ACA-2026-XXXX, each application linked to a chemical product name, active ingredient, total dosage (L/ha), and application date.
  • MRL status — Compliant, PHI Restricted, MRL Violation Risk.
  • PHI countdown & harvest lockout — a dedicated calculation derives days left in the interval from the application date and window length; a harvest lockout is active while any days remain — the trigger condition for locking harvest on that field.
  • Applicator license verification — a verified-license flag and license number per application, plus an MSDS URL.
  • Residue lab tests — a list of lab test results (residue ppm, export-market MRL threshold, test date) attached per application.
  • Source linkage — a record can carry a reference to its originating soil test (auto-derived from a Soil & Water Testing fertilizer deficit) or its originating alert (auto-derived from a Pest & Disease Alerts escalation).

Integration triggers

ActionWhat it does
Set Harvest LockoutSets the harvest lockout flag on every Season & Harvest Scheduling schedule targeting that field while the PHI countdown is active — see Agro-Tech Execution.
Deduct Inventory StockReconciles the applied chemical volume against stored stock in Agro-Input Staging — see Harvest & Supply Inventory.
Attach Compliance to PassportPushes a residue-clearance certificate reference directly into this service's own Farm-to-Fork Traceability ledger for the matching batch's digital passport.

5. Farm-to-Fork Traceability

Purpose: Compile a per-lot digital product passport that aggregates lineage data from field orders, soil/water tests, chemical applications, and yield/weighbridge data, then export a public QR code for consumer-facing verification.

Key features

  • Lot codes — LOT-2026-XXXX, each linked to a harvest batch code, crop variety, origin field, and optionally a storage silo.
  • Certification status — Not Certified, GlobalGAP Pending, GlobalGAP Certified, Organic Certified.
  • Compliance status — Verified Complete, Missing Lab Clearance, Quarantined.
  • Digital Product Passport modal — compiles a treatment-history record, a list of lineage source entries (source type, id, code, compiled timestamp) drawn from field orders and agro-chemical records.
  • Supply Chain Lineage Score — a dedicated calculation is a 6-factor completeness gauge: planting date set, treatment history non-empty, residue clearance attached, weighbridge reading present, cold-chain log summary present, storage silo linked. Each factor passed contributes 1/6 to the 0-100 score.
  • Public QR export — generates a consumer-facing verification token once the passport is compiled.

Integration triggers

ActionWhat it does
Compile Batch PassportAggregates lineage data from Field/Greenhouse Orders and Agro-Chemical Analytics (filtered by origin field), and pulls the weighbridge reading from the linked Crop Yield record, writing the combined treatment history and marking the passport as compiled.
Export Public QR PassportGenerates a public QR token and marks the passport as exported, written directly onto this service's own traceability record.
Verify Storage OriginValidates the lot's intake parameters against the Silo & Storage Management registry and links the matching storage silo once matched — see Harvest & Supply Inventory.

Under the hood — the passport is real aggregation, not a mock

Compiling the batch passport performs real cross-service reads against the Agro-Tech Execution screens' own data (field orders, yield records) and this same file's own agro-chemical ledger — it is not placeholder text. The one gap: verifying storage origin checks against the silo registry directly rather than a dedicated screen's own validation UI, since Silo & Storage Management's registry only recently moved out of the shared Agro-Tech Execution service (see the implementation note in Harvest & Supply Inventory).

End-to-end data flow

Source screen / actionWritesTarget screen / record
Soil & Water Testing — Sync Soil Data to Field ProfileUpdates last soil test dateFields & Greenhouses
Soil & Water Testing — Create Remediation Field OrderNew Fertigation field orderField/Greenhouse Orders
Soil & Water Testing — Sync Fertilizer RequirementsNew fertilizer application recordAgro-Chemical Analytics (same file)
Crop Health Checklist — Escalate Checklist to AlertNew pest/disease alertPest & Disease Alerts (same file)
Crop Health Checklist — Approve Pre-Harvest ChecklistSets pre-harvest clearance approvalSeason & Harvest Scheduling
Crop Health Checklist — Request Soil TestingNew soil sample testSoil & Water Testing (same file)
Pest & Disease Alerts — Dispatch Emergency Pesticide OrderNew Pesticide Spraying field orderField/Greenhouse Orders
Pest & Disease Alerts — Log Chemical Active IngredientNew chemical application recordAgro-Chemical Analytics (same file)
Pest & Disease Alerts — Project Yield Loss PenaltyDiscounts ML yield baselineTarget Harvests + Crop Yield Dashboard
Agro-Chemical Analytics — Set Harvest LockoutSets harvest lockout flagSeason & Harvest Scheduling
Agro-Chemical Analytics — Deduct Inventory StockDeducts staging stockAgro-Input Staging
Agro-Chemical Analytics — Attach Compliance to PassportAttaches residue clearanceFarm-to-Fork Traceability (same file)
Farm-to-Fork Traceability — Compile Batch PassportCompiles lineage historyOwn record (aggregates 3 upstream screens)
Farm-to-Fork Traceability — Verify Storage OriginLinks storage siloSilo & Storage Management registry

Frequently Asked Questions

What triggers a harvest lockout on a field?
Any Agro-Chemical Analytics application whose PHI (Pre-Harvest Interval) window hasn't elapsed yet. Setting the harvest lockout flag on every harvest schedule targeting that field is automatic, and it isn't cleared until the PHI countdown reaches zero.
How is a pest/disease alert automatically opened from a field audit?
When a Crop Health Checklist audit's insect pressure rating is 4 or 5, it is treated as critical and escalating the checklist to an alert opens a new alert record directly — severity Critical Quarantine for a 5 rating, Moderate for a 4.
What exactly does the Supply Chain Lineage Score measure?
Six completeness checks on a traceability lot: planting date set, treatment history non-empty, residue clearance attached, weighbridge reading present, cold-chain log summary present, and storage silo linked. Each passed check contributes one-sixth of the 0-100 score — it measures data completeness, not product quality.
Can a fertilizer application from a soil test skip the PHI/MRL workflow?
No — syncing fertilizer requirements writes those adjustments into the same Agro-Chemical Analytics ledger as pesticide applications, just with a Compliant MRL status and a zero PHI window by default, so they still show up in the same compliance table.
What data sources feed the Digital Product Passport?
Compiling the batch passport pulls from Field/Greenhouse Orders and Agro-Chemical Analytics (both filtered to the lot's origin field) plus the weighbridge reading from the linked Crop Yield Dashboard record. Storage silo linkage is added separately when verifying storage origin.
Why does verifying storage origin check the silo registry directly instead of a dedicated screen?
At the time this check was written, the silo registry lived only as a minimal store inside the shared Agro-Tech Execution service. It has since moved into its own dedicated service with a full management screen (Silo & Storage Management) — the validation logic still works the same way, just against the now-canonical store.