Managing Change in Your UK Pub

Last updated: 12 April 2026

Most pub operators assume their staff will resist change because they’re afraid of it. That’s only half true. The real resistance comes from feeling blindsided — from not understanding why you’re changing something that already works. Managing change in a UK pub is not about forcing new processes onto people who’ve been doing things one way for five years. It’s about taking them with you, step by step, and proving the change solves a real problem they actually care about. This is how you execute change that sticks, rather than change that causes staff burnout and customer complaints within a fortnight.

Why Pubs Resist Change (And How to Fix It)

The most common reason staff resist change in pubs is they weren’t consulted before the decision was made. You announce on a Monday morning that you’re switching EPOS systems on Wednesday, and by Thursday evening you’ve got three staff members phoning in sick and customers complaining about 20-minute waits. That’s not resistance to change — that’s shock.

I’ve seen this play out dozens of times across wet-led pubs, food-led operations, and venues trying to add new revenue streams. The pattern is always the same. A landlord identifies a problem (slow till speeds, cash handling errors, stock discrepancies), finds a solution (new EPOS, new scheduling system, new supplier), and implements it without bringing the team into the conversation. The team then spends the next three weeks arguing the old way was better, because nobody explained to them why the old way wasn’t working in the first place.

Here’s what actually works: involve your team in the diagnosis phase, not just the implementation phase. If your bar staff are hitting the same terminal three times during Friday night service, they’ve already noticed. If your kitchen staff are constantly asking where items are because your storage system is chaotic, they know it’s a problem. Give them permission to articulate the pain before you announce the solution.

The Communication Plan Before Change

Before you change anything operational or technological, you need a communication sequence. Not a memo. Not a five-minute briefing before service. A proper plan:

• Week 1: One-to-one conversations with key staff members (head bartender, kitchen lead, senior server) explaining the problem and the proposed solution. Listen more than you talk. Ask for their concerns.
• Week 2: Team meeting where the change is announced, but framed as a solution to a problem they’ve identified or experienced. Show how the change improves their working day, not just your bottom line.
• Week 3: Begin practical training and soft rollout. Don’t go live with a new till system during your busiest service. Go live on a quiet Tuesday lunch.

The mistake most operators make is thinking staff will embrace change if it saves the business money or time. Staff don’t care about margin improvement or operational efficiency in the abstract. They care about whether the change makes their shift easier or harder, whether it makes them look bad in front of customers, and whether it means less take-home money (through tips, bonuses, or hours cut). Address those concerns directly.

Identify What Actually Needs to Change

Before you implement any change, you need absolute clarity on what problem you’re solving. Not vague problems like “we’re not efficient” or “staff morale is low.” Specific, measurable problems.

At Teal Farm Pub, Washington, Tyne & Wear, we manage 17 staff across front-of-house and kitchen, and we run quiz nights, sports events, and regular food service simultaneously. When we evaluated EPOS systems, the decision wasn’t based on feature lists or pricing tables. It was based on one specific problem: during peak Saturday nights with full house, card-only payments, kitchen tickets, and bar tabs running at the same time, our old till couldn’t handle it. Three staff hitting the same terminal meant queues, customer frustration, and lost sales. That wasn’t a ‘nice-to-have’ efficiency problem. It was directly costing us revenue.

Before you change something — whether it’s your till system, your stock management, your staff scheduling, or your ordering process — write down:

• What is the current problem, measured in specific terms? (slow till times, cash errors, staff confusion, customer complaints)
• How is this problem affecting revenue, staff experience, or customer satisfaction? (quantifiable impact)
• What is the cost of not fixing this problem over the next 12 months?
• Who experiences this problem most acutely — customers, staff, or you?

This clarity is crucial because when staff resist the change, you’ll need to refer back to this diagnosis. “We’re implementing a new stock system because we can’t currently account for why we’re short 40 bottles of Guinness every month, and that’s costing us £300 a week.” That’s specific. That’s defensible. That’s the kind of argument staff will accept, because they’ve probably witnessed the problem themselves.

Equally important: identify what is not changing. If you’re switching EPOS systems, be explicit that the way staff take orders, interact with customers, and clock in and out remains the same. The more continuity you can preserve, the less cognitive load the change creates.

Build Your Change Management Timeline

The biggest mistake pub operators make with change management is compressing the timeline. You find a new EPOS, sign a contract, and want to go live within two weeks. That always — and I mean always — results in chaos.

The minimum timeline for implementing substantial change in a pub is four weeks from announcement to full rollout. Here’s what that looks like in practice:

Week 1: Announcement and Diagnosis

Hold individual conversations with your senior staff. Explain the problem in detail. Show them data if you have it (till reports, stock counts, customer feedback). Ask for their input on the solution. Some will offer genuinely useful perspective. Some will push back, which gives you valuable information about where resistance will be strongest. Address concerns directly — don’t dismiss them.

Week 2: Training Preparation and Demo

Bring in the supplier or trainer for a demonstration. Invite your entire team. Let them see the new system working, ask questions, and get hands-on with it if possible. Don’t position this as a one-off training session. Position it as “familiarisation.” Training happens later.

This is also the week to run a pub staffing cost calculator if the change affects scheduling or working patterns. If you’re moving from manual rostering to a scheduling system, staff will want to know how this affects their flexibility, their hours, their notice of shifts. Address this now.

Week 3: Soft Launch and Intensive Training

Go live with the change on your quietest service. Don’t switch your EPOS on a Friday night. Don’t launch your new ordering system during a quiz night event. Choose a quiet Tuesday lunch or Wednesday afternoon. Your team will make mistakes. They’ll forget steps. They’ll need help. You want headspace for that learning to happen without the stress of a full room and a queue out the door.

Run hands-on training sessions during this week, multiple times. Not everyone learns the same way. Some staff need to watch a demo, then practice independently. Others need to practice while someone watches and corrects. Some need to read documentation. Some don’t read documentation at all — they just need to do it until it becomes muscle memory. Accommodate these different learning styles, or you’ll have staff members who are competent and staff members who are still flailing after two weeks.

Week 4: Full Rollout and Support

By week four, you go live at full service load. But you need contingency. Your head bartender might know the new system well, but when the lunch shift manager tries it for the first time on a busy Friday, they’ll find edge cases nobody anticipated. Build in extra support during this week. Can you bring in the trainer for two or three shifts? Can you stand behind the bar yourself during peak service to help troubleshoot? This is where you prevent the “new system is rubbish” narrative from taking hold.

The reason most change fails in pubs is that operators underestimate this support requirement. They think once training is done, the system runs itself. It doesn’t. It needs a champion — someone who knows the system well and is available to unblock problems quickly.

Train Your Staff Properly — Not Just Once

Most training in pubs happens in one session. You sit the team down for 90 minutes, go through the new process, answer questions, and assume they’re trained. Then wonder why they’re struggling to execute it properly three days later.

Effective training for operational or technology change in pubs follows the 70-20-10 model: 70% learning happens by doing, 20% happens through observation and feedback, 10% happens in formal training.

Your formal training session (the 10%) should cover:

• Why the change is necessary (the diagnosis from earlier)
• How the new process works, step by step
• How it’s different from the old process (explicitly compare)
• Common mistakes and how to avoid them
• Where to get help when something goes wrong

Keep it to 45 minutes maximum for groups. Attention spans in a noisy pub are short, and staff are often tired before the briefing even starts. If you need more than 45 minutes to explain something, break it into two sessions.

The learning by doing (70%) happens during the soft launch week and the first weeks of full rollout. Your job is to be present, notice when staff are struggling, and give immediate, specific feedback. “You forgot to close that screen” is feedback. “Try closing that screen before you move to the next customer — it saves a few seconds and keeps the next person from seeing sensitive data” is useful feedback that helps them understand why the process matters.

The observation and feedback piece (20%) happens through pub onboarding training protocols and ongoing shadowing. Don’t just train new staff on the old system as a workaround during transition. Train them on the new system, even if they’re starting mid-rollout. You’ll have temporary inefficiency, but you’re reinforcing the new way as the standard, not the exception.

One practical thing that works: pair each team member with a buddy who’s competent on the new system. During the first two weeks of the soft launch, the buddy sits with them during their first and last order of the shift. Just watches, answers questions, normalises the process. This costs you very little operationally and dramatically accelerates competence.

Managing Systems and Technology Change

Technology change is the most common catalyst for operational change in pubs. You’re switching EPOS systems, implementing a new scheduling tool, moving to cloud-based stock management, or integrating a payment system. These changes have unique challenges.

The Real Cost of Technology Change

When you budget for a new pub IT solutions implementation, you think about the monthly fee. That’s typically the smallest cost. The real cost is:

• Staff training time: Every staff member needs hands-on training. That’s hours away from revenue-generating work.
• Lost productivity during rollout: Your till times will be slower for the first two weeks. Your stock counts will take longer. Your ordering will be less efficient. You’ll lose revenue during this period.
• Management time troubleshooting: You’ll spend 5-10 hours per week answering questions, resetting passwords, and fixing configuration issues during the first month.
• Data migration and cleanup: Moving from one system to another always uncovers data problems. Your customer database has duplicates. Your product list has discontinued items. Your staff records are incomplete. Cleaning this up takes weeks.

If you’re moving to a new EPOS system, the financial impact during rollout can be significant. Budget for reduced productivity and slower service for at least three weeks. If you’re in a tied pub operating under a pubco agreement, check your terms before implementing any major system change. Some pubcos have restrictions on EPOS systems you can use, or require their systems to integrate with your new selection.

Compatibility and Integration

Before you select any new system, verify it integrates with your existing technology stack. If you’re using accounting software, the EPOS needs to feed sales data into it automatically, not create manual entry work. If you’re using a scheduling system, payroll needs to pull hours from it without double-entry. If you’re using pub management software, all these systems need to talk to each other.

Many operators choose a system based on feature lists and price, then discover it doesn’t integrate with their accounting software, their till can’t connect to their kitchen display system, or their payment processor isn’t compatible. This creates manual workarounds that negate the efficiency gains you were trying to achieve. Verify integration before you sign anything.

What Happens When the Internet Goes Down

Most modern EPOS systems are cloud-based, which is great for data security and accessibility. But pub operators worry: what happens when the internet drops? Can I still take payments and serve customers?

The answer depends on the system. Most modern EPOS platforms have offline mode — they cache recent transactions and sync when the connection is restored. Card payments still process. Till functions remain available. But you’re operating blind: you can’t see real-time stock levels, you can’t access customer accounts, you can’t see what your kitchen is preparing. And if the internet is down for more than a few hours, your ability to operate degrades significantly.

Before you go live with any cloud-based system, know how it performs offline and what your contingency is. Some operators keep their old manual till available as a backup. Some print off key information (current menu, customer records, staff phone numbers) at the start of each day. Some accept that a total internet failure will close the pub for the day and plan their insurance and reputation management accordingly.

Sustaining Change After the First Two Weeks

The critical window for change management in pubs is weeks three and four of the rollout. This is when initial enthusiasm fades, when staff have practised the new process enough to notice inefficiencies, when customers start asking “why has the menu changed” or “why does my bill look different.” This is when change either solidifies into the new normal or reverts back to the old way.

Monitor Adoption Without Micromanaging

After the soft launch, you need to monitor whether the team is actually using the new process. Not by standing over them or checking logs obsessively. You’ll kill morale. But by paying attention during service. Are they still reverting to the old process sometimes? Are they using the new system efficiently or working around it? Are they training new staff on the new way or the old way?

If you see reversion — staff switching back to old processes — intervene immediately. Not to criticise, but to understand why. Maybe the new system has a genuine usability problem. Maybe the old way is actually faster for edge cases they encounter regularly. Maybe staff haven’t had enough practice to build confidence. Find out which, and address the root cause, not the symptom.

Show Early Wins

Within three weeks of full rollout, you need to show your team that the change is working. This is where pub profit margin calculator tools and KPI dashboards matter. Can you show that till speeds have improved by 15 seconds on average? Can you show that cash discrepancies have dropped from £60 per week to £10? Can you show that the new system has reduced stock wastage by 5%?

Staff respond to evidence. If the new EPOS is genuinely faster, they’ll feel it after three weeks. If it’s saving money, show them the number and explain how it benefits them (better margins might mean staff bonuses, better staffing ratios, investment in the pub). If the change is purely abstract (“this helps us scale better” or “this is more professional”), they’ll never truly buy in.

Build the Change Into Your Standard Operating Procedures

Once the new system or process is operational, it needs to become standard. Update your staff manual. Update your front of house job description to reflect the new process. Make sure that when you hire new staff, you train them on the new system, not the old one. If you continue training new hires on the old process as a “simpler introduction,” you’ve created two parallel systems that will confuse everyone.

Plan for Continuous Improvement, Not Perfection

The new EPOS system will have quirks. The scheduling software will have edge cases that don’t work for your pub. The stock management system will require manual overrides sometimes. This is normal, not a failure. Build in a monthly review where staff can flag things that aren’t working. Some of these problems are user error — staff not following the process correctly. Some are genuine system limitations that require workarounds. Some require a settings change that the supplier can make.

The worst thing you can do is implement a new system and then ignore feedback for six months. That signals to staff that you don’t care about their experience, and they’ll stop bothering to suggest improvements. Monthly check-ins show you’re listening and you’re willing to adapt the process based on their input.

Addressing Common Change Management Objections

“My Current Till Works Fine, Why Change It?”

If your current till genuinely works fine during your busiest service period, and you’re not losing sales or making errors because of it, then you don’t have a problem that needs solving. But most operators asking this question are experiencing some version of the problem — slow till times, payment failures, staff confusion. The “it works fine” narrative is usually resistance to the unknown, not an accurate assessment of performance. Test your current system during peak service specifically. Are you hitting any limits? Are customers complaining about waits? Are staff making shortcuts to speed things up? If the answer is yes to any of these, you have a problem.

EPOS Systems Are Too Expensive for a Small Pub

The monthly EPOS cost for a small wet-led pub is typically £50-150 depending on transaction volume. That’s not the main expense. The main expense is staff training time and the productivity loss during rollout. If you operate a small pub with 4-5 staff, you’re looking at 15-20 hours of training plus two weeks of slower service. If your average transaction is £15 and you serve 100 transactions a day, a 10-second slowdown per transaction during the rollout week costs you about 15 minutes per day of lost productivity — maybe £30-50 per day. Multiply that by 14 days, and you’ve lost £400-700 in throughput. That’s the real cost. The software fee is almost irrelevant compared to this.

Too Complicated for Staff to Learn Quickly

Staff can learn any system if the training is done properly. The issue is rarely the system’s complexity — it’s the training approach. If you’re giving staff 90 minutes of abstract explanation and expecting them to execute it perfectly, they’ll struggle. If you’re giving them four weeks of soft launch with hands-on practice and a buddy system, they’ll get it. Most modern EPOS systems are actually more intuitive than the old ones. The resistance isn’t to the system’s complexity. It’s to the change itself.

What If We Get Locked Into a Long Contract?

Before you sign anything, check the contract terms. Most EPOS providers in 2026 offer monthly contracts with 30-day exit clauses, not three-year commitments. If they’re pushing a long-term contract, negotiate. The best suppliers know their product is good and will let you try it month-to-month. If they won’t, that’s a warning sign.

Will It Integrate With Our Accounting Software?

Ask this before you demo. Ask for a technical specification sheet. Ask to speak with the supplier’s integration team. Don’t sign anything until you’ve verified the integration works in your specific setup. Most EPOS systems integrate with common accounting software (Xero, QuickBooks, Sage), but custom integrations or older software might require workarounds.

Is It Worth It for a Wet-Led Only Pub With No Food?

Yes. Wet-led pubs have completely different EPOS requirements to food-led operations, and most comparison sites miss this entirely. A wet-led pub needs fast till speeds, reliable payment processing, cellar integration for stock tracking, and good reporting on drink categories (draught vs bottled vs wine). A food-led EPOS often prioritises kitchen display systems and table management, which you don’t need. The right wet-led EPOS will streamline your operation. The wrong one (designed for restaurants) will frustrate you. Choose deliberately.

For more information, visit pub profit margin calculator.

For more information, visit pub drink pricing calculator.