RACKWiki:Incident report policy: Difference between revisions

From RACKWiki
(Created page with "Category:Incidents Guidelines on how case studies are written. == Selection == == Information gathering == == Peer review == == Style guide == Category:Procedures")
 
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Incidents]]
'''Incident reports''' are a special class of articles on RACKWiki that discuss specific incidents where harm occurred or could have occurred. Due to the sensitive nature of this content, incident reports can only be written and edited by RACKWiki editorial staff and will adhere to the policies described in this article. Official incident reports will always exist in the <span class="plainlinks">[https://rackwiki.org/wiki/Special:AllPages?from=&to=&namespace=4238 "Incident" namespace]</span>. Unofficial incident reports or discussion of a non-official incident within another article will always be removed and the user who submitted the content may have their authorship privileges revoked.
 
== Information gathering and selection ==
Community-submitted [https://docs.google.com/forms/d/e/1FAIpQLSccAAGMc8yQ6vd70LYHIfC3ARMoStQSt5KqYQ9vn92sH-56gQ/viewform?usp=sf_link Incident Reporting Forms] are the primary method for RACKWiki editorial staff to gather information from primary sources. Follow-up questions may be required, so we encourage form submitters to allow us to contact them.
 
== Peer review ==
Each incident is assigned to a member of the RACKWiki editorial staff to draft a report. The draft is reviewed by at least one other staff member prior to publication.
 
== Style guide ==
Incident reports are meant to be objective analyses of near-fatal or fatal events. The style guide is used to ensure that information is presented in a consistently clear, concise, and unbiased manner.
 
=== Identification of subjects ===
By default the subject of the report will not be named. Subjects will only be named under the following circumstances:
 
# In a non-fatal incident, the subject submitted an incident reporting form and requested to be identified.
# In a fatal incident, a minimum of three close friends and/or family request that the subject be identified in the report. RACKWiki staff will make best efforts to corroborate and confirm the relationships, but will default to anonymizing the subject if they can not obtain sufficient proof of consent.
 
=== Format ===
 
==== Synopsis ====
High level summary of the incident.
 
==== Summary table ====
Synopsis presented in a table format.


Guidelines on how case studies are written.
==== Environment ====
This section illustrates the context and events leading up to the incident.


== Selection ==
==== Timeline ====
Detail the sequence of events. In contrast to the Environment section which describes the broader setting of the incident, this section lays out the order that the events occurred.


== Information gathering ==
==== Risk analysis ====
What went wrong? Analysis of contributing factors that led to the outcome of the incident.


== Peer review ==
==== Risk mitigation summary ====
Things that could have been done differently. Provide recommendations on risk mitigation strategies that could be used to prevent the incident from happening.


== Style guide ==
==== Sources ====
[[Category:Procedures]]
[[Category:Incidents]]
[[Category:Policies]]
{{DISPLAYTITLE:Incident report policy}}

Latest revision as of 23:43, 18 January 2024

Incident reports are a special class of articles on RACKWiki that discuss specific incidents where harm occurred or could have occurred. Due to the sensitive nature of this content, incident reports can only be written and edited by RACKWiki editorial staff and will adhere to the policies described in this article. Official incident reports will always exist in the "Incident" namespace. Unofficial incident reports or discussion of a non-official incident within another article will always be removed and the user who submitted the content may have their authorship privileges revoked.

Information gathering and selection

Community-submitted Incident Reporting Forms are the primary method for RACKWiki editorial staff to gather information from primary sources. Follow-up questions may be required, so we encourage form submitters to allow us to contact them.

Peer review

Each incident is assigned to a member of the RACKWiki editorial staff to draft a report. The draft is reviewed by at least one other staff member prior to publication.

Style guide

Incident reports are meant to be objective analyses of near-fatal or fatal events. The style guide is used to ensure that information is presented in a consistently clear, concise, and unbiased manner.

Identification of subjects

By default the subject of the report will not be named. Subjects will only be named under the following circumstances:

  1. In a non-fatal incident, the subject submitted an incident reporting form and requested to be identified.
  2. In a fatal incident, a minimum of three close friends and/or family request that the subject be identified in the report. RACKWiki staff will make best efforts to corroborate and confirm the relationships, but will default to anonymizing the subject if they can not obtain sufficient proof of consent.

Format

Synopsis

High level summary of the incident.

Summary table

Synopsis presented in a table format.

Environment

This section illustrates the context and events leading up to the incident.

Timeline

Detail the sequence of events. In contrast to the Environment section which describes the broader setting of the incident, this section lays out the order that the events occurred.

Risk analysis

What went wrong? Analysis of contributing factors that led to the outcome of the incident.

Risk mitigation summary

Things that could have been done differently. Provide recommendations on risk mitigation strategies that could be used to prevent the incident from happening.

Sources