> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/institutions/risk-academy.md). # Risk Academy Risk Academy, led by the Nexus Consortium: the free learning-by-doing environment where everything the programme does is taught in the open; its faculties, streams and levels, how completion is record **Where this fits.** Institution and pillar home: Risk Academy, led by the Nexus Consortium, with GCRI Canada as issuer of record. Pillar: the Academy pillar (teach in the open). Phases: course modules from adopted standards and qualified participants at Renewal (F09, F11); completion evidence from assessed cycle tasks at Closeout (F10); learning-by-doing courses from the Foundry's systems at Planning (F14). Kind: institutional reference. ## In brief Risk Academy, led by the Nexus Consortium, is a learning-by-doing environment for the study of risk. Its courses and learning materials are free. Learners work on live models, open data and digital twins of real places, and every result states its source and date ([The Academy in the Nexus ecosystem](https://risksacademy.com/ecosystem/)). GCRI, GRF and GRA author courses in their own domains, and Risk Academy hosts them ([GCRI learning and courses](https://therisk.global/programmes/academy/)). Completing a course gives a completion record. A completion record is not a licence to practise, and no credential is issued until an accountable issuer, an assessment method and a revocation path are on record. The full pillar, with its handoffs and its work through the year, is in [Risk Academy, the pillar](/organization/programme/academy.md). ## How the Academy is organised | Element | As published | Source | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | Faculties | Nine faculties, 32 departments and 118 disciplines, spanning the Earth system and natural hazards, infrastructure, health, finance, technology and governance | [Faculties](https://risksacademy.com/faculties/) | | Streams | Five streams: RAF Foundation, RAT Technical, RAN Nexus, RAS Systems and RAX Nexus-Based Risk Management | [Programme](https://risksacademy.com/programme/) | | Levels | Four study levels: L1 Introductory, L2 Intermediate, L3 Advanced and L4 Integrative. Every course belongs to one stream and one level | [Programme](https://risksacademy.com/programme/) | | How a course works | Outcomes written so they can be assessed; lessons and worked cases; labs on real or openly licensed data; assessed activities; a completion record kept when every assessed activity is passed; achievements that stack on completion records | [How learning works](https://risksacademy.com/how-learning-works/) | | Nexus-Based Risk Management | A method that keeps enterprise risk management, ISO 31000 and COSO as its entity layer and adds the nexus layer around them ("ERM inside, NRM outside"): entity registers feed the nexus layer, and nexus findings return to entities as tolerances, scenarios and triggers | [Nexus-Based Risk Management](https://risksacademy.com/nrm/) | Nexus-Based Risk Management rests on the international risk-management standard ISO 31000 ([ISO, 2018](https://www.iso.org/standard/65694.html)) and extends it from the single entity to the coupled systems the [Model](/organization/model.md) describes, in line with the systemic-risk framing of the UNDRR Global Assessment Report ([UNDRR, 2022](https://www.undrr.org/gar2022-our-world-risk)). ## Tracks, levels and formats in the programme model The programme model sets the Academy's tracks, its achievement levels and the open formats in which any future credential would be expressed: | | | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Tracks | Foundry systems; Nexus Standards; Programme roles; Evidence and reporting; Leadership | | Achievement levels | A1 Course completion; A2 Microcredential; A3 Role qualification; A4 Cycle achievement | | Credential formats | Open Badges 3.0; Verifiable Credentials Data Model 2.0; European Learning Model | | Issuance rule | GCRI Canada is the issuer of record. No credential is issued until the assessment method, the signing key and the status and revocation path are on record. Until then completion is recorded, not credentialed. | | Credentials issued to date | 0 | What each institution contributes to the Academy pillar: | Institution | Contribution | | ----------- | ---------------------------------------------------------------------------------- | | GCRI | Authors courses on methods, data and the Foundry systems, hosted on Risk Academy. | | GRF | Authors courses on governance, policy and programme roles, hosted on Risk Academy. | | GRA | Authors courses on finance, insurance and readiness, hosted on Risk Academy. | ## Boundary A completion record is not a licence to practise. No credential is issued until an accountable issuer, an assessment method and a revocation path are on record; until then completion is recorded, not credentialed. Courses never confer a professional, regulatory or governmental status. Institutions are named as Academy partners only once a cooperation is in place. ## Naming The academy's name is **Risk Academy** (owner ruling, 2026-10-21). It is led by the Nexus Consortium. Nexortium, the technology protocol of the Nexus Consortium, powers its site; Nexortium is not its operator. ## Status today Many courses are open; the RAX stream is in development. Credentials issued to date: none (the model table above). The programme's service level is R0: information and enquiries. ## Read further * [Risk Academy, the pillar](/organization/programme/academy.md): role, records, handoffs and the year * [Academy in the ecosystem](https://risksacademy.com/ecosystem/), [Programme](https://risksacademy.com/programme/) and [Open learning](https://risksacademy.com/open-learning/) on the Academy site * [For organisations](https://risksacademy.com/for-organisations/) ## Sources * Risk Academy (2026). *Risk Academy*; *The Academy in the Nexus ecosystem*; *Programme*; *Faculties*; *How learning works*; *Nexus-Based Risk Management*. risksacademy.com, pages modified 2026-10-20, read 2026-10-21. * GCRI (2026). *Learning and courses*. [therisk.global/programmes/academy/](https://therisk.global/programmes/academy/). * ISO (2018). *ISO 31000:2018 Risk management — Guidelines*. Geneva: ISO. [iso.org](https://www.iso.org/standard/65694.html). * UNDRR (2022). *Global Assessment Report on Disaster Risk Reduction 2022: Our World at Risk*. Geneva: UNDRR. [undrr.org](https://www.undrr.org/gar2022-our-world-risk). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/institutions/risk-academy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.