In this guide

The starting point

Turn a changing pattern into a focused question you can investigate on the ground.

Check the observation first

Start with the image date and the information available about image quality. A map should make it clear whether you are looking at a recent observation, an older usable image or a modelled estimate. Do not treat those as interchangeable.

Satellite missions collect observations on a schedule; a new clear view of every field is not guaranteed whenever you open an application. Understanding data availability is part of interpreting the result.

Make the question specific

Instead of asking 'What is wrong with the field?', begin with something you can investigate: 'Why does this area look different from the surrounding crop?' Review the crop, recent weather and relevant management notes. Keep more than one explanation open until you have supporting observations.

Compare, record and discuss

Where appropriate, compare an area showing change with an area that appears more consistent. Record the date, location, crop stage and visible differences. Photographs and notes can make a later discussion more useful than relying on memory alone.

Share relevant findings with the person advising the field. An imagery pattern can help determine where to look; it does not independently determine an irrigation volume, fertilizer rate or crop-protection treatment.

Close the loop

Record what was checked, what you learned and what happened next. A later observation may help you assess whether the original question was useful. Keep uncertainty in the record rather than rewriting the original interpretation as a certainty.

The value of monitoring is not the number of maps collected. It is the quality of the questions and follow-up those observations support.

Sources

  1. European Space Agency, S2 Mission, SentiWiki (Copernicus). sentiwiki.copernicus.eu/web/s2-mission. Accessed . Used for: Background on Sentinel-2 for “Check the observation first”: satellite missions collect observations on a schedule.
  • Field guide · Understand the score

    What a field score can - and cannot - tell you

    A single score can make a long list of fields easier to review. It can also hide detail if you treat the number as a complete answer. The useful question is not simply 'Is the score high or low?' It is 'What information produced this score, and what should I check next?'

    By AgriNova AI Published Updated 2 min read

  • Field guide · Evaluate a pilot

    How to prepare for a farm-software pilot

    A useful pilot starts with a clear question. Before trying a new tool, decide which part of your work you want to understand or improve. That makes it easier to choose a suitable scope and judge the outcome honestly.

    By AgriNova AI Published Updated 2 min read

Next step

The platform page describes the planned workflow from a field signal to a recorded field check.

Explore the platform