Who runs the account when staff turn over

Most restaurant social accounts were set up by an enthusiastic member of staff who has since left. The password went with them, the tone went with them, and the account has been dormant since.

This is a hospitality problem more than a marketing one. Turnover is high, the person with the eye for it is rarely the owner, and nothing about the setup survives their notice period.

Ownership has to sit with the business

The account must be owned by the restaurant, with staff granted access rather than holding it. On most platforms that means a business account with roles, not a personal login shared around.

This sounds bureaucratic until the day someone leaves badly and you discover the recovery email is their personal address.

  • Business email for the account, never a personal one.
  • Two-factor tied to a device or number the business controls.
  • At least two people with admin, one of them an owner or manager.
  • A written note of what exists: every platform, every listing, every review site.
  • Access removed the day someone leaves, as part of the same routine as returning keys.

Voice should belong to the restaurant

When the account is one person's personality, it dies with them and the replacement sounds like an impostor. When it is the restaurant's voice, a new person can pick it up in a week.

Writing down a handful of rules, what you sound like, what you never do, which jokes are yours, turns a personality into something transferable.

Do not make posting a favour

Content produced by whoever feels like it produces exactly the pattern most restaurants have: bursts followed by silence. Turnover then converts a burst into a permanent stop.

It works better as a defined shift task with a defined moment, in the same way opening checks are.

Keep the archive

Photographs taken on a departed employee's phone are gone. A shared folder that images land in as they are taken means the restaurant keeps its own library.

That library is also what lets a new starter publish immediately instead of waiting until they have shot enough material to begin.

Scheduling is the real continuity

A queue that is filled a fortnight ahead keeps publishing through a resignation, a bad month or a closed kitchen.

It converts turnover from an outage into a handover, which is the difference between an account that has run for five years and one that has restarted four times.

In short

Own the account at business level, write the voice down so it transfers, and keep a queue that survives someone's notice period.

Noian writes, schedules and publishes this kind of content for restaurants, with every post held for your approval first.

See how it works for restaurants

More for restaurants

Food content that survives a phone camera
Practical shooting and content rules for restaurants with no photographer, no studio and no time during service.
Handling reviews in public without making it worse
A practical approach to public review responses for restaurants, and why the reply is written for everyone except the reviewer.
Specials, menu changes and the daily post problem
Restaurants have genuinely new inventory every day and still run out of things to post. A system for turning the menu into a calendar.