Question and scope
This protocol measures how often an active vendor commitment has no delivery date that the vendor has confirmed in writing. A confirmed date is a specific calendar date the vendor has acknowledged, not a requested date the buyer hopes to meet. Commitments without that confirmation tend to stall because the coordinator cannot tell whether the vendor has planned the work or is merely aware of it. The protocol produces a share, a count, and a list of the commitments that need a confirmation.
Scope is one coordination team, one defined vendor population, and a stated observation window. Include commitments recorded in a vendor tracker, a procurement system, a shared inbox, or a recurring operations review, provided the record identifies a vendor and a deliverable. Exclude internal work that does not depend on an outside supplier. Name the systems and the window so another analyst can rebuild the population.
What counts as a confirmed delivery date
A date is confirmed when the record shows a specific day and evidence that the vendor accepted it. The evidence can be a vendor email, a signed order acknowledgment, a portal status, or a meeting note that names the vendor representative and the date. A date that appears only in an internal plan is a requested date, not a confirmed one. The test is whether the coordinator can point to the vendor's own acknowledgment without asking again.
Distinguish a confirmed date from a delivery window. A window such as the second week of March can be useful, but it does not let the receiving team schedule dependent work with confidence. Code a window separately and report it outside the confirmed share. The same applies to expedited language such as as soon as possible, which describes urgency rather than a commitment.
Unit of analysis and exclusions
The unit is one vendor commitment with one deliverable, one vendor, one owning coordinator, and one needed-by date. Split a bundled entry when each deliverable has its own date and confirmation. Keep one unit when several items ship together under a single acknowledgment and a single date. Use the record as it stood at the cut-off, not a cleaned version rewritten during the audit.
Exclude quotes that were never accepted, cancelled orders, and internal purchases that do not involve an outside vendor. Exclude duplicate entries created when an email and a tracker record describe the same commitment, but count the pair once and note the overlap. Report each exclusion category with a count so the denominator is defensible. Keep a short log of what was removed and why.
Building the commitment list
Start with the vendor tracker and the open purchase orders that have a future delivery obligation. Search the shared inbox for confirmations, revised dates, and partial shipments, because a vendor may confirm a date in a message that never reaches the tracker. Add commitments discussed in the recurring operations review but missing from both sources. The goal is a complete list of live obligations, not a history of every vendor conversation.
Give every unit a stable identifier before coding so the same commitment can be matched across sources. Record the source, the date the record was created, and the vendor's name as written. Mark units found only in messages or meeting notes, since those are more likely to be informal and incomplete. Freeze the list before reading the confirmation fields to reduce selection bias.
Reading the date fields
Record three dates for each unit: the date the receiving team needs the item, the date the vendor first offered, and the date the vendor last confirmed. The needed-by date belongs to the receiving team and may not match the vendor's schedule. The offered date is the vendor's first proposal and is often provisional. The confirmed date is the latest date the vendor has accepted in writing, and it is the one that drives the headline measure.
Flag every unit where the confirmed date is later than the needed-by date. That gap is more useful than a simple pass or fail, because it shows how much schedule risk the receiving team is carrying. Also flag units where the confirmed date has passed without a delivery or a revised confirmation. A stale confirmation is not evidence that the vendor is still on track.
Evidence standards for confirmation
Accept a confirmation only when it is attributable to the vendor and specific enough to act on. A forwarded internal email that says the vendor agreed is weaker than the vendor's own message, and a verbal note should be coded as unconfirmed until it is written down. Record the evidence type so the analysis can show how many confirmations rest on strong versus weak records. This distinction keeps the headline from overstating certainty.
Do not upgrade a date because a coordinator remembers a phone call. Ask the coordinator to send a short confirming message and attach the reply, then recode the unit. If the vendor will not confirm in writing, that refusal is itself a finding worth reporting. The purpose is not to police memory but to make the commitment visible to everyone who depends on it.
Sampling and verification
Use a census when the vendor population is small enough to review in full, which is common for a single coordination team. Above roughly one hundred active commitments, draw a random sample and publish the method. Stratify by vendor and by receiving team so one large supplier does not dominate the result. Freeze the sample before contacting anyone about missing confirmations.
Have a second reviewer recode at least ten units and compare the results. Resolve disagreements by returning to the original message or order record, not by discussing which answer sounds more reasonable. Record the resolution so a later reviewer can see how the definition was applied. If disagreement is high, rewrite the definitions and recode the full sample before reporting.
Decision rules before coding
Decide before coding whether a commitment with a confirmed date but no named receiving owner counts as covered. The date may exist while accountability for the handoff does not, and the report should say which gap it is measuring. Decide whether a date confirmed before a scope change still counts, or whether the change requires a new confirmation. A scope change can invalidate a date even when the vendor has not said so.
Decide how to treat partial deliveries. A vendor may confirm a date for part of an order and leave the rest open, which is neither fully confirmed nor fully missing. Code the unit as partially confirmed and report it separately from the main share. The split keeps the headline honest and gives the team a clear next action for the remaining quantity.
Analysis and reporting
Report the share of active commitments with a confirmed date, the share with only an offered date, and the share with no date at all. Show raw counts beside every percentage, especially when the population is small. Add the share of confirmed dates that fall after the needed-by date and the count of confirmations that have gone stale. A single headline number hides which part of the date chain is weak.
Break the result down by vendor, receiving team, and commitment age. Suppress groups with fewer than five units so one unusual order does not look like a pattern. Pair the date result with the time each commitment has been open, because a missing confirmation matters more as a deadline approaches. The dependency register is the right place to record the confirmed date once it exists.
Limits and sources of error
The sources cited here describe internal control, project management, and risk practice in general terms; they do not provide a benchmark for vendor confirmation rates. A missing confirmation in the record may mean the vendor never confirmed, or that the coordinator did not save the message. A date may also be confirmed in a portal the analyst cannot access. Treat a low share as a prompt to inspect the records, not as proof about vendor reliability.
Informal commitments are undercounted when they never reach a written record. Check a sample of calls and meeting notes to estimate the size of that gap, and report it as a limitation. If a large share of commitments is invisible to the tracker, fix intake before setting a target. A precise share built on an incomplete list is less useful than a range with a clear caveat.
Review cadence
Review the result at a fixed point and end with one change, one owner, and one check date. A practical first change is to require a vendor-confirmed date before a commitment enters the active list. Repeat the measurement after two full cycles before setting a target, because a single quarter may reflect a seasonal peak or a supplier change. Keep the definitions and the sample method with the result so the next reviewer can compare like periods.
Retire the measure if every active commitment carries a written confirmation and the share stops changing. If the team keeps it, publish the confirmed and partially confirmed shares together, because a strict headline can hide a larger partial problem. Use the weekly blocked-work review to confirm that stale dates are being revised rather than quietly ignored. The purpose is a date the receiving team can plan around, not a perfect count.
Sources
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, reviewed November 12, 2026.
- Project Management Institute, PMBOK Guide, reviewed November 12, 2026.
- National Institute of Standards and Technology, SP 800-39: Managing Information Security Risk, reviewed November 12, 2026.
