In general, the Certificate of Insurance and any additional certificates should be issued by the insurance agent who wrote the coverage, and should provide the contact name, phone and address, policy number, insurance coverage, limits, effective and expiration dates. In every case, it is important to request the Certificate of Insurance from the agent, and not the carrier. You’ll find in the long run that it’s much easier to avoid fraudulent certificates and claims if all information is gathered from the correct sources and kept in order.
With the publication and immediate suspension of the URS, existing carriers will need to continue to follow the same procedures and forms for registration updates as they do today. According to FMCSA spokesman Duane DeBruyne, the agency intends to lift the suspension once the technology to implement the URS is complete.
Since the passing of 2015’s FAST (“Fixing America’s Surface Transportation”) Act, carriers’ compliance, safety and accountability scores (CSA scores) have been temporarily removed from public view, leading to a select group of companies developing their own systems of determining a safety score based on information still available to the public.
Last time we discussed how not having a Certificate of Liability Insurance from a potential trucking company business partner can itself be an unexpected form of liability. Now that we’ve established why a certificate is effectively required to carry out a freight transportation partnership without surprises, let’s take a moment to examine what the Certificate of Liability Insurance form is, exactly. This deep dive includes the liability insurance and certificate formats most commonly used in freight transportation and how to ensure your specific needs are met.
If insurance companies and shippers use CSA data then they should have a list of high risk indicators they suspect affect the carriers’ safety management programs, i.e. brake violations, hours of service (HOS) violations, controlled substance & alcohol related events, etc.