Promise Date vs Realistic Date: Scheduling Discipline
Why this matters
The fastest way to lose a customer's trust is to give them a date and miss it. Not because the work was bad - because you said a day and it did not happen. Most shops over-promise on dates for an understandable reason: in the moment of booking, a sooner date wins the job and feels generous. But a promise date pulled from optimism instead of real capacity is a debt you will fail to pay, and the customer remembers the broken promise long after they would have forgotten a slightly later one honestly given. The discipline of separating the date you wish you could hit from the date you can actually hit is what makes a shop dependable.
The two dates are not the same
- The optimistic date assumes everything goes right: no job runs long, no tech calls in sick, no part is backordered, no traffic, no callback steals a slot. It is the date you give when you are eager and have not looked hard at the calendar.
- The realistic date assumes the normal friction of a real week: some jobs run over, surprises happen, buffer gets used. It is the date your actual capacity supports.
The gap between them is where broken promises live. Owners hand out the optimistic date and then operate in the realistic world, so they miss. The fix is to quote the realistic date even when the optimistic one is tempting.
Why "under-promise, over-deliver" actually works
This old line is not a slogan, it is a mechanic. If you promise the realistic date and then a job happens to go smoothly, you finish early - and finishing early is a delight that builds trust. If you promise the optimistic date and the normal friction shows up, you finish late - and finishing late, even by the same margin, is a disappointment that erodes trust.
Same actual performance, opposite customer experience, decided entirely by which date you promised. A shop that consistently beats its dates earns a reputation for reliability; a shop that consistently misses earns the opposite, even if it does the exact same work in the exact same time. Set the bar where you can clear it.
How to set a date you can keep
- Start from real open capacity, not wishful thinking. Look at what is already committed and what is genuinely free after drive time and buffer.
- Add padding for the known unknowns. You cannot predict which job runs long, but you can predict that one will. Build that into the date instead of pretending the week will be perfect.
- Quote the date your capacity supports, not the date the customer hopes for. It is fine to say "I'd love to say tomorrow, but to give you a time we will actually keep, it's later this week."
- Write it down where the whole team sees the same commitment. A promise that lives only in the booker's memory is a promise waiting to be dropped at the handoff.
Set a range or a window, not a false-precise time
A common trap is promising more precision than you can deliver - a specific hour when your day genuinely cannot be controlled to the hour because of variable job lengths and drive times. Over-precise promises break constantly and for no good reason.
- Where you can hold a tight window, give one - customers value it and it shows control.
- Where you genuinely cannot, give an honest window and a heads-up call when you are on the way, rather than a precise time you will miss. An honest "between these hours, and we'll call when we're thirty minutes out" beats a precise time that slips.
Precision you can keep builds trust. Precision you cannot keep destroys it faster than vagueness would have.
When you are going to miss anyway
Even with discipline, a date will sometimes slip - a part is backordered, a prior job blows up. The promise is not really about the date; it is about being treated honestly. So:
- Communicate early, the moment you know, not the morning of. Customers forgive a slip they hear about in advance far more than one they discover by waiting on a no-show.
- Give a new realistic date, not another optimistic guess. Missing twice is how you turn a slip into a lost customer.
- Own it plainly. No elaborate excuse - a clear "we hit a snag, here's the new time we'll keep" preserves the relationship.
The reputation you are protecting is "this shop does what it says." That reputation is built one kept date at a time and broken one missed date at a time, and it is worth more than any single job you might win with an optimistic promise.
References
- See related: Can We Take This Work? A Capacity Decision Tree
- See related: Backlog - When the Schedule Is Full Decision Tree
- Capacity-based scheduling, standard operations and service-management practice
- U.S. Small Business Administration guidance on customer communication and service delivery