The Global Centre for Risk and Innovation (GCRI)
The annual synthesis draws together what was learned across a year of work: findings revised, methods improved, errors corrected and questions left open. An annual record is only useful if it is honest about what did not work and comparable from one year to the next. This page sets out how an annual synthesis is compiled from versioned sources, how learning records are made safe to publish, and how readers can trace each statement back to its origin.
GCRI · Established · service level R0
An annual synthesis is a report that draws together what a year of work learned: findings revised, methods improved, errors corrected and questions left open. It is useful only if it is honest about what did not work and comparable from one year to the next, with every statement linked to a versioned source.
Where people and networks concentrate, the exposure through which shocks travel between systems, shown for Middle East and North Africa as an example geography for this subject.
The working screen behind this subject: its structure, terms and states. Names are placeholders and values illustrative.
Nexus Universe annual synthesis · Annual synthesis · Edition 5
| Annual synthesis | Global | Data check | 75 | W33 |
| Country profile 7 | Country | Peer review | 96 | W13 |
| Water outlook | Sectoral | Drafting | 35 | W17 |
| Methods note 4 | Methods | Released | 100 | done |
Annual public-safe learning records. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
A year's record drifts toward what succeeded and what was memorable. Without a defined method for selecting what enters the synthesis, the annual account becomes a narrative rather than evidence.
Definitions, scopes and methods change from one year to the next. Comparisons across annual syntheses that ignore those changes report shifts in method as shifts in the world.
Lessons from incidents, tests and partnerships can expose people, systems or confidential agreements. Making records public-safe means removing identifying and security-sensitive detail while keeping the lesson intact.
If a report corrected during the year is summarised from its original version, the synthesis reintroduces the error. Synthesis must draw on the current version of each source.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Lessons learned | Documented knowledge from experience, positive or negative, recorded to change future practice. |
| Public-safe learning record | A learning record reviewed and, where needed, redacted so that publishing it creates no new risk. |
| Carried-forward question | An open question recorded in one year's synthesis and tracked in the next. |
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Synthesis statements linked to a versioned source | percent of statements | annual | Editorial audit | REPORTED |
| Reports corrected during the year | count | annual | Correction notices and version history | OFFICIAL |
| Changes in definition or scope from the prior year | count, each described | annual | Methods annex | DECLARED |
| Learning records withheld or redacted for safety | count by reason | annual | Disclosure review record | DECLARED |
| Open questions carried forward | count | annual | Synthesis annex | REPORTED |
| Outputs in the year with persistent identifiers | percent of outputs | annual | Crossref and DataCite deposit records | OBSERVED |
The topic as a computational graph: named sources feed the methods, an evidence review gates the outputs, and the decisions stay with the authorities that hold them.
Fig. 02Nodes carry their type, two metric rows and a state; connectors show what feeds what; dashed frames name the owners; the timeline is the cadence. Design of the pipeline, not a record of a run.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Source | What it gives | Licence class |
|---|---|---|
| Crossref metadata | DOIs, versions, update notices and relationships for the year's outputs | Open metadata, no reuse restrictions |
| DataCite metadata | DOIs and metadata for datasets, software and other outputs | CC0 |
| OpenAlex | Citations and uses of the year's outputs across the literature | CC0 |
| Zenodo | Archived versions of reports, data and annexes | Metadata CC0, licence per record |
| UNDRR Global Assessment Report and UN SDG progress reports | External annual and periodic syntheses for comparison of scope and method | Free to read, United Nations terms |
Nexus Reports prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Governing boards and their audit or ethics committees | Whether the year's record is complete and honest about failures and corrections | Correction register, withheld records by reason and open questions |
| Partner institutions and funders | Which lines of work to continue, change or stop | Synthesis statements with sources and the lessons from tests and incidents |
| Series editors | Which open questions to prioritise in the coming year | Open questions carried forward with the evidence gap behind each |
Exercises and integration programmes generate learning that is easily lost: participants disperse, temporary systems stand down and lessons stay in private notes. An annual synthesis turns that experience into a public-safe record, so that the next cycle starts from evidence rather than memory and so that others can learn from the programme's failures as well as its results.
The synthesis covers the whole annual cycle.
What the year set out to do and what happened, stated against the objectives.
Findings from exercises, described at the level of systems and processes, not individuals.
Changes adopted as a result, with the owning institution named.
The synthesis follows established after-action practice in emergency management and engineering: it focuses on what happened, why, and what will change, rather than on assigning blame. It separates observations from interpretations, and it records actions with named owners so that the following year can check whether they were taken. Learning that cannot be published safely is kept in restricted records and summarized at a level that protects people and systems.
Structured reviews held after exercises, aggregated for publication.
Technical records from the temporary Nexus Core and retained sites, summarized where safe.
Content is reviewed to remove details that could harm people, systems or security.
The synthesis is versioned like every edition; later findings lead to a new version.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.