What to do when a contractor's insurance document is rejected

A contractor uploads an insurance certificate, but the reviewer cannot accept it. Perhaps it is out of date, names a different insured company, does not show the agreed cover, or omits a schedule needed to understand exclusions. The next step is not simply to mark a box red. Someone must explain the gap, get the right evidence and decide whether work can start or continue.

This guide is about the correction and decision trail **after a document is rejected**. The broader contractor compliance checklist owns the initial insurance review and wider appointment checks. Insurance suitability can be legally and commercially complex; where coverage is uncertain, involve the insurance or legal adviser rather than treating a platform status as a coverage opinion.

Classify the rejection precisely

Record the contractor, legal entity, work package, site, document version and reviewer. Then select the reason in terms a contractor can act on. Examples include unreadable or incomplete certificate, expired period, wrong company, missing insurer details, wrong insurance class, apparent cover below the contractual requirement, or an exclusion that may affect the work. Do not use “failed compliance” as the only explanation.

Distinguish an administrative defect from a substantive risk. A cropped upload may be solved by a complete certificate. A policy that excludes the activity may require an endorsement or different cover. The reviewer should not assume a letterhead proves all terms; ask for the relevant policy schedule or confirmation from a broker or insurer where needed.

Tell the contractor exactly what will resolve it

Send one clear request naming the rejected version, the issue, acceptable evidence and the deadline. For example, request a current certificate in the correct legal name together with the schedule showing the agreed class and limit. If the answer depends on an endorsement, specify that the endorsement must refer to the actual work. Keep the response in the same case as the rejected file so later reviewers can understand the sequence.

Avoid asking for every possible insurance document where the gap is narrow. The review should be proportionate to the work and the contract. Do not publish a universal “safe” cover limit: required limits vary with the task, client terms and exposure. Employer's liability requirements also depend on the employer's circumstances; a generic contractor status should not settle that question.

Decide what happens to the work

If the contractor has not started, hold authorisation for the affected activity until the evidence is acceptable or an authorised decision maker records a justified alternative. If work is under way, notify the site decision owner promptly. Consider whether work must pause, whether a different scope is covered and how to make the area safe. The reviewer of a certificate should not quietly decide operational continuity alone.

There may be a legitimate reason to allow a narrowly defined preparatory task while a separate policy question is resolved. If so, document the exact scope, authority, control measures and expiry of the exception. Do not label the contractor “fully approved” when the insurance issue remains open. A waiver from a customer cannot rewrite an insurer's policy or remove legal obligations.

Re-review the replacement, not the old status

When a new file arrives, verify that it addresses the specific rejection and covers the relevant period. Compare the insured name, insurer, insurance class, limit, scope and any endorsement against the agreed requirement. Record who reviewed it and when. Preserve the old version and decision so the history is intelligible; do not silently replace an expired document with a new one while retaining an earlier approval date.

Then send a clear outcome to the contractor and site team: accepted for the defined work, still rejected, or escalated for specialist advice. If the document expires during the job, treat that as a new decision. Acceptance of evidence is not a promise that a claim will be paid; coverage decisions rest with the policy and insurer.

Improve the process after repeated rejections

Recurring errors may mean the request template is vague, the document upload instruction is poor or the contract requirement is unclear. Measure why documents are rejected and whether corrections arrive before planned starts. A useful process gives suppliers a precise request and gives managers a visible work decision without inventing certainty about insurance law.

Complys contractor management software is a relevant product area to compare. Ask for a live demonstration of how a rejected file, reason, supplier response and human acceptance decision would be captured. Do not infer an automated coverage judgement from marketing copy.

Example: the wrong insured company

Suppose a contractor's certificate names its parent company while the purchase order names a subsidiary doing the work. The reviewer should not infer that group membership extends cover. Mark the exact identity mismatch, ask for evidence that the working entity is insured for the agreed activity and period, and refer uncertain wording to the insurance adviser. Keep the planned start on hold for the affected task until the authorised person has a clear answer. When the contractor supplies a revised certificate or insurer confirmation, link it to the rejected version and record who reviewed the change. If only a different entity is insured, the contract or work allocation may also need correction. The document problem is closed only when the commercial and operational decision is clear.

If a replacement insurance certificate arrives, compare its insured entity, covered activity, dates, limits and exclusions with the actual contract and work. Keep the rejected version and reason in the decision trail. A newer upload is not automatically an acceptable one, and an insurance review does not replace the contractor competence or work-risk decision.