All insights
1 September 2026 4 min read

Tender promises don’t create continuous improvement—systems do

The tender illusion: big promises, short-lived momentum I often compare the tender phase to a firework show. Imagine the organiser starts with the bouquet final: the biggest explosions, the loudest bang, the wow-moment. And then, minute by minute, the spectacle becomes smaller and smaller. At some point you’d ask yourself: why am I still staying until the end?

Tender promises don’t create continuous improvement—systems do

In workplace catering, the same dynamic can happen—without anyone having bad intentions.

During the pitch phase, caterers bring their best thinking forward:

·      A new concept

·      A higher service standard

·      Better food, better experience, better everything

Then the contract is awarded—and the takeover team arrives. New uniforms. New signage. New processes. New energy. For a few weeks, it feels like transformation.

But after the transition period, many Facility Managers experience the same reality:

The new normal settles in—and the pace of improvement slows down.

What actually happens after the takeover

The early-phase intensity is real. But it’s often built on project energy, not operational rhythm.

Once the site is in steady state:

·      The client is in a multi-year contract

·      The caterer’s focus shifts from “launch mode” to “delivery mode”

·      Evolution becomes harder to sustain unless it’s built into the operating system

And that’s the core point: continuous improvement can’t rely on goodwill alone—it needs a system.

The silent drift: how standards erode in real life

This drift rarely looks like a dramatic failure. It’s gradual. And because it’s gradual, it becomes invisible.

A concrete example I see all the time:

·      At the start, every dish is properly signalled with clean name tags, nutritional information, allergens—the full professional setup.

·      I come back a year later and the same operation has a dish tag made in a rushed PowerPoint template with an unreadable font.

·      Or worse: a handwritten tag.

It’s not about the tag. It’s what it represents: the operation has slipped into routine mode.

And once routine mode takes over:

·      Small things don’t get done anymore

·      Standards become “flexible”

·      The team stops noticing what’s off

·      The client experience slowly declines

This is not a “people problem”. It’s a rhythm problem.

Why KPI follow-up rarely protects service standards

Most contracts rely on a limited set of KPIs. They matter—but they rarely guarantee day-to-day excellence and evolution.

Because many KPIs:

·      Measure outputs, not operational discipline

·      Capture averages, not drift

·      Don’t force a structured pause to review standards

·      Don’t create a shared improvement backlog with clear ownership

So the Facility Manager often ends up carrying the improvement burden:

·      Spotting what’s slipping

·      Challenging priorities

·      Escalating when needed

That’s not sustainable—and it’s not the best use of anyone’s time.

Hospitality had a better mechanism: the quarterly compliance scorecard

In hospitality, we used a mechanism that many workplace catering environments can benefit from: a compliance scorecard and brand-audit rhythm.

The idea was simple and powerful:

·      Every quarter, the operational responsible had to self-evaluate the operation

·      The scorecard forced a structured review of standards and procedures

·      It reminded the team—again and again—what “excellence” looks like

·      The output wasn’t just a score; it triggered an action plan

That quarterly pause mattered because operations are absorbing. Firefighting is constant. Even strong teams drift.

I’ve lived it myself: you do things well in one quarter, then for some reason you stop doing them. Not because you don’t care—because routine takes over and the issues become invisible.

The scorecard brings the operation back to reality before the standard is permanently lost.

What ALOHA is building: a continuous improvement system that stays with the client

At ALOHA, we’re working on a system designed to support continuous improvement and create a positive spiral—not just a strong start.

The goal is straightforward:

·      Help Facility Managers and caterers align on what “good” looks like

·      Make standards visible and measurable in operations

·      Turn quarterly review into a practical action plan

·      Keep service level improving over time

A key principle: the system must run with the client.

Because continuity matters. If a company changes caterer, the improvement history should not disappear.

The client needs:

·      A consistent standard framework

·      A quarterly rhythm that doesn’t depend on personalities

·      A documented history of scores, actions, and follow-through

And caterers benefit too:

·      Clear expectations

·      Fewer subjective discussions

·      A structured way to demonstrate progress over time

The takeaway

Tender promises can create momentum.

But if you want multi-year evolution, you need something stronger than good intentions and a few KPIs.

Tender promises don’t create continuous improvement—systems do.

workplace cateringcorporate cateringfacility managementfacilities managementFMcatering operationsfoodservice operationscontract cateringcatering contract managementtender processcatering tenderservice standards

See your own restaurant's flow, backed by data

ALOHA CaterFlow simulates your company restaurant so you can cut queues, remove bottlenecks and get a boardroom-ready action plan in 2–3 weeks.

Get started

Related insights

The impact of flow on the customer experience

The impact of flow on the customer experience

Flow is the first and most decisive part of the self-service lunch experience—before customers even taste the food. When queues, counter stops, or payment take too long, people feel stress because lunch time is limited, and that pressure can start as early as leaving their desk. As a result, customers rush, choose the fastest queue over the best offer, and often skip extras like starters or desserts—reducing both satisfaction and average tray value. Poor flow also drives wasted labor, because teams compensate with extra staff instead of fixing the underlying design. Since flow is a connected system, improving one bottleneck can create another (for example, faster service can shift the problem to seating availability). Simulating scenarios with CaterFlow makes it possible to test changes safely, see their impact immediately, and optimize both customer experience and operational performance.

Why the Freeflow Was Doomed From the Beginning

Why the Freeflow Was Doomed From the Beginning

For decades, workplace restaurants (then still called canteens) worked like school canteens: one line, one daily menu, one simple rhythm. It wasn’t glamorous, but it matched the reality: a captive audience, a fixed lunch window, and predictable demand. Then choice arrived. Salad bars, soups, multiple mains, desserts, coffee corners. Suddenly the old “everyone in one queue” started to feel wrong. Why should someone who only wants soup stand behind a full-tray meal? And as employees started paying a share of the meal, expectations shifted: lunch needed to feel like an experience, not a school routine.

The Next-Gen Company Restaurant: Great Food Isn’t Enough Without Data-Driven Service & Flow

The Next-Gen Company Restaurant: Great Food Isn’t Enough Without Data-Driven Service & Flow

Walk into many company restaurants and you’ll see serious investment: modern interiors, better ingredients, motivated teams, and a clear ambition to improve employee experience. And yet, too often, the daily lunch rush still feels like a stress test nobody prepared for. Not because the food is bad. Not because the people don’t care. It happens because the experience system is broken. The next generation of company restaurants won’t be defined by who has the best menu. They’ll be defined by who delivers the best service and the smoothest employee experience—consistently—because they’ve designed the operation around data.