Supercases come in two types, each designed for a different kind of multi-borrower event. The type determines the detail fields displayed on the supercase, how the supercase is created, and whether FEMA-specific data is available.
Availability: All clients Required permissions: supercase:update (to manage supercases of either type)
Generic supercases are for any multi-borrower event that does not fall under a specific category — bulk policy changes, system-wide adjustments, or ad-hoc groupings of borrowers who need the same action.
Creation: Manually by an agent from the company view. Select Add supercase in the NavColumn, enter a name, and create.
| Field | Description | Editable | Values / Format |
|---|---|---|---|
| Event description | A description of the event or situation that prompted this supercase. | Yes | Text (multiline) |
| Event started at | The date and time the event began. | Yes | Date and time |
Detail fields are editable directly from the supercase detail page. Changes save automatically with a brief delay.
Generic supercases have no predefined workflow steps. Use the final outcome section to record the resolution when work is complete.
FEMA supercases track the impact of federally declared disasters on your borrower population. They include structured data from FEMA — disaster details, incident type, declaration dates, government relief programs, and impacted geographic areas.
Creation: Automatically by Peach's Compliance Guard when a FEMA disaster declaration is detected that may affect your borrowers. FEMA supercases match borrowers by comparing their primary address FIPS codes against declared disaster areas. Only borrowers with active loans are matched.
| Field | Description | Editable | Values / Format |
|---|---|---|---|
| FEMA monitoring end date | The date Peach stops automatically checking for updates to this disaster declaration. | Yes | Date |
| Disaster description | The FEMA-assigned disaster number and title. | No (read-only) | Text |
| Incident type | The type of disaster (e.g., Flood, Fire, Hurricane, Tornado, Severe Storm). | No (read-only) | Text |
| Began on | The date the disaster event started. | No (read-only) | Date |
| Ended on | The date the disaster event ended. | No (read-only) | Date |
| Declared on | The date FEMA issued the disaster declaration. | No (read-only) | Date |
| Last updated | The timestamp of the most recent data refresh from FEMA. | No (read-only) | Date and time |
| Government programs | A summary of declared relief programs. | No (read-only) | Codes: IH (Individual Households), IA (Individual Assistance), PA (Public Assistance), HM (Hazard Mitigation) |
| Impacted areas | A downloadable CSV of geographic areas affected by the disaster. | No (download) | CSV with county area, FIPS code, state, and applicable government programs |
Only the FEMA monitoring end date is editable. All other FEMA fields are populated automatically from FEMA data and update when Peach refreshes the disaster information.
When a FEMA disaster is declared, Peach identifies affected borrowers by:
- Matching borrower primary address FIPS county codes against the FEMA-declared impacted areas.
- Filtering to borrowers with active loans only.
Matched borrowers appear in the supercase's impact population. You can review and adjust the population before creating subcases.
FEMA supercases create subcases of the Federal Emergency case type on each affected borrower. These subcases include a disasterId field referencing the FEMA disaster declaration. See Case types reference — Federal emergency for the subcase field details.
| Generic | FEMA (Federal Emergency) | |
|---|---|---|
| Created by | Agent (manual) | Compliance Guard (automatic) |
| FEMA data | No | Yes (disaster details, impacted areas, programs) |
| Editable detail fields | Event description, event date | FEMA monitoring end date only |
| Typical subcase type | Any case type | Federal Emergency |
| Borrower matching | Manual CSV upload | Automatic FIPS code matching |