Pacific Division disaster responder intent baseline
Where the Labor Day intent campaign is starting from — recorded intent, availability, deployment history, and how to reach people.
Intent recorded
3.3%
217 of 6,504 responders. This is the campaign metric, and it is where Labor Day starts.
Disaster responders
6,504
Pacific Division, 9 regions
Intent on Primary GAP
3.2%
210 of 6,504
No Primary GAP at all
4%
241 have nothing to confirm
Available right now
9%
555 show Avail = Yes
Reachable by email or cell
100%
6,504 have a live channel
The starting line is 3.3%, not 80%.
217 of 6,504 disaster responders — 3% — have any deployment
intent recorded at all. On the Primary GAP specifically it is 210
(3%). Reaching even a 50% target by Labor Day means moving
3,035 people in 25 days; a 90% target means
5,636. That is the real shape of the ask, and it should be said out
loud before a percentage gets promised upward.
Who already recorded intent, by deployment history
This is the most useful cut in the file. Intent tracks deployment activity, so the recently
deployed are the warm list — ask them first and the early numbers move fastest. The
never-deployed block is the long tail and will not respond to the same message.
0-30 days14% of 537
31-90 days6% of 432
91-180 days5% of 223
181-365 days7% of 520
1-2 years2% of 632
2+ years1% of 1,084
Never / no date1% of 3,076
When were they last deployed?
Half this roster has never been assigned to a DRO. That is not a data problem — it is
the population. Any campaign target set against the full 6,504 is really a target against
two very different groups.
0-30 days537 (8%)
31-90 days432 (7%)
91-180 days223 (3%)
181-365 days520 (8%)
1-2 years632 (10%)
2+ years1,084 (17%)
Never / no date3,076 (47%)
When was the roster record last confirmed?
The closest thing this export has to the "last profile update" measure. Blank means never
confirmed, which is a third of the roster.
0-30 days1,343 (21%)
31-90 days404 (6%)
91-180 days320 (5%)
181-365 days453 (7%)
1-2 years834 (13%)
2+ years823 (13%)
Never / no date2,327 (36%)
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 is asking people to re-confirm.
0-30 days200 (3%)
31-90 days288 (4%)
91-180 days677 (10%)
181-365 days990 (15%)
1-2 years1,678 (26%)
2+ years2,430 (37%)
Never / no date241 (4%)
Can we actually reach them?
Contactability is the one thing not standing in the way. 100% have an email address
or a cell number on file, and 5,563 (86%) have opted in to text messages. If the
campaign is email-only it is leaving the fastest channel unused.
Email on file6,494 (100%)
Cell phone on file6,418 (99%)
Opted in to texts5,563 (86%)
Available now (Avail = Yes)555 (9%)
Intent by current availability
Even among responders flagged available right now, intent is barely recorded — so this
is a data-entry gap, not a willingness gap.
By region
What this file cannot tell you
There are no login or profile-update columns in the Disaster Responder Roster export, so this
report cannot say how often these responders sign in — the measure the earlier
14-region engagement baseline was built on. If the campaign needs reachability by login
recency for Pacific, ask for the Active Members Report for these nine regions; that export
carries Last Login, Days Since Last Login, and Profile Last Updt. Run together, the two files
answer the whole question.
What this means for a Labor Day target
Three things follow from the numbers above. First, name the denominator: 6,504 responders,
or the 3,428 with any deployment history, or the
555 currently available — the same campaign scores completely differently against
each. Second, sequence by deployment recency, because that is where intent already
concentrates. Third, use text messages: 5,563 opted in, and 6,287 people have
to be moved in 25 days.