When Someone Stops Being Requested
A falling request rate is visible months before anyone mentions it, and the conversation almost always happens too late. What the decline usually means, and how to raise it without making it worse.
Six months ago they were requested four times a week. Now it is once.
Nobody has said anything. They have noticed, obviously — the schedule is the same and the earnings are not. And by the time management raises it, the person has usually already drawn their own conclusion, which is frequently the wrong one.
What a decline usually is not
The instinct is to read it as performance. Sometimes it is. Frequently it is one of these instead:
A shift change. Moved from Friday to Tuesday, and their regulars come on Fridays. The decline is arithmetic, not ability, and it is the most common cause by a distance.
A regular who left. Two or three departing guests can halve a request count on their own. Look at who stopped coming before you look at the person.
Availability that quietly narrowed. Fewer shifts submitted, or narrower windows, means fewer chances to be requested. The rate may be unchanged while the count falls.
Somebody new. A new arrival absorbs the guests who were undecided. That is not a loss of standing — it is a redistribution, and it usually settles.
⚠️ All four are visible in the record and none of them requires a difficult conversation. Ruling them out first is not avoidance; it is the only way to know what you are actually looking at.
The one number that separates them
Requests per shift worked, not requests per week.
The count falls when the person works less. The rate falls when something changed about the demand. They are different problems and the weekly count cannot tell them apart — which is why a decline in the count so often gets attributed to the wrong thing.
If the rate is steady and the count is down, the answer is in the schedule, and the conversation is a scheduling one.
When it is real
Sometimes the rate really has fallen and none of the four explains it.
Even then, the causes are usually specific and fixable: a change in how they are presented, photographs that no longer match, an approach that worked with one type of guest and not the current crowd.
A specific observation is actionable. "Your numbers are down" is not — it tells the person something they already know and gives them nothing to do with it.
How to raise it
Three things that make the conversation work.
Early, while the numbers are still good enough to be non-threatening. A conversation at a twenty percent decline is coaching. The same conversation at seventy percent is a warning, whatever words are used.
With the four alternatives already ruled out. Arriving with "I checked the schedule and your regulars, and it isn't those" shows the person they were looked at fairly. That single sentence changes how the rest lands.
With one specific thing to try. Not an assessment — an experiment. One shift moved, one photo updated, one different section.
⚠️ What you must not do is nothing. Silence is read as a verdict, and the person will act on that reading before anyone has spoken to them.
The part that is management's
If several people show the same decline in the same period, it is not several people.
It is the crowd changing, or the schedule, or the marketing. The individual conversation is the wrong instrument for a venue-level shift, and having it three times causes three people to lose confidence over something none of them caused.
The check: is the total request count across everyone flat while individuals fall, or is the total falling too? Those point at completely different things.
Three to hold
Requests per shift worked, per person, rolling. The rate, not the count.
Total requests across everyone. Distinguishes an individual issue from a venue one.
Requests traced to guests who have since stopped coming. Explains a large share of individual declines on its own.
Where the record has to sit
Requests are in the booking, shifts are in the rota, and guest history is a third thing. Until they are joined, a falling count has no explanation and gets attributed to the person by default.
tasteck keeps requests, shifts, and guest history on one record, so is this the schedule, the guests, or the person is answerable before anyone has to have the conversation.
They noticed months ago. The only question is whether you arrive with an explanation or with a verdict.
Related articles
Your Pour Cost Is a Schedule Problem
Most venues chase pour cost with tighter counts and better jiggers. The variance usually tracks who was behind the bar, not what they were pouring. How to read pour cost by shift, and why the fix is often on the roster.
Your Coat Check Is a Queue Problem
In cold markets the coat check decides how your night starts and how it ends. What the queue costs in unbought first drinks and in clearance time at close, and the three changes that move it without new staff.
Your Best Night Was Not Your Best Night
The night with the highest take is rarely the night that earned the most. What has to be subtracted before a night can be ranked, and why the answer usually reorders the whole week.
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