Straight into the service manual page
WrenchQuarry
More

Climate normals: 2 periods to compare for dispatch planning

WrenchQuarry Editorial Team · Published · 10 min read · How these guides are written

The two climate normals periods to compare for seasonal dispatch planning are 1991–2020 and 1981–2010. Both are official 30-year sets published by the National Centers for Environmental Information, and comparing them shows how your local baseline moved so you can adjust seasonal crew plans before the season opens.

Key takeaways

  • The current release is 1991–2020; the previous release is 1981–2010, and there are twenty years of overlap between the two datasets.
  • NCEI recommends the current release unless you have a specific use case for the older versions; for baseline drift checks, comparing against 1981–2010 is one reason to use the older set.
  • Most of the U.S. was warmer, and the eastern two-thirds of the contiguous U.S. was wetter, from 1991–2020 than the previous normals period, 1981–2010.
  • January temperatures have risen in the new normals by 0.5–1.5°F across most of the country.
  • Pull both 30-year sets for your stations, compare month by month, and check each proposed shift against your own call log before you commit crew hours.

What climate normals are and why dispatchers should care

Seasonal dispatch planning rests on a weather-based guess. When you schedule spring tune-ups, summer AC overload calls, or winter freeze response, you are estimating demand based on past weather patterns. Climate normals give you a stable, official baseline for that estimate. They are averages, not forecasts, but averages built on decades of station data give you something better than memory.

The National Centers for Environmental Information (NCEI) produces the official set. According to NCEI, the official normals are calculated for a uniform 30 year period, and consist of annual/seasonal, monthly, daily, and hourly averages and statistics of temperature, precipitation, and other climatological variables from almost 15,000 U.S. weather stations.

For a dispatch lead running a small crew, those daily and hourly statistics matter as much as the monthly means. You are not buying a consumer weather subscription. You are reading the official NCEI baseline, then translating it into crew hours and call volume.

Normals also answer a question your memory cannot: what counts as normal in the first place? A winter that felt mild, a spring that felt late, a storm season that felt long — each of those impressions is one realization of a much longer record. The 30-year window smooths out the single seasons that stick in your head and gives you a baseline you can defend when you explain the staffing plan to an owner or a bookkeeper.

The two normals periods you should compare

According to NCEI, the agency generates the official U.S. normals every 10 years in keeping with the needs of our user community and the requirements of the World Meteorological Organization (WMO) and National Weather Service (NWS). The current release covers 1991–2020. The previous release covered 1981–2010.

Why compare two periods instead of simply using the newest one? Because each window shifts the baseline for your shoulder seasons. A spring that used to begin in a certain month may begin earlier in the newer window. A fall that ran long may taper sooner. Comparing the two windows side by side shows you how your local baseline moved, and that movement is exactly what should inform your seasonal crew plan.

The comparison also protects you from a subtle planning error. If you only ever read the newest window, you will have no sense of how fast things moved under you. A dispatcher who refreshes the schedule every year against a single fixed baseline can feel confident while the ground shifts quietly beneath the plan. Two windows side by side make the shift visible rather than assumed.

NCEI's normals search lets you search for one or multiple station locations, conventional 30-year normals and 15-year normals for all available variables and statistics. For dispatch planning, you want the 30-year sets.

For this comparison, the older set is justified because you are checking drift between windows, and that drift affects your scheduling windows.

Here is how the two windows stack up:

Feature1991–2020 normals1981–2010 normals
Standard period length30 years30 years
Overlap between windows20 years of overlap20 years of overlap
Recommended default useCurrent releaseOlder version, only with a specific use case

How the baseline moved between the two periods

NCEI notes there are twenty years of overlap between the current normals and the previous iteration (1981–2010), with the shared years falling in 1991–2010, which makes the annual changes between these two datasets somewhat muted compared to trends over the same period. Read that carefully: even with a muted signal, the newer window shifted enough to matter for a dispatcher planning crew coverage.

NCEI reports that most of the U.S. was warmer, and the eastern two-thirds of the contiguous U.S. was wetter, from 1991–2020 than the previous normals period, 1981–2010. Two different directions of change, and both have dispatch consequences. Warmer baselines move freeze events and tune-up demand. Wetter baselines move storm-driven call spikes and the slack you need in the schedule around them.

The shift in January is worth calling out because January is when many firms plan the spring push. NCEI reports that January temperatures have risen in the new normals by 0.5–1.5°F across most of the country.

One region went the other way. The north-central region was a notable outlier that cooled by more than 1.0°F in some places, but generally follows annual cooling patterns. If you dispatch in the north-central U.S., the direction flips for you.

That contrast is the practical reason to read your own stations rather than a national headline. The national direction and your service area's direction can disagree, and the crew schedule has to follow the local one.

Pulling the numbers for your stations

Your first task is to pick the stations. Use two or three nearest to your service area rather than the city label alone. Station siting matters because your technicians care about the neighborhood where they park the van, and a station on the far side of a ridge or a river may not describe the conditions your crews actually drive into.

In the NCEI normals search, look up the 1991–2020 30-year set for the same stations, then confirm on the NCEI site that the 1981–2010 set is available for those stations. Pull monthly temperature and precipitation averages first. Then add the daily and hourly statistics if your dispatch planning touches on time-of-day coverage, such as a night freeze window or an afternoon peak load window.

Export the data and keep it in one file. Label each column with the window as well as the variable name. When you are several windows into a spreadsheet, a column headed only by the variable name will cost you an hour of guessing later.

If your firm works across county lines or across a metro area with varied terrain, pull a station on each side. A single station can hide a meaningful difference between the north end and the south end of your service radius, and your crew plan may need to reflect both.

Turning a baseline shift into a crew schedule

Once you have both windows in front of you, walk the calendar month by month and ask one question: does this month's baseline shift enough to move my crew plan?

If the newer window shows a warmer January across most of the country, your freeze calls may land differently than they did under the old window. If the eastern two-thirds of the contiguous U.S. was wetter in the newer window, storm-driven service calls in those months will need more slack in the schedule.

If your service area sits in the north-central region that cooled, your plan inverts. Later starts for spring work. Your crew plan needs to reflect that direction, not the national direction.

Treat each month as a planning cell. Write down the crew hours the old window implied, the crew hours the new window implies, and the difference between them. That difference is your adjustment. It does not have to be dramatic. It has to be deliberate, and it has to be written down so the person who inherits the schedule can see why the numbers moved.

An adjustment this size also gives you something to defend. When an owner asks why the spring crew plan differs from last year's, a month-by-month comparison of two official 30-year windows is a stronger answer than a hunch about the weather.

Illustrative example: one month's crew hours

Suppose your firm has 4 technicians, and a month that needed 30 crew hours under the old baseline looks warmer in the newer window. You might plan 20 hours for that month instead. The 10-hour difference is your adjustment, and you write it down with the reason before you change the schedule. These figures are illustrative only and come from no company or data source.

Checking your shift against your own call log

Weather normals tell you what the climate did. Your call log tells you what your customers did. A dispatch lead who aligns the two gets a much sharper picture than one who trusts either source alone.

Take the months where the two normals windows diverged most. Look at your call volume in those months across the same years. If warmer Januarys in the newer window corresponded with earlier spikes in service calls in your log, you have local confirmation of the shift.

Do this for the months that matter most to your dispatch plan: the shoulders where you decide to add or drop a truck. Those are the months where a baseline shift changes a real decision about crew coverage rather than a minor tweak.

You are looking for pattern, not precision. If your call log shows a clear move in the same direction as the normals shift, you can plan with more confidence. If it does not, your customer base may be behaving differently than the regional climate suggests, and your own log should win the argument.

Where normals leave a question open

Normals do not give a number of extra calls for your service area. The relationship between a normals shift and call volume is yours to read from your own history. Ask your scheduling or customer service lead what the pattern looked like over the past two windows, and let your log and the normals baseline meet in the middle.

A practical checklist before you commit the schedule

  • Confirm you have both 1991–2020 and 1981–2010 30-year sets for your stations.
  • Note the direction of change in your service area, not the national direction.
  • Pull monthly, daily, and hourly statistics for the months that drive your seasonal plan.
  • Compare the two windows month by month and write down the adjustment.
  • Check each adjustment against your own call log across the same years.
  • Hand the plan to your scheduling lead before the season opens.

Next step: Today, open the NCEI normals search, pull the 30-year monthly temperature and precipitation for your nearest station, and mark the months where you add or drop a truck.

Related guides: 5 Atlassian flow limits to check for a dispatch queue · Avoidable truck rolls: 3 dispatch mistakes to fix · Check 5 guardrail and toeboard limits before dispatch.

FAQ

Do I need the 15-year normals for dispatch planning? No, the 30-year sets are the ones to use for this comparison.

Should I use only the newest window? No. A single window cannot show drift, so you need 1981–2010 alongside 1991–2020.

What if my area warmed in one month and cooled in another? Plan month by month. A single annual figure hides the seasonal moves you actually schedule around. The north-central region is a reminder that direction can flip against the national pattern, so read your own stations rather than assuming the country's average describes your service area.

How often should I refresh this comparison? Rerun it when the next NCEI release lands, and compare against your call log the same way. Keeping the process repeatable means you are not rebuilding your method from scratch.

Sources

More field guides