| Information needed | Response |
|---|---|
| Title and link to statistical output | Biannual Diversity Publication April 2021 https://www.gov.uk/government/statistics/uk-armed-forces-biannual-diversity-statistics-2021 |
| Name of producer organisation | Ministry of Defence, Analysis Tri-Service
|
| Name and contact details of person dealing with report | Responsible Statistician, Tri-Service Head of Branch Analysis-Tri-Hd@mod.gov.uk |
| Name and contact details of Head of Profession for Statistics or Lead Official | Chief Statistician Analysis-Chief-Analyst@mod.gov.uk |
| Link to published statement about the breach (if relevant) | |
| Date of breach report | 9 June 2021 |
| Information needed | Response |
|---|---|
| Relevant principle(s) and practice(s) | Trustworthiness, practice T3.4 - Statistical content has been made public or supplied to parties not essential for statistical production without prior permission for access, through accidental or wrongful release. |
| Date of occurrence of breach | 9 June 2021
|
The UK armed forces biannual diversity statistics 2021 was due for publication by Ministry of Defence (MoD) on 10 June 2021. Following a check of the pre-release list in advance of sending out the pre-release email, one person changed roles and remained on pre-release list. This meant that when we circulated the pre-release email for the biannual diversity publication at 9:30am on 9 June 2021 this individual received the email when they should not have done. The deputy head of profession was informed of the breach by another colleague at 1pm on 9 June 2021 and breach policies were then immediately implemented.
Externally there was no impact. Internally there was minimal impact. Following the breach, the individual was contacted to ensure the pre-release email was forwarded onto the correct person.
- The incident highlighted the need to check the pre-release contacts 2 weeks prior to release to ensure this doesn’t happen again. Contacting individuals directly to confirm prerelease access is still required.
- 2. Investigated how it happened, team leader discussed with other team leader of imminent release of official statistics to ensure it doesn’t happen there.
- 3. A whole team meeting, before the next major round of publications, to discuss further options on reducing pre-release risks and re-stressing the importance of the process. Ensure that everyone confirms they understand their responsibilities under the Code of Practice, with particular reference to trustworthiness and orderly release.
- MOD wide communication will be tightened, e.g. briefings, email cascades, workshops etc to ensure learnings are cascaded to all.