Saturday, January 28, 2017

Procedure which needs to follow in case of an accident in the Factory

Dear All,

We often observe that in case of an accident happens in factory the surrounding individuals at the time of said accident get clueless about what need to be done or in common language what procedure needs to follow in case of an accident in the Factory.

To give insight for above pertained query, we are sharing information as follows:

When an accident occurs in a factory which causes death or bodily injury by the reasons of which, the injured person is prevented from working for a period of 48 hours or more immediately following such an accident, is a reportable accident under section 88 of Factories Act.

Any such accident which results in death is a fatal accident. All other accidents, wherein an injured worker return / resume work are non-fatal accidents.


Further, both fatal and non-fatal accidents are required to be intimated in the manner and within the time limit prescribed in the relevant provisions of the respective State Factories Rule. These requirements are different for i) accidents resulting in death and ii) for other reportable non-fatal accidents.


If you find this article useful then kindly re-share with you professional circle.

Thank you.
Transerve Advisors Team
Transerve Advisors Private Limited.
A-55, Pravasi Industrial Estate,
Vishveshwar Road, Goregaon (E),
Mumbai – 400 063.


IMPORTANT:

Information in this blog is being provided as-is without any warranty/guarantee of any kind.

This blog is intended to provide information only. If you are seeking advice on any matters relating to information on this blog, you should – where appropriate – contact us directly at 
support@transerve.in  with your specific query or seek advice from qualified professional people.

We encourage you to take steps to obtain the most up-to-date information and to confirm the accuracy and reliability of any information on this blog in general by directly communicating with us.


Disclaimer – IMPORTANT


Privacy Policy:-

We do not share personal information with third-parties nor do we store information we collect about your visit to this blog for use other than to analyze content performance through the use of cookies (see below), which you can turn off at anytime by modifying your Internet browser’s settings. We are not responsible for the republishing of the content found on this blog on other web sites or media without our permission.

Terms and Conditions:-

All content provided on this blog is for information purpose only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this blog site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information.

Blog Comments Policy:-

The owner of this blog reserves the right to edit or delete any comments submitted to this blog without notice. The owner of this blog is not responsible or liable for any comments made by others on this blog.


Cookie Policy:-

This site uses cookies which are small text files that are placed on your machine to help the site provide a better user experience. In general, cookies are used to retain user preferences and provide anonymous tracking data to third-party applications such as Google Analytic.

As a rule, cookies will make your browsing experience better. However, you may prefer to disable cookies on this site and on others. The most effective way to do this is to disable cookies in your browser. We suggest consulting the Help section of your browser or taking a look at the About Cookies website (http://www.aboutcookies.org/ ) which offers guidance for all modern browsers.


I hope the above Disclaimer will give you my concern for your privacy and security and would like to inform that this blog is only founded for the purpose of information purpose only.


Thank you.

No comments:

Post a Comment