The Refund You Argue About

A guest is unhappy and wants something back. The person facing them has no rule to apply, so the answer depends on who is on, how busy it is, and how confident they feel.

That inconsistency costs more than any refund does.

What the absence of a rule produces

Different answers to the same situation. Two guests compare notes and one of them was treated worse. ⚠️ That comparison is where the real damage happens — not in the refund, in the difference.

Escalation as the default. Every case goes to a manager, including the ones that should take thirty seconds.

Decisions made under pressure. At the moment the guest is unhappy and the room is watching, which is the worst possible condition for judgement.

Nothing learned. Cases resolve individually and disappear. The pattern in them never surfaces.

The three lines worth drawing

Not a policy document. Three answers, decided in advance.

What the front line can resolve alone, up to what value. ⚠️ This is the one that matters most. A figure — any reasonable figure — lets most cases resolve at the table, immediately, which is also when resolution is cheapest and most effective.

What always escalates. Serious complaints, anything involving conduct, anything above the threshold. Clear, short list.

What is never refunded. Also short, also explicit. ⚠️ Staff need to know where the wall is, or they will either promise things you cannot honour or refuse things you would have granted.

The number nobody sets

The front-line threshold.

Most venues have not set one, which means it is effectively zero, which means everything escalates. ⚠️ Set it higher than feels comfortable. The cost of a manager's involvement, the delay, and the guest's experience of being passed along usually exceeds the amount in dispute.

A guest whose small complaint is resolved instantly by the person in front of them frequently ends up more loyal than one who never complained. A guest who waits twenty minutes for a manager to authorise the same amount does not.

Recording them

Not for control. For the pattern.

One line each: what happened, what was given, who decided. ⚠️ Three months of that shows the recurring causes — and the recurring causes are usually two or three things that are fixable at source.

Refunds are a symptom. The record is how you find the cause.

The one to watch for

The same issue appearing repeatedly.

A particular course, a particular timing, a particular expectation set at booking. ⚠️ When the same complaint arrives ten times, the refunds are not the problem — the thing generating them is, and it is usually cheaper to fix than to keep paying for.

Three to hold

Refunds by cause, monthly. The report that turns individual concessions into a fixable pattern.

Share resolved without escalation. ⚠️ Should be most of them. If it is not, your threshold is too low.

Repeat causes. The two or three that produce most of the total.

Where the record has to sit

A refund recorded only in the till is a number without a reason, and a reason written on a note behind the bar does not survive the week. The two have to be attached to the same booking, or the pattern cannot be assembled later.

tasteck keeps adjustments against the order they belong to, so a month of refunds can be read by cause rather than only by amount.

The argument is not really about the money. It is that nobody decided in advance, so it has to be decided in front of the guest.