Personal PR for hospitality managers
How to make sure you're represented accurately when you're not in the room — by colleagues, by senior managers, and by the customers whose events you've worked.
A free practical guide from AO Hospitality
Why this matters. Your reputation in any organisation is partly built by you and partly built by people talking about you when you're not there. You can't stop the conversations. You can give them better material. The same applies to your customers — brides, corporate organisers, repeat guests, function hosts — who form their own narrative about you in the days and weeks after the event, based on what they remember and who they speak to.
Most managers either ignore narrative entirely and lose ground they didn't know they were losing, or overcorrect into office politics and lose the operational focus that made them good in the first place. The right answer is neither. It's quiet, deliberate discipline. Five minutes here, ten minutes there, that protect you over years.
This is the practical version. What to actually do.
Daily habits (five minutes a day, max)
End-of-shift one-liner to yourself. Last thing before you log out, send yourself an email summarising the shift. "Saturday 8/3. Wedding of 200, dance finished midnight, two minor noise complaints handled in person, one near-miss in the kitchen (broken glass), no guest injuries. Bar takings on track. Two staff late, both spoken to." Three sentences. Personal email. Takes 90 seconds. You will be glad of this email exactly once in your career and it will save you when you are.
Photograph the duty manager log. At the end of every shift, take a phone photo of your log page. The log is your defence and the log can be edited, lost, or "misplaced". A photo timestamp can't.
Date everything that might matter later. Every notebook entry, every email, every Slack message that matters — put the date and shift at the top. "Tues 11/3, late shift." It feels excessive when you do it. It feels essential when someone asks you about a specific date six months later.
Getting to people first — internal
Tell your boss the news before they hear it elsewhere. The single biggest narrative loss happens when your manager hears about an incident from someone else first. By the time they get to you, they've already formed an impression — usually unfavourable, because the person who got there first had a reason for getting there first.
If something material has happened on your shift, your manager knows about it from you, in writing, before they walk in. Even a one-line text the night before is enough. "Heads up — we had an incident in the bar at 11pm, full report on your desk in the morning, no immediate action needed but you should know." The text takes 30 seconds. The narrative protection lasts months.
Send the full write-up the same shift. Not the next day. Adrenaline fades. Detail fades. Write it before you go home. If you're too tired, write the bare facts and timeline, then fill in the detail in the morning when you're sharper. But get the timeline down before sleep.
Copy a second person. If the incident is significant, the write-up goes to your line manager and one other person — head office, group H&S, a senior peer. Two copies in two inboxes means the record can't be quietly lost. The redundancy is the answer to a question you don't get to ask in advance.
Keep the original. Whatever you submit, keep a copy on your personal email. Not work email. Personal. Work emails belong to the company; personal emails belong to you.
Getting to people first — customers
The customer side of narrative is the one most managers ignore entirely. They think the event ended when the guests left. It didn't. The customer's story about that event is still being written for days afterwards — to their family, their friends, their colleagues, future suppliers, online review sites. You can shape it or you can let it shape itself.
Call the bride or organiser the next morning. Even if nothing went wrong. Especially if nothing went wrong. "Just wanted to say thank you for trusting us with yesterday — the team really enjoyed it, everything looked beautiful, hope you're getting some rest now." Two minutes. It builds the relationship for the next time, and it gives them a positive framing while the memory is still being consolidated.
Call same-day if anything went wrong. A noise complaint, a delayed course, a small mishap, a moment of friction. Don't wait for them to call you. Call them. "I wanted to reach out about [thing] last night before you started your day today. Here's what happened from my side, here's what we've done about it, and I wanted you to hear it from me first." This is the same principle as telling your boss before they hear it elsewhere — applied to customers.
Apologise for the experience without admitting fault. Important distinction. "I'm sorry your evening had that moment in it" is different from "I'm sorry we failed you." The first acknowledges their experience. The second is an admission that can be used against you, the venue, or your insurance. Senior managers don't always know this distinction; teach yourself to make it.
Follow up the follow-up. A week after the event, send a short message — "Hope you've had time to settle back into normal life. Wanted to say once more, thank you for choosing us. If you ever want to come back for an anniversary, you know where we are." Almost nobody does this. The customers who receive these messages remember them for years.
For weddings specifically. Brides and grooms talk to their families for weeks afterwards. The version they tell their parents and in-laws sets the narrative permanently. Your one phone call the morning after, asking how they slept and wishing them well on their honeymoon, becomes part of that family story. It's the single highest-leverage 90 seconds you can spend on customer relations.
For corporate clients. The event organiser is the person you should be calling the next morning, not the most senior delegate. The organiser is the one who'll be back next year with the booking, the one whose reputation is on the line internally, and the one who'll either recommend you or quietly use someone else. They are the customer, not the company that hired them.
For function hosts who had an incident on their day. A handwritten note within the week is unusually powerful here. "I've thought about you all week. I know yesterday didn't go the way either of us hoped. I want you to know we've already changed two things in how we handle that kind of moment — your day taught us something and we're better for it." That note costs you a stamp and twenty minutes. It's also the difference between a one-star review and a five-star one.
When you've been overruled on a decision you think is wrong
Send the "to confirm" email. Within 24 hours of the conversation, send a brief email: "To confirm what we discussed — the decision is to proceed with X. As I mentioned, my concern was Y. I'll support the decision and let you know if I see Z develop." This is not insubordination. It is documenting that you raised the concern. The senior person who overruled you will either acknowledge it, ignore it, or push back — and any of those three is now part of the record.
Don't send it as a complaint. The "to confirm" email is short, neutral, and supportive of the decision being made. "I'll support the decision." Those four words are the difference between protective documentation and a paper trail of insubordination.
Note what they said back. Whatever response you get — verbal, written, none at all — note it the same day. Date, what was said, who else was present. Your future self will need this and your present self is the only one who can record it.
When you've made a difficult call
(Refusing a guest, ending a contract, intervening on a colleague, closing the bar earlier than expected.)
Write up the reasoning at the time. Not just what you did, but why. The decision will be questioned later and "I felt at the time that..." reads weaker than a contemporaneous note that says exactly what you were thinking. Three sentences is enough. "Refused service to Mr X at 11.45pm. Visibly intoxicated, slurring, had been served four doubles in the previous hour by bar staff before I intervened. Decision under Licensing Act 2003 s.141."
Don't apologise in writing. Anywhere. Ever. Apologising for a correct decision converts it into a wrong decision you felt bad about. "I had to refuse service" is correct. "Sorry I had to refuse service" is the start of a case against you.
Don't editorialise. Stick to what happened. Not how you felt about it, not your view of the guest's behaviour, not commentary on whether the bar staff should have spotted it earlier. The record is for facts. Opinions can be misquoted; facts can't.
Building relationships before you need them — internal
Identify your two senior allies. Across any organisation, there will be one or two senior people who get it — who understand operations, who back competent decisions, who tell the truth in meetings. Find them within your first three months. Have coffee with them quarterly. Not networking. Not politics. Just being known to the people who'll one day be in a room talking about you.
Send a thank-you note to people who back you. Brief, sincere, in writing. After a difficult shift where a colleague had your back. After a senior person made a call that supported you. Two sentences. It costs you nothing and people remember the ones who say thank you in writing — most don't bother. It also creates a quiet record of the relationships that work in the building.
Brief your trusted colleagues on significant decisions. Not the whole company. Just enough that when your decisions get discussed in your absence, there's someone in the room who can say "actually, what happened was...". This isn't politics. It's making sure the version of you being discussed is at least roughly accurate.
Building relationships before you need them — external
Two references outside your current company at all times. People who'd vouch for you who don't work where you work. A former boss, a supplier you've dealt with for years, an industry contact, a long-term customer. Buy them coffee twice a year. The day you need a reference urgently is not the day you want to be reconnecting with someone you haven't spoken to in four years.
Speak well of competitors and former employers. Always. In every room. The hospitality industry is small and the person you slag off this year is your future GM, your future supplier, or your future reference. Speaking well of people you have legitimate criticism of is also a quiet flex — it shows you're senior enough not to need to score points.
Be findable on LinkedIn. Most hospitality managers don't bother. Three lines about your current role, a clear photo, your career history accurate. That's it. The point isn't self-promotion — it's making sure that if someone googles you in connection with an incident, the first result is your version of who you are, not a TripAdvisor review or a tagged photo from a Christmas do.
Keep a quiet list of customers you genuinely helped. Names, what their event was, what you did, when. Half a dozen names is plenty. These are the people you can ask for a review, a recommendation, a testimonial when you need one — and the relationship is real because you actually looked after them. The list is for you to remember them, not for showing anyone.
In meetings about decisions you weren't part of
Ask, don't defend. If a decision you made comes up and the framing is wrong, don't launch into defending yourself. Ask a clarifying question. "What's the source on that — I want to make sure I'm understanding what's being said about the incident." This slows the narrative drift, and it forces whoever's misrepresenting the situation to either back up their claim or correct it themselves.
Offer to share the write-up. "I have the full incident report from that night. Happy to forward it to everyone before we discuss further." Almost always, the framing softens immediately. People are willing to characterise an incident from rumour; they're less willing to do it once they know a primary document exists.
Take notes. Visibly. In every meeting where your decisions might be discussed. The act of taking notes changes how other people speak about you because they know there will be a record. It also gives you the source material for any follow-up you need to do.
When someone is briefing against you
Don't escalate, document. The instinct is to confront the briefer. Don't. Confronting them gives them ammunition ("X is being aggressive in the office") and makes you look paranoid. Instead, note specific things they've said and when, and to whom. If a pattern emerges, you'll have evidence. If it doesn't, you'll have peace of mind.
Find one person to tell honestly. A mentor, a senior peer, a friend in another company. Not to vent — to sense-check. "Here's what I think is happening. Am I reading it right or am I imagining it?" External perspective stops you either spiralling into paranoia or missing real signal.
Be impeccable in your work. Counterintuitive but true. When someone is briefing against you, the temptation is to fight that narrative. Don't. Just be unimpeachably good at the job. Bad-mouthing someone whose actual work is excellent becomes hard. Your work is your strongest defence.
Long-term maintenance
Update your CV every three months. Even if you have no intention of moving. The act of writing what you've achieved this quarter sharpens your sense of your own value. It also means that when an opportunity comes up — internal or external — you're ready in 20 minutes rather than two weeks.
Keep a written record of your wins. A simple document on your personal cloud — "Quarter 1 — recovered Smith wedding after kitchen fire, increased Sunday bookings 18%, retained chef X through job offer from competitor." Three or four bullet points per quarter. Two reasons: appraisal conversations go better when you have data, and when (not if) you start looking for your next role, your CV writes itself from this document.
Don't drink beyond moderation with the team. You don't have to be teetotal. You do have to be the person who's still composed at the end of the night when others aren't. The stories told about your composure are the ones that build the reputation you want. The stories told about your behaviour at the staff Christmas party are the ones that don't.
Don't fight every battle. Some narratives aren't worth correcting. Someone misremembering a Tuesday three years ago, a colleague who tells a slightly unflattering story at the staff drinks, an offhand comment in a meeting — these aren't fights you can win and trying to win them makes you look like the person who can't let things go. Save your narrative energy for the ones that matter: incidents that could affect your reputation seriously, decisions that could be relitigated in your next review, situations where the record is going to be tested.
A closing thought
None of this is about being a careerist. It's about making sure that the person being talked about when you're not in the room is, at least roughly, the person you actually are. Most operational managers in hospitality get this wrong by doing nothing at all — and then wonder why a five-year track record can be undone by one person with an agenda and a louder voice in the right meeting, or by a wedding customer whose family heard a different version of the day than what actually happened.
The work is small. Five minutes a day. Ten minutes after a significant shift. A two-minute phone call the morning after a wedding. A photograph of a log book. An email to yourself before bed. A quarterly coffee with two people. Done consistently, over a career, this is the difference between "I keep getting passed over and I don't know why" and "I keep being promoted and customers keep asking for me by name and I'm not sure how that keeps happening."
It's not magic. It's just doing the small invisible work that almost nobody does.
Created by AO Hospitality. This is a free tool designed to support your journey — not a substitute for professional advice. Please get your work validated by a professional in the field. Alun Pomfrett and AO Hospitality cannot be held liable for any loss or damages arising from use of this tool.