RMU Incident Investigation and Report Form Instructions: Fill in form by clicking on fields to enter data. Save file and print for proper distribution. SECTION I. INCIDENT INFORMATION Date of Incident Time of Incident Location of Incident: (Be specific to building, room, area, or location on premises ex. ISC, Golf (m/d/y) AM PM Dome, Practice Range, North Stair to mezzanine)

Incident Investigation / Report completed by (Employee or Department Supervisor name): Witness(es) to Incident:

Name/phone number Name/phone number

SECTION II. INJURED PERSON DETAILS Name of Injured Person:

Male Female

Age:

Home Ph: Cell Ph:

Address: Person Injured Is: RMU Employee

Department: Full-Time

RMU Student

Position: Part-Time

Was Person Involved In:

Student Emp. League

Staff Start Time:

Other Describe:

Sporting Event

Other

Explain event: Visitor / Guest

Release / Waiver Signed?

Yes (forward copy with report)

Equipment Involved in Incident?

Owned by RMU

No

Owned by other

Describe equipment: SECTION III. INJURY DESCRIPTION

Nature of Injury:

Bruising

Dislocation

Strain/Sprain

Scratch/Abrasion

Internal

Fracture

Amputation

Foreign Body

Laceration/Cut

Burn/Scald

Chemical Reaction

Treatment:

Needle Stick Other Explain here:

List Body Part(s) Injured:

Emergency/Ambulance (List where taken)

None First Aid

Other Explain:

SECTION IV. DAMAGED PROPERTY Name of Property, Equipment or Material Damaged: Description of Damage:

Cause of Incident / Damage: SECTION V: DESCRIPTION OF INCIDENT Describe in detail what happened (attach photographs or diagrams if necessary):

RMU Incident Investigation Form

Page 1 of 2

Rev. 9/11

RMU Incident Investigation and Report Form SECTION VI: ROOT CAUSE ANALYSIS (Check All That Apply)

Unsafe Acts

Unsafe Conditions

Management Deficiencies

Improper work technique

Poor workstation design or layout

Lack of written procedures or policies

Safety rule violation

Congested work area

Safety rules not enforced

Improper PPE or PPE not used

Hazardous substances

Hazards not identified

Operating without authority

Fire or explosion hazard

Personal Prot. Equip. unavailable

Failure to warn or secure

Inadequate ventilation

Insufficient worker training

Operating at improper speeds

Improper material storage

Insufficient supervisor training

By-passing safety devices

Improper tool or equipment

Improper maintenance

Guards not used

Insufficient knowledge of job

Inadequate supervision

Improper loading or placement

Slippery conditions

Inadequate job planning

Improper lifting

Poor housekeeping

Inadequate hiring practices

Servicing machinery in motion

Excessive noise

Inadequate workplace inspection

Horseplay

Inadequate guarding of hazards

Inadequate equipment

Drug or alcohol use

Defective tools/equipment

Unsafe design or construction

Unnecessary haste

Insufficient lighting

Unrealistic scheduling

Unsafe act of others Other: Explain

Inadequate fall protection Other: Explain

Poor process design Other: Explain

Incident Analysis – describe what action, condition, and / or circumstances caused the incident:

Summarize other conditions related to the incident -even contributing factors that may have reduced the severity. (ex. What type of personal protective equipment (PPE) was being worn-gloves, safety glasses, goggles, mask, etc.?):

SECTION VII: PREVENTIVE OR CORRECTIVE ACTIONS Describe the actions that will be taken to prevent recurrence: Explain

Responsible person:

Date to be completed by:

Explain

Responsible person:

Date to be completed by:

SECTION VIII: SIGNATURES Employee / Person Involved:

Date: Sign Here:

Print name:

Department Supervisor / Manager:

Date: Sign Here:

Print name:

SECTION IX: DISTRIBUTION Per policy, send completed report to: (include all attachments)

Human Resources

Safety Officer

Director of Affected Dept.

SECTION X: OFFICIAL USE ONLY

____

________________Date received

RMU Incident Investigation Form

Recorded in database __

Page 2 of 2

___________________Date

Rev. 9/11

RMU Incident Investigation and Report Form

Unsafe Acts. Unsafe Conditions. Management Deficiencies. Improper work technique. Poor workstation design or layout. Lack of written procedures or policies. Safety rule violation. Congested work area. Safety rules not enforced. Improper PPE or PPE not used. Hazardous substances. Hazards not identified. Operating ...

592KB Sizes 3 Downloads 235 Views

Recommend Documents

Automated External Defibrillators – Incident Report Form 8310F3.pdf ...
Automated External Defibrillators – Incident Report Form 8310F3.pdf. Automated External Defibrillators – Incident Report Form 8310F3.pdf. Open. Extract.

Google Apps Incident Report
Mar 17, 2014 - Issue Summary. From 8:35 AM to 12:10 PM PT, Google Talk, Google Hangouts (including Chat and Video), Google. Voice, and the Google App ...

Google Apps Incident Report
Apr 17, 2013 - The following is the incident report for the Google services access ... Talk, Google Sync, the Admin panel, and the Cloud Console, and to a ...

Google Apps Incident Report
Mar 19, 2013 - Applications using the Google Drive and Docs APIs also returned errors. ... We thank you for your business and continued support. Sincerely,.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted further deployment. Restoration Process. While analyzing the issue and its root cause, Google Engineering also worked on the process to restore users' accounts. At 6:0

Google Apps Incident Report
Apr 17, 2012 - Prepared for Google Apps for Business customers. The following is the ... Enhance internal documentation for configuration management.

Google Apps Incident Report
This misconfiguration prevented changes to existing customer data for upgraded users. ... Eliminate the need for server restarts to recover from this type of error.

Google Apps Incident Report
At 7:50 AM PT | 16:00 UTC November 15, Google Calendar Engineering brought a system of servers ... your business and continued support during this time.

Incident Report
Feb 24, 2009 - The root cause of the problem was a software bug that caused an ... we monitor our systems 24 x 7, we have engineers available to analyze.

Google Apps Incident Report
Nov 15, 2010 - Prepared for Google Apps Customers ... Apps customers on November 15, 2010. ... your business and continued support during this time.

Google Apps Incident Report
Feb 27, 2011 - Google Engineering reverted the storage software update, and halted ... better identify this class of bug during the software development cycle.

Google Apps Incident Report
We understand this service issue has impacted our valued customers and users, and we apologize to everyone ... At 6:12 AM PDT, a bug in a thirdparty software update caused a partial failure of a Google network router in ... escalated the software iss

Google Apps Incident Report
Mar 18, 2013 - service disruption was an issue in the network control software. Actions and Root Cause Analysis. At 6:09 AM PT, a portion of Google's network ...

Google Apps Incident Report
Google Drive list. Applications using ... The Google Engineering team conducted an internal review and analysis of the March 21 event. They ... Modify the Drive software to more reliably serve user requests during short periods where overall.

Google Apps Incident Report
Dec 10, 2012 - Actions and Root Cause Analysis. Background: The load balancing software routes the millions of users' requests to Google data centers.

Google Apps Incident Report
Google Apps Incident Report. Google Docs Outage - September 7, 2011. Prepared for Google Apps for Business customers. The following is the incident report ...

Google Apps Incident Report
Google Apps Incident Report. Gmail Outage - September 23, 2011. Prepared for Google Apps for Business customers. The following is the incident report for the ...

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...
Whoops! There was a problem loading more pages. 2016-2017 Incident Report Form (CPTSB Form 139-16).pdf. 2016-2017 Incident Report Form (CPTSB Form ...

Google Apps Incident Report - PDFKUL.COM
Apr 17, 2013 - The following is the incident report for the Google services access disruption that occurred on. April 17 ... Talk, Google Sync, the Admin panel, and the Cloud Console, and to a lesser extent Groups,. Sites, and ... misconfiguration oc

2016-2017 Incident Report Form (CPTSB Form 139-16).pdf ...
CPTSB OFFICE (303) 894-7785. Office: Cell: Location: Larry Smith (303) 894-7786 (303) 929-3494 Arvada. Joyce Young (303) 894-7781 (720) 331-8985 Denver. 2016-2017. Passenger Tramway Safety Board. PASSENGER TRAMWAY. INCIDENTS. Page 2 of 2. 2016-2017 I

[I687.Ebook] Free PDF Incident Investigation and ...
documents can be conserved or saved in computer system or in your laptop computer. So, it can be greater than a book Incident Investigation And Accident ...

Google Apps Incident Report - PDFKUL.COM
Google Docs Outage - September 7, 2011. Prepared for Google Apps for Business customers. The following is the incident report for the Google Docs access ...

Postini Services Incident Report
May 7, 2013 - Prepared for Postini and Google Apps customers. The following is the ... We thank you for your business and continued support. Sincerely,.

Incident Summary Report -
Offense Class Code. Offense Class Description. Count. 320. ROBBERY - STRONG-ARM. 1. 450. ASSAULT AND BATTERY. 6. 460. INTIMIDATION / THREAT. 1. 510. BURGLARY - HOME INVASION - 1ST DEGREE. 1. 1410. MDOP - MALICIOUS DESTRUCTION OF PROPERTY. 3. Grand To