Customer insurance requirements: how hardware companies can compare a request before signing

Separate limits, certificate delivery, additional-insured status, waiver wording, primary wording, and notice requests. They are not interchangeable.

Note the exact legal names, product, site, and deadline in the agreement before asking for evidence.

Keep the agreement and amendments, current declarations, certificates, and requested endorsement forms together.

Identify whether the request concerns ongoing operations, completed operations, property, or a project-specific exposure.

• Named entities and requested status
• Limits and policy lines
• Delivery deadline and renewal obligation

Ask whether the policy and endorsement provide the requested status; do not infer it from a certificate.

Flag requirements that conflict with the operational facts or cannot be confirmed from the issued forms.

Track expiry dates and amend the file when the contract or policy changes.

Policy wording, declarations, and endorsements control, and contract review is not a promise that every request can be met.

For each customer agreement, make one row for legal entity names, policy line, required limit, aggregate, additional-insured wording, waiver, primary wording, certificate deadline, renewal duty, and required notice. Include the agreement section and the person who owns follow-up. A matrix prevents one customer’s unusual requirement from disappearing into an email thread.

Also note whether the requirement applies to a pilot, delivery, installation, completed work, access to a site, or a master agreement. The same business may have different obligations across customers, and those distinctions matter when asking what a policy or endorsement actually says.

A certificate can be produced quickly, which makes it tempting to start there. The better sequence is agreement, declarations, endorsement, then certificate. That order keeps the administrative evidence aligned with the underlying insurance documents.

If a customer asks for a term that cannot be confirmed, pause the representation and identify the correct next step: an endorsement request, a contract revision, a different risk allocation, or a discussion before work begins.

A customer may request general liability, products-completed operations, cyber, professional liability, commercial auto, workers compensation, or an umbrella. It may also demand a certificate, additional-insured endorsement, waiver, primary wording, specified notice, and renewal evidence. Put each requirement on its own row with the exact contract section, policy line, legal names, limit, timing, and party responsible for responding.

This prevents a single “insurance requirements met” checkbox from hiding distinct decisions. A policy limit can be present while the requested endorsement is absent, or a certificate may be current while the contract names an affiliate not shown in the policy record.

A pilot shipment, routine component sale, on-site installation, remote diagnostics service, and completed product support can create different expectations. Capture the customer site, product, duration, acceptance point, subcontractors, and any operational warranty. The coverage review should use the real scope, not a boilerplate exhibit detached from the statement of work.

If the contract requires insurance to continue after delivery or completion, note the period and what products or services it refers to. That is a question for both the legal and insurance review teams; do not infer compliance from one current certificate.

California Insurance Code section 384 addresses what a certificate can represent. A certificate provides evidence about identified policies; it does not itself amend a policy to add an insured or waive a right. Where the customer asks for additional-insured or other status, compare the actual issued endorsement, named entity, covered operations, and effective period with the contract.

If a requested term is unavailable, identify the gap before signing or beginning work. Possible outcomes may include an endorsement request, revised clause, different commercial allocation, or a decision not to accept the work as written. The guide cannot choose among those options for a specific contract.

Read per-occurrence and aggregate limits separately, and ask whether a product or completed-operations aggregate applies. If the customer demands an umbrella, check the scheduled underlying policies, attachment point, retained limit, and exclusions instead of adding headline limits arithmetically. For cyber or professional-liability requests, review claims-made dates and reporting terms where relevant.

A high number on a certificate may not address an excluded activity or a different legal entity. Put the form number, endorsement, and unresolved question beside each row. Ask for a written answer when the contract language and policy language do not use the same terms.

Record who requested the certificate, the version delivered, the recipient, delivery date, policy period, endorsements checked, and next renewal date. Reopen the file when the customer adds a site, expands installation scope, changes product specifications, or amends an insurance exhibit. Do not reuse a prior certificate automatically for a new purchase order.

Coordinate the operational team’s start date with the agreement and policy review. A certificate deadline may be an administrative milestone; it should not be mistaken for proof that every contractual risk allocation has been satisfied.

The final matrix should show each contract request, supporting policy document, unresolved exception, decision owner, and follow-up date. Keep the signed contract, final certificates, issued endorsements, and submission facts in one controlled folder. This record can be reused at renewal only after the current product and policy facts are confirmed.

Policy wording, declarations, endorsements, contract terms, facts, and applicable law control. This independent guide helps a hardware company identify questions; it does not certify contract compliance or guarantee coverage.

• Exact customer and company legal names
• Scope, site, and completed-work period
• Certificate plus supporting endorsements
• Exception owner and renewal date