The Change They Think They Made
A guest updates something, the screen appears to accept it, and nothing happened. The gap between believing and being recorded, and the two-line habit that closes it.
Somebody told you they changed something — a booking, a preference, a detail. Your record says otherwise.
Neither of you is lying. They did something, and it did not arrive, and the gap only surfaces later at the worst moment.
Where the gap opens
A form that was filled and not submitted. Interrupted, closed, or a button that did nothing visible.
A message sent to somewhere nobody reads. ⚠️ They told you. Nobody received it, and from their side those are the same act.
Told to a person who did not write it down. The most common by far — it was heard, understood, agreed, and never recorded.
A change made and then silently reverted. Overwritten by a later save, or by someone working from the old version.
Why they believe it happened
Nothing contradicted them. ⚠️ Absence of an error reads as success, and for most people that is entirely reasonable.
They were not told what to expect. With no "you will receive a confirmation", there is nothing whose absence they could notice.
The interaction ended normally. A conversation that ends politely feels concluded, whatever was written down.
What it costs
The wrong thing happens. The old preference, the old time, the old detail — at the moment it matters, in front of them.
Trust, disproportionately. ⚠️ Being told "you never told us" when you did is worse than the original problem, and it is what people remember.
Nobody learns. It gets treated as a one-off misunderstanding rather than a gap in how changes are captured.
The two-line habit
One: say it back. "So that is Saturday at eight, six people, moving from four." ⚠️ Ten seconds, and it catches the misunderstandings while both people are present.
Two: confirm in writing. Short, immediate. Its purpose is not the content — it is that its absence is noticeable.
The second line is what makes the difference. With it, a change that failed to record is visible within minutes rather than at the table.
Where to look for the gaps
Ask staff which changes they take verbally. ⚠️ There will be several, and they are the highest-risk ones by definition.
Check whether every route produces a record. Phone, message, in person, through a third party. The one nobody thought about is where this happens.
Look for the second copy. If a change has to be made in two places, one of them will be missed — and it will be the same one every time.
When it has already happened
Do not lead with the record. ⚠️ "Our system says" is a losing sentence — it is technically defensible and it costs the relationship.
Fix the immediate thing first. Then find out where it broke, separately.
And say what you changed about the process. ⚠️ The part that repairs the trust — not the apology, the change.
Announcing is not the same as changing
Said in a meeting heard by the people who attended
Said to one person becomes their private version
Written and posted read by whoever happens to look
Built into the flow happens whether anyone remembers or not
⚠️ Only the last one is a change. The other three are announcements that decay at different speeds.
Why the belief survives so long
⇒ ⚠️ Nobody reports back that a change did not take. The people who never heard it are, by definition, not raising it — so silence gets read as adoption.
The three shapes this gap takes
Never heard the person was off that week and nobody repeated it
Heard, not agreed the person kept the old way and said nothing
Heard, misheard the person changed something adjacent instead
⚠️ The third is the most expensive because everyone believes it worked, including the person who did it, and nothing looks wrong until it does.
What it costs before anyone notices
Two versions running guests get different answers on different nights
The fix stops working the original problem quietly comes back
The next change lands worse people now doubt whether changes stick
⚠️ The third cost is cumulative. Every change that failed silently makes the next one less believable, and after four or five of them announcements stop working entirely.
Two lines, at the end of the change
Who has to do something differently, by name
How you will know, within a week
⚠️ The second line is the whole thing. Without it, a change has no moment at which it is either done or not — so it is never either.
What "how you will know" looks like
Not "I will ask them" but "on Friday I will look at X and expect Y"
⇒ ⚠️ If you cannot name what you will look at, the change is not specific enough to have been made.
Where the gaps live
People who were off a week's absence hides most announcements
The second shift things said at handover reach one person
Anyone hired after a change made before they arrived is invisible to them
⚠️ The third is permanent and grows. Six months of new staff have never heard any of the changes that predate them, and nobody thinks to tell them because it is no longer news.
When you find one that never landed
Re-announce it decays again, faster this time
Ask why not you get an answer worth having
⚠️ Half the time the old way was better for a reason nobody told you. ⇒ Ask before you repeat yourself. The person who quietly kept doing it the old way often knows something the change did not account for.
Three to hold
Changes taken verbally with no written trace. ⚠️ Ask; do not estimate.
Incidents of "I told you" per month. Uncomfortable to count and the clearest measure there is.
Whether every change route ends in a confirmation. List the routes. There are more than expected, and at least one will end nowhere.
Where the record has to sit
A change is only real when it is on the record the next person will open. If it lives in a message, a note, or a memory, it exists for one person and disappears with them — while the guest goes on believing it was done.
tasteck keeps changes on the booking and guest records staff open during service, so what was agreed is where the work happens.
They are not misremembering. They did something, it looked like it worked, and nothing in your operation was ever going to tell either of you otherwise.
Read next
Related articles
Who Types The Request In
A guest asks for somebody by name. Between that sentence and the figure on your monthly sheet, three or four people handle it. Every one of them is a place where it can quietly vanish.
What One More Regular Is Worth
Venues in this trade know what a quiet Tuesday costs them. Far fewer can say what one additional regular is worth over a year — which is the only number that tells you what you can sensibly pay to find one.
What a Listing Is Worth To One Room
A single-room salon and a twelve-room clinic get the same price from the same portal. Only one of them can work out whether that price is defensible, and it is the small one — because the arithmetic is smaller.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days