What document coverage and each status mean

In Vendarity, document coverage means requirements that have an accepted, in-date document. It isn't the cover an insurance policy gives, and it isn't a legal compliance check: it counts what your team accepted.

Every requirement you assign to a supplier gets one status, worked out from the documents your team accepted and their dates. The same rules drive Home, Documents, the supplier page, reports and exports, so a requirement reads the same everywhere.

How is document coverage counted?

It is the number of requirements with an accepted, in-date document divided by the number of requirements that apply. Expiring soon counts as current, because the document is still in date.

• A requirement marked not required, or outside the dates it applies, isn't counted at all.
• A requirement with only an exception stays in the count but isn't current. Reports show it separately.

What does each status mean?

What does “Current until” mean?

It is the last day the accepted documents keep a requirement current without a gap. It appears as a column on Documents, on each requirement row of a supplier’s Requirements tab, and as current_until in the document coverage CSV.

• It follows the accepted document’s expiry date, or its review date when that comes first.
• When a later accepted document starts the day after, or overlaps, the date runs on to the later document’s end. A gap between documents ends it.
• When an accepted document keeping it current has no expiry or review date, Documents shows “No end date” and the supplier’s page shows “Current, with no end date”. The CSV leaves the cell empty.
• It is empty when the requirement isn’t current on documents, including when it has only an exception or is marked not required.

Where do I see why a requirement has its status?

Each status comes with a short reason, such as “Accepted document has expired” or “Company name or site doesn't match”. It appears in the Why this status column on Documents, on the supplier’s Requirements tab, and in reports and exports.

Why does a requirement stay Current while a new document waits?

A replacement changes nothing until someone accepts it. The earlier accepted document keeps the requirement current for its own dates, and the row says the new version is waiting for review and the current one still counts.

A waiting replacement never extends the old expiry. If the old certificate expires on 31 Oct 2026 and the new one is still waiting on 1 Nov 2026, the requirement shows the gap on 1 Nov (example, fictional data).