10.05.2018 Views

Cleaning Buyers’ Guide

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

How to protect your company from liability and avoid<br />

legal mistakes?<br />

As you probably noticed, the last few interview questions listed are regarding<br />

insurance and avoiding liability or legal mistakes. This is one of the crucial<br />

things you need to know before hiring a commercial cleaning company. Hiring<br />

the wrong company can seriously cost you if property is lost, stolen or<br />

damaged. So make sure you are well-informed on this subject.<br />

There are 4 types of insurance:<br />

General Liability Insurance – this is the first line of defense against a variety of<br />

claims from alleged negligence to wrong doing by your commercial cleaning<br />

company and it is a must have. It’s strongly recommended that you make sure<br />

your cleaners have at least a minimum of 1 million dollars of general liability<br />

insurance. NEVER HIRE a company without General Liability Insurance.<br />

Workers Compensation Insurance – is basically a form of “social insurance”<br />

which covers job related injuries or in worst situation death of an employee. It<br />

compensates the employee or their heirs regardless of whose fault it was. It<br />

covers employees’ injury both at your place of business and during business<br />

related travel. Again, make sure to verify that the cleaning company has this<br />

insurance and their coverage is at least 1 million dollars and it’s clearly stated on<br />

the insurance certificate.<br />

Automobile Liability Insurance – as the name states itself, this insurance policy<br />

protects people and property from accidents that occur involving your cleaning<br />

Commercial <strong>Cleaning</strong> <strong>Buyers’</strong> <strong>Guide</strong> – citywidejani.com Page: 11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!