Air quality alerts that reach your dispatchers before restrictions do

Why air quality can change tomorrow's schedule

In several major cities, air quality restrictions are part of everyday fleet planning. Mexico City is the best-known example. Its standing Hoy No Circula program restricts which vehicles may circulate on which weekday, based on plate digits and emissions verification status. When pollution climbs, authorities can declare a contingency and tighten those rules with little notice, sometimes pulling in vehicles that are normally exempt and adding measures for cargo operations.

For an individual driver, a late update means changing tomorrow's plans. For a fleet, the same update sets off several coordinated actions: reassigning trips to eligible vehicles, shifting departure and delivery times, notifying drivers and customers, and revising routes and shift plans. All of it has to happen before the first vehicle leaves the yard.

The practical answer is to stop guessing at restrictions and turn changing environmental readings into time to act.

Readings warn, declarations decide

Air quality authorities in cities like Mexico City base contingency declarations on continuous monitoring of pollutants such as ozone, PM2.5 and PM10, combined with meteorological conditions. Crossing a published reference value does not automatically activate restrictions. An official declaration does that.

That distinction matters for how you phrase any automated alert. A good message reads: "pollution levels near this vehicle have reached a threshold associated with restrictions, so check the official source and prepare." It should never claim that restrictions are active unless the authority itself has said so.

With that framing, an environmental reading becomes a preventive trigger: a signal that gives your dispatch team hours rather than minutes to confirm the official position and adapt the plan.

Location makes environmental data useful

Public air quality information is usually available, but it is scattered across services and normally requires someone to go looking for it. The fix is to combine two data streams you already have or can cheaply obtain:

• the live positions of your vehicles, reported continuously by the telematics devices on each asset
• third-party environmental data, queried for the coordinates where each vehicle is actually operating rather than one fixed monitoring point for the whole city

Querying by current position makes the environmental picture follow the vehicle. The result is still an approximation tied to the coverage of the external data source. But it is far more operationally relevant than checking a single static city value for a fleet spread across a metropolitan area.

One practical detail: public APIs often report gas concentrations in micrograms per cubic metre, while official references may use parts per billion. A simple conversion, multiplying by 24.45 and dividing by the molecular weight of the gas at standard conditions, puts the readings into comparable units before thresholds are evaluated. Particulate matter values are usually already in matching units.

From signal to alert to action

A workable monitoring loop has four steps:

• Set a cadence. Poll on a schedule matched to how often the environmental source updates, typically hourly. Polling more often adds little if the data or the GPS position has not refreshed.
• Normalize the values. Extract the pollutant fields and apply unit conversions once, so thresholds stay readable.
• Evaluate preventive conditions. Compare ozone, PM2.5 and PM10 against configured limits, and treat these as preventive triggers rather than declarations.
• Deliver the alert with context: vehicle name, time and place, the readings that fired the condition, and a link to the official source.

An alert only earns its keep if it changes the plan before the restriction changes the route. A practical response sequence looks like this:

• Check the official declaration and read the measures for the relevant date.
• Identify affected vehicles by comparing official criteria with your fleet records, including plate endings and verification status.
• Protect the schedule: reassign trips, adjust departure times or update routes before dispatch.
• Notify drivers and customers with one consistent update tied to the official source.
• Record the decision, the alert and the source link for later operational review.

The same pattern applies to any external condition

Air quality is one instance of a broader pattern. Whenever an external authority or condition changes what your fleet can do, you want the delay between the signal and your response to be as short as possible. Weather warnings, low-emission zones, wildfire zones, port status and local road rules all fit the same shape: vehicle location supplies context, an external service supplies the signal, and automation turns the two into an alert an operations team can act on, while the external authority remains the source of truth.

How RAAD fits in

RAAD's Track module already holds the piece this pattern depends on: a live position for every vehicle, plus rules and scheduled reports you can use to structure recurring checks. Because RAAD takes over the hardware you already run, you do not need to replace devices to bring external signals into your workflow. When an environmental or rule-based alert arrives alongside everything else, AI Insights reads it, holds back what does not need a person, and brings the rest forward with a reason and a proposed fix. A dispatcher sees one prioritized decision instead of a wall of notifications. Nothing touches a vehicle until someone approves it.

For partners who resell RAAD under their own brand, location-aware alerting is a straightforward way to turn a one-off hardware sale into a monthly service a customer actually notices, billed under the partner's own name and invoice.

The takeaway

Do not wait for drivers to discover a restriction after the engine starts. Combine the positions your telematics already reports with public environmental data, and frame the alert honestly as a preventive trigger. That gives your dispatch team the window they need to re-plan. The external authority stays authoritative; the automation removes the delay.