01Record the promise at line level
A purchase order can contain items with different expected dates and quantities. The first acknowledgement should be matched to the supplier, order and line, with an owner for anything unconfirmed. An order-level green status can hide one critical late component.
02Capture changes without losing history
Supplier updates arrive by email, portal, spreadsheet or telephone. The team needs the latest confirmed date, its source and when it was received. A changed promise should remain distinct from the original requirement so repeated slippage can be reviewed.
03Escalate an actionable exception
Overdue, unacknowledged and partially delivered lines enter a queue with a next action and responsible buyer. Delivery or project teams receive approved updates about dependencies. An estimated supplier date should not silently become a firm commitment to your customer.