Professionals or consultants who are unaware of professional indemnity/liability insurance may run the risk of being taken to court if one of their projects goes awry. Here's a look at how such coverage may protect you and your livelihood.
As an independent contractor, you’ve probably had set up your own insurance coverage, including property, business insurance, health insurance and possibly other policies. Along with these, you must evaluate your need for professional liability insurance, which will protect you if a client files a suit regarding how you did or didn’t fulfill your professional obligations. This coverage, also called errors and omissions insurance, may be necessary, in addition to any general liability policies you may have, to protect you in the event that clients taking legal action against you, claiming that you caused them financial loss or interruption of services.
It’s important to evaluate your risk and consider coverage, because as an independent, you don’t have the financial resources of a big company to back you up in the event of a client lawsuit. Also, more companies have recently begun requiring independent contractors to carry liability insurance when working on a project for them. If you subcontract, you may find that many computer-consulting companies are requiring their staff to carry professional indemnity/ liability insurance coverage in an amount equal to their own. You can assess your risk based on the type of work you do, the clients you take, and how well your contracts protect you from this type of lawsuit.
Examples
Let’s say you design a customer database for a client. A glitch after implementation prevents anyone from accessing that data for one week. The company sues, using weekly sales figures to argue that you caused the company to lose RM500,000 in sales. Professional indemnity/ liability insurance with coverage of at least that amount plus your legal fees would protect you in the event of a judgment.
How real is the risk?It’s easy to look at these examples and downplay the risks. You may be thinking, “My software would never fail completely like that. I would at least have a backup to the legacy system. I use virus safeguards, so an attack wouldn’t be my fault.”
- You’re at higher risk in the tech businessThe tech industry is particularly susceptible because technologies—and even our jobs—are so new: The law is still being defined and shaped, and there’s no clear standard on what constitutes acceptable and reasonable client expectations or even on what an IT consultant is. There are simply not enough legal precedents in this industry yet.
- Dissatisfied/dishonest clients could bring claimsThe standard IT claim is brought when clients perceive that they’ve lost money because of something you did (an error) or something you should have done but didn’t (an omission). Another type of claim could arise when a client simply isn’t satisfied with the job you’ve done. Perhaps the client expected your solution to deliver something it doesn’t or to function in a different way. However, to your understanding, it functions exactly as agreed. Ideally, you and the client will negotiate a solution, but if you can’t, your client may sue. Worse, dishonest clients with well-equipped legal departments may decide to sue to avoid paying monies they owe you. Contemplate the prospect of explaining why your solution does work as intended to a judge who knows little or nothing about technology, and insurance may suddenly look like a good idea after all.
- The work you do and the type of clients you take place you at low risk.
- You make sure that every contract you sign—perhaps using a contract that’s been approved by a lawyer experienced in IT professional liability cases—offers some degree of protection
against lawsuits.
You can assess risk by looking at the type of work you do and the financial stake your clients have in it. For example, I don’t carry professional liability insurance. The reason isn’t because I’ve decided I can’t afford it; it’s because the work I’m doing at this time isn’t particularly risky. As a technical writer, I create user manuals, software documentation, and help systems for companies. I don’t develop solutions that process credit card transactions or handle billions of dollars in customer investments. If I took on a project that involved even documenting such products, I’d reassess my risk.
Although neither of these criteria offers foolproof protection, they do help you balance investment with benefits, as you must do with all other expenditures.Do you have professional liability insurance?
As an independent consultant, have you bought errors and omissions insurance for your business? Have you decided it’s not worth the expense?