TerraGuard

Reports & Notifications

TerraGuard generates AI-powered structured reports and delivers multi-channel notifications to keep response teams informed about disaster events.

Overview

TerraGuard provides two complementary systems for communicating event information to response teams: AI-generated reports that provide comprehensive situational analysis, and automated notifications that deliver timely alerts through email and Telegram.

Report Generation

AI Agent Architecture

Reports are generated by an AI agent that uses the ReAct (Reasoning + Acting) pattern. The agent has access to five MCP (Model Context Protocol) tool servers, allowing it to actively research and compile information rather than relying on a static prompt.

Loading diagram...

The five MCP tools available to the agent:

MCP ServerPurpose
Database SearchQuery event records, measurements, timeline, affected countries
Vector SearchSemantic search over the knowledge base for relevant content
Document RetrievalFetch specific documents, SITREPs, and advisories
GeoPopPopulation exposure data, reverse geocoding, admin regions
Web LinksGenerate links to external resources and source documents

ReAct Pattern

The agent follows an iterative loop:

  1. Reason — Analyze what information is needed for the current report section
  2. Act — Call one or more MCP tools to retrieve that information
  3. Observe — Process the returned data and decide if more information is needed
  4. Repeat — Continue until the section has sufficient content
  5. Synthesize — Compile findings into structured prose

This approach produces higher-quality reports than single-pass generation because the agent can iteratively gather and cross-reference information.

Report Structure

Generated reports follow a standardized 10-section structure:

SectionContent
1. Executive SummaryHigh-level overview of the event and key impacts
2. Event DetailsType, location, measurements, source data
3. TimelineChronological progression of the event
4. Impact AssessmentCasualties, displacement, infrastructure damage
5. Population ExposureAffected population by country and region
6. Response ActionsGovernment and humanitarian response activities
7. Situation AnalysisCurrent conditions and operational environment
8. Access & ConstraintsLogistics, access limitations, security concerns
9. Outlook & ForecastExpected development and anticipated needs
10. Sources & ReferencesLinks to all referenced documents and articles

Screenshot: Report generation interface showing a "Generate Report" button, progress indicator with current agent step, and the resulting report with expandable sections

Editing Reports

Generated reports are loaded into a rich text editor (TipTap) where you can:

  • Edit any section's content manually
  • Reorder sections
  • Add custom sections or notes
  • Format text with headings, lists, bold, italics, and links
  • Insert tables and images

Screenshot: Rich text editor showing a generated report being edited, with the formatting toolbar visible and a section being modified

Exporting Reports

Completed reports can be:

  • Downloaded as PDF
  • Shared via a permanent link
  • Sent directly via the notification system
  • Attached to email notifications

Notification System

How Notifications Work

The notification engine evaluates organization-specific matrices to determine which teams should be alerted about which events. This ensures that the right people receive the right information based on their organization's mandate and operational focus.

Loading diagram...

Notification Triggers

Notifications are sent in several scenarios:

TriggerDescription
New EventA disaster event is first detected above the organization's threshold
Alert Level ChangeAn event is upgraded (e.g., GREEN to ORANGE, ORANGE to RED)
Downgrade NoticeAn event's alert level is reduced
Scheduled Follow-upAutomatic updates at +2h, +12h, and +24h after event onset
Manual TriggerA team member manually sends a notification to their team

Scheduled Notifications

For significant events, the system automatically schedules follow-up notifications:

  • +2 hours — Initial enrichment summary with early news coverage
  • +12 hours — Comprehensive update with full knowledge base content
  • +24 hours — Situation evolution report with response status

These intervals are configurable per organization. Each scheduled notification includes the latest available information at send time.

Email Notifications

Email notifications use a templated format that includes:

  • Event title, type, and alert level with color coding
  • Location map thumbnail
  • Key measurements (magnitude, wind speed, etc.)
  • Affected population summary
  • Latest AI summary excerpt
  • Links to the full event detail page and report

Screenshot: Sample email notification showing the TerraGuard header, event details card with map, measurements summary, and action buttons linking to the platform

The email template system supports:

  • HTML-formatted messages with responsive layout
  • Organization branding and customization
  • Inline map images
  • Direct links to the platform

Telegram Integration

Teams can connect a Telegram channel or group to receive event notifications. Telegram messages include:

  • Event title and alert level emoji indicators
  • Location and key measurements
  • Brief AI summary
  • Direct link to the event detail page

Configure Telegram integration in the team settings by providing a Telegram bot token and chat ID.

Screenshot: Notification settings page showing email configuration, Telegram bot connection, and notification preference toggles for different alert levels

Notification Preferences

Each team can configure:

  • Alert level threshold — Minimum alert level to receive notifications (RED only, RED + ORANGE, or all)
  • Event types — Which disaster types to be notified about
  • Channels — Enable/disable email and Telegram independently
  • Quiet hours — Suppress non-critical notifications during specified hours
  • Digest mode — Batch low-priority notifications into periodic digests

Next Steps

On this page