Selecting a Solar Contractor

Selecting a solar contractor – 6 must do's!

You have made the decision to put a solar array on your roof…now what? Selecting the right solar contractor may be more important than you think, so being an informed consumer should be your top priority. Here is what you need to know when selecting a solar contractor: 

1. Find a quality contractor – Don’t make your decision on price alone, as the quality of work may vary considerable from one firm to the next. To avoid being duped, look for businesses with strong reputations that have paperwork to back it up. As for proof of solar certifications of employees and references to verify they’ve built a good reputation.
2. Protect yourself – In case something should go wrong on the job, make sure your solar contractor has insurance and proper license so you’re not held liable. At a bare minimum, your contractor should have liability insurance, worker’s compensation, and a contractor’s license. 
3. Look for a one-stop shop contractor – There are a lot of companies that appear to offer a turnkey solution, but actually subcontract bits and pieces of their work to other contractors. The result is you get passed on from one contractor to the next and may end up paying more or left hanging if something goes wrong. Find a contractor that truly offers a turn-key solution – they can capitalize on economies of scale to save you money and minimize the steps involved for you. 
4. Know what you’re paying for – The devil is in the details of each bid so make sure you understand what is included and what is not included in your contractors’ bids. 
5. Get a warranty – You’re making a big investment that your contractor should be able to stand behind. Solar panels typically have a 10-year payback so go with a warranty that lasts at least this long. 
6. Last, go with your gut. If you got a funny feeling about a particular contractor, there may be something to your wariness. Happy hunting for your solar contractor!

Image: Monkey Business Images/Shutterstock

Something incorrect here? Suggest an update below: