Why food and beverage staff leave and how to understand why
Kitchen, service and outlet staff leave quickly in food and beverage. How to ask what lies behind the first answer, compare outlets and act on what you learn.
7 min readRead articleA corporate caterer feeds offices, tech parks and company events on a contract. Cooks, servers and counter staff are judged by the client's employees every day, so presence, manners and consistency decide renewals.

Make this work for your business. Share your team size, priorities and what you need help with. We’ll use your brief to prepare for the first conversation.
Share your requirementsA corporate caterer holds contracts with offices, campuses and tech parks. The work has two sides. One is the daily cafeteria or pantry service, with a fixed team on site, a menu cycle, a rate per meal or per head and a client contact who reviews it. The other is event catering for meetings, launches and festive lunches, which needs extra hands at short notice. Staff work among the client's own employees, who notice a late counter, an untidy apron or a rude word. A site manager or supervisor may run two or three sites. A change in the client's headcount or a new facilities manager can alter the staffing in a week. The wider food and beverage hub covers what food businesses share.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
Why GullyHR for corporate caterers
For owners of contract catering teams on office and campus sites. Each site gets a written brief, a float team and a scorecard, so standards hold across the cafeteria, the pantry and event days.
A one-page brief names the client contact, service timings, menu cycle, dress standard and escalation steps, so a new counter server knows the site before the first lunch rush.
A set limit on sites per supervisor, with visits that cover early set-up and the lunch rush, replaces the drift that follows the days nobody senior is present.
A few trained people rotate across sites and cover launch lunches, so the daily counter is not stripped bare whenever an event is booked.
A short routine on greeting, queue control and handling a complaint gives servers and cashiers a shared way to face the client's own employees every day.
Start with any one of these. Scope and fee are agreed in writing after a free first conversation.
The audit starts at the busiest site, in the hour before lunch service. We read the site brief, the duty rota, the attendance register and the log of client feedback, then compare them with what the cook and the counter servers say they actually do. Next come the supervisor's visit records across sites, the event crew lists and the way past headcount changes from the client were handled. Stores and purchase staff are asked how wastage is noted. The result is a plain account of where service rests on one person's memory.
What you receive
An example, not a client storyPicture a facilities head who mentions, in passing, that the evening tea counter has been late twice this month. The owner suspects the supervisor, who covers three sites, but the audit shows the pantry attendant never received a written brief. The first fix is a one-page site brief and a visit day that falls on the early shift.
How the hr audit works →Process design begins with the paperwork a new cook or server meets on day one: the site brief, the dress standard and the escalation steps when a client raises a complaint. Then the resizing routine is written, covering who is told, which people stay because they know the site and how notice is handled. Event staffing follows, with the float team's call-out order and a rule on which regular counters never lose cover. Each process is tried at one site before it travels to the others.
What you receive
An example, not a client storySay a client announces that a floor of its office is moving out next month, and the pantry needs fewer attendants. Without a routine, the site manager guesses who goes and loses the tea attendant the office staff love. With one, the choice follows a written order that the owner's own adviser has confirmed.
How the hr process design works →Week to week, the work follows the contract calendar. Monday brings the attendance and leave review for every site and the float team's allocation for the days ahead. Midweek, we check that supervisor visits are happening on the early and lunch shifts, and we log client comments against the person concerned. Before each event, we confirm who leaves the daily counter and who covers it. Site managers get one place to take rota changes, absence cases and awkward talks with a cook or a server.
What you receive
An example, not a client storySuppose a launch lunch is booked at a client campus on the same day two cooks are on leave at another site. The manager is tempted to pull servers from the regular counter. Instead the float team goes to the event, the leave is moved against the rota, and the daily counters at both sites stay staffed.
How the hr management works →The roles hardest to fill are the site manager who can hold a client relationship and the cook who stays at one contract site for years. We write a role page for each, then shortlist applicants against the same questions. A practical step is added: a mock queue for counter staff, a menu cycle review for the dietitian, a rota exercise for the manager. Candidates meet the existing site team where possible. Offers are for permanent roles only, and the owner's own adviser confirms the engagement terms.
What you receive
An example, not a client storyTake a site manager who resigns just before a client's annual review. The owner has no written profile of what the role needs. A role page is drafted from the best manager's real week, every candidate faces the same rota exercise, and the facilities head is told the successor's start date before the review.
How the recruitment for permanent roles works →Training is built around the counter and the pantry, not the classroom. Site managers practise supervising several sites, giving feedback to a cook and recording a client complaint properly. Counter servers, cashiers and token staff rehearse greeting, queue control and what to say when a dish runs out. Pantry attendants learn tidy service in front of the client's own employees. Event crews get a short briefing before each launch lunch. Each session ends with a check and a record against the person, repeated whenever a new site opens.
What you receive
An example, not a client storyPicture a cashier who is blamed for a long queue at the token counter every day at midday. Watching the hour shows the real fault: the tea counter and the token counter share one helper. A short queue-control session, a revised station plan and a set phrase to use at the counter give the team a shared routine.
How the manager and team training works →The handbook for a corporate caterer has to work for a person who sits far from head office. It sets out attendance and shift rules, dress and hygiene standards, conduct towards the client's staff and a grievance route that does not run through the same supervisor. We then set up HR software so site rosters, leave, training records and signed documents sit together, and each site manager sees only their own team. The owner's own adviser confirms any rule that is tied to the client contract or to local employment practice.
What you receive
An example, not a client storySay a server at a client site feels unseen by the company and mentions a worry to the client's facilities head, not to the caterer. A written grievance route that bypasses the site supervisor gives that server a direct, private way to reach head office, and the owner hears of the issue before the client does.
How the policies, handbook and hr software works →We would first map the visits each site actually receives, then write a visit pattern that covers early set-up and the lunch rush. Weekly attendance and client feedback reviews move to us, so the supervisor spends time at counters. If you want us to run that cycle, it is fractional management, not a new hire.
We would write a resizing routine: who the client contacts, how the site manager is told, which people stay because they know the site and how others move to the float team or another contract. Notice and pay questions go to your own adviser to confirm. The aim is a planned week, not a scramble.
We recruit permanent site managers. We write a role page from your best manager's real week, use one question set for every candidate, then add a rota exercise and a short client scenario. Candidates meet the existing site team where possible. We do not supply temporary or contract staff, and your own adviser confirms the engagement terms.
We would set a regular check-in with each site team, write a grievance route that bypasses the site supervisor and add recognition to the monthly scorecard. A long-serving cook is asked directly what would keep them. We cannot promise who stays, but the routine gives site staff a visible and regular link to head office and to the owner.
GullyHR runs talent acquisition for permanent roles in corporate caterers. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
A counter person's manner, a cold dish or a slow queue is noticed by hundreds of people, and complaints travel quickly to the facilities head.
A supervisor covers sites across a city, so standards drift on the days they are absent and the cook becomes the only authority.
A client cuts or adds employees on site and the caterer must resize the team within days, without losing the people who know the site.
Cooks and servers working at someone else's premises can feel unseen by their own employer, and leave for a closer, steadier job.
The same ten dishes in a four week cycle bore both the cooks and the diners, and the energy at the counter falls.
A launch lunch pulls people from the regular counter, and both the daily service and the event suffer if nobody plans it.
Start with the topics that matter most here: Onboarding and Probation; Performance Management; Employee Engagement and Experience. Then work through the rest. Each topic is written for food and beverage, not in general.
A first day that is the same for the fifth joiner as the first.
Goals, reviews and ratings that hold up in a conversation.
Communication, recognition and the conditions people actually work in.
How many people, in which roles, by when, and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Training planned from need rather than from the calendar.
Named backups for the roles that cannot be vacant.
Two routes, one for complaints, one for conduct, kept separate.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Who leaves, when, why, and which of them mattered.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a corporate caterers business puts in place, in an order that makes each easier. Open any card for the detail.
A page naming the client contact, service timings, menu cycle, dress standard and escalation steps, handed to every new person on arrival.
A page naming the client contact, service timings, menu cycle, dress standard and escalation steps, handed to every new person on arrival. See the employee onboarding process.
A limit on sites per supervisor, with visits that include early mornings and the lunch rush.
A limit on sites per supervisor, with visits that include early mornings and the lunch rush.
A short routine on greeting, handling a complaint and queue control.
A short routine on greeting, handling a complaint and queue control. The customer-service skills training suits this.
A few trained people who rotate across sites, so events do not strip the daily counter.
A few trained people who rotate across sites, so events do not strip the daily counter. Use the attendance and leave process to plan them.
Client feedback, wastage, absence and complaints on one sheet, reviewed monthly.
Client feedback, wastage, absence and complaints on one sheet, reviewed monthly. Performance management can supply the format.
Confirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
A site brief and first week plan for cooks and servers joining a client premises.
Float teams, early shifts and cover so no counter opens short.
Counter manners, queue handling and complaint calming for staff facing client employees.
A monthly site scorecard that clients and supervisors can both read.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in food and beverage, and one on each of the topics this page points to.

Kitchen, service and outlet staff leave quickly in food and beverage. How to ask what lies behind the first answer, compare outlets and act on what you learn.
7 min readRead article
A first-week plan for bringing in an outside specialist: what access to give, how to protect client data, and the confidentiality steps to settle on day one.
7 min readRead article
A practical design for an IT services appraisal cycle: when to run it, how to rate fairly across projects, and how to explain hikes so they hold.
7 min readRead article
Eighty per cent responded, the report was thorough, and six months later trust was lower than before. What went wrong between the survey and the silence.
8 min readRead articleMore on the GullyHR blog.
Visit regularly, recognise good work, give a clear path to supervisor and keep pay on time. People stay where someone notices them.
Use ten minute sessions before opening, on one habit at a time. Pair a new person with a steady one for the first week.
Keep a float team, move the most flexible people first and tell the affected staff early. Honest notice protects trust.
It depends on size and distance. Test it by asking when each site was last seen at lunch. If some are not seen for weeks, the span is too wide.
Not entirely. A float team protects the daily counter. Pay extra for event hours so the regular staff see a benefit.
First we would visit one site at lunch, ask the manager what the client complains about and count sites per supervisor. A site brief and a counter manners routine are a natural first piece of work, with scope agreed in writing.
All 6 business types in catering & institutional food services · Find another business type
See all HR topics for food and beverage, or another industry.
Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.