Disaster responder intent: all divisions
Where the intent campaign stands across dated roster sources. — recorded intent, availability, deployment history, and what to fix first.
Self-updated intent
22.4%
7,380 of 32,915 responders entered their own Primary GAP intent. This is the campaign outcome metric.
Disaster responders
32,915
8 divisions, 53 regions
Any intent recorded
43.5%
14,307 of 32,915
No Primary GAP at all
7%
2,374 have nothing to confirm
Available right now
12%
4,101 show Avail = Yes
Never deployed
50%
16,299 have no DRO history
Across the dated roster sources, 22.4% of responders
entered their own Primary GAP intent. 7,380 of 32,915 count toward the
campaign outcome; 14,307 have any intent recorded. The 6,927-record
gap does not count as responder action. Reaching 90% requires 22,244
more self-updated records in -65 days.
By division
The spread is narrow, which matters: no division has solved this, so there is no internal
model to copy. North Central leads at
27.6% and NHQ trails at
16.9%.
Pacific24.2% of 6,650
SECAR20.5% of 6,291
SWARM17.8% of 6,229
Northeast25.6% of 5,818
North Central27.6% of 3,936
Central Atlantic20.2% of 3,388
NHQ16.9% of 522
OCONUS27.2% of 81
Who entered their own intent, by deployment history
The most useful cut in the data, and it holds across all 8 divisions. Self-updated intent
concentrates in the recently deployed. Sequence the campaign this way and the early numbers move
fastest; the never-deployed block is the long tail and will not answer the same message.
0-30 days61.3% of 1,112
31-90 days57.5% of 2,118
91-180 days47.4% of 2,177
181-365 days33.4% of 2,398
1-2 years26.1% of 2,593
2+ years17.2% of 6,218
Never / no date11.7% of 16,299
When were they last deployed?
50% of the combined roster has never been assigned to a DRO. That is the
population, not a data gap — and it means any target set against the full 32,915 is really
a target against two very different groups.
0-30 days1,112 (3%)
31-90 days2,118 (6%)
91-180 days2,177 (7%)
181-365 days2,398 (7%)
1-2 years2,593 (8%)
2+ years6,218 (19%)
Never / no date16,299 (50%)
When was the roster record last confirmed?
0-30 days5,027 (15%)
31-90 days7,628 (23%)
91-180 days1,647 (5%)
181-365 days1,421 (4%)
1-2 years2,499 (8%)
2+ years4,081 (12%)
Never / no date10,612 (32%)
How old is the Primary GAP assignment?
Age of the GAP start date — an assignment set years ago and never revisited is exactly
what the campaign asks people to re-confirm.
0-30 days1,086 (3%)
31-90 days2,388 (7%)
91-180 days2,252 (7%)
181-365 days5,174 (16%)
1-2 years7,009 (21%)
2+ years12,626 (38%)
Never / no date2,380 (7%)
Self-updated intent by current availability
Even among responders flagged available right now, self-updated intent is barely recorded. This is a
data-entry gap, not a willingness gap — which is the argument for the campaign, and the
reason a big number is reachable if the ask is made easy.
By region
Contactability is not in the current six-division export.
Cell phone and text opt-in remain unavailable nationally, so this report does not claim a national
text-message reach rate.
What this means for a Labor Day target
Three things follow. Name the denominator: 32,915 responders, or the
16,616 with any deployment history, or the 4,101 currently available — the same
campaign scores completely differently against each, and the difference decides whether the target
is met. Sequence by deployment recency, because that is where intent already
concentrates. Ask for the text-message columns for every division, because
-65 days is not long enough for email alone.
What these exports cannot tell you
The Disaster Responder Roster carries no login or profile-update fields, so nothing here says
how often these responders sign in. The Active Members Report carries those and not intent. To
know both reach and intent for the same person, both exports are needed for the same division.