Supplier Owner and Deadline Verification Checklist

When a supplier names an action but omits its owner or deadline, request a current record linking that action to one accountable role or appropriately disclosed person, a specific due date or checkable completion trigger, and an identifiable source or version. A redacted or pseudonymised extract may be sufficient if it preserves those details. This verification supports one pre-sourcing decision: whether the response establishes accountable follow-up. It does not prove completion, future performance or the supplier’s overall capability.

What counts as verifiable ownership and timing

Set a narrow verification target before requesting evidence:

• Owner: The role or person accountable for completing or approving the stated action.
• Deadline: A calendar date and, where material, a time and time zone; or an objective trigger whose occurrence can be checked.
• Evidence: Documented information connecting the action, owner and deadline to a current status.
• Provenance: Information identifying the record’s origin, date, version, approval status or other controlling source.

Documented information can exist in different media and formats. ISO guidance on documented information for ISO 9001:2015 explains that organisations may maintain documented information appropriate to their processes and use it as evidence. That principle does not require a supplier to use the buyer’s preferred system, form or template.

Potential evidence includes:

• An action-log extract.
• Approved meeting minutes.
• A workflow or ticket extract.
• A dated project-plan entry.
• A corrective-action or follow-up record.

These are buyer-defined acceptable formats, not documents universally required by ISO. ISO 10013:2021 provides guidance on developing and maintaining documented information, but it does not prescribe this verification checklist or require a particular action log.

Apply the following minimum decision rule:

1. The action is unambiguous.
2. One accountable owner can be identified.
3. The deadline is objectively interpretable.
4. The record can be tied to the supplier’s answer.
5. The record date, revision or equivalent identifier is visible.

Assignment is not proof of completion. A deadline does not prove that work will finish on time, and one action record does not demonstrate the effectiveness of the supplier’s wider management system.

Request wording that closes the evidence gap

Ask for the missing evidence directly instead of requesting unspecified “more information.”

Your response describes [action], but it does not identify who is accountable for it or when it is due. Please provide a current record showing:

1. the responsible role or appropriately disclosed individual;
2. the target completion date and time zone, or a defined completion trigger;
3. the current status; and
4. the record date, version or approving source.

A redacted or pseudonymised extract is acceptable if it preserves the action, accountable role, timing, context and record traceability. If no such record exists, please state that directly and identify who will create or approve it and by when.

Use a targeted follow-up when the response is only partly complete:

• Owner without a deadline: “What approved date or objective completion trigger is assigned to this action?”
• Deadline without an owner: “Which role is accountable for delivery by that date?”
• Vague timing: “Please replace ‘soon,’ ‘as needed’ or similar wording with a date or checkable trigger.”
• Multiple owners: “Which single role is accountable, and which roles are contributing or approving?”
• Out-of-date record: “Please provide the current revision or explain whether the earlier assignment remains valid.”
• No existing record: “Please distinguish the proposed commitment from an approved or recorded commitment.”

Do not request unnecessary personal details when a functional role such as “Quality Manager” is enough to verify accountability. If a named person is necessary, document the business reason and request only the fields needed for this task.

The ICO guidance on pseudonymisation distinguishes pseudonymised information from anonymised information. Pseudonymised information may remain personal data because additional identifying information is retained separately. Accepting pseudonymised evidence therefore does not determine the legal basis for processing it or remove applicable data-protection obligations.

Practical verification checklist

Verification check	Acceptable indication	Clarification or hold signal	Buyer action
Action identity	The record clearly matches the action in the supplier’s answer	Generic plan or record with no link to the stated action	Ask for an action reference, quotation or direct link
Accountable owner	One responsible role or appropriately disclosed person is identified	No owner, “the team,” several names without accountability distinctions, or an unexplained code	Ask for the single accountable role and separate contributors or approvers
Owner authority	The record indicates that the role owns, approves or is assigned the action	A contact is copied or mentioned but not assigned	Ask whether the role is accountable, contributing or merely informed
Deadline	A specific date is stated, including time zone where timing matters	“Soon,” “ASAP,” “ongoing” or an undated priority	Request a date or objective completion trigger
Trigger-based deadline	The trigger is observable and its consequence is clear	The trigger depends on an undefined event or subjective judgment	Ask how the trigger will be observed and when completion becomes due
Current status	Status is dated or tied to the current record	Status has no date or conflicts with the written response	Request a current status update and reconciliation
Record provenance	Source, record date, revision, approval or equivalent identifier is visible	A screenshot or extract has no origin, date or version	Ask for enough context to identify and date the record
Internal consistency	Action, owner and deadline agree across the answer and evidence	Different owners or dates appear without explanation	Request the controlling record and an explanation of superseded information
Privacy handling	Redaction or pseudonymisation preserves role, accountability, timing and context	Masking prevents verification of ownership or traceability	Request a role-based or limited extract retaining the necessary fields
Completion evidence	If the action is said to be complete, the record shows completion status and date	Only a planned deadline supports an action claimed as complete	Ask for the completion entry or revise the status to planned or in progress
Evidence availability	A current record is supplied, or its absence is stated plainly	Repeated narrative assurances without supporting documented information	Record the gap and hold this verification decision
Decision boundary	Evidence is used only to answer the ownership-and-deadline question	Evidence is used to infer broad quality or future performance	Limit the finding to accountability for the named action

Record the review in a separate worksheet:

Buyer worksheet field	Entry
Supplier
Response or action being checked
Evidence title or identifier
Record date or version
Accountable owner or role
Deadline or trigger
Current status
Redactions or pseudonymisation noted
Conflicts requiring clarification
Verification outcome
Reviewer and review date

Decide whether to accept, clarify or hold

Accept for this verification task when:

• The action, owner and deadline are explicit.
• The evidence is current enough for the decision.
• Its source, revision or equivalent identifier is visible.
• Any privacy masking still permits accountability and timing to be checked.

Clarify when:

• The owner is a team rather than one accountable role.
• The deadline is relative or subjective.
• A trigger exists but is not objectively observable.
• The record is undated, materially redacted or inconsistent with the answer.
• The owner or deadline changed without a visible revision or explanation.

Hold the specific decision when:

• No owner or deadline can be established.
• The supplier provides only unsupported narrative assurances.
• Records conflict and no controlling version is identified.
• The evidence cannot be linked to the action under review.

Use a concise outcome statement:

• Verified: “Current documented information identifies the accountable role and deadline for the stated action.”
• Partially verified: “Ownership is identifiable, but timing remains undefined.” Reverse the wording if the deadline is verified but ownership is not.
• Not verified: “The response and supplied record do not establish an accountable owner or deadline.”

Do not convert this result into a wider conclusion about certification, compliance, product quality, legal compliance or future delivery performance.

Sources

Source	Relevant use	Date and scope handling
ISO guidance on documented information for ISO 9001:2015	Supports the limited propositions that documented information can provide evidence, can use different media, and should suit the organisation’s processes	Retain the ISO 9001:2015 context. Recheck the PDF title, displayed date, availability and URL before publication
ISO 10013:2021 — Quality management systems: Guidance for documented information	Supports proportionate development and maintenance of documented information for a quality management system	Record the edition and publication date displayed by ISO. Recheck the page before publication; the landing page does not provide the full standard text
ICO guidance on pseudonymisation	Supports the distinction between pseudonymisation and anonymisation, including that pseudonymised information may remain personal data	Record the displayed publication or update date during final review. Limit its use to UK data-protection guidance and recheck the URL before publication

ISO-based statements should remain narrow: ISO does not require suppliers to provide a buyer’s preferred action log, ticket format or verification template.

Scope and limits

This task verifies whether one supplier response identifies accountable ownership and an objective deadline during pre-sourcing research. It does not evaluate:

• The supplier’s overall management system.
• Certification status or conformity with an ISO standard.
• Product quality, capacity, pricing or delivery performance.
• Whether the planned action will succeed or finish on time.
• Legal compliance or the legal basis for processing personal data.

ISO 9001 documented-information guidance and ISO 10013 inform the evidence approach; they do not prescribe this checklist or request wording. ICO guidance applies to UK data-protection concepts. Pseudonymisation is not anonymisation and does not automatically remove information from data-protection scope.

Before relying on the result, confirm that the supplied record is current and limit the final finding to whether it establishes an owner and deadline for the named action.