Insurance and Certification Evidence Pack

Every certificate-of-insurance tracker watches one thing: the expiry date, with a reminder before it lapses. That catches the certificate that lapsed last month. It misses the far more common failure: a certificate that has not expired, sent against a contract asking for a limit or endorsement the policy does not actually carry. Vendor compliance guidance names a missing endorsement as the most common cause of a rejected certificate, ahead of an expired date. The security questionnaire beside it checks answers against evidence; nothing checks a certificate against the figure it was asked to meet.

So this pack checks three things per document against the request's own wording, not a generic assumption: the limit, the endorsement, and the entity name. In the worked example below, all six documents are current by their own date, and only two actually clear what was asked. An umbrella policy held at three million dollars against a five-million-dollar contract minimum is sixty percent of the ask, not compliance with it. A certificate marking additional-insured status with a checkbox is a claim; the endorsement itself, commonly form CG 20 10, has to confirm it.

Not every gap here closes inside this pack. A limit shortfall or an unconfirmed endorsement goes to the broker, on the broker's own timeline; drafting the ask is as far as a document can go. A stalled deal blocked on an engineer's queue instead of a broker's is a different problem, priced and escalated on its own. The audit reports, policies and pen test summaries this register skips keep their own coverage periods in the trust package; everything else sits in the template library and the tool index.