Choosing an operation's working window involves more than checking the weather before departure. You need to compare forecast conditions throughout the job and align that period with the available area, team and equipment.

In Farms, start with an overview of the coming days, explore hourly details and compare forecast models. This guide shows how to use that information to choose a working interval and review it before starting execution.

Check the forecast for the right area

Open Weather and check the location below the title. Tap the selector to choose Main location or an area available in your account. In an area's detail, View full forecast also opens the forecast for that location.

This keeps planning connected to where the job will happen. Checking another area's weather does not change the account's saved main location, and moving the map does not automatically change the Weather query.

Before comparing times, check three references on screen: location, date and model. Then, when switching areas or days, you know which job each forecast refers to.

Compare days before choosing the hour

In Forecast, view the available day cards. Six-hour periods help compare parts of the day and identify those needing closer analysis. Accumulated rain corresponds to the interval shown on the card; check Hour by hour for an hourly reading.

Use GFS, ECMWF, ICON and CMA to view different models. Keep the same location and period when comparing results. If forecasts differ, account for that in planning and check again closer to execution.

Check the model identified after loading. Each model has its own readings and data availability; switching models does not mean they will all provide the same variables or cover the same hours.

Examine the whole interval in Hour by hour

Open Hour by hour, select an available day and scroll the table horizontally. Compare columns for the expected start, middle and end of the job. If the operation should last three hours, examine that entire sequence as well as the departure time.

Tap a time to open its details. Tap a measurement's name to view its explanation, unit and the scale shown by the app. Now helps return to the current available interval, whose time appears on screen.

The aim is to find a period compatible with the job's criteria. Farms provides readings for comparison; you choose the window, also considering the product, crop, equipment and applicable technical guidance.

Read wind, gusts and direction together

Compare wind and gusts in the same column and unit. Wind describes forecast speed; gusts indicate speed increases that must also be considered. Looking at only one value leaves out part of the information.

Direction adds spatial context. In Farms, degrees and the cardinal point indicate where wind comes from; the arrow points where it travels. The table uses North up. Relate this reading to the area's position and surroundings.

ReadingWhat to compare between times
WindForecast speed, keeping the same unit
GustsForecast speed increases in the same period
DirectionWind origin and direction relative to the area
Temperature and humidityHow both values change during the job
RainForecast amount and the interval it refers to

Compare with temperature, humidity and rain

After comparing wind, examine temperature and humidity at the same hours. Embrapa explains how these conditions influence droplet evaporation. Assessing spraying therefore requires considering these variables alongside the application's characteristics.

Also check forecast rain for the period. In Farms, millimeters of rain and relative air humidity as a percentage represent different information. Soil moisture, when available, has its own reading and indicated depth.

Colors make values easier to compare, but do not classify an hour as authorized for application. Use the criteria defined for the job and the product instructions. A single wind, temperature or humidity rule does not suit every operation.

Refresh before mobilizing the team

A forecast can change between planning and execution. In Forecast, pull the list to refresh and check Updated on. This time identifies when data was obtained; forecast dates and hours remain shown on the cards and table.

Without a connection, the app may show queries previously saved for that context. Opening one model does not download the others, and viewing Forecast does not guarantee all Hour by hour details will be available offline. Check the update time and notices before using the data.

If a reading appears as —, it is unavailable. Do not interpret it as zero. When important information is missing, check again instead of completing your assessment with an assumed value.

Use the chosen window to organize the operation

With the period chosen, schedule the operation in Farms and coordinate the date, time, areas, team and service providers. This helps prepare the resources needed for execution. If the forecast changes, review the schedule and agree on adjustments with participants.

In the field, check actual conditions before starting and during work. The distinction between forecast and observation matters: INMET describes forecasting as the result of analyzing observations, models and other sources, while an observation represents conditions recorded at a particular place and time.

If you include weather information in operation observations, identify the location, time and source. A forecast you consulted and a field measurement should remain recognizable as different records. See also how to record operation execution.

Revisit the context in History

After the job, the History tab lets you view available data for a past date. Tap the day field, choose a permitted date and confirm View day. Availability depends on data returned for the location and period.

This helps revisit weather context, but does not replace a field measurement or automatically add data to the operation record. Check the source, units and times when relating the query to completed work.

To explore the tools, return to Agricultural weather. To bring planning, participants and execution together, explore Operations.

Sources for further reading