What it means
A sales order may contain several dates: order placement, requested delivery, estimated shipment and committed arrival, and managers need to know which one the customer actually heard. If teams report against a date that was never promised, the metric can look unfair; if they replace the original date every time there is a delay, performance can look perfect while customers wait.
Before offering a date, check what is available and what remains uncertain. A warehouse may have stock on hand but already reserved for another order, a factory may have material but no production slot, and a service company may have a technician free while the customer has not confirmed site access.
Build the promise from usable inventory, realistic labour capacity, supplier lead time and a delivery route that can meet the destination. Some promises are conditional.
A quotation may say delivery is expected within ten business days after artwork approval or deposit receipt, so the team should record that trigger and confirm when it occurs. Avoid wording that turns an assumption into an unconditional date.
Keep the original promise, current promise, actual completion and reason for change as separate fields. A customer-requested postponement is different from a supplier shortage, although both alter the current plan.
Change history lets a business examine how often it makes promises it cannot keep, and it helps resolve disputes about whether notice was given in time. When a problem appears, assess alternatives before sending a new date.
Could a partial delivery, substitute item, other location or revised scope still meet the customer's critical need? Check cost and quality, get any required approval, then tell the customer early and clearly what changed, what is affected, the credible new date, and when the next update will come.
Measure both promise accuracy and recovery. On-time performance can be calculated against the original committed date, while a separate measure tracks performance against revised dates, segmented by product, supplier and order type; repeated delays in a particular line may require a longer standard lead time or different stock policy.
For owners, a promise date is a commercial decision, not merely an entry in a system, because better forecasting may produce a later first promise but fewer broken commitments, and the right trade-off depends on customer need and the actual capacity to deliver.
In practice
Real-world examples.
Example
A distributor receives a request for delivery on 10 October. After checking that the stock is usable and not reserved, it confirms 15 October because that is the first date for which a delivery slot is booked. The customer hears a date the warehouse can actually meet, and the 10 October request stays on the record as the requested date.
Example
A customer asks to defer an equipment installation because its site is not ready. The installer keeps the original promised date in the system and records the customer-requested change as a separate reason code. Later reports can then show that the delay came from the customer and not from the installer's own capacity.
Example
A printer learns that artwork approval is late on a $14,000 brochure order. It confirms a new date only after checking press capacity and the approval trigger written into the quotation. The customer receives a short message stating what changed, the new date and when the next update will come.
Formula
Calculation
Original-promise on-time rate = Orders completed on or before the original customer promise date / Orders due under an original promise in the period x 100
Worked example. An invented seller has 80 orders with original promise dates in September. It completes 68 by those dates, and seven other orders meet later revised dates.
- Original-promise on-time rate = 68 / 80 x 100 = 85%.
- Recovery measure = (68 + 7) / 80 x 100 = 75 / 80 x 100 = 93.75%, meaning 75 orders reached the customer by either the original or a revised date.
- The remaining 80 - 75 = 5 orders were still late against both dates and deserve a root-cause review.
- The seven successful revised dates belong in the separate recovery measure, not a rewrite of the 85% result.
Define how partial deliveries and customer-requested deferrals are treated before comparing teams.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Fieldstone Furnishings, an invented office supplier. Its sales team routinely promised two-week delivery by copying a catalogue lead time. Production slots had stretched to three weeks, but the order system showed only the latest revised date. Monthly reports claimed 97% on-time delivery while several customers complained about missed openings.
The operations manager reconstructed the original customer confirmations and compared them with actual delivery dates. She found that the company changed dates repeatedly after orders were placed. Sales and production then introduced an available-capacity check before confirmation, preserved every original promise, and gave account managers a clear route to propose partial deliveries or substitutions. Customers received notices earlier when a date was at risk.
The first month's reported on-time percentage fell because the measure stopped hiding revisions. Over the following quarters the company lengthened its standard quoted lead time for its slowest product line from two weeks to three. The original-promise rate then climbed steadily because the dates being promised were achievable, and complaints about missed openings fell. The case illustrates that a later first promise can be a better commercial result than an early promise that is repeatedly broken.
Watch out
Common mistakes.
- Treating a customer's requested date as a confirmed promise before checking capacity.
- Replacing the original promise with each revised date and reporting only the latest version.
- Offering a new date to calm a customer before verifying stock, labour and transport.
Questions
People also ask.
Is the requested delivery date the promise date?
Only if the business confirms it to the customer after checking that it can reasonably meet it.
Should a customer-requested deferral count as a miss?
Define the metric's treatment clearly and retain evidence of who requested the change; contractual effects may differ.
What if a promise is missed?
Check recovery options, tell the customer promptly, preserve the original commitment and record a credible revised plan.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%