Localizing an LSOP Without Losing the Brand Standard

Localization does not mean lowering the standard

When we talk about localizing an operating procedure, there is a common temptation to think that adaptation means making exceptions.

For me, it means the opposite.

Localizing an LSOP means taking the brand standard, understanding the experience it is designed to protect, and translating it into the actual conditions of the property. The goal is not to change the standard. The goal is to make the standard work.

This becomes particularly important during a pre-opening. Before the first guest arrives, many things may look simple on paper but have a completely different dimension in the operation: distances, service locations, available resources, position structures, technology, interdepartmental communication, and above all, the team's actual ability to execute consistently.

A procedure can be perfectly written and still be useless if nobody can execute it as designed.

Standard first, operation second

One of the most important lessons a pre-opening has reinforced for me is that you should not start by writing the procedure.

You start by understanding the standard.

What is the brand trying to protect? Which elements are mandatory? What behavior is expected from the associate? What experience should the guest perceive?

Only then does it make sense to look at the property.

At that particular property, for example, the operation required us to think about positions and service flows that had to be built from the ground up. Front Office was not simply about placing people behind a desk. We had to define how Bell Stand, Front Desk, Concierge and Pool Concierge would work together as part of one coherent guest experience.

Housekeeping required the same approach. Housekeeping leadership, public areas and laundry needed procedures that reflected the property's operational reality while maintaining the logic of the brand standards.

That is where localization really begins.

The LSOP should explain the "how"

A brand standard normally tells us what must happen.

The LSOP should help us answer how it will happen here.

That difference may seem small, but operationally it is significant.

A good LSOP should allow a newly hired associate to understand what to do, in what sequence, who is involved, what information needs to be communicated, which tools are used and what the expected outcome is.

The associate should not have to interpret a corporate document to discover how the operation works.

That is why, when I develop a procedure, I try to bring it back to the real operation. Who starts the process? Who receives the information? Where does it happen? Which system is used? What happens when something does not go as expected? Who receives the escalation?

When those questions are unanswered, we do not yet have an operating procedure.

We have an intention.

Adaptation also has limits

This is probably the most delicate part.

Not everything can be localized.

Some elements belong directly to the brand standard and should not be changed simply because another approach is more convenient for the operation. A leader's role is not to choose which standards to follow and which ones to ignore.

The role is to find the right way to execute them.

That is why I find it essential to separate three things:

• The standard: what the brand requires.
• The intent: why the standard exists and what experience, safety, consistency or control it is designed to protect.
• The local execution: how we achieve that result within the specific conditions of our property.

When these three levels become confused, we usually end up doing one of two things. We either copy procedures that do not work in our reality, or we modify them so much that we lose the original intent.

Neither is good operations.

A pre-opening forces you to think differently

In an operating hotel, we often inherit existing processes. We identify problems, make adjustments and measure results.

In a pre-opening, we have to build while we are still learning.

That completely changes the role of the leader.

It is not only about training people. We have to design the operation, define responsibilities, establish work sequences, create control tools and prepare the team to understand why we do things in a particular way.

During a pre-opening, every decision has a consequence.

A poorly designed procedure can become a poor practice repeated every day. An unclear responsibility can turn into an interdepartmental issue. A workflow that ignores the property's physical reality can directly affect the guest experience.

That is why the real test of an LSOP is not whether it is well written.

The test is watching it being executed during an actual shift.

Training is not memorization

This is another distinction I consider essential.

A prepared team is not the team that memorizes the manual. It is the team that understands the intention behind each standard and can apply it correctly when the situation changes.

In hospitality, no two shifts are exactly the same.

We may have the correct procedure, but a guest may arrive early, a room may not be ready, another department may need support, a system may experience an issue or a request may fall outside the expected scenario.

The associate needs to know the procedure, but also understand the reasoning behind it.

That is where operational leadership stops being supervision and becomes development.

The real indicator is consistency

For me, a well-localized LSOP has one very simple characteristic: it makes the correct way of working easy to understand and repeat.

It does not need to become an endless document.

It needs to be clear enough to guide the team, specific enough to reduce interpretation and flexible enough to account for operational reality without compromising the standard.

Consistency does not mean that everyone works mechanically.

It means that, regardless of who is on duty, the guest receives the experience the brand promised.

That is the point where a corporate standard truly becomes a service experience.

What I take away from the pre-opening

Building an operation from the ground up reinforced something I had already learned after many years in Rooms Division: procedures are not the heart of the operation.

They are a tool.

The real work is connecting standards, people, processes and guest experience.

Localizing an LSOP does not mean writing an "easier" version of the standard. It means understanding the standard well enough to implement it in a real property, with its own characteristics, resources, distances, teams and guests.

In the end, the question I ask myself is quite simple:

Does this procedure allow our team to deliver the experience the brand expects within the reality of our operation?

If the answer is yes, then the standard has stopped being a document.

It has become a way of working.