Every active event has its own page: where the data came from and how fresh it is, the impact zones and what each means, what is inside them, and how it compares with the past.
Help Center
How the platform works, written for the people who use it daily. Each guide covers what a feature does, how to set it up, and what its output does and does not tell you.
For the page you were on
Monitor
The live map, what is coming for your areas, and how Calchis gets your attention when something changes.
Where the map opens and why, setting a home view, choosing layers, reading a hurricane's forecast cone, and looking up an address without losing your place.
The Hazard Vulnerability Analysis pre-filled from your county's federal record, and the live National Weather Service products that should activate the plan it supports.
How to fill in the 52-hazard analysis in Calchis: what each column asks, which three run backwards, how relative risk is worked out, and how to approve the document a surveyor will read.
The forecasts that cover the places you monitor — NWS watches, SPC outlooks and the NHC hurricane cone — each with its own expiry, and the conditions that fire on them before anything has happened.
The scoreboard along the bottom of every page: what is active inside your areas, what is new since you last looked, and how to set it up for a wall display.
Every active event has its own page: where the data came from and how fresh it is, the impact zones and what each means, what is inside them, and how it compares with the past.
Set the name that goes on your forms, change your password, export everything, choose which Calchis product your navigation shows, or close the account.
See your plan and what you are using against its limits, upgrade, and manage or cancel a subscription.
What Calchis will and will not do to reach you: the on-screen banner and tone, email alerts for your areas, condition notices on an incident, and the settings that decide them.
Analyze
Hazard scoring, parametric triggers, portfolios, and the exports an underwriting or ILS workflow depends on.
What the 0–10 score means, why it is labeled hazard rather than risk, and how to read the components behind it.
Create an API key, know your rate limit and daily quota, and send trigger events to your own systems by webhook.
Define a parametric threshold against live federal event data, choose where to be warned, and get an auditable record of every evaluation.
Load locations, see aggregate hazard exposure, and understand what an exceedance probability curve does and does not tell you.
Get analysis out of the platform in the formats downstream systems and other people actually accept.
What is in the catalog, how to read a bond's trigger structure, and how the catalog connects to live trigger monitoring.
Respond
Running an incident, tracking what you have, and coordinating across agencies from the EOC.
Create your agency, add colleagues by email, and choose what each can change — the agency's conditions and incidents are shared by everyone in it.
Send CCIR-met and trigger-breached notices to an EOC duty inbox or a distribution list, with confirmation and a stop link.
Create an incident, build a common operating picture, generate ICS forms, and share a live link with partner agencies.
Plan a tabletop, drill or full-scale exercise, run its injects, record who took part, and turn it into an after-action report.
Place a hypothetical earthquake, hurricane or wildfire, see who and what is inside its zones, and take it into a tabletop exercise.
Keep a readiness picture of what you have, catch shortfalls before an activation, and commit resources to incidents.
Register your agency, post and answer mutual-aid requests, and track fulfillment on one board across jurisdictions.
How CCIRs, escalation prompts and decision points fit together: what fires, what it forces someone to decide, and where that decision is recorded.
Add a county, city, tribal area or state as a monitored area, then use it as the jurisdiction on the dashboard and in the briefing PDF.
Looking for the scoring architecture rather than a how-to? See methodology, data sources, or the API documentation.