Data and privacy responsibilities

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.

1. 01 Reporter

   1. 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.

2. 02 Route and acknowledge

   1. 02Routed by kind of concernStepA scientific correction or integrity concern goes to the responsible editor or source owner.
   2. 03AcknowledgementRecordAnyone who raises a question, shares local knowledge or reports a concern gets an acknowledgement and an issue disposition.

3. 03 Review

   1. 04Review by editor or source ownerStep · The responsible editor or source ownerA reviewer with a declared conflict never signs the relevant acceptance.
   2. 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.
   3. 06Privacy, security and safeguarding queuesStepPrivacy and rights requests go to the Privacy Officer queue, security reports to the security disclosure queue.

4. 04 Outcome

   1. 07Accepted correction becomes a new versionRecordAn accepted correction creates a new recorded version.
   2. 08Issue disposition recordedRecordThe reporter gets an issue disposition and, where appropriate, a remedy or referral. The docs name no appeal for a declined correction.

5. 05 Carried into the record

   1. 09Affected analysis re-run with corrected inputsStep · Foundry pillarThe affected analysis is re-run with the corrected inputs.
   2. 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.
   3. 11Courses that taught the finding updatedStep · Risk AcademyRisk Academy updates any course that taught the corrected finding.
   4. 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, a certification or a deployment authorisation. The competent authority decides.