FlowsBook a callSign inCreate free accountSign up
Workflows by industry

Weather alerts for operations: thresholds per site, the right person, enough warning

How to set up weather alerts for operations that people act on: a threshold for each kind of work, a forecast for each site, one message to the person who can act.

Part of the guide Workflow automation

By the xMap team · · 4 min read

Good weather alerts for operations start from the work, not the weather. For each kind of job, decide the condition that stops or changes it (rain over a set amount, wind above a set speed, heat above a set temperature), check the forecast at the exact position of every site each morning, and send one short message only to the person who can change the plan, early enough to change it. A forecast that names every site every day is ignored by the second week.

This guide is for operations managers who run work outdoors or on the move: crews, depots, construction and maintenance, deliveries, events, farms and ports. It covers how to set thresholds that match the work, how much warning each decision needs, a made-up setup for a field services company in Auckland, the mistakes that turn alerts into noise, and how an AI employee can run the check.

Start from the decision, then pick the number

Every weather alert should answer one question: what will someone do differently? If the answer is nothing, it is not an alert, it is a forecast. Write down the decisions first, then the condition that triggers each.

Kind of workDecisionA condition to start from
Roofing, painting, exterior repairsMove the job to another dayRain of a few mm or more in working hours
Crane lifts, work at heightStand the crew down or move the liftWind above the limit in the equipment's manual
Concrete and asphaltReschedule the pourHeavy rain, or very high or freezing temperatures
Delivery roundsAdd time, add a van, tell customersHeavy rain on the day
Outdoor events and terracesSwitch to plan BRain or wind in the hours the event runs
Field crews in hot climatesStart earlier, add breaksA high maximum temperature or UV

Starting points only. Use your own equipment limits, contracts and safety rules.

Forecasts give rain in mm, wind in km/h, temperature in degrees Celsius and the UV index. A rain day is usually taken as one with 0.5 mm or more, which is too low a bar for most outdoor work; set your own.

How much warning each decision needs

  • Same morning: standing a crew down, delaying a lift. A check at 05:00 to 06:00 is enough.
  • A day or two: moving a job, calling the customer, booking an extra van.
  • A week: planning next week's jobs around a wet spell or a heatwave. A weekly forecast on Friday afternoon helps the planner.
  • Hour by hour: events and work with a short weather window, where it matters whether the rain arrives at 11:00 or 16:00.

A worked example, made up

A field services company in Auckland runs about 40 jobs a day: exterior painting, gutter cleaning and solar panel installs, spread across the region. Until now a supervisor looked at a forecast app each evening.

The company sets three rules. Painting jobs move when more than 2 mm of rain is forecast for the next day. Installs on roofs move when wind is expected above the limit in the installer's safety rules. Gutter jobs ignore rain but move in very strong wind. Each evening at 17:00 the forecast is checked for the position of every job on tomorrow's list, and the scheduler gets one email listing only the jobs that break a rule, with the reason next to each. On a typical wet day the email names a dozen jobs; on a dry, calm day it says all clear in one line. All the figures here are invented.

Mistakes that turn alerts into noise

  • One forecast for the whole region. A city forecast can say dry while one valley gets the storm. Check each site's own position.
  • The same threshold for every job. Rain that stops a painter does not stop a plumber. Rules belong to the kind of work.
  • Sending to everyone. Crews, schedulers and managers need different things. Send each the part they act on.
  • No all-clear. Silence can mean no risk or a broken check. A one-line all clear tells people the check ran.
  • Never reviewing the rules. If crews keep working through alerts, the threshold is too low. Adjust it after a month.

Running the check with an AI employee

In xMap Flows a weather check per site is a short flow:

  1. Schedule: every day at 17:00 for tomorrow's jobs, or 05:30 for same-day decisions.
  2. My data or New rows: the jobs or sites, each with a position and its kind of work.
  3. Weather forecast: for each incoming site, the next one to three days with rain, wind and temperature. Each site gets rain expected, rain in mm, the strongest wind, the highest temperature and a one-line summary.
  4. Branch or Filter: keep only the sites that break the rule for their kind of work.
  5. Approval, if you want: the scheduler confirms the moves before customers are told.
  6. Email, Slack or WhatsApp: the sites at risk with the reason, or one line saying all clear.

The template Rain alert for my city is the simplest starting point, Next week's jobs planned around the weather does the weekly planning version, and Wind at the port: when to hold crane work shows a wind rule. More ways AI employees support field work are on the field operations page.

Questions

How far ahead can the forecast look?

Up to 16 days, though the first few days are the most reliable. For decisions about tomorrow, use the next day or two.

Can I get the forecast hour by hour?

Yes, for cities, a point or an area, which suits events and short weather windows. For many sites at once, day by day is the usual choice.

Can different sites have different rules?

Yes. Keep the kind of work in your site table and use a Branch or Filter per kind, so each site is judged against its own threshold.

Where should the alert go?

To the person who can change the plan: usually the scheduler or dispatcher, not every crew member. Crews can get their own changed job list afterwards.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.