Blog

Fire progression map vs. daily perimeter update: what's the difference?

Aerial view of a wildfire's glowing edge cutting across dark terrain under a smoke plume at dusk.

If you've sat through more than a few IMT briefings, you've heard both terms thrown around like they mean the same thing. They don't, and mixing them up in a planning meeting is a good way to hand Ops a product that answers the wrong question.

Fire progression map: the history of the burn

A progression map is a time series. It stacks successive perimeters, usually one per operational period, on a single base map so you can see the fire's growth day by day, or sometimes hour by hour during a run. Each ring is a snapshot of where the edge sat at a given point. Line them up and you get a visual record of spread rate, direction, and the terrain or fuel breaks that slowed or sped things up.

Planning Section pulls progression maps for a few specific jobs:

  • Briefing incoming overhead on how the fire has behaved so far
  • Supporting the narrative in the ICS-209 and other situation reports
  • Feeding after-action review and, eventually, the long-form fire history

A progression map is backward-looking by design: it shows how the fire got where it is, which matters when you're trying to predict where it's headed next or explain a run to a cooperator who wasn't on scene for it.

Daily perimeter update: where the line sits today

A daily perimeter update is a single, current snapshot: the active fire edge as of this morning's overflight, infrared pass, or satellite capture. No history stacked underneath it, just today's line, often split into active fire front and already-burned interior.

This is the product that drives tomorrow's operational period. Division supervisors use it to set tactics. Resource advisors use it to flag what's now inside the line versus still threatened. Structure protection groups use it to recheck which addresses just moved from "watch" to "burned over." If the morning briefing runs on yesterday's perimeter, crews are working off a line that's already wrong, and on an active fire that gap can be the difference between a defensible position and a crew getting cut off.

Why the distinction matters for planning

Pull the wrong one and the briefing goes sideways. A progression map in a tactical briefing buries the one line that matters under six days of history nobody needs for tomorrow's shift. A single daily perimeter dropped into an after-action report, with no context for how the fire got there, leaves out the story anyone reviewing the incident wants.

The two aren't competing products. A progression map is just a series of daily perimeters, captured consistently and stacked. If your daily perimeter updates are solid, discrete, and timestamped, building the progression view afterward is bookkeeping, not a separate data collection effort. If the daily layer is spotty (skipped days during smoke-choked overflights, inconsistent GSD between sources, a missed update over a long holiday weekend) the progression map inherits every one of those gaps, and now your fire history has a hole in it that someone has to explain in the closeout report.

That's the part worth building into standard operating procedure before the next big one: whoever owns the daily perimeter product should also own making sure it's archived in a form the progression map can use later. Separate workflows, same underlying data, and a lot less rework if someone thinks about both uses on day one instead of day twelve.

Where this fits for an active incident

On an active or recently contained fire, the operational need is almost always the daily update first: the current line, active front separated from burned interior, graded for severity where that matters for rehab planning. The progression view comes later, built from whatever daily perimeters got captured along the way.

That's the gap Fire Perimeter Map is built to close. It generates a fresh fire perimeter daily from wide-swath satellite imagery while the event is active, splitting active front from burned ground and grading severity across it, so Planning has a current line for tomorrow's shift and a clean, consistent record to build the progression map from once the thing is out.

If your next incident needs a perimeter that updates every day without someone chasing down a flight schedule, that's worth a look before the next activation.

Get started

← Back to the blog