Your Wage Bill Is Your Biggest Cost — Are You Actually Tracking It?

I was three months into running Teal Farm when I realised I had no idea how much I was actually spending on wages per week. I knew roughly what people were paid — £12 an hour for bar staff, £11 for kitchen staff, £9.50 for casuals — but I didn’t know if my 17-person team was costing me £3,000 a week or £4,000 a week. And I certainly didn’t know which shifts were burning the most money.

This is absolutely mad when you think about it. The wage bill is easily my biggest single cost — often 25-35% of revenue depending on the week. And I was managing it the way a lot of pubs do: by accident. I’d hire someone, I’d keep them on their normal hours unless something went obviously wrong, and then at month-end I’d look at the payroll total and feel vaguely concerned.

That ended the day my accountant asked me, “So what’s driving your wage bill? Is it overstaffing? Are your shift patterns wrong? Are you paying above market rates?” And I had absolutely no answer.

That’s when I got serious about wage tracking. Because if you can’t see your wage bill in detail, you can’t control it. And an uncontrolled wage bill is the difference between a pub that’s profitable and one that’s treading water.

The Problem with Reactive Wage Management

Most pub operators manage their wage bill the way I used to: reactively. Someone calls in sick, you scramble to cover the shift. It costs more (you might have to pay overtime or call in agency staff), but it’s cheaper than being understaffed. Someone quits, you post a job and hire a replacement. It takes a few weeks, so you’re short-staffed and working long hours yourself. Business slows down in winter, and you keep your staff on because it’s easier than managing variable hours. Business is busy in summer, so you keep extra staff on even though it’s stretching your wage budget.

None of this is terrible individually. But collectively, it means your wage bill is often 2-3 percentage points higher than it needs to be. For a £80,000 a year revenue pub (a small village pub), that’s £1,600-2,400 a year. For a £200,000 a year pub, that’s £4,000-6,000 a year. For a busy town-centre pub doing £400,000+ a year, that’s £8,000-12,000 a year in unnecessary wage costs.

And most operators don’t even realise they’re leaving that money on the table.

The issue is that without proper tracking, you can’t see the problem. You think your wage bill is fine because it’s been consistent the last few months. You don’t notice that you’re overstaffed on Mondays (when you’re dead) or that your closing shift is always running two extra hours because you’re inefficient at close-down.

What a Real Wage Bill Tracker Needs to Show

A proper wage bill tracker for a pub needs to show you:

Total wage costs by week or month: What’s your actual spend right now? Not a forecast based on standard hours, but your actual payroll cost.

Wage cost as % of revenue: This is the key metric. If your revenue is £4,000 this week and your wages are £1,200, you’re at 30% labour cost. If next week your revenue is £4,200 but your wages are £1,400, you’re at 33%. That 3% change matters, and you need to see it in real time.

Breakdown by shift: How much are you spending on your Monday opening shift versus your Friday night shift? On your kitchen versus your bar? On your full-time staff versus your casuals? You need to see which shifts are eating your budget.

Breakdown by staff member (if you want that level): This is sensitive data, but some operators want to see which team members are actually costing them the most — sometimes because they’re working the most hours, sometimes because they’re paid the most. This helps with scheduling and payroll decisions.

Comparison to target: You’ve budgeted 30% wages. This week you’re at 32%. You’re £80 over. Is that a one-week blip or a trend? You need to know.

Overtime and additional cost flagging: Did you have to pay anyone overtime this week? Call in agency staff? Pay for a cover shift that wasn’t planned? These are visible in the tracker, so you can review them and decide if they were necessary.

Trending: Is your wage bill creeping up slowly over time? Are you trending toward higher labour costs in summer and lower in winter (which is normal, but you need to anticipate it)? These patterns matter for planning and budgeting.

How I Built My Wage Tracking System

I started by asking my payroll provider for a detailed breakdown of wages by week. I got a spreadsheet showing exactly what I’d paid each person each week. I then reorganised this to show:

• Total payroll by week
• Payroll as % of revenue (which I pulled from my till system)
• Breakdown by shift (opening, evening, night, weekend)
• Breakdown by role (bar, kitchen, management)
• Overtime and agency costs flagged separately

Then I looked back over six months and calculated my average labour cost %. For Teal Farm, it was 31.5%. I set that as my target. Anything above 32% I flagged as “requires investigation.”

The first week I did this analysis, I found that my Friday evening shift was consistently running 2.5 hours longer than planned, and no one had even questioned it. It was just “how closing always takes.” But that 2.5 hours of overage, times 4 weeks a month, was costing me about £120 a month. I looked at what was causing the overrun, realised we were inefficient at stock rotation and bin-out procedures, redesigned the closing process, and cut the average Friday close-down from 5 hours to 3.5. Saved £120 a month, every month, just by spotting a pattern in the data.

The second thing I found was that my Monday wage bill was 18% of Monday revenue, while my Friday wage bill was 28% of Friday revenue. This is normal — Mondays are dead, Fridays are busy — but I wasn’t adjusting my staffing accordingly. I was keeping the same staff on Mondays as Fridays. I reduced Monday staffing by one person (25 hours a week), hired a part-time weekend person to pick up extra Friday/Saturday hours, and my overall wages went down even though my weekend coverage improved. Saved about £80-100 a week, or £4,000-5,000 a year.

The third thing I found was that I had three casual staff members working at different rates: £9.50, £11, and £10. The £11 person was more experienced and sometimes worked shifts they shouldn’t have needed help with. But the tracking showed they were worth the premium. The £9.50 person was either unavailable or inexperienced — I wasn’t using them efficiently. I restructured casual hiring, kept my best person, and made the budget work better.

None of these decisions would have been possible without detailed wage tracking. I was flying blind until I could see the actual numbers.

The Pub Operator Console Wage Tracker

Once I’d built my manual wage tracking system, I realised I was spending hours every week pulling data, reorganising it, and analysing trends. And it was still error-prone — I’d miss a bonus payment, or I’d miscalculate hours, or I’d forget to include agency costs.

This is where the Pub Operator Console transformed wage management at Teal Farm. The Console’s wage bill tracker is built specifically for pub labour dynamics — casual staff, variable shift patterns, overtime, agency cover, bonus payments, all of it.

Here’s what the system does:

• Automatic payroll data import: If your payroll system integrates with the Console (which most major UK payroll systems do), your wage data flows in automatically. Every payment, every overtime, every agency cost is captured without manual data entry.
• Real-time labour cost tracking: You don’t wait for payroll to be finalised. The Console shows you your labour costs for the week in real time, as shifts are worked. If you’re trending over budget, you see it immediately.
• Revenue-linked analysis: The Console pulls your revenue from your till and automatically calculates wages as % of revenue. This is the metric that actually matters — 30% wages against £5,000 revenue is different from 30% wages against £3,000 revenue.
• Shift-level breakdown: You can see exactly how much you spent on Monday opening, Friday evening, Saturday night, etc. This lets you compare like with like (Monday opening this week vs. Monday opening last week) and spot inefficiencies.
• Staff member view (optional): If you want to see which team members are costing you the most, you can. This helps with scheduling decisions — you can see if one person works so many hours they’re becoming uneconomical, or if another person is underutilised.
• Budget vs actual: You set your target labour cost %. The Console constantly compares actual to target and flags when you’re over. This turns wage management from reactive (“oh no, payroll is high”) to proactive (“we’re tracking 2% over budget this week, let me understand why”).
• Overtime and agency flagging: Every overtime payment or agency shift is visible and flagged separately. You can see immediately if you’re paying too much in overtime or if agency costs are out of control.
• Trending and forecasting: The Console shows your labour cost % over the last 4, 13, and 52 weeks. You can see seasonal patterns, and you can forecast what your budget should be for the coming months based on historical trends.
• Comparison to industry benchmarks: The Console lets you see how your labour costs compare to industry standards for UK pubs. Are you at 30% (which is typical)? Or at 35% (which is getting expensive)? Knowing this helps you make decisions about whether you need to adjust staffing.

The effect is that you move from “I hope my wage bill is under control” to “I know my wage bill and I’m managing it actively.”

What Changes When You Track Wages Properly

Once I started using the Console’s wage tracker, my relationship with labour costs changed completely.

First, budgeting got real: Instead of guessing what I should budget for wages, I could look at historical data and say, “Okay, January is dead, so I need to plan for 28% labour costs. February picks up a bit, 29%. Summer is busy, so 32%. I need to schedule accordingly.” This let me forecast my P&L much more accurately.

Second, inefficiency became visible: One Wednesday evening, the Console flagged that I was at 34% labour costs — way above my 30% target. I pulled the report and saw that I’d called in two cover shifts and had two people on overtime because someone had called in sick. It cost me about £60 in extra wages. But at least I could see it, assess it (yes, it was necessary), and decide going forward whether I needed contingency planning.

Third, staff scheduling got smarter: I could see that my full-time bar manager was consistently working 45 hours a week when the contract said 40. Rather than slowly burning them out, I hired an additional part-time bar person to pick up 5 hours a week. Cost me about £50 a week, but it improved scheduling flexibility and staff morale.

Fourth, I could justify staffing decisions: When my landlord asked if I was overstaffed (because they’d heard from other operators), I could pull the Console and show them my labour cost % was 30% — right at industry average. I wasn’t overstaffed; I was staffed appropriately for a pub of our size and sales level. This conversation would have been much harder without actual data.

Fifth, bonuses became strategic: Instead of giving Christmas bonuses to everyone by default (which costs about £500), I could see which staff members were actually driving profits, and I could reward them more and reward lower performers less. This improved morale because it felt fairer, and it improved the wage bill because it was more targeted.

The Objections

Won’t this take forever to set up? If your payroll integrates with the Console, you literally just connect it and the data flows in. If not, you enter your payroll data once (usually copy-paste from your payroll provider) and the system handles the analysis going forward. It’s not complicated.

Is this too granular? You can use the wage tracker at whatever level is useful for you. You want to just see total wages and wages % of revenue? That’s available. You want to drill down by shift and by staff member? That’s available too. You choose the level of detail you need.

What if I don’t have variable hours? Then wage tracking is even more straightforward. Your labour costs are predictable. The Console still shows you what you’re actually spending and whether you’re on budget. And it spots any anomalies (unexpected overtime, agency costs, etc.) immediately.

Will my staff think I’m spying on them? No. You’re tracking payroll data that already exists. Your staff aren’t seeing anything they wouldn’t see on their payslip. You’re not tracking when they take breaks or how long they spend on each task. You’re just managing labour costs like any professional business would.

What’s the cost? The Pub Operator Console is £97. One payment, no subscription. Given that most pub operators can find £200-500 a month in wage savings by optimising staffing, it pays for itself in one salary review.

Take Control of Your Biggest Cost

Your wage bill is probably your biggest single cost — often 25-35% of revenue. Most pub operators don’t control it actively. They manage it reactively. And they lose thousands of pounds a year to inefficiency.

The Pub Operator Console’s wage tracker gives you visibility into your labour costs, real-time alerts when you’re over budget, and the data you need to make smart staffing decisions.

Get the Pub Operator Console — £97

30-day money-back guarantee. No subscription. No hidden fees. Just real wage cost tracking that works for pubs.

Once you understand your wage bill, you can make better decisions about the other major cost — stock. Use the pub profit calculator to model different scenarios: what if I reduce wages by £100 a week? What if I reduce COGS by 1%? How does each change affect my bottom line?

Want more free tools to run your pub better? SmartPubTools has everything you need: explore all the tools available for pub operators.