Start here: how this desk | Reports Risk Academy

01What Reports is

Reports is the Consortium’s quarterly publication, and Risk Academy writes the desk on capability. If you teach risk, learn it or plan a workforce, this desk reports what competence exists, what is missing and which pathways close the gap.

Atlas of the Academy Capability desk: its mandate, the series it leads, the eight chapters of its edition, what to send here and its Zenodo community. The sections below give the same facts as text. — The Academy Capability desk atlas, with its facts written out below.

02This desk: Capability

The Academy reports learning and workforce capability: competencies, completions, practicum outcomes and gaps. It reports in aggregate only and never publishes a learner record.

Mandate: The capability of the workforce that manages the risks in scope: the competencies needed, what learning and practicum show, and where the gaps are. Reported in aggregate only; no learner record is published.

This desk leads no series of its own yet. Its edition is the Consortium’s Capability edition.

03The six desks

Capability is one of six desks, and it deposits to its own Zenodo community under the flagship.

Diagram of the six desks and the flagship Zenodo community nexusreports. The table below lists the desks.

The six desks
Desk	Edition	Zenodo community
GCRI	Systems Evidence	nexusreports-gcri
GRF	Public Deliberation	nexusreports-grf
GRA	Capital Readiness	nexusreports-gra
NXS	Standards Progress	nexusreports-nxs
RA	Capability	nexusreports-ra
GRX	Measurement	nexusreports-grx

04The edition in eight chapters, in this desk’s terms

The chapters move from the capability needed to the competency map that a curriculum can use.

The eight chapters of the Capability edition
Chapter	Title	What it covers
1	Capability needed	The competencies the systems in scope require of those who manage them.
2	Capability findings	What learning, practicum and workforce evidence show, in aggregate, each with its source.
3	Faculties and roles	Capability read by faculty and by professional role.
4	Gaps and pathways	The gaps between capability needed and capability taught, and the learning pathways that address them.
5	Workforce scenarios	How workforce needs would change under stated scenarios; conditional, never predictions.
6	Readings from the other desks	Readings from the other desks: cross-references to their editions for the same scope, not copies of them.
7	Curriculum agenda	The courses, pathways and research notes the next cycle takes up.
8	Competency map	The competencies in scope, mapped to roles, faculties and courses.

05How to contribute

Send learning outcomes, competency evidence or practicum results. Send aggregates. Do not send any record that names a learner.

This desk takes:

Learning outcomes from a course or programme, in aggregate
Competency evidence from a role, a profession or a framework
Practicum results, with the brief they answered
A gap between the competencies needed and those taught

The gateway page of the Academy Capability desk gives the route.

06The editorial workflow

An educator’s contribution goes through the same review as a research paper. The declared review model tells you in advance who will read it.

Diagram of the editorial workflow in six steps: submit, screen, review, decide, accept, publish, with a revision branch and a decline or appeal branch. The list below gives every step.

The editorial workflow
Step	What happens
1. Submit	Contributor declarations and licence terms are signed first.
2. Screen	Editors check scope, completeness and licensing.
3. Review	Peer review runs under the model declared at submission. Authors may revise, then the work returns to review.
4. Decide	Named editors decide and record their reasons. Declined work can be appealed through a separate route.
5. Accept	The decision is recorded and the work moves to production.
6. Publish	A named editor publishes. The DOI is issued.

07The sixteen-gate quarterly cycle

Teaching terms and publication cycles rarely line up. Use the submission deadline to decide which term’s outcomes reach which quarter.

Diagram of the sixteen gates of a quarterly cycle, from the call opening to the corrections window closing. The list below gives every gate.

The sixteen gates of a quarterly cycle
Order	Gate	Meaning
1	call_open	The call opens.
2	call_close	The call closes.
3	submission_deadline	Last moment to submit into this cycle. Later submissions roll to the next cycle.
4	triage_close	Intake triage must be finished.
5	review_open	The review window opens.
6	reviewer_reminder	First reminder to reviewers.
7	review_close	Reviews are due. Overdue reviews escalate and are reassigned.
8	decision_date	The editorial decision is due.
9	revision_close	The revision window ends.
10	copyedit_freeze	Copyedit and data-check freeze.
11	evidence_close	Evidence close.
12	production_close	Production ends.
13	release_approval	The named approver signs the release.
14	release	Release date. It is the anchor of the cycle.
15	deposit_approval	Zenodo deposit approval. The deposit stays a draft until then.
16	corrections_close	The corrections window ends.

08Release control

The accessibility check applies to the edition itself. A course team can reuse the edition because it has passed it.

Diagram of release control: seven checks must pass, the named approver signs, six artefacts are fixed with checksums, the Zenodo deposit stays a draft, then the record is published with a DOI.

09Open licensing

Teaching materials built on an edition can reuse its text under CC BY 4.0. Give credit as the licence requires.

Licence rules

Text, figures and maps: CC BY 4.0 (SPDX: CC-BY-4.0).
Data: CC0 1.0 (SPDX: CC0-1.0).
Code: an OSI-approved licence.
Media: CC BY 4.0 or CC0 1.0.
No NC, ND or SA licence on our own outputs. No paywall, no embargo on text, no fees.

Shared text. It is the same on every Reports site by design.

10Zenodo community and DOIs

Academy records go to the Academy’s community on Zenodo. It exists and is curated by the Academy desk; nothing is deposited in it yet.

This desk’s community: zenodo.org/communities/nexusreports-ra

Flagship community: nexusreports. It exists and holds records today.
Every record carries a DOI and a full version history. A correction becomes a new version and keeps the concept DOI.

Shared text. It is the same on every Reports site by design.

11The open science stack, with its honest status

Learners with an ORCID can receive credit for a review. The integrations that are not complete are marked below.

Diagram of the open science stack with the status of each integration. The table below gives every status.

The open science stack and its status
Integration	What it does	Status
Zenodo	DOIs, deposits and versions	Built
ORCID	Contributor identity and review credit	Built
ROR	Institution identifiers	Needs the id
COAR Notify	Inbox for peer review services	Built
OAI-PMH	A harvesting endpoint	Built
JATS XML	Journal article markup	Built
RO-Crate	Research object packaging	Built
Crossref	An export, not in use	Export only

Cite

Reports, Academy Capability, start here [Draft under review]. The Global Centre for Risk and Innovation (GCRI) for the Nexus Consortium.

Review copy. The DOI is issued at deposit. Text under CC BY 4.0.

Name	Purpose	Duration	Party
`wordpress_*`cookie	Strictly necessaryThis site	Until you sign out	First party
`wordpress_logged_in_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_sec_*`cookie	Strictly necessaryThis site	Until you sign out, or 14 days	First party
`wordpress_test_cookie`cookie	Strictly necessaryThis site	Session	First party
`wp-settings-*`cookie	Strictly necessaryThis site	1 year	First party
`wp-postpass_*`cookie	Strictly necessaryThis site	10 days	First party
`comment_author_*`cookie	Strictly necessaryThis site	About 347 days	First party
`wpEmojiSettingsSupports`browser storage	Strictly necessaryThis site	Session	First party
`nexus_consent`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_id`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent_reset`cookie	Strictly necessaryPrivacy choices	Session	First party
`wp_consent_*`cookie	Strictly necessaryPrivacy choices	180 days	First party
`nexus_consent`browser storage	Strictly necessaryPrivacy choices	180 days	First party
`nx_theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.theme.default`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bx-color-mode-against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.embed.theme`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_dark_mode`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`buddyx_color_mode_against`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.a11y`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`nexus.dock`browser storage	Preferences and functionalDisplay preferences	Until you change it	First party
`bp-activity`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-groups`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-members`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-blogs`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party
`bp-messages`browser storage	Strictly necessaryCommunity directories (BuddyPress)	As the provider sets it	First party

Start here: how this desk of Reports works