AdvertorialIndependent hospitality editorial · United Kingdom
Inside the restaurant An interview

THE MOMENT EVERYTHING CHANGED

This answer changed the course of the interview.

This restaurant owner explains why he stopped preparing his team’s rotas on his own

Dramatised advertising interview. The character and establishment shown are fictional

Fictional restaurant owner being interviewed at a table with an amended paper rotaTHE INTERVIEW / LONDON
One interview, one paper rota, and a candid answer about a difficult service.
FIELD NOTE / SHIFT PLANNINGSCROLL TO READ ↘
THE STORY01 / THE QUESTION

A simple question prompted an unexpected answer

“When did the rota stop working for you?”

At first, the question sounded routine. The interviewer was asking about the practical side of running a busy restaurant: how the owner organised the team, dealt with absences and kept the evening service moving.

Across the table sat Simon, the fictional owner of a neighbourhood restaurant. Next to his glass of water was a weekly rota, folded at the corners and covered with arrows, crossed-out names and amendments in different pens. He had brought it as an example of how he used to organise staff.

There was a pause before his answer. Not because the question was difficult, but because the paper made the answer impossible to dress up.

INTERVIEWERTHE QUESTION

“What actually went wrong on the evening you decided to change the way you planned shifts?”

Simon looked at the rota and ran a finger along one of the handwritten changes.

SIMON / RESTAURANT OWNERTHE ANSWER

“We had the people in the messages. We just didn't have them on the rota.”

It was not an admission about a complicated technical problem. It was about something ordinary: changes had been agreed in conversations, but the piece of paper treated as the official schedule never caught up. In the course of the interview, he explained why he later moved his team’s working rota to Deputy rather than continuing to reconcile handwritten revisions.

No one expected this admission about how he organised his team

A Friday service. A rota that told the wrong story.

The restaurant was preparing for its busiest part of the evening. A table booking had been moved, the kitchen had started its preparation, and the floor manager was working from the rota pinned in the back office.

During the week, one team member had said they could no longer work their original shift. A colleague was willing to change places. Another absence had been mentioned in a separate chat. Simon believed the arrangements had been made because he remembered the exchanges.

But the working rota had not been updated. The manager opened service expecting a fuller team than the one actually due to arrive. By the time the discrepancy was noticed, the restaurant was already handling guests with fewer people on the floor than planned.

Nothing here depended on someone being careless or unhelpful. The problem was that the messages and the published plan had become different versions of the same evening.

Busy evening service in a small British restaurant, shown as a dramatised scene
THE EVENING SERVICE / A DRAMATISED SCENE

THE ADMISSION

“I was the only person who knew which version was supposed to be right.”

What unsettled Simon was not that someone had asked to swap a shift. Changes were inevitable in a restaurant. What troubled him was the process: a message was treated as confirmation, a note on paper was treated as a record, and everyone assumed the other had been updated.

When the interviewer asked why he continued making the rota himself, he admitted that his system relied far too heavily on him remembering each conversation. Even when he thought he had communicated an amendment, it was not necessarily visible in the schedule the rest of the team used.

That evening became the point at which he decided to stop using the paper sheet as the place where every change had to be reconciled manually.

THE DECISION

One place for the rota. One clear route for changes.

Simon’s first decision was not to reorganise the restaurant. It was to change how shifts were recorded and shared.

He began looking at digital staff scheduling rather than sending another photograph of a handwritten rota. He wanted to build the working week in a shared system, make a change when circumstances changed, and let the team see the schedule without having to find the right message in a conversation.

In this dramatised account, the service he chose was Deputy. Deputy offers scheduling tools for hospitality businesses, including creating rotas, publishing them to employees, handling availability and supporting shift swaps under configurable rules. The choice did not remove his responsibility to check staffing levels, manage approval decisions or talk to employees about unexpected situations.

It changed what the schedule was: no longer just a paper copy awaiting handwritten corrections, but a shared rota which could be updated and republished.

A DIFFERENT WAY TO PLAN

The next rota, without the scribbles.

These are examples of the kinds of scheduling tasks Deputy supports, not a depiction of a particular customer's outcome.

01 / CREATE

Build the working week

A manager can arrange shifts for the people and areas of a hospitality team, taking availability into account while preparing the rota.

SHIFT PLANNING↗
02 / CHANGE

Revisit a change where it belongs

When a shift needs attention, the schedule can be adjusted. Eligible employees can use shift-swapping tools, subject to the settings and approval arrangements in use.

SWAPS & APPROVALS↗
03 / PUBLISH

Put the updated rota in view

Managers can publish rotas to employees via web or app, giving team members a way to check what has been scheduled for them.

TEAM VISIBILITY↗
Dramatised restaurant manager reviewing a work rota on a laptop
FROM THE BACK OFFICE / DIGITAL ROTAS AND DAY-TO-DAY SERVICE
THE IMPORTANT DISTINCTION

The software is a tool. The judgement stays human.

A digital rota is not a substitute for a manager knowing who has the skills to cover a station, understanding a colleague's circumstances, or making a call when service changes at short notice. Shift swaps may require eligibility checks or approval, depending on settings. A published rota still needs to be reviewed and communicated thoughtfully.

Deputy provides features intended to support the scheduling process. It does not make staffing difficulties disappear, guarantee every shift can be covered, or remove an employer's obligations under employment law. Which features are appropriate for a business depends on its requirements and the settings it chooses.

PRODUCT IN FOCUS / INDEPENDENT PROVIDER

The tool behind the change.

Deputy is a separate company and software provider. The Service Ledger is an independently operated editorial publication and is not the provider of Deputy's platform.

THIRD-PARTY SOFTWAREHOSPITALITY / ROTAS

Deputy.

Workforce scheduling tools for hospitality teams

Discover Deputy ↗You will be taken to the official Deputy website, operated by a separate provider.

WHAT THE PRODUCT OFFERS

↗

Staff rotas

Create, edit and publish staff schedules for restaurant and hospitality teams.

↗

Availability and leave

Allow staff to set availability and request leave for managers to review.

↗

Shift swaps

Support requests to swap eligible shifts, with configuration and approval controls.

Features, eligibility, availability and terms are determined by Deputy. Consult the provider's official website for current product details.

THE FINAL ANSWER

The rota should not live in someone's memory.

At the end of the interview, Simon folded his marked-up paper and moved it aside. The useful lesson from the fictional evening was not that every problem could be solved by a platform. It was that agreements about shifts need to reach the schedule everyone actually uses.

For hospitality owners interested in that approach, Deputy's own website explains how its scheduling tools work and what is currently available.

Discover Deputy on its official website ↗

External link: opens Deputy's official website. Deputy is an independent third-party provider.