Why Kitchen Layout Breaks Your Productivity Benchmarks (and How to Fix It)

The comparison trap: same people, different reality

A simple example makes the point.

·      5 cooks in a 200 m² oversized kitchen will not have the same productivity as 5 cooks in a 30 m² kitchen.

·      10 cooks in a 100 m² kitchen on the same level as self-service will not have the same productivity as the same 10 cooks in the same kitchen… if the kitchen is on a different floor.

In both cases, you can keep the same number of staff, the same menu, and the same service hours.

But the output changes—because the layout changes:

·      walking distance

·      vertical transport (stairs/lifts)

·      split service points

·      storage and replenishment routes

·      handover points and “micro-delays” that add up all day

When those factors change, your “standard” KPIs stop being standard.

A real case: the tender that asked for -25% labour

A client once approached me while building a new head office. Incredible design. Big ambition.

They issued a catering tender with a clear target: reduce labour cost by 25%.

The problem?

In the new building:

·      the kitchen was in the basement

·      the restaurant was split into two rooms on different floors

Yet the client was using the same productivity KPIs they used in their old restaurant—where everything was on one level, with short walking lines and direct access to service.

That’s not benchmarking.

That’s applying yesterday’s logic to a completely different operating system.

Why “average productivity” is a dangerous number

Here’s what we see in the market: even caterers often don’t use layout-adjusted productivity metrics.

Instead, productivity is calculated based on averages.

And at tender stage, many providers prefer not to include complexity because:

·      if they price the real complexity and a competitor ignores it, they look “expensive”

·      it feels safer to win first and “solve later”

But that approach creates predictable outcomes:

·      under-resourced operations

·      service stress and quality drop

·      hidden labour creep after go-live

·      friction between client and caterer (“you promised this would work”)

All of it comes back to one root cause:

gut feeling instead of data.

The fix: a productivity factor you can actually compare

This is exactly why we use our KPC (Kitchen Productivity Calculator).

The goal is simple:

·      create a factor that allows fair comparison between two outlets

·      compare an outlet against optimum standards, not against a misleading average

The calculator helps you quantify where productivity is lost—before you blame people, suppliers, or “bad management.”

It gives you a clear, operational explanation you can use with stakeholders:

·      “This is where the time goes.”

·      “This is what the layout forces the team to do.”

·      “This is what it costs.”

The best moment to use it? Before the building exists.

The KPC is not only useful in existing restaurants.

It’s a strong tool when the restaurant is still a concept in the drawing room.

Because design decisions have operational consequences.

Architects and kitchen builders are great at designing beautiful spaces.

But too often, the design is approved without a hard look at what happens later—when the space needs to run every day, at speed, with real people.

With the calculator, you can test scenarios early:

·      What happens if the kitchen is one floor lower?

·      What happens if service is split into two rooms?

·      What happens if storage is further away?

You don’t need opinions.

You need visibility.

Limited-time access: test our calculators online

For a limited time, you can use and test our calculators online.

If you’re planning a new build, preparing a tender, or trying to understand why productivity “should be higher” but isn’t—this is a fast way to get clarity.

We turn catering operations into boardroom-ready numbers.