SD-FORM-003 Near Miss-Good Catch Report
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Near</strong> <strong>Miss</strong> / <strong>Good</strong> <strong>Catch</strong> <strong>Report</strong><br />
Environmental Construction Service: ☐ MAS ☐ SAS ☐ SPS ☐ SLC<br />
☐ <strong>Near</strong> <strong>Miss</strong><br />
☐ <strong>Good</strong> <strong>Catch</strong><br />
Date of Event:<br />
Date Submitted:<br />
Location of Event: Brief Description of Event:<br />
Contributing Factors:<br />
What changes, modifications, or actions will be implemented?<br />
How will you implement these corrective actions?<br />
Office Use Only: Date Received: ☐ Logged<br />
☐<br />
Statistics Documented<br />
Document Title<br />
NEAR MISS-GOOD CATCH REPORT<br />
Approving Authority:<br />
Joe Snorek<br />
Origination Date:<br />
March 12, 2015<br />
Owner / Author:<br />
Joe Snorek<br />
Document Number:<br />
<strong>SD</strong>-<strong>FORM</strong>-<strong>003</strong><br />
Revision Level / Date:<br />
REV 3 / August 30, 2018<br />
<strong>SD</strong>-<strong>FORM</strong>-<strong>003</strong> <strong>Near</strong> <strong>Miss</strong> <strong>Good</strong> <strong>Catch</strong> <strong>Report</strong>.dotx Page 1 of 2 - CONFIDENTIAL -
<strong>Near</strong> <strong>Miss</strong> and <strong>Good</strong> <strong>Catch</strong> <strong>Report</strong>ing Instructions<br />
Definitions:<br />
<strong>Good</strong> <strong>Catch</strong> – An unsafe condition or act was recognized, which if let unaddressed, could have resulted in an<br />
injury, property damage, or outage. This could also be a positive recognition of a good work practice or behavior<br />
which helped create a safer environment.<br />
<strong>Near</strong> <strong>Miss</strong> – An incident occurred where no property was damaged, and no personal injury was sustained, but<br />
where, given a slight shift in time or position, damage and/or injury could have occurred.<br />
Intent:<br />
The intent of this document is to capture the <strong>Good</strong> <strong>Catch</strong>/<strong>Near</strong> <strong>Miss</strong> Event reports received from multiple<br />
contractors on one standard document. This document is not intended to replace the contractor's own <strong>Good</strong><br />
<strong>Catch</strong>/<strong>Near</strong> <strong>Miss</strong> reporting process or documentation.<br />
Procedure:<br />
1. Once a <strong>Near</strong> <strong>Miss</strong> has occurred, or an unsafe condition or act has been recognized, an employee should<br />
report it to their Supervisor or Safety & Compliance Representative per the guidelines of their own company's<br />
reporting policy.<br />
2. The Supervisor or Safety & Compliance Representative will record the <strong>Near</strong> <strong>Miss</strong>/<strong>Good</strong> <strong>Catch</strong> on the<br />
company <strong>Good</strong> <strong>Catch</strong> and <strong>Near</strong> <strong>Miss</strong> <strong>Report</strong> and submit the form to: safety.field@sterlingsolutions.com<br />
3. Please fill out the form in its entirety. The report should include the following:<br />
1. Date of <strong>Near</strong> <strong>Miss</strong>/<strong>Good</strong> <strong>Catch</strong><br />
2. Location of <strong>Near</strong> <strong>Miss</strong>/<strong>Good</strong> <strong>Catch</strong><br />
3. Contributing Factors (states, critical errors, other)<br />
4. Also, it is highly important that suggestions or recommendations be made regarding what actions<br />
will be taken<br />
<strong>SD</strong>-<strong>FORM</strong>-<strong>003</strong> <strong>Near</strong> <strong>Miss</strong> <strong>Good</strong> <strong>Catch</strong> <strong>Report</strong>.docx Page 2 of 2 - CONFIDENTIAL -