The record your consultants work from, and hand back to.
A jurisdiction pays for a study. The study leaves with the vendor. Five years later somebody pays to rebuild the same data from the same sources. Hazzard is the other arrangement: you hold the repository, the people you hire get scoped access to it, and what they produce comes back into it.
Six things, in one place, with their sources attached.
Documents
Mitigation plans, emergency plans, flood studies, consultant reports — parsed to pages, sections, tables and figures, and searchable across the whole shelf.
Addressed by content hash, so the county and the town uploading the same plan hold one document between them, not two copies.
Hazards and threats
A 73-item registry across 14 categories — seeded from national data for your exact counties, decided by your team, established by an authorized approver.
62 hazards and 11 threats. 18 carry a FEMA National Risk Index crosswalk; the rest are hazards NRI does not model, shown as the gap they are.
Footprint
Jurisdictions, county-wide declarations, facilities, service territories, corridors — and the watched places outside your boundary whose failures land on you.
Counties and towns both, including New England county subdivisions, so a 15-town county is one footprint rather than 15 accounts.
Evidence
Every hazard finding in the record traces to a verbatim quote on a numbered page of a named document, with the date that document was current.
Page anchors are durable and survive reprocessing; block-level anchors are verified at render and fall back to the page rather than breaking.
Decisions and audit trail
Who included a hazard, who excluded one, who approved the list, what changed since the last version — kept as a record, not a memory.
Append-only. There is no update path and no delete path anywhere in the codebase, by design.
Government data
8 federal feeds synced daily and joined to your footprint — plan statuses, the National Risk Index, mitigation grant awards, disaster declarations, census profiles, county climate history, active weather alerts, and the county count of residents who depend on electricity for life-maintaining medical equipment.
Every row carries the vintage of the source that produced it, so nobody has to ask which version of the flood data a decision was made on.
Every row knows where it came from, and when.
“Which flood layer is current?” is a question that costs real consultant hours on every project, on every cycle. It costs them because vintage is usually a thing someone remembers rather than a thing the data carries. Here it is a field.
| Feed | Source | Scale | Stamped with |
|---|---|---|---|
| Plan Status Registry | FEMA OpenFEMA — Hazard Mitigation Plan Statuses | ~36,600 plan records | lastSyncedAt per rollup |
| National Risk Index | FEMA National Risk Index v1.20 (county table) | 18 hazards × 3,200 counties | nriVersion 1.20.0 |
| HMA Projects | FEMA OpenFEMA — Hazard Mitigation Assistance Projects | ~56,000 awarded projects | run watermark |
| Disaster Declarations | FEMA OpenFEMA — Disaster Declaration Summaries | ~70,000 declaration × area rows | lastRefresh |
| Census ACS Profile | U.S. Census Bureau — ACS 5-year Data Profile | Counties, places, county subdivisions | vintage 2023 |
| Jurisdiction Bridge | Derived — jurisdiction identity resolution | Plan IDs → county, place, county subdivision | writes only where a value is absent |
| NOAA County Weather | NOAA NCEI — nClimGrid-Daily county averages | 60-month rolling window | quality: prelim → scaled |
| NWS Active Alerts | NOAA National Weather Service — active alerts | National active set, county-joined | expiresAt, filtered on read |
| HHS emPOWER | HHS emPOWER — electricity-dependent Medicare beneficiaries | 3,233 counties, monthly | run watermark |
| Atlas Rollups | Derived — plan-cycle counts per state and county | Every state and county in the registry | computedAt + populationSource |
Daily, 07:00 UTC. 8 of the 10 entries fetch from an upstream publisher. The 2 whose source reads derived are computed from data already held, so they are not counted as sources. A feed that is skipped is recorded as skipped — it never reads as a zero.
Access has a start date and an end date.
Consultants, neighbouring jurisdictions, regional planning agencies and state programs all need to see some of your record. None of them needs to become a member of your organization to do it.
01
Notice to proceed
Grant read-only access to the surfaces the scope actually needs. The grant is logged with who issued it.
02
During the work
They work from the same footprint, the same hazard inventory and the same cited evidence you do — so there is no reconciliation call about whose flood layer is current.
03
Deliverable
The plan, the studies and the models come back into your library as documents you hold, parsed and cited alongside everything else.
04
Closeout
Revoke the grant. The work stays; the access does not.
You hold the record. That is the whole arrangement.
Your data leaves whenever you want it to
Export the documents, the hazard inventory, the evidence and the audit history in open formats, on demand — not as a courtesy at the end of a contract, and not conditional on renewing.
Consultants get scoped access, not your login
A partner grant is read-only, limited to named surfaces, granted when work starts and revoked when it closes. It is not a role, so nobody becomes a member of your organization to do a study.
Every consequential action is on the record
Hazard decisions, approvals, uploads, access grants and re-runs all write an audit event. The table is append-only: no update path, no delete path, no exceptions.
One document, however many jurisdictions hold it
Documents are addressed by content, so a regional plan shared across member towns is one document with many claims on it. Release the last claim and it is gone; release yours and everyone else's stays.
Hazzard is in beta and we don't claim certifications we haven't earned. If your security or procurement review needs something specific, ask us for it directly.
Start the record with what you already have.
Create your organization, define the footprint, and upload the plan you paid for last cycle. The hazard list seeds itself from national data for your exact counties.
- A footprint that spans every jurisdiction you cover
- A 73-item hazard and threat registry, seeded for your counties
- 8 federal data feeds joined to it, synced daily
- Findings cited to a source page, with the rejections shown too