February 8, 2012 By John Hargaden Comments are Off
An effective Risk Assessment process is the cornerstone of any effective safety management system. In turn a Safety Statement is a description of the organisations manner for securing safety and records in detail the risk assessments carried out. As a result, it is vital that organisations carry out a risk assessment and prepare a safety statement. For more information click here
While both the risk assessment and safety statement are legally required, from an ethical perspective, the main reason to carry out a risk assessments and prepare a safety statement is to make sure that no one is killed or injured or becomes ill at your place of work. Carrying out risk assessments and preparing a safety statement will not in themselves prevent accidents and ill health but they will play a crucial part in reducing their likelihood.
Accidents and ill health can ruin lives, and can also affect business financially if output is lost, machinery is damaged, insurance costs increase or if you have to go to court.
Employers, managers and supervisors should all ensure that workplace practices and procedures reflect the content of the in-house risk assessments and safety statement. The behaviour, the way in which everyone works, must reflect the safe working practices laid down in these documents. Supervisory checks and audits should be carried out to determine how well the aims set down are being achieved. Corrective action should be taken when required. Additionally, if a workplace is provided for use by others, the safety statement must also set out the safe work practices that are relevant to them.
Hence, it is important to carry out a Risk Assessment and prepare a Safety Statement for:
1. Financial reasons:
There is considerable evidence, borne out by companies’ practical experiences, that effective safety and health management in the workplace contributes to business success. Accidents and ill-health inflict significant costs, often hidden and underestimated.
2. Legal reasons:
Carrying out a risk assessment, preparing a safety statement and implementing what you have written down are not only central to any safety and health management system, they are required by law. Health and Safety Authority inspectors visiting workplaces will want to know how employers are managing safety and health. If they investigate an accident, they will scrutinize the risk assessment and safety statement, and the procedures and work practices in use.
It should be ensured that these stand up to examination. If the inspector finds that one of these is inadequate, he or she can ask the employer to revise it. Employers can be prosecuted if they do not have a safety statement.
3. Moral and ethical reasons:
The process of carrying out a risk assessment, preparing a safety statement and implementing what you have written down will help employers prevent injuries and ill-health at work. Employers are ethically bound to do all they can to ensure that their employees do not suffer illness, a serious accident or death. The HSA have assembled a set of guidelines to be followed.
For more information on Safety Statements Click Here
Related Courses:
Comments are closed.
Cookie | Duration | Description |
---|---|---|
wpfront-notification-bar-landingpage | session | This cookie is set by WPFront Notification Bar WordPress plugin. The cookie is used to determine whether the visitors have decded o show or hide any current notification bars on the website. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | The cookie is set by Google Analytics. The cookie is used to determine new sessions/visits. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. The cookie is not used by ga.js. The cookie is used to enable interoperability with urchin.js which is an older version of Google analytics and used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | The cookie is set by Google Analytics and is used to throttle request rate. |
__utmv | 2 years | This cookie is set by Google Analytics. The cookie is used to store visitor-level custom variable data and is updated every time data is sent to Google Analytics. |
__utmz | 6 months | This cookie is set by Google analytics and is used to store the traffic source or campaign through which the visitor reached your site. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 4 months 5 days 14 hours 3 minutes | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt-remote-connected-devices | never | These cookies are set via embedded youtube-videos. |
yt-remote-device-id | never | These cookies are set via embedded youtube-videos. |
yt.innertube::nextId | never | These cookies are set via embedded youtube-videos. |
yt.innertube::requests | never | These cookies are set via embedded youtube-videos. |
Cookie | Duration | Description | |
---|---|---|---|
2ebb1802fb | session |
| |
383aeadb58 | session | Used by Zoho forms on form submission | |
663a60c55d | session | Identifies the visitor across devices and visits, in order to optimize the chat-box function on the website | |
6e4b8efee4 | session | No description available. | |
cmsetraining-_zldp | 2 years | This cookie identifies the unique visitors for the website | |
cmsetraining-_zldt | 1 day | This cookie identifies unique visits for a visitor in the website | |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". | |
crmcsr | session |
| |
e188bc05fe | session | No description available. | |
gclid | 1 month | Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution | |
iamcsr | session | Ensures visitor browsing-security by preventing cross-site request forgery. | |
store_notice[notice id] | session | Allows customers to dismiss the Store Notice. | |
tk_ai | session | Stores a randomly-generated anonymous ID. This is only used within the dashboard ( /wp-admin ) area and is used for usage tracking, if enabled. | |
woocommerce_cart_hash | session | Helps WooCommerce determine when cart contents/data changes. | |
woocommerce_dismissed_suggestions__[context] | 1 month | Count of suggestion dismissals, if enabled. | |
woocommerce_items_in_cart | session | Helps WooCommerce determine when cart contents/data changes. | |
woocommerce_recently_viewed | session | Powers the Recent Viewed Products widget. | |
woocommerce_snooze_suggestions__[suggestion] | 2 days | Allows dashboard users to dismiss Marketplace suggestions, if enabled. | |
wp_woocommerce_session_ | 2 days | Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. | |
_zcsr_tmp | session |
|