What is document coverage, and how do you measure it?

Document coverage tells you how many of the documents you need from suppliers you actually have, in a form you can rely on today. It is the share of assigned requirements that have an accepted, in-date document. Two words do the work: accepted, because a document counts only after a person has checked it, and in-date, because it counts only until its expiry or review date.

This is general information about measuring supplier documents, not legal or insurance advice. Document coverage records what your team accepted; whether that meets a law or a contract is for your team to decide.

What is the difference between received, accepted and current?

Every supplier document passes through the same states, and only some of them count:

Why doesn’t a received document count?

Because receiving a file proves only that a file arrived. It may be last year’s certificate, a different company’s, a quote instead of a policy, or the wrong kind of cover. Someone has to compare it with what you asked for before it means anything.

Regulators say the same about the most common supplier document. The Connecticut Insurance Department says a certificate of insurance generally serves “only as evidence of insurance in lieu of an actual copy of an insurance policy” and contains “a snapshot of the insured’s coverages as of the day of issue”. New York’s Department of Financial Services warned that a certificate “is not the best evidence of the terms of an insurance policy and may not accurately reflect the actual terms of the policy”. A check against your requirement is how a received certificate becomes one you can rely on.

AI can help with that check by suggesting the insurer, policy number and dates and showing where it found each one, but the decision to accept stays with a person.

How do you calculate document coverage?

Divide the number of requirements that have an accepted, in-date document by the number of requirements that apply:

• Count each requirement once, however many documents it has. Two accepted certificates for the same requirement still make one requirement current.
• Leave out what doesn’t apply. A requirement you have recorded as not required for a supplier, or one outside the dates it applies, is not counted at all.
• Keep exceptions in the count, but not as current. If you have agreed to go without a document for a while, that requirement stays visible as not current, so the exception is never mistaken for a document.

A worked example, with fictional data: a supplier has three requirements on 14 Oct 2026. Its ISO 9001 certificate (accepted, valid until 30 Nov 2027) and its code of conduct (accepted, valid until 30 Sep 2027) are both current. Its public liability certificate has been requested but not received.

The certificate arrives, gets scanned and gets read, and coverage doesn’t move. It moves once, at the moment a person accepts it. The home page plays the same example step by step.

When does a document stop counting?

• At the earlier of its expiry date and its review date. A document with a review date before its expiry stops counting at the review date.
• On the first day of a gap. Back-to-back documents keep a requirement current; if the new one starts even one day after the old one ends, the gap shows.
• Not when a replacement arrives. A replacement waiting for review doesn’t extend the old document. If the old one expires before anyone accepts the new one, the requirement shows the gap.

Current means current on what you accepted, not a guarantee about the world. A certification can be suspended or withdrawn before the expiry date printed on it, as IAF CertSearch statuses show, and the Connecticut bulletin says a certificate holder “is owed no duty to be notified” if the policy is cancelled. Checking a register or asking for confirmation is still worth doing for the documents that matter most.

How do you keep document coverage from falling?

Most coverage is lost at renewal, not at the start. When Richmond, Virginia’s City Auditor reviewed 17 paving contracts, certificates for all 17 had arrived before signing, yet for 13 of them (76%) the cover dates ran out before the work was finished. Three habits prevent most of that:

1. Ask before the date, not after. In Vendarity, once an Owner or Admin turns on automatic reminders, the standard schedule asks the supplier for the next document 30, 14, 7 and 1 days before the current one expires.
2. Review replacements promptly. A replacement sitting unreviewed counts for nothing, and the old document keeps running down.
3. Watch the measure per supplier and per requirement, not only the overall percentage, so one important gap doesn’t hide behind many current documents.

Is document coverage the same as compliance?

No. It records which requirements have a document your team accepted and that is in date today. It doesn’t say the document is genuine, that the cover is adequate for a particular job, or that a supplier meets a law or a contract. Those are judgements your team makes, and the measure helps by showing exactly which documents they rest on.

How does Vendarity show document coverage?

Every requirement shows one status, such as Current, Expiring soon, Awaiting review or Missing document, and a current one shows the date it stays current until. The same rules drive the home screen, supplier pages, reports and exports, and replaced documents stay on record with their history. See what document coverage and each status mean in the help centre.