Protect whistleblowers who raise AI safety concerns
4 submissions. Each submission counts once for this shared ask. Counts do not measure importance or merit.
A shared ask groups requests for substantially the same action from three or more submissions when the group was created. Groups remain listed if withdrawals reduce their counts. AI models summarised recommendations, grouped them and checked the groups. The label summarises the requests; it is not a quote. A shared ask does not mean agreement on anything else.
Theme: AI incident reporting
Recommendations from submissions
Quotes are the submitter’s own words. Text taken from documents, including scanned pages read by text-recognition software, can differ from the PDF. Check the original. Extracts are chosen by an AI model. Submissions are listed in submission number order; recommendations follow their order on each submission’s page.
Mr Stuart Le Gros Submission 344
During operation, require outcome and override monitoring, incident reporting, independent audit, workforce consultation, vendor access rights, protected whistleblowing and periodic reauthorisation.
During operation Outcome and override monitoring; incident reporting; independent audit; workforce consultation; vendor access rights; protected whistleblowing; periodic re-authorisation.
Mr Nathan Lou Submission 388
Strengthen whistleblower protections.
Similarly, I support: - Mandatory reporting of AI safety concerns/events, in a standardised fashion E.g categorised into deceptive behaviour, escapement, misc., etc. - Mandatory audits of safety policies by 3 rd parties - Stronger whistleblower protections
Name withheld Submission 393
Employees raising credible concerns about significant safety risks should have appropriate whistleblower protections.
Name withheld Submission 439
Strong protections for whistleblowers within the AI industry and the government departments and companies partnering with AI companies, products and tools.