nutrient management / Agronomists, applicators, farm managers, data specialists, and equipment support teams
Prescription-map handoff preflight
Review prescription intent, field identity, spatial files, attributes, units, machine constraints, authorization, fallback, and evidence before a map reaches field execution.
See the whole mission
Orient before entering the field.
Connect the intended outcomes, operating stages, stop conditions, and supporting technology concepts before opening the detailed action sequence.
- 01Keep agronomic intent separate from file validity and machine execution
- 02Make field, product, units, zones, rates, versions, and authority inspectable
- 03Detect incomplete or mismatched handoffs before field work
- 04Preserve an approved input and later as-applied reconciliation path
- 01Freeze the decision intent
A technically readable file can still carry the wrong field, product, unit, season, rate attribute, treatment boundary, or unapproved revision.
3 field actions ↓ - 02Inspect the spatial package
Missing components, coordinate ambiguity, damaged headers, conflicting geometry, incomplete attributes, duplicate versions, and transfer errors can change or block interpretation.
3 field actions ↓ - 03Match the receiving machine workflow
The controller, terminal, task software, implement, sections, product setup, limits, and conversion behavior determine whether intent can be executed and recorded.
3 field actions ↓ - 04Authorize, transfer, and reconcile
Accountability requires the approved version, receiver confirmation, field execution record, exceptions, and later comparison to stay connected.
3 field actions ↓
- G01
This guide does not create an agronomic prescription, recommend a rate or product, validate a legal application, or command machinery.
- G02
Follow labels, regulations, product stewardship, field restrictions, equipment instructions, and qualified local advice.
- G03
A successful import does not prove correct application, placement, material delivery, crop response, or economic result.
Freeze the decision intent
A technically readable file can still carry the wrong field, product, unit, season, rate attribute, treatment boundary, or unapproved revision.
- 01Record field and boundary identity, crop and operation, product or material context, responsible author, reviewer, date, and version
- 02Define the target attribute, units, zone or grid meaning, valid value domain, excluded areas, and intended fallback
- 03Keep the agronomic basis and local authority outside the file-format check but linked to the handoff
Inspect the spatial package
Missing components, coordinate ambiguity, damaged headers, conflicting geometry, incomplete attributes, duplicate versions, and transfer errors can change or block interpretation.
- 01Inventory every file or package component and preserve names, sizes, dates, source, and transfer route
- 02Check declared coordinate context, geometry type, field envelope, attribute names and types, units, nulls, unexpected values, and visible overlaps or gaps using appropriate tools
- 03Reject placeholder, unknown, conflicting, or locally absolute paths and do not silently repair the approved source
Match the receiving machine workflow
The controller, terminal, task software, implement, sections, product setup, limits, and conversion behavior determine whether intent can be executed and recorded.
- 01Record receiving hardware, software, supported format, field and product mapping, control channel, section or rate capabilities, and required licenses
- 02Preview or import through a safe supported workflow and compare field, units, legend, values, orientation, zones, and summary statistics with the approved source
- 03Define behavior for missing position, missing value, communication loss, out-of-bound travel, overlap, and operator override
Authorize, transfer, and reconcile
Accountability requires the approved version, receiver confirmation, field execution record, exceptions, and later comparison to stay connected.
- 01Capture reviewer approval, checksum or stable identity where available, transfer time, destination, receiver, and import result
- 02Keep the operator review and stop authority explicit before field execution
- 03After work, retain the as-applied record, gaps, overrides, alarms, substitutions, and reconciliation status without treating commanded rate as measured outcome
Continue through the operation
See where this field guide fits.
Move beyond one task into the complete evidence, technology, operating, and review sequence around it.
Follow the complete field-season evidence loop
Move from a reviewed field model through representative soil evidence, planter setup, emerged-stand verification, nutrition, water, integrated protection, application readiness, harvest-loss diagnosis, and a qualified yield record that can support the next planning cycle.
- 01 / DEFINE FIELDVerify the operational field modelField guide→
- 02 / OBSERVEBegin with representative soil evidenceField guide→
- 03 / ESTABLISHVerify the planter in the fieldField guide→
- 04 / VERIFYAssess the emerged standField guide→
- 05 / PLANBuild the nutrient application decisionField guide→
- 06 / DIAGNOSEInvestigate crop nutrient statusField guide→
- 07 / SCHEDULE WATERBuild the irrigation scheduleField guide→
- 08 / VERIFY FLOWQualify the flow readingField guide→
- 09 / TEST DISTRIBUTIONRun a center-pivot uniformity checkField guide→
- 10 / VERIFY WATERAudit application uniformityField guide→
- 11 / RECONCILE WATERClose the field water balanceField guide→
- 12 / INVESTIGATE CROPInvestigate suspected crop water stressField guide→
- 13 / VERIFY VRIReview variable rate irrigation readinessField guide→
- 14 / PROTECTUse the IPM decision loopField guide→
- 14B / HAND OFF SAMPLEProtect the diagnostic sample handoffField guide→
- 15 / PREPARE SPRAYERVerify sprayer calibration readinessField guide→
- 16 / GATE APPLICATIONMake the spray-condition decisionField guide→
- 16A / VERIFY LABELAudit the pesticide label-authority packetField guide→
- 16B / CONTROL INVENTORYAudit pesticide inventory and storageField guide→
- 16C / AUDIT LOADAudit the pesticide mix-load eventField guide→
- 16D / AUDIT CLEANOUTAudit application-equipment cleanoutField guide→
- 16E / CLOSE CUSTODYAudit container and rinsate dispositionField guide→
- 17 / ALIGN CANOPYCalibrate delivery to an orchard canopyField guide→
- 18 / RETAINDiagnose combine harvest lossField guide→
- 19 / VERIFY COMBINEVerify one combine adjustmentField guide→
- 20 / QUALIFY DATAQualify the harvest dataField guide→
- 21 / MAINTAINPlan machine maintenance before the next operationField guide→
- 22 / QUALIFY WEATHERCheck the local weather evidenceField guide→
- 23 / CHECK DELIVERYVerify a drip irrigation zoneField guide→
- 24 / TRIAGE PLANTERTurn a planter alert into a field checkField guide→
- 25 / GROUND TRUTHTest a remote-sensing pattern in the fieldField guide→
- 26 / ACCEPT POSITIONAccept the exact GNSS and RTK field chainField guide→
- 27 / VERIFY CONNECTIONReview mixed-fleet ISOBUS compatibilityField guide→
- 28 / PREFLIGHT INTENTPreflight the prescription handoffField guide→
- 29 / BOUND AUTOMATIONReview automation site readinessField guide→
- 30 / CONTROL DATAReview farm-data consent and exitField guide→
- 31 / VALIDATE VISIONValidate machine vision in the fieldField guide→
- 32 / PLAN UASBuild the UAS mission evidence planField guide→
- 33 / TRIAGE TELEMATICSInvestigate telematics data qualityField guide→
- 34 / CLOSE WORKClose the work order with evidenceField guide→
- 34A / BASELINE MACHINEAudit the machine configuration baselineField guide→
- 34B / QUALIFY CONDITIONAudit machinery condition evidenceField guide→
- 34C / INVESTIGATE FAILUREReview the machinery failure eventField guide→
- 34D / RELEASE MACHINERun the return-to-service readiness gateField guide→
- 35 / MANAGE DRAINAGEAudit the drainage water management planField guide→
- 36 / MONITOR OUTFLOWAudit edge-of-field evidenceField guide→
- 37 / HAND OFF TREATMENTReconcile the conservation drainage practiceField guide→
- 38 / BASELINE ENERGYAudit the farm energy baselineField guide→
- 39 / REVIEW DUAL USEReview the agrivoltaic site evidenceField guide→
- 40 / EXERCISE RESILIENCERun the farm critical-load exerciseField guide→
- 41 / AUDIT STORAGEAudit manure storage from outsideField guide→
- 42 / AUDIT MANUREAudit the manure sample evidenceField guide→
- 43 / REVIEW RECOVERYReconcile anaerobic digestion evidenceField guide→
- 44 / AUDIT SOIL DESIGNAudit the soil sampling designField guide→
- 45 / COMPARE SOIL REPORTSReconcile soil laboratory reportsField guide→
- 46 / REVIEW SOIL HEALTHReview soil health indicatorsField guide→
- 47 / REVIEW SOIL CHANGEAudit the soil evidence timelineField guide→
- 48 / REVIEW MICROCLIMATEAudit the microclimate network designField guide→
- 49 / PREPARE FOR FROSTReview frost-monitoring readinessField guide→
- 50 / AUDIT THERMAL TIMEAudit a degree-day model runField guide→
- 51 / QUALIFY WEATHER SOURCEReview weather-network representativenessField guide→
- 52 / AUDIT WATER SAMPLEAudit the irrigation-water sampleField guide→
- 53 / COMPARE WATER REPORTSReconcile irrigation-water reportsField guide→
- 54 / REVIEW SALT EVIDENCEReview salinity and sodicity evidenceField guide→
- 55 / AUDIT WATER REUSEAudit agricultural recycled-water governanceField guide→
- 56 / REVIEW FERTILIZERReview fertilizer product authorityField guide→
- 57 / AUDIT BLENDAudit blend production custodyField guide→
- 58 / AUDIT FERTILIZER STOREAudit fertilizer inventoryField guide→
- 59 / TRACE NUTRIENT LOADReconcile nutrient source to fieldField guide→
- 60 / CLOSE FERTILIZER CASEReview fertilizer nonconformance closureField guide
Preflight the prescription handoff
Keep agronomic intent, spatial package, units, machine constraints, approved version, fallback, and reconciliation connected before execution.