GRA · Financial Stability
Spatial financeWhere capital meets hazard, exposure and transition
Corrections, concerns and escalation
Financial Stability records corrections as new versions with passage, source, reason and date. The errors that matter here are a modelled network presented as observed, a scenario loss read as a forecast and a sector figure read as one firm's position.
Corrections, concerns and escalation in four parts.
And their fixes.
| Error | Fix |
|---|---|
| Reconstructed network presented as observed | Relabel MODELLED and state the method |
| Scenario loss read as a forecast | Restate the scenario's assumptions |
| Sector aggregate attributed to a firm | Remove the attribution |
Raise a correction at corrections and concerns.
How the process runs.
Process explorer · Process
How a correction moves
12 steps·5 stages
Process
How a correction moves
Anyone may request a correction without membership; an accepted one becomes a new version, and the earlier version stays on record with the reason.
01 Reporter
- 01Anyone may ask for a correctionActor · AnyoneAnyone may ask for a correction, without membership. No membership or Account is needed to report harm or correct public information.
02 Route and acknowledge
- 02Routed by kind of concernStepA scientific correction or integrity concern goes to the responsible editor or source owner.
- 03AcknowledgementRecordAnyone who raises a question, shares local knowledge or reports a concern gets an acknowledgement and an issue disposition.
03 Review
- 04Review by editor or source ownerStep · The responsible editor or source ownerA reviewer with a declared conflict never signs the relevant acceptance.
- 05Complaint about a decisionStep · A reviewer not responsible for the decisionA programme or decision complaint is reviewed by someone not responsible for the contested decision.
- 06Privacy, security and safeguarding queuesStepPrivacy and rights requests go to the Privacy Officer queue, security reports to the security disclosure queue.
04 Outcome
- 07Accepted correction becomes a new versionRecordAn accepted correction creates a new recorded version.
- 08Issue disposition recordedRecordThe reporter gets an issue disposition and, where appropriate, a remedy or referral. The docs name no appeal for a declined correction.
05 Carried into the record
- 09Affected analysis re-run with corrected inputsStep · Foundry pillarThe affected analysis is re-run with the corrected inputs.
- 10Change proposal to the standardsRecord · Nexus StandardsMethod and correction findings go to Nexus Standards as change proposals (F06). It records the correction as a change to the evidence.
- 11Courses that taught the finding updatedStep · Risk AcademyRisk Academy updates any course that taught the corrected finding.
- 12New version with correction and reasonRecord · ReportsReports publishes a new version with the correction and its reason. The earlier version stays on record with the correction history.
Status and service levels · Reports · The programme yearDesigned process, not a record of any case. No cycle has run and every programme is at service level R0, information and enquiries. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The competent authority decides.
What happens next.
- 01
Acknowledgement
You receive a reference and the next step.
- 02
Review
The concern is reviewed by someone not involved in the original work, where possible.
- 03
Outcome
A correction is published as a new version with its history; a declined challenge receives reasons.
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.
Can I raise a concern anonymously?
Bring an exposure or capital question to the Alliance.
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.