GCRI · Registry
Programme status
A programme status such as planned, active, paused or closed is a short word that readers take as a long claim. They infer funding, staffing, delivery and even results from it, though the word asserts none of these on its own. This page sets out what a status assertion records, who may make and change it, how statuses drift away from the programme they describe, and what a funder, auditor or partner needs to see before relying on one.
How the work runs.
Record ledger
Programme status · Registry · Ledger head 4520089
- Records registered3446
- Complete provenance, % of records93Normal
- Open corrections15Watch
- Rights holds0Info
Latest records
| NX-R-20740 | Programme status | v2 | 3557271 | Registered |
| NX-P-99526 | Publication | v1 | 9568898 | Registered |
| NX-E-98224 | Evidence record | v2 | 2471930 | Correction open |
| NX-C-85422 | Participation | v1 | 7123058 | Rights hold |
Version history
- v1NEWRegistered with sources
- v2FIXUnit corrected, reason recorded
- v3OPENCorrection requested
Fig.Record ledger: example names and illustrative values, not a record or a live system.
Programme status: how the risk develops.
What a programme state does and does not mean. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Status outlives its evidence
A status is set at one moment and then left. Staff move, funding lapses or a phase ends, but the record still reads active. Without a review date and a named owner, an unchanged status cannot be told apart from a confirmed one.
Target read as delivery
Registries often hold planned scope beside actual progress. When a design target, a launch announcement or a pilot sits under the same status as an operating service, readers take intention for implementation, and implementation for a verified outcome.
Vocabulary drift
Each partner uses its own words: open, live, ongoing, in delivery. When records are merged without a controlled list and a crosswalk, one status means different things in different rows, and counts across the registry stop being comparable.
Reliance cascades
Funders schedule tranches, partners commit staff and reviewers cite the programme as evidence of capacity, all from the status field. A stale or inflated status therefore travels into budgets, reputations and later audit findings far from where it was entered.
How programme status 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.
Datasets and provenance
The data classes behind programme status and what is recorded about each before it is used.
| Data class | Provenance recorded | Resolution stated | Licence checked |
|---|---|---|---|
| Satellite imagery, optical and radar | sensor, processing level, acquisition date | pixel size and revisit | per scene |
| Reanalysis and climate model output | model, experiment, member, version | grid and time step | per release |
| In-situ sensors and gauges | station, instrument, calibration record | point and sampling rate | per network |
| Population and asset exposure | method, vintage, input sources | cell size and unit | per release |
| Boundaries and reference geography | producer, edition, date | scale | per edition |
- Lineage
- W3C PROV record from source to figure
- Principles
- FAIR: findable, accessible, interoperable, reusable
- Gaps
- shown as missing, never filled silently
Status records keep each domain’s work honest about what exists.
- WaterIn practiceA basin study listed as planned is not shown as under way.What a reader can checkStatus and the record behind it
- HealthIn practiceA surveillance analytics capability is described by purpose until verified.What a reader can checkVerification evidence
- EnergyIn practiceA grid study waiting for operator data says so.What a reader can checkBlocking dependency stated
Status records feed the Foundry Build and Readiness series. Each status would carry a contextual identifier under NS-9 of the proposed Nexus Standards; readiness is never authority or approval.
- Corrections where a status is wrong.
- Requests to see the record behind a status.
How the process runs.
Process
Programme status: Edition from scope to correction
Each country agrees profile scope before Q1; G6 authorises release, and a correction is a new version, never a silent change.
01 Scope and draft
- 01Profile scope agreed before Q1Record · The country programmeEach country agrees its profile scope before Q1, and nothing outside it is published. Regional profiles never override a country’s findings.
- 02DraftingStep · Series editorsSeries editors lead each edition under the series method. National Working Groups draft country-edition sections for review.
- 03Evidence cutoff and labelsRecordEach edition states its evidence cutoff. Observed, modelled and estimated evidence stay apart.
02 Review
- 04Review on methodGate · Qualified, conflict-managed reviewersFindings are accepted on method by conflict-managed reviewers. The review may send the draft back for revision.
- 05Public-safe reviewGatePublic-safe review is the gate before any release. A report may be cleared for limited circulation or for publication.
03 Authorise and release
- 06G6 · Publication authorisedGate · The Global Risks ForumGRF authorises publication of results that have passed scientific and editorial review. It cannot publish personal data.
- 07Release with identifiersRecord · ReportsEvery edition carries a DataCite persistent identifier and a UNI under NS-1. The programme publishes one edition each quarter.
04 Correct
- 08Correction as a new versionStep · ReportsA correction produces a new version of an edition. The earlier version stays on record with the correction history.
Reports · The programme year · Identifiers and recordsDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. No edition has been released and none is on record.
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 |
|---|---|---|---|---|
| Programme records with a named status owner | share of programme records | quarterly | Registry record audit | OBSERVED |
| Time since last attested status change | days | continuous | Record timestamps | OBSERVED |
| Owner attestation currency | share of records attested within the review cycle | quarterly | Steward attestations | DECLARED |
| Status assertions with linked evidence | share of status assertions | monthly | Evidence link check | OBSERVED |
| Status vocabulary conformance | share of records using the controlled list | monthly | Schema validation | OBSERVED |
| Agreement with funder award records | share of programmes matching the funder’s status | annual | Funder grant records | Published statistics |
| Planned against reported milestone completion | ratio of reported to planned milestones | per milestone | Programme reports | REPORTED |
| Status changes later reversed or corrected | count per reporting period | quarterly | Correction trail | 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 |
|---|---|---|
| IATI Standard and its activity status codelist | Machine-readable programme records from development and humanitarian publishers, with a controlled list of activity states | Open data, licence set by each publisher |
| CORDIS | Project records, participants, dates and reported results for EU-funded research and innovation programmes | Free reuse with attribution under the European Commission reuse policy |
| NIH RePORTER | Award records, project periods and linked publications for United States federally funded research | Public domain |
| UKRI Gateway to Research | Grants, organisations, people and reported outcomes from UK Research and Innovation | Open Government Licence |
| Crossref grant identifiers | Persistent identifiers and metadata deposited by funders for individual awards | Open metadata, no restrictions on reuse |
| Research Activity Identifier (RAiD, ISO 23527) | A persistent identifier and metadata record for a project across its lifetime, linking people, organisations and outputs | Open metadata, terms of each registration agency |
Who decides, and what the evidence serves.
Registry 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 |
|---|---|---|
| Funders’ programme officers | Whether to release the next tranche, extend or close an award | Status with its attestation date, linked milestone evidence and agreement with the funder’s own award record |
| Programme stewards and boards | When to change a status, and who must confirm the change | Status definitions, the evidence each state requires and the history of earlier changes |
| Internal and external auditors | Whether reported status matched the programme’s actual state over the audit period | Time-stamped status history, correction trail and the evidence linked at each change |
| Partner institutions | Whether to commit staff, data or co-funding to a programme | Current status with owner, scope boundaries and the difference between planned and delivered work |
Outputs this topic produces
- A status glossary defining each programme state, what it asserts and what it does not
- Programme record views showing the status owner, the date of last attestation and linked evidence
- A status history for each programme with every change, its author and its stated reason
- Crosswalks between partner status vocabularies and the controlled list
What experts ask about programme states.
- What is the minimum evidence for each state, and who must hold it?
- How can a vocabulary stay stable across institutions, languages and legal systems?
- How should a status separate the existence of a programme from the quality of its work?
- What happens to a status when its evidence lapses, is challenged or is withdrawn?
- How are past states preserved so that history cannot be rewritten?
Why status claims drift.
Status inflation is a well-documented pattern in programme reporting. Organisations describe intentions as commitments, memoranda as agreements and pilots as operations, often without bad faith, because incentives reward visible progress. Each restatement in a press release, slide or directory strips a little more context, until a programme in exploration is cited as active. The drift is compounded when different institutions use the same word for different things.
Records practice counters this with three disciplines: a controlled vocabulary with written definitions, a rule that each state is tied to a named type of evidence, and an append-only history so that every change is dated and attributable. The Registry applies these to its seven published states, from exploration to historical record, set out on programme states.
How states are recorded, and what they cannot show.
- 01
Controlled vocabulary
Each state has a definition and a statement of what it does not mean, kept as a versioned glossary.
- 02
Evidence binding
A state is linked to the record that supports it, such as a constituting decision or a closeout record, with its issuer and date.
- 03
Event history
Changes are recorded as events, so the state on any past date can be reconstructed.
- 04
Limits
A status shows formal standing, not effectiveness, quality or compliance. Evidence held privately can only be described, not shown, so readers rely on the issuer’s authority for it.
How it is studied, and what the methods cannot say.
- 01Data engineering, interoperability and stewardshipSchema-validated ingestion · Persistent identifier reconciliation · Lineage capture in pipelinesApplied here
- 02Digital identity and public digital systemsIssuer authentication and authority · Contributor disambiguation by the personApplied here
- 03Cybersecurity and cryptographyTamper-evident record history · Signed exports and releases · Threat modelling of edit pathsApplied 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.
Does an active status mean a programme is delivering results?
Who can change a programme’s status?
Why does a status carry a date of last attestation?
How do partner status terms map to the registry’s list?
Does an active programme have approved findings?
Can a country listing imply a programme exists there?
What if a recorded state is wrong?
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.