How it works
How a mobe runs on Mobilize
Every wildfire mobilization runs more or less the same arc. Local resources are overwhelmed, mutual aid is exhausted, and to protect lives and property an ask goes out for more help, up to the region, the state, or the nation.
The word travels up and down the chain until it reaches a fire department: engines, tenders, crews, and more. From there every department coordinator has to work out fast what rigs and people are ready to roll, get word back up the chain about what they're committing, and get the manifests and resource orders into the hands of the strike team leader taking resources to the fire, and up to the agency funding it, whether that's regional, state, or national. Mobilize runs that whole arc in one place, from the first availability check to the packet handed off at check-in. Here's how a mobe goes.
-
Before the call comes.
Every rig and every firefighter has a record that holds the important details, with alerts on the timelines you can't afford to miss. A lapsing certification flags itself before you find out the hard way that a firefighter isn't eligible for the role you need them in. Overdue maintenance on the tender's pump throws an alert before the tender has to roll. And keeping it current is easy: a coordinator inspecting a rig in the apparatus bay updates its status from their phone, while the bulk office work can happen at a desk. So the moment a mobe call lands, the picture you're working from is what's true today, not a status somebody typed in 2019 and never looked at again.
-
The heads-up: Ready.
The regional coordinator gets a heads-up that a call for resources is likely coming. Before anyone commits to anything, a Ready broadcast goes out to the departments most likely to roll, so crews can start squaring away their gear, their day jobs, and their families. Nothing's moving yet. They just know it's coming, which is most of what people want at that stage anyway.
-
The ask: Set.
Set is the formal ask, and it comes with a clock. Each department answers yes or no for its rigs and crews, in the app or by text, because a text still reaches a phone when the signal's too weak for the app to load. So the answer is clean and it's on the record. Commitments across the whole region show up on the regional coordinator's dashboard as they come in, keeping situational awareness sharp.
-
The roll: Go.
Go is the roll order. Once the resource orders are complete and the rigs are moving, the app submits the paperwork to every place and person it has to reach, and the current status stays visible in the app, so nobody's thumbing through a forty-message thread hunting for the one reply that counts.
-
The manifest and the packet.
When a rig commits, its manifest is already half-built from the apparatus record sitting in the system. The coordinator confirms what's changed and signs. The crew side holds the minimum staffing for each engine type and keeps the different crew roles separate, so the coordinator knows the right skill sets are going out the door. The strike team leader pulls the resource order and the whole packet of manifests on a phone, as a single PDF, and forwards it to finance at check-in.
-
And what it leaves behind.
Every broadcast, every yes or no, every clock that ran out, all of it gets recorded as it happens. If your program ever needs to show what went on during a mobe and when, it's already there waiting. If it never does, it stays out of the way.
See where you fit.
Or just talk to us: info@stationworks.io