A supplier thread can move from we hope to deliver Friday to confirmed for Tuesday and later dispatched. A tracker that extracts every date as a promise creates false overdue flags. A tracker that always replaces the old date with the newest one can hide how commitments changed.
The proposed report below preserves each date statement, links it to the purchase and item being discussed, and compares confirmed commitments with actual receipt evidence. Its purpose is procurement review. It does not determine breach, impose penalties or establish a supplier's overall performance from a few messages.
Identify what was promised and what was merely proposed
Record the supplier wording, message reference, sender context, purchase reference and relevant items. Classify the statement as proposed, estimated, confirmed, revised or unresolved using the procurement team's approved rules. If the wording is ambiguous, keep it unresolved rather than choosing the strongest interpretation.
A revision needs its relationship to the earlier commitment recorded. Was the new date accepted through the approved process, or was it only suggested? Keep both statements and the acceptance evidence. Do not silently overwrite a confirmed date because a later message sounds more recent.
Google's Gmail push guide documents mailbox-change notifications and retrieving changes through history identifiers. That supports an update collection path, not the meaning of a supplier's promise. The application still needs authorised message retrieval and a verified relationship to the purchase record. Source: Gmail push notifications
Use receipt records for the actual outcome
Choose the organisation's authoritative receipt or delivery evidence. A supplier's dispatched message describes a different stage from goods received and accepted. A calendar delivery appointment also does not prove that the delivery occurred.
Record delivered quantity as well as date where the purchase is divisible. If eight of ten units arrive, an item-level report should preserve the remaining quantity. The procurement owner decides how partial receipt relates to the commitment and any applicable requirements; the assistant should not label the whole order complete because a delivery exists.
Missing receipt evidence creates uncertainty. It may mean the goods have not arrived, or that the relevant record is unavailable or incomplete. Show the known commitment and evidence gap, then ask the designated owner to investigate. Avoid turning absence in one data source into an unsupported statement of supplier failure.
Supplier follow-through report
Use this complete hypothetical report format. All purchase references and dates are fictional; lateness uses calendar-date comparison only under the proposed review rule.
| Purchase item and evidence | Commitment status | Actual receipt evidence | Review result and next step |
|---|---|---|---|
| TEST-PO-A item 1; message M01 confirms 3 November 2026 | Confirmed date, no approved revision | Receipt R01 records the full item on 5 November | Receipt is two calendar days after the recorded date; procurement reviews the cause |
| TEST-PO-B item 1; M02 says aiming for 4 November | Proposed or estimated, not confirmed | No verified receipt record available | Do not label overdue against a confirmed promise; owner requests clarification and checks receipt source |
| TEST-PO-C item 2; M03 confirms 6 November and M04 suggests 9 November | Revision acceptance unresolved | Receipt not yet available in the fixture | Preserve both dates and hold the current-commitment conclusion |
| TEST-PO-D item 1; M05 confirms ten units for 7 November | Confirmed quantity and date | R02 records eight units on 7 November | Partial receipt; two units remain unresolved under the fixture comparison |
| TEST-PO-E item 3; two copies of M06 | One verified commitment duplicated in collection | One matching receipt R03 | One commitment and one receipt, with duplicate source references retained |
Each row stores supplier reference, purchase and item reference, original wording, date purpose, interpreted date, message reference, revision relationship, acceptance evidence, promised quantity where applicable, receipt reference, actual quantity and date, comparison rule, uncertainty and owner. Keep the report's covered period and source retrieval status visible.
Comparison rules: compare like items and approved commitment versions only. Use the agreed date convention and report partial receipt separately. Mark missing evidence as unresolved. Preserve the original commitment history when a revision is accepted. A date difference is an operational review flag, not a legal conclusion or penalty calculation.
Follow-up queue: assign a responsible procurement reviewer to each unresolved row. Draft the exact question needed: confirm the intended date, explain a discrepancy, identify the accepted revision or locate the missing receipt. Do not send those drafts externally or amend a purchase order as part of generating the report.
Acceptance fixtures: ordinary confirmed delivery; tentative date; unaccepted revision; partial receipt; duplicate message; and ambiguous purchase reference. Check that the report preserves statuses, calculates the two-day and two-unit examples correctly, avoids duplicate commitments and holds uncertain joins.
The report is complete when every included item has a traceable commitment status and actual-evidence disposition. A reviewer can resolve a row through approved evidence, but the assistant should not close it merely because a newer message says everything is sorted.
Extract structured fields while preserving wording
OpenAI's Structured Outputs guide supports schema-constrained responses and refusal handling. It can help separate commitment status, date, quantity, source and uncertainty. A valid schema does not establish that aiming for means confirmed or that the purchase reference was matched correctly. Source: OpenAI structured outputs
Keep the original phrase alongside the structured interpretation. Review uncertain dates such as next Friday against the message timestamp and intended context, using the owner's approved clarification rule. Do not infer a date when the context remains unresolved.
Likewise, do not match an email to an order using only a supplier name. One supplier may have several open purchases. Require the verified purchase reference or an approved item-context match; otherwise place the message in an unassigned evidence queue.
Keep the tracker from erasing evidence
A spreadsheet report may be useful for procurement, but its edits need a controlled mapping and version. Google Sheets documents grouped updates to spreadsheet details and a separate values resource for cell data. Those capabilities do not decide which commitment is authoritative or prove that a report row reflects a real delivery. Source: Google Sheets batch updates
Use stable row references and a history record for accepted revisions. Do not make the current report the only place where the original promised date exists. If staff correct a join or status, retain the correction reason and reviewer so later summaries do not silently repeat an earlier error.
Also distinguish report publication from source-system updates. A procurement reviewer may approve a corrected report while the purchase order still requires a separate authorised change. The workflow should make that difference visible.
Work through normal, missing and duplicate evidence
In the hypothetical TEST-PO-A case, the verified message confirms 3 November and the receipt records 5 November. The report shows a two-calendar-day difference with both references. Procurement can investigate the explanation; the assistant does not infer a contractual consequence.
In a missing-receipt case, a confirmed date has passed but the receipt system is unavailable. The report states that receipt evidence could not be checked and identifies the affected source. It does not claim definitively that the goods never arrived. The owner reconciles the source before closing the outcome.
In a duplicate-message case, two collection events refer to the same original message. They produce one commitment record with the duplicate collection references, not two promises or two supplier incidents. If the messages are similar but have different purchase references, keep them separate until the item match is verified.
FAQ about tracking supplier commitments
Should every date in a supplier email enter the overdue calculation?
No. Identify its purpose and status first. Proposed, estimated and unresolved dates need different treatment from a confirmed commitment under the approved review rule.
Can a dispatched message count as actual delivery?
Not unless the organisation's approved evidence process specifically establishes the relevant outcome from it. This proposed report uses verified receipt evidence and keeps dispatch as a separate stage.
What should happen when the supplier changes the date?
Preserve the earlier commitment, proposed revision and acceptance evidence. The procurement owner determines the current approved commitment; do not overwrite the history automatically.
If your business needs help defining this process, explore Workflow automation, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.