Implementation library
Choose a playbook
Each playbook explains the data flow, technical controls, and operational safeguards for a specific service. Start with the category closest to your product.
Six implementation guides written by the people on our side of the integration. Prevention, monitoring, insurance, public information, civil protection, alerting.
Implementation library
Each playbook explains the data flow, technical controls, and operational safeguards for a specific service. Start with the category closest to your product.
01 / Prevention
Prevention teams can combine wildfire risk, vegetation indicators, land condition, and historical events to rank areas for inspection, maintenance, or fuel-management work.
02 / Monitoring
Monitoring teams can build a dashboard that combines live telemetry with slower-moving datasets. The goal is a trustworthy operational view, not just a collection of charts.
Use a scheduled worker for ingestion, store normalized observations with their source timestamps, and let the dashboard read from your application store. This avoids making every visitor wait for upstream services and provides a stable audit trail.
03 / Insurance
Insurers can use historical and current wildfire information to support portfolio review, exposure mapping, customer communication, and claims triage. API results should inform professional review, not automatically deny coverage or determine an individual outcome.
04 / Wildfire information
Websites and information portals can publish regional conditions, current observations, and links to official advice. Public information should be clear, accessible, and careful about the distinction between a data observation and an official emergency instruction.
05 / Civil protection
Civil protection teams can use EFPRP data to enrich situation reports, compare conditions across jurisdictions, and provide a shared operational view. Integrate with existing command workflows rather than creating a second source of truth.
Every automated insight should identify the responsible team, the observation time, the affected area, and the next action. Keep the system advisory unless it has been formally approved as part of an emergency operating procedure.
06 / Alerting systems
Alerting systems combine EFPRP observations with local thresholds, geography, schedules, and recipient preferences. A robust service uses a queue, deduplication, retry policy, and audit record so a temporary API or messaging outage cannot silently lose an important notification.
Include alert type, affected area, severity, observation time, source timestamp, explanation, expiry or next review time, and a link to the responsible operational team.