The Change They Think They Made

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.

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.