ERM Gap Analysis
Score Your ERM Program: Fully, Partially, or Not in Place
You run or inherited an existing ERM program, and the honest answer to "where does it actually stand?" is that you are not sure. Policies exist, a risk register exists, controls are named, but you cannot separate what is operating in substance from what is only documented. An enterprise risk management framework is a program, not a document, and organizations that treat it as a documentation exercise often fail audits and produce governance outputs disconnected from operational reality. You need an objective read before an examiner gives you one.
Free Download
Get instant access to the checklist
- The fully / partially / not-in-place scoring method
- A gap log with named owners you can take to the board
- Section-by-section checklists across all nine ERM domains
The Enterprise Risk Management Framework Checklist
Yes. Gap analysis against an existing program is one of three supported use cases, alongside initial design and audit readiness. You score each element where it stands today rather than building from a blank page.
It is framework-neutral and cross-references multiple authoritative sources. Where an item maps to a specific component, the source is noted, and you are expected to layer your own sector obligations on top.
It covers the enterprise program. Single-domain programs, such as a standalone information security risk program, are addressed only where they must integrate into the broader ERM framework, not as separate scopes.
No. It is an informational and educational self-assessment reference, not legal, regulatory, or audit advice, and it does not guarantee any particular examination outcome. Calibrate it to your size, industry, and applicable law, and confirm requirements against primary sources.
Get an objective read on where your program really stands