Covers per labour hour: The metric most operators have never heard of

There’s a metric that tells you if your restaurant is running well before the financial damage shows up, but most operators have never used it.

It's called covers per labour hour, and it’s one of the clearest ways to understand whether staffing, demand, and execution are aligned in real time, while there’s still time to act.

I want to be honest about why most operators haven't used it. It's not widely taught and it sounds technical. Not to mention, when it's misunderstood or misapplied, it can do more harm than good. 

But when used correctly? It changes how leaders see and manage their operations.

By the end of this article, you’ll know what CPLH measures and how to use it correctly to improve results. 

What are covers per labour hour (and what does it actually measure)? 

Covers per labour hour (CPLH) are a measure of how many customers a restaurant serves for each hour of labour worked. The result tells you how much demand your team converted per hour of labour deployed, which helps you measure your labour efficiency and productivity. 

The CPLH calculation is simple: 

Covers served divided by labour hours worked. 

What makes this restaurant productivity metric powerful is what it reveals about the relationship between demand and staffing: 

• When CPLH is within its expected range, the operation is broadly in balance. You have the right people working at roughly the right time, relative to what the business needs. 

• When it moves significantly above or below that range, something has shifted. Demand was different from the forecast, staffing didn't match what was needed, or execution broke down somewhere in the system.

It’s an early signal that shows whether things are aligned before the consequences surface financially.

Why CPLH should guide decisions, not set targets

CPLH is useful when it helps you understand what’s happening in your restaurant. However, the metric becomes a problem when you turn it into a number your managers and teams are expected to hit.

Say a manager sees that CPLH is lower than usual. Maybe the restaurant had a quieter service, a late booking spike, or a team member spent more time than usual supporting a section. 

In this situation, the answer isn’t automatically to cut hours. But because the manager is chasing a higher CPLH without looking at the context, they do it anyway. As a result, their decision leads to understaffing, slower service, and more pressure on the team.

Recommended reading: How to reduce restaurant labour costs without cutting hours.

Instead, use CPLH alongside your other operational data. 

Look at how staffing compares with demand, whether service levels held up, and what was happening in the restaurant at the time. A drop in CPLH might point to excess labour, but it could also show that the team needed those extra hours to handle a busy or unusually demanding service.

There’s no single CPLH figure every restaurant should aim for, either. A quick-service restaurant, a full-service restaurant, and a fine-dining operation will all have very different staffing needs. Your own historical data gives you a much more useful reference point.

‍The goal is to understand what healthy CPLH looks like for your operation, then use changes in the number to ask better questions about your labour and demand.

Why tracking CPLH daily is key to better performance

CPLH gives you the most useful information when you review it often enough to do something with it. Daily tracking lets you spot changes while there’s still time to adjust restaurant staffing, rather than looking back at the numbers after the week or month is over.

For example, if CPLH is running below your usual range on Tuesday and the forecast shows a busy weekend ahead, you have time to look at the rota and make changes. You can add hours where demand calls for more cover or reduce them where you’ve scheduled more labour than you need. 

Leave that review until the end of the week, and the same number can tell you what happened, but it can’t change the shifts that have already been worked.

That kind of day-to-day adjustment can add up across a larger restaurant group. In one 20-unit full-service group, using CPLH as a core operating metric helped reduce labour drift by more than 20% over 12 months. Restaurant CPLH improved by 8%, while total labour costs fell by more than $600,000. 

The takeaway is simple: review CPLH while you can still act on it. The sooner you spot a mismatch between demand and labour, the more options you have to fix it.

Barge East shows why this matters when demand can change quickly. The London floating restaurant has to account for weather, nearby events at London Stadium, ABBA Voyage, and seasonal changes, all of which can affect how busy a service will be. 

Using more granular forecasts gives managers a chance to adjust staffing before service rather than reacting once the restaurant is already busy.

As Tommo (Founder at Barge East) puts it: 

Nory has allowed us to have the right number of staff at the right time. It's helped us save labour costs and also make sure that when we're busy, we're ready to serve guests properly.

Nory is an agentic AI restaurant operating system that brings key data into one place, connecting demand forecasts with workforce management. Restaurant teams can make staffing decisions based on what’s actually happening in the business in real-time. 

Managers can see where labour needs to change, adjust rotas before service, and track whether those decisions are improving productivity over time.

How to know when CPLH is moving off track

A change of around 5-8% from your usual CPLH range is worth investigating. It doesn’t automatically mean something is wrong, but it’s a useful prompt to look at what’s changed in demand, staffing, or service.

If CPLH suddenly jumps, don’t assume that higher productivity is better. The team might be handling more covers with fewer hours, but they could also be stretched too thin. Look at what happened during the service and whether the higher number came at the expense of speed, service, or team capacity.

The same applies when CPLH falls. Maybe demand was lower than expected and the extra hours weren’t needed, or perhaps the team needed more time to handle a particularly demanding service. The number tells you where to look, but you need the context to understand why it moved.

That’s why CPLH should inform staffing decisions rather than become a score for managers to chase. Use it alongside your demand forecast, sales, service levels, and other operational data to decide what needs attention.

The real value comes from acting while there’s still time to change the outcome. A CPLH shift spotted early gives you a chance to adjust upcoming rotas, investigate what’s driving the change, and avoid carrying the same problem into the next service.

This article draws on research and operator perspectives featured in The Definitive Guide to Restaurant Success in 2026, produced in partnership between Benchmark Sixty and Nory. Download the full guide here.