Standards Don't Drive Recovery. Requirements Do.

The International Organization for Standardization just released ISO 14092:2026, a framework for climate adaptation planning aimed at local governments and communities. It covers risk assessment, stakeholder engagement, and progress monitoring. On paper, it’s exactly what the disaster recovery field needs: a structured, evidence-based approach to building community resilience.

My gut reaction? It depends entirely on what happens next.

The federal hook problem

In my work helping states design and implement CDBG-DR programs, I’ve watched plenty of good frameworks gather dust. A well-constructed standard or guidance document gets published, practitioners are encouraged to adopt it, and then nothing much changes. Because nothing requires it to change.

In federally funded disaster recovery, standards stick when they show up in one of two places: statute or the Federal Register. If HUD or FEMA don’t reference a framework in their program requirements or notice of funding availability, it won’t meaningfully shape how programs get designed. States follow what gets measured and what gets enforced. That’s not a criticism; it’s rational behavior given the volume of guidance they’re already trying to navigate.

ISO 14092 is a solid framework. But if it never appears in a Federal Register notice tied to disaster recovery funding, most communities will never touch it.

What it would take to matter

Moving from “published standard” to “changed practice” requires a few specific things.

Federal agencies need to explicitly require or strongly incentivize alignment. Not a general reference — specific outcomes embedded in regulatory language and program guidance. “Your Action Plan must demonstrate how proposed activities align with the adaptation planning principles in ISO 14092” is the kind of language that changes behavior. Vague encouragement doesn’t.

HUD or the relevant federal agency also needs to provide technical assistance that’s actually useful. There’s a version of federal guidance that helps practitioners understand and apply new requirements: specific, grounded in real examples, timed to when programs are being designed rather than after they’ve already been built. And there’s a version that just adds to the pile.

This matters because community development can feel like all your homework is due at once. States implementing CDBG-DR programs are simultaneously standing up multiple programs, drafting policies and procedures, hiring staff, satisfying audit requirements, and reporting to oversight bodies. Layering in a new compliance framework — even a genuinely useful one — can break implementation rather than improve it.

Capacity before frameworks

Here’s what I’d tell a state recovery director or community development officer reading about ISO 14092 right now: don’t make this your next initiative unless you have the bandwidth to do it well.

That’s not anti-progress. Building community resilience matters. Climate adaptation planning matters. But a framework adopted as a paperwork exercise produces worse outcomes than not adopting it at all. It creates the illusion of structured planning without the substance, and it consumes staff time that could have gone toward actual program delivery.

If your team is already stretched, focus there first. Get your core programs running effectively. Build institutional knowledge. Document what’s working and what isn’t. That foundation will make any future framework adoption more meaningful and more likely to stick.

For the practitioners who do have capacity — and for the federal agencies watching this space — the question worth asking isn’t “Is ISO 14092 good?” It is. The question is: what would it take to actually implement this in communities, and how do we create the conditions for that to happen? Enforcement through funding requirements matters. Targeted technical assistance matters. But the most underestimated factor is making sure communities can actually carry the load.