Vendor Management Research

Measuring vendor credential expiry lead time before delivery

A method for measuring how far ahead of a scheduled delivery a dispensary confirms a vendor's license or registration is current, scoped, and recorded.

Measuring vendor credential expiry lead time before delivery

Key takeaways

  • Measure lead time from the delivery date, not from the purchase order date, because the delivery is the moment the credential must be valid.
  • Score scope and entity match separately from the expiration date so a current but wrong document is not counted as valid.
  • Report the share of deliveries released with a credential check inside the store's chosen window.
  • A vendor that renews on time but supplies an unreadable document has a different problem from a vendor that renews late.

Question and scope

This review asks how much lead time a dispensary has between confirming a vendor's license or registration and the delivery it is meant to cover. The unit is one scheduled vendor delivery tied to one purchase order and one credential review. The review measures the date the credential was checked, the date the delivery was scheduled, and the date any renewed document arrived. It does not judge whether the vendor is reliable or whether the product should have been ordered.

Set the scope to one store, one purchasing system, and one defined period. Record the vendor set, the credential types, and the trigger window in force during that period. If the store changed purchasing systems or onboarding requirements inside the window, split the period. A system change can alter both the check date and the record quality, and combining the two periods would hide that effect.

What the sources establish

The Virginia Cannabis Control Authority sets the licensed framework for cannabis businesses in the state and publishes the categories of licensed activity that a vendor may hold. NIST's supplier and cybersecurity guidance is not a cannabis rule, but it offers a documented supplier-review structure that maps well to a vendor credential file. The GAO's data reliability guidance describes how to assess records that were created for operations rather than for research. Use the authority's current published list as the reference and check it before each review cycle.

These sources support the idea that a supplier check should be documented and repeatable. They do not define a required lead time for this store. The review must build its own baseline and state the trigger window it is testing. A benchmark from another market would not account for the store's delivery schedule or its vendor mix.

Definitions and measures

Define a credential review as a dated check of the vendor's license or registration against the delivery it will support. Define lead time as the number of calendar days between the review date and the scheduled delivery date. Define a valid review as one where the document is current on the delivery date, covers the licensed activity, and matches the vendor entity and facility on the purchase order. Write the definitions into the review sheet before the first delivery is scored.

Measure the number of deliveries, the number with a recorded review, and the lead time for each. Score scope, entity match, and expiration separately so a current document with the wrong facility is not marked valid. Also measure the number of deliveries held or rescheduled because a credential was missing. Report the counts by vendor and by credential type.

Sampling and collection

Sample scheduled deliveries rather than vendors. A single vendor can have one delivery with a timely check and another with no check at all, and a vendor-level average would hide the difference. Include deliveries that were released, held, rescheduled, and cancelled. Stratify the sample by vendor size, product category, and delivery route.

Collect the purchase order, the credential document, the review timestamp, the delivery schedule, and any hold or release note. Record the sampling rule and the observation window before opening the files. Mask individual staff names where they are not needed. If the review timestamp is missing, note the gap and keep the delivery in the sample rather than excluding it.

Calculating lead time

Calculate lead time as the scheduled delivery date minus the credential review date. A negative value means the review happened after the delivery was scheduled, which is not necessarily a failure but is worth reporting. A review that happens after the delivery is a different and more serious finding. Keep those two cases separate in the table.

Report the median, the interquartile range, and the share of deliveries reviewed inside the store's chosen window. The median alone can hide a cluster of last-minute checks. Show the distribution and the count of deliveries that were never reviewed. A single late delivery in a high-volume week may matter less than a pattern of late checks across one vendor.

Separating date, scope, and entity

A credential can be current and still fail the review. The document may cover a different licensed activity, name a different entity, or list a facility that is not the one shipping the product. Score each condition on its own so the review can show which failure is most common. A current date does not compensate for a scope mismatch.

Record the specific mismatch in plain language. "License current, entity name differs from invoice" is more useful than a generic invalid flag. If the vendor supplies a temporary authorization, note what it covers and what it does not. The vendor license follow-up routine describes the operating response to each of these cases.

Reporting by vendor and window

Report the share of deliveries with a review inside the window, by vendor and by credential type. Show the number of deliveries that were held and the number that were released after a late check. Include the count of reviews that failed on scope or entity even though the date was current. That separation keeps the result from implying that date compliance is the only measure.

Describe the observation window and the trigger rule beside the counts. State whether the store can link a specific review to a specific delivery or only to a vendor file that was updated sometime before the delivery. The weaker linkage should be labeled as such. A reader should be able to see what the record supports without reconstructing the method.

Limits and sources of error

The purchasing system can show when a review was recorded, but it cannot prove when the reviewer actually read the document. A review entered on the delivery morning may have been based on a file that arrived weeks earlier. The analysis should describe the recorded date and avoid claiming more precision than the record supports. Keep the retrieval date and the document date in separate columns so a later reviewer can see which one moved.

A vendor file may contain a document that was current when downloaded but has since been superseded. The review should note the retrieval date and the document date separately. A missing hold note does not prove that a delivery was released without a check, because the hold may have been handled by phone. Those cases should be flagged as record gaps rather than counted as failures.

Review and next action

Choose one change: move the credential check to a fixed number of days before the delivery, add a scope field to the review form, or require a document retrieval date. Assign the owner and the next sample date. Keep the change small enough to test with one vendor or one delivery route. Repeat the review with the same definitions so the comparison is meaningful.

Close the review when the store accepts the result and schedules the next check. Report the remaining uncertainty beside the counts. The vendor sample log review covers a related supplier-record question. Use the result to improve the vendor file and the purchasing trigger, not to rank individual buyers. The NIST Cybersecurity Framework offers a documented supplier-review model that can be adapted, while the state authority remains the source of the licensing rule. Schedule the next check and name the person who will run it.

Sources

The sources below support the regulatory, supplier-review, and data-quality context for this review. Keep the citation list visible beside the analysis table during the review. They do not measure this dispensary, and no source is presented as a local benchmark. Each link should be checked for its date and scope before reuse. The operational finding comes only from the store records described in the method.

This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation. Store the signed scope note with the review file, and give the owner a copy before the next sample begins.

Reviewed by the DispensaryVA editorial team on 2026-11-07.