RC Respond

RC Respond Tracks Calls To The Contact Center. It Does Not Track Fire Events Or Cases.

This page exists because the same request keeps arriving: "use RC Respond data to track the fires we respond to" or "to deploy Mass Care." Usually the right answer is RC Care, not RC Respond.

RC Respond

Contact Center Calls

Every call that reaches the Red Cross line. One fire can generate several calls; some calls are never a case.

RC Care

Events And Cases

The system of record for disaster events, client cases and the formal DCS home fire response goal.

Rule Of Thumb

Count Fires In RC Care

Use RC Respond for demand signal and call volume, never for "fires responded to."

Guidance from Eric Klein, NHQ DCS Business and Geospatial Intelligence, 6 October 2026.

Calls vs Events

Dimension	RC Respond (calls)	RC Care (events)
Unit of record	One phone call	One event or client case
Answers	Who called, from where, about what	What happened, who we served, what we delivered
Home fire goal	Not the measure	The measure
Geography key	ZIP code on the call	Event address, county, chapter codes
Where it lives	Power BI app plus the EventLog feature layer	RC Care reports plus RC Care-derived AGOL dashboards

Which Source Answers The Question?

How many fires did we respond to?RC Care events.

Progress toward the DCS home fire goal?RC Care. Use the Home Fire Campaign Regional Dashboard or the DCS Monthly Goals Report.

Where are people calling from, and how often?RC Respond.

Deploying Mass Care?Case and event data in RC Care. RC Respond only shows the incoming call signal.

Resources

RC Care

Home Fire Campaign Regional Dashboard

Filterable, RC Care-derived. A second version sits in the DCS Monthly Goals Report.

RC Respond

RC Respond Power BI Dashboards

Many report pages. Requires a Red Cross Microsoft sign-in.

RC Respond

EventLog Feature Layer

All RC Respond calls as points, hosted on ARC NHQ GIS. Search by item name "EventLog". Very large.

Data Access

Layer: EventLog, hosted feature layer, ARC NHQ GIS. Point geometry, about 1.73 million records.
Join key: ZipCode. Enrich to chapter and county with the Red Cross geography tables; never join on names.
Derived views: "All Calls" and "SFF / MFF" (single-family and multi-family fire calls) in the DCS layer catalog, plus "National 800-RedCross Calls by County (FY24-FY26)" rolled up by FIPS.
How to pull: Page the query (2,000 per request) or run a hosted ArcGIS Notebook. Do not load the whole layer in a browser.
Rules: Read only. Sign in with your own Red Cross account. Tokens never go in documents, code or chat.

Mass Care planners asking for RC Respond usually want case counts by county and date. That is an RC Care export, filtered by event type, joined on FIPS.

Papers And Notes

OneSource And SharePoint Background

What each system holds, how OneSource is built, SharePoint history, and where RC Respond fits.

Paper library

Briefs, memos and field notes about RC Respond and RC Care are filed here as they are written.

Eric Klein, "Sage counsel" reply, 6 October 2026

Source of the calls-versus-events rule and the three resource links above. Preserved in the repository README.

Open Questions

EventLog field schema: call type, disposition, timestamp, region or chapter codes?
Refresh cadence of EventLog and of the county rollup.
How RC Respond calls link, if at all, to RC Care case numbers.