GCRI · Reports
Universe annual synthesis
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.
Universe annual synthesis on the record.
Universe annual synthesis: how the risk develops.
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.
Selective recall
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.
Drift between years
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.
Disclosure risk in learning records
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.
Corrections must carry forward
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.
Series production desk.
The screen a team would use to follow this subject: its measures, states and decisions. Names are examples and values are illustrative.
Series production desk
Universe annual synthesis · Annual synthesis · Edition 5
Editions in production
| 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 |
Data check, annual synthesis
Edition pipeline
- Outlineboard
- Draftauthors
- Data checkevery value
- Peer reviewtwo rounds
- Editorialdecision
- ReleaseDOI
- Correctionsversioned
The annual synthesis reads the year’s exercises across domains.
The synthesis draws on after-action records with verification evidence (NS-11). The annual cycle’s one-day stage is a planned stand-down; review and corrections continue afterwards.
- After-action contributions.
- Evaluator volunteers.
How universe annual synthesis is modelled, measured and tested.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
Model, equations and assumptions
The model structure used for universe annual synthesis, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)hazard, exposure, vulnerability and coping capacityEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Assumption | Why it is made | How it is tested |
|---|---|---|
| Hazard and exposure are independent within an event | Keeps the loss integral tractable | Compare with a copula fit on joint records |
| Couplings are linear near the operating point | Lets shocks propagate through A | Perturb beyond the linear range and compare |
| Vulnerability curves transfer between places | Local curves are rarely available | Validate against observed losses where they exist |
- Inputs
- versioned datasets with provenance
- Outputs
- distributions, never single numbers
- Code
- released with the model card and tests
- Reproduction
- same data, code, environment and seed
What is measured, and how well.
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 | Published statistics |
| 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 |
Where the evidence comes from.
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 |
Who decides, and what the evidence serves.
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 |
Outputs this topic produces
- Annual synthesis with each statement linked to a current, versioned source
- Methods annex recording changes in definition and scope
- Register of corrections made during the year
- Public-safe learning records with the basis for any redaction
What the series asks.
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.
- Which objectives did the annual programme set, and which were met, partly met or not met?
- What did exercises reveal about coordination, decision-making and technical systems under stress?
- Which findings can be published safely, and which must be withheld to protect people or systems?
- What will change in methods, systems or governance as a result?
What the series covers.
The synthesis covers the whole annual cycle.
Objectives and results
What the year set out to do and what happened, stated against the objectives.
Learning under stress
Findings from exercises, described at the level of systems and processes, not individuals.
Actions and owners
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 summarised at a level that protects people and systems.
How editions are built, and their limits.
- 01
After-action records
Structured reviews held after exercises, aggregated for publication.
- 02
System evidence
Technical records from the temporary edition Core and retained sites, summarised where safe.
- 03
Public-safe review
Content is reviewed to remove details that could harm people, systems or security.
- 04
Corrections
The synthesis is versioned like every edition; later findings lead to a new version.
How it is studied, and what the methods cannot say.
- 01Data engineering, interoperability and stewardshipStructured publishing in JATS XML · Persistent identifiers across the recordApplied here
- 02Uncertainty quantification and model validationCalibrated language in assessments · Certainty of evidence ratingsApplied here
- 03Probability and statisticsMeta-analysis with heterogeneity stated · Small-study and publication biasApplied here
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
What makes a learning record public-safe?
Why can’t one year be compared directly with the last?
Does the synthesis measure impact?
Is the synthesis an event report?
Are participants named?
Does the stand-down mean records are deleted?
Who writes the synthesis?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.