Wildland Season Is Here. Is Your Scheduling System Ready for the Deployment Surge?

Every June, the same scene plays out in fire departments across the West and increasingly across the entire country. The first major incident of the season hits, a state mobilization order comes down, and within hours you're sending an engine, a tender, and four of your most experienced people out the door for a 14-day deployment.

And then the real work starts back home.

Who's backfilling those seats tonight? Which pay codes apply from the moment the apparatus left the station? How do you keep the deployment hours separate from regular operational hours so your reimbursement package doesn't get kicked back six months from now?

If you're managing this with spreadsheets, whiteboards, and a payroll clerk's institutional memory, wildland season isn't just a staffing challenge — it's a financial liability.

The Three Problems Wildland Season Creates for Every Department

1. Backfill at the worst possible time

Wildland deployments don't pull from your bench — they pull from your starters. The people who get mobilized are often your most qualified members, and they leave behind mandatory minimum staffing requirements that don't pause because half your B shift is on a fire line three states away.

That means hiring back into vacancies, fast, in rank order, against your CBA rules — overtime distribution logic, rotation lists, seniority provisions, rest requirements. Doing this manually during a multi-week deployment is how grievances get filed and how overtime budgets blow up without anyone noticing until the end of the quarter.

First Due Scheduling automates the hireback process against your actual business rules. When a deployment vacancy opens, the system identifies who's next, notifies them, and documents every offer and response — so when a member asks why they were skipped, the answer is in the audit trail, not in someone's memory.

2. Pay code complexity that multiplies overnight

A single deployment can generate a half-dozen distinct pay scenarios: portal-to-portal pay from mobilization to demobilization, base pay versus overtime splits, hazard or incident pay differentials, backfill overtime at the home station, and standby or staging time that's compensated differently than line time.

Get the coding wrong in either direction and you have a problem. Underpay your members and you have an FLSA exposure and a labor relations issue. Overcode hours into the wrong bucket and your reimbursement claim falls apart under review.

With First Due, deployment-specific pay codes are applied at the time the shift is created — not reconstructed weeks later from handwritten CTRs and text message threads. Every hour is tagged to the right code, the right incident, and the right funding source from day one.

3. Reimbursement packages that live or die on documentation

Whether you're submitting through a state mobilization or conflagration program, FEMA Public Assistance, an FMAG declaration, or a mutual aid cost-recovery agreement, the requirement is the same: itemized, defensible personnel cost documentation, by person, by hour, by incident.

Agencies leave real money on the table every season — not because the costs weren't eligible, but because the records couldn't survive scrutiny. Hours that can't be tied to a specific incident number. Backfill overtime that can't be distinguished from routine overtime. Pay rates that don't match the personnel roster.

When deployment hours are tracked in the scheduling system from the start, your reimbursement package essentially builds itself. Export personnel hours by incident, by pay code, by date range — with the audit trail attached. Your finance team stops reverse-engineering payroll three months after demob, and your claims stop bouncing.

What This Looks Like in Practice

A department sends a Type 3 engine on a state mobilization on June 14. In First Due:

• The deployed members are coded to the incident with portal-to-portal pay rules applied automatically, tied to the incident number.

• The vacancies at the home station trigger the hireback process immediately, run against the department's CBA rules, with every notification logged.

• Backfill hours are coded as deployment backfill — distinct from routine overtime — so they're recoverable under the applicable cost-recovery agreement.

• When the crew demobilizes 14 days later, finance pulls a single report: every deployed hour, every backfill hour, every applicable pay code, ready for the reimbursement submission.

No reconstruction. No spreadsheet archaeology. No money left behind.

Built by People Who've Worked a Fire Season

First Due Scheduling wasn't designed by a generic workforce software company that discovered the fire service as a market. It was built by people who've been on mobilizations, managed backfill from the BC's office, and chased reimbursement paperwork long after the smoke cleared.

That's why the system handles the things generic schedulers can't: CBA-driven hireback logic, incident-coded pay tracking, FLSA work period rules, and the documentation standards that state and federal reimbursement programs actually require.

Get Ready Before the Big One Hits

The best time to fix your deployment tracking was last season. The second-best time is before your first mobilization order of this one.