Luxury Service Benchmark

document: Aleph SOP Engine - Luxury Service Benchmark
version: 2.0
date: 13 September 2026
status: Controlled — Approved for English Production
owner: Deep Hospitality
scope: SOP-controlled hotel operations and guest service at MRG and MLR

1. Purpose

This benchmark helps the SOP Engine identify a small number of relevant opportunities to strengthen an original SOP, A, for luxury hotel delivery.

It describes service outcomes and operational behaviours. It is not an assessment system, a copy of any assessment provider's standards, or authority to rewrite every SOP in a more elaborate style.

The benchmark is a supporting source. The Runtime Contract, Markup Output Contract, Editorial Intent and A govern how an English operator-review markup is produced.

2. Core principle

Luxury service is not created by adding more words. It is created when a procedure helps a Team Member deliver the right outcome accurately, naturally, discreetly and with minimal effort for the guest.

Use this benchmark only where it materially improves what a Team Member must do, notice, decide, communicate, record, hand over or escalate.

3. Relevance gate

Before using a benchmark criterion, confirm all five conditions:

1. Direct connection: The criterion applies to a real step, risk or guest interaction within A's scope.
2. Material gap: A does not already give enough practical direction at the point of use.
3. Operational value: The proposed change would alter or clarify behaviour, responsibility, a decision, a control or the guest outcome.
4. Supportable content: The wording is supported by A or another authorised source, or is visibly presented for validation.
5. Proportionate response: A concise change can close the gap without adding training material, philosophy, repetition or unnecessary controls.

If any condition fails, do not add the criterion to the SOP.

The following are not sufficient reasons for a change:

• the criterion exists in this benchmark;
• the wording sounds more luxurious;
• the behaviour could be useful in many situations;
• an isolated low-risk incident occurred;
• similar wording appears in another SOP; or
• the change makes an implicit expectation more elaborate without making the procedure more usable.

There is no required number of luxury additions. Many SOPs will need only a few. If more than eight benchmark criteria appear to require changes, recheck for overlap, repetition and scope expansion before drafting.

4. How to use the criteria

For each relevant service moment in A:

1. identify the intended guest or operational outcome;
2. check only the criteria connected to that moment;
3. decide whether A is already adequate, needs a concise improvement, conflicts with the outcome, or needs human validation;
4. combine related needs into one well-placed instruction where practical; and
5. propose the smallest change that produces consistent action.

Do not create a criterion-by-criterion scorecard, gap readout, source register or separate benchmark output. Keep the reasoning in the engine's concise internal per-run evidence assessment. Surface only the proposed tracked change and, when the Markup Output Contract requires it, one short operator comment.

Evidence that the property is not consistently following an already adequate SOP is an execution issue, not a reason to add more wording to the SOP.

5. Luxury service criteria

LSB-01: Recognition and attention

Apply when: A guest arrives, approaches, waits or initiates contact.

Desired outcome: The guest feels noticed and receives calm, attentive service.

Consider adding only if material: Acknowledgement when service cannot begin immediately; focused attention; professional conduct within the guest's view.

LSB-02: Clear and natural communication

Apply when: A Team Member explains information, choices, limitations, progress or next steps.

Desired outcome: The guest can understand the message easily and feels helped rather than managed.

Consider adding only if material: Plain language; positive construction; complete and accurate explanations; avoidance of internal jargon, blame, defensive phrasing and abrupt service shorthand.

Do not build a universal list of prohibited phrases into an SOP. Describe the intended communication outcome. Provide recommended wording only where an interaction is sensitive, risky or easily mishandled.

LSB-03: Natural personalisation

Apply when: Reliable information about the guest's identity, preferences or circumstances is available and appropriate to use.

Desired outcome: The guest feels recognised without the interaction becoming scripted, repetitive or intrusive.

Consider adding only if material: Natural use of known preferences or the guest's name; sensitivity to pronunciation, title, culture, privacy and stated preference.

Do not prescribe a number of times to use a guest's name. Do not require a name or title where it would feel unnatural or compromise discretion.

LSB-04: Listening, anticipation and adaptation

Apply when: The guest's words, visible circumstances or the next stage of the journey reveal a reasonable need.

Desired outcome: The service responds to the person and situation, not only to the literal transaction.

Consider adding only if material: Listening without interruption; confirming understanding; relevant proactive help; meaningful choices; adaptation within approved authority; accessibility, dietary, cultural or wellbeing needs.

Do not require speculative guessing, intrusive questions or offers unrelated to the procedure.

LSB-05: Accuracy and informed assistance

Apply when: The procedure creates, changes or communicates a booking, charge, order, record, request, delivery or recommendation.

Desired outcome: Information and execution are correct, complete and trustworthy.

Consider adding only if material: Critical verification; confirmation of requirements; an authorised source of information; recording changes; correction of discrepancies; obtaining help instead of guessing.

LSB-06: Ease and end-to-end ownership

Apply when: A request or service outcome crosses steps, roles, departments, systems or channels.

Desired outcome: The hotel carries the operational burden and the guest does not have to coordinate the process or repeat information.

Consider adding only if material: A clear owner; supported transfer; what information must pass; confirmation of acceptance; responsibility until handover is complete.

LSB-07: Timeliness, waiting and updates

Apply when: The guest waits, a completion time matters or a commitment may change.

Desired outcome: Service is prompt but not rushed, and the guest is not left to chase progress.

Consider adding only if material: An approved timing or its authorised source; realistic estimates; monitoring; an update before a commitment is missed; a revised next step or alternative.

Never invent a timing. Use the appropriate validation label when a useful service expectation has not been approved.

LSB-08: Positive alternatives and service recovery

Apply when: A request cannot be met, or a delay, error, defect or concern occurs.

Desired outcome: The guest receives acknowledgement, a constructive response and useful corrective action without blame or defensiveness.

Consider adding only if material: Listening; appropriate apology; feasible alternatives; immediate action within authority; proportionate escalation; protection of the guest's dignity.

Complaint classifications, serious-complaint categories and management-notification timings belong only in complaint-handling procedures and require the validation defined in the Runtime Contract.

LSB-09: Completion and follow-through

Apply when: An interaction ends or an action remains outstanding.

Desired outcome: The guest knows what has been completed, what happens next and who remains responsible.

Consider adding only if material: Confirmation; next steps; owner and due point; completion check; guest update; appropriate closure or offer of further assistance.

Do not add ceremonial closing language to internal or purely technical steps.

LSB-10: Privacy, dignity and discretion

Apply when: The procedure involves identity, stay information, access, money, health, complaints, guest property or another sensitive matter.

Desired outcome: Information and interactions are handled securely and without embarrassment, exposure or unnecessary explanation.

Consider adding only if material: Appropriate setting or channel; minimum necessary information; discreet handling of names, room details and documents; access or identity checks; secure transfer and storage.

LSB-11: Readiness, cleanliness and condition

Apply when: A space, item, amenity, setup, vehicle, garment, equipment, food or beverage must be ready for use or presentation.

Desired outcome: The complete result is clean, functional, safe and ready at the intended moment.

Consider adding only if material: Authorised setup or specification; completeness and function checks; inspection from the guest's perspective; defect, rejection or removal-from-service action; verification after correction.

Do not invent products, quantities, materials, layouts or technical specifications.

LSB-12: Presentation, comfort and sensory quality

Apply when: Placement, appearance, temperature, light, sound, smell, taste, texture or ease of use materially affects the result.

Desired outcome: Delivery feels deliberate, comfortable and well considered.

Consider adding only if material: A practical presentation or comfort check; an authorised reference standard; accessibility and usability; corrective action where the intended result is not achieved.

Use observable instructions. Avoid subjective embellishment such as “create a magical experience” or detailed aesthetic language without an approved reference.

LSB-13: Care of guest property

Apply when: A Team Member handles, moves, stores, cleans or returns a guest's belongings.

Desired outcome: The property remains secure, identifiable, carefully handled and correctly returned.

Consider adding only if material: Identification; custody and handover; condition; privacy; storage; discrepancy action; presentation on return.

LSB-14: Channel and transition continuity

Apply when: Service moves between in-person and remote channels, or the guest arrives, departs or moves between material stages.

Desired outcome: The next stage feels prepared and connected, with no unexplained dead end.

Consider adding only if material: Advance preparation; orientation; channel-appropriate acknowledgement; confirmation; supported movement between people or channels; access to human help for digital processes.

LSB-15: Consistency and contingency

Apply when: Demand, staffing, shift, season, system failure or service availability may affect delivery.

Desired outcome: Essential quality and controls remain reliable under real operating conditions.

Consider adding only if material: Non-negotiable requirements; proportionate contingency action; escalation trigger; honest communication about unavailable or reduced service.

Do not turn every possible disruption into an SOP branch. Include only credible conditions that materially affect this procedure.

LSB-16: Responsible and locally relevant delivery

Apply when: The procedure directly controls resource use, disposal, local recommendations, destination information or a distinctive property experience.

Desired outcome: Approved responsible or locally relevant choices enhance the experience without compromising safety, hygiene, comfort, accuracy or guest preference.

Consider adding only if material: An approved responsible default; verified claims; respectful local knowledge; a relevant choice or explanation; required handling or disposal.

Do not add sustainability claims, storytelling, local colour or property facts merely because they are available.

6. Drafting controls

When a criterion passes the relevance gate:

• place the instruction where the Team Member needs it;
• state the responsible role when ownership matters;
• describe an observable action, decision or result;
• combine related requirements rather than repeating them across sections;
• preserve A's valid controls and operational meaning;
• use short, translation-ready English;
• use Team Member as the general workforce term;
• use an exact job title where responsibility or authority matters;
• use only the validation labels authorised by the Runtime Contract; and
• prefer a precise insertion or replacement to a broad rewrite.

Avoid:

• luxury philosophy or training explanations;
• fixed gestures, theatrical behaviour or emotional claims;
• repeated reminders to smile, personalise or anticipate;
• scripts where a behavioural guide is sufficient;
• audit checklists or scoring language;
• unsupported timings, authority levels, products or promises;
• copying an example from another procedure without independent relevance; and
• adding a separate section called “Luxury Standards” when the requirement belongs within the operational sequence.

7. Guest wording

Include a Guest Verbiage section only where Team Members need approved or recommended language for a sensitive, risky or easily mishandled interaction.

Label every example Guide. Introduce the examples with this meaning:

Use these examples as guides. Adapt the words naturally while keeping the intended meaning. Use the guest's preferred language where possible.

Recommended language must be concise, respectful, natural and solution-first. It must not sound theatrical, overly formal or translated from promotional copy.

8. Adequacy check

Before proposing a luxury-related change, ask:

1. Is this situation genuinely part of the SOP?
2. What practical failure could occur if the change is not made?
3. Does A already address it adequately?
4. Will the change tell the Team Member something useful at the point of action?
5. Can the requirement be expressed once, simply?
6. Is every local fact or value authorised or visibly left for validation?
7. Will the accepted wording remain natural and easy to translate into French?

If the answers do not support a change, leave A unchanged.

9. Output boundary

This benchmark does not create an additional deliverable. Its influence appears only through relevant tracked changes and selective comments in the operator-review markup.

Do not include benchmark codes, coverage states, evidence grades or internal reasoning in the SOP. A comment may explain the service or operational reason in plain English when the Markup Output Contract requires it.

10. What this benchmark does not authorise

This benchmark does not authorise the engine to:

• override mandatory corporate wording or A's valid controls;
• claim that a property currently fails a standard without supporting evidence;
• invent local practice, legal requirements, timings, staffing or authority;
• add every relevant-sounding behaviour to every SOP;
• reproduce confidential evidence or assessment methodology;
• redesign the corporate Word template;
• create a gap report, scoring matrix, parameter register or clean D; or
• translate the markup.

Amendment record

Version 2.0 - 13 September 2026. Rebuilt as a compact, relevance-gated benchmark for the current A-to-markup workflow. Removed retired stages, gap-readout and scoring machinery, parameter-register instructions, universal scripting rules and legacy citation mapping. Consolidated overlapping criteria while retaining the full range of material luxury-service outcomes.

Deep Hospitality for Aleph Hospitality.

English–French Glossary and Protected Wording

document: Approved English–French Terminology and Protected Wording
version:  1.2
date:     28 September 2026
status:   Controlled Reference Asset
built by: Deep Hospitality
for:      Aleph Hospitality
source:   56 delivered French Rooms SOPs (Concierge, Front Office, Housekeeping, Public Areas)
applies:  FR translation stage only. Does not govern English runs.

1. What this document is

The approved French rendering for every term below. Each entry is a decision, not an option.

Where the delivered French SOPs used more than one rendering for the same term, the dominant usage has been adopted and the alternatives discarded. Those alternatives are not recorded here and are not to be reintroduced.

2. The two statuses

There is no third category. If a term appears in this glossary, it is decided.

3. Protected wording — reproduce verbatim

3.1 Confidentiality title

INFORMATIONS CONFIDENTIELLES ET EXCLUSIVES D’ALEPH HOSPITALITY DMCC

3.2 Confidentiality statement

Le contenu du présent document constitue une information confidentielle et exclusive
appartenant à ALEPH HOSPITALITY. Il ne peut être reproduit, communiqué, diffusé, distribué
ou utilisé, en tout ou en partie, sans l’autorisation expresse préalable d’un représentant
dûment habilité d’Aleph. Toute utilisation non expressément autorisée est strictement
interdite.

4. Standard policy blocks

4.1 Compliance Measurement

Mesure de la conformité : Le département de la Division Hébergement veillera au respect de
la présente politique au moyen de diverses méthodes, notamment, sans s’y limiter, les
rapports issus des outils de gestion, les audits internes et externes, ainsi que les retours
d’information adressés au responsable de la politique.

4.2 Exceptions

Exceptions : Toute dérogation à la présente politique doit être approuvée au préalable par
le département de la Division Hébergement.

4.3 Non-Compliance

Non-respect : Tout membre de l’équipe reconnu en infraction avec la présente politique
pourra faire l’objet de mesures disciplinaires pouvant aller jusqu’à la résiliation de son
contrat de travail.

4.4 Scope sentence

Cette procédure s’applique à tous les hôtels sous la gestion d’Aleph Hospitality et peut
être modifiée par le Directeur Général, sous réserve de l’approbation du siège social.

Where the English scope sentence differs from this, translate the English as written.

5. Document control fields

Header and footer text remains in English under section 12.1 of the translation contract. These entries exist for the document body and for any future reversal of that ruling.

6. Departments and divisions

7. Roles

Team Member is the single general workforce term in English and membre de l’équipe is its single French equivalent, including inside the Non-Compliance block.

8. Operational terms

9. V2.0 section names

10. Guest verbiage

Guest-facing wording is a guide, not a script. Translate the example, keep its conditions, and do not harden it into a fixed phrase.

11. Never translated

Reproduce exactly as written in the English source:

• Michlifen Resort & Golf; Marchica Lagoon Resort; MRG; MLR
• Aleph Hospitality; ALEPH HOSPITALITY DMCC
• System, product and programme names, such as Opera
• Parameter references such as [P1], [P2]
• Policy numbers and SOP codes

12. How the engine uses this

1. Consult this glossary before choosing any term.
2. Apply the entry. Add no validation label, no comment and no alternative.
3. Where a term is absent, translate it faithfully and consistently, and move on. A term this glossary does not cover is not by itself a reason to raise a label.
4. Never treat an individual delivered French SOP, an archived glossary or a former engine file as an alternative authority.

12.1 Nothing about this glossary appears in the document

The translated SOP must contain no reference to this glossary, no section number from it, no statement that a term was chosen from alternatives, and no explanation of a terminology decision. The reader sees the translated term and nothing else.

This is absolute. If a rendering is genuinely uncertain, choose the most defensible option and say nothing in the document. A property reviewer will correct wording at localisation, which is what that stage exists for.

This clause does not affect property validation labels. Labels such as [VALIDATION PAR L'ÉTABLISSEMENT REQUISE: ...] carried over from the approved English, and the property parameter rows, remain in the French exactly as they appear in the English. They record operational facts the property must confirm, not terminology choices, and they are required.

13. Source

Built from 56 French Rooms SOPs across Concierge, Front Office, Housekeeping and Public Areas, with five aligned position-by-position against their English originals: CON001, CON007, PA006, FO 005 and FO 006. Where the corpus was inconsistent, the dominant usage was adopted.

The delivered French SOPs are evidence, not authority. Individual files in that set contain known errors and must not be used as a terminology source.

Amendment record

Version 1.2 - 28 September 2026. Confirmed the finalised glossary and its protected wording as a controlled reference asset for the client French translation workflow.

Deep Hospitality for Aleph Hospitality, 24 September 2026.

MRG Property Context

property: Michlifen Resort & Golf
code: MRG
version: 1.0
status: Standing optional engine input
reviewed: 13 September 2026
owner: Deep Hospitality for Aleph Hospitality

1. Purpose and use

This file gives the SOP Engine compact context about Michlifen Resort & Golf. Use only the parts relevant to the SOP under review.

The engine can work without this file or without any property-supplied additions. Missing context does not prevent a run unless it is essential to a safe and faithful procedure. Where a local fact would improve the SOP but is not confirmed, use the appropriate property-validation label rather than inventing it.

This file does not override A, protected corporate wording, an approved operating instruction, legal requirements or the Runtime Contract.

2. Evidence status

Interpret entries using these labels:

• Property-confirmed: information supplied or approved directly by the property for operational use.
• Current public context: information published on the property's official website. Useful for relevance, but validate it before converting a variable service detail into a mandatory operating instruction.
• Approved positioning: the intended identity and guest-experience direction in supplied positioning material. Use it to guide proportionate tone and relevance, not to invent procedures.
• Strategic proposal: a future initiative, affiliation, programme or ambition. Never state it as current practice.

If sources conflict, prefer the most recent property-confirmed or formally approved operating source. Do not resolve a material conflict silently.

3. Current public context

• MRG is a five-star mountain resort in Ifrane in Morocco's Middle Atlas region.
• The property presents itself as a luxury mountain retreat with an Alpine chalet character and warm Moroccan hospitality.
• The official resort page lists 70 rooms and suites plus one Royal Pavilion.
• Its principal guest facilities include restaurants and bars, a 3,500 m² spa and wellness operation, indoor and outdoor leisure facilities, meetings and celebrations, and a separate golf and country club.
• The golf offer includes an 18-hole Jack Nicklaus-designed course, a Golf Academy and a Club House.
• The resort advertises 24-hour concierge support for reservations, transport and tailored experiences.
• The property serves family, leisure, wellness, golf, event and business-retreat guests across different seasons.

These facts identify potentially relevant SOP context. They do not confirm departmental workflows, service timings, staffing, systems, authority limits, charges, opening hours or seasonal availability.

4. Approved positioning

MRG's supplied positioning emphasises:

• an established Moroccan mountain-luxury identity rather than wholesale reinvention;
• nature, seasonal mountain experiences and the character of Ifrane;
• golf, wellness and gastronomy as central experience pillars;
• family holidays and executive or board retreats;
• authentic, warm and personalised hospitality; and
• refinement expressed through natural materials and a luxury chalet setting.

For SOP use, translate this positioning into relevant colleague behaviour only when it improves the procedure. Do not insert promotional descriptions, theatrical gestures or generic luxury language.

5. Operational relevance cues

Use these cues only to locate relevant standing evidence or to test whether A needs a proportionate property-specific addition:

• Front Office and Concierge: seasonal arrivals, transport and experience reservations, family needs, golf and spa coordination.
• Rooms and Housekeeping: luxury presentation, family and connecting accommodation, accessibility and seasonal comfort.
• Food and Beverage: multiple outlets with distinct concepts and possible seasonal operation.
• Spa and Recreation: spa, pools, fitness, multisport facilities and age or access conditions.
• Golf: coordination with the golf course, academy and Club House.
• Events: meetings, executive retreats, weddings and celebrations.

Do not infer a procedure, promise or fixed service standard from these cues alone.

6. Strategic proposals and aspirations

The July 2026 strategic vision includes possible international affiliations, international luxury recognition, shared collection programmes, cross-property talent initiatives, shared CRM and cross-selling, new experiences, sustainability certification and product enhancement.

Treat all of these as strategic proposals unless a later authorised source confirms implementation. They must not create present-tense SOP requirements, systems, benefits, affiliations, roles or guest promises.

7. Property-supplied additions

The property may add current operational context here. The engine can continue to run when this section is empty.

Add only information that may materially affect an SOP. Do not use this table as a general property description or duplicate information already recorded above.

8. Update rules

• Record the effective date and source or approver for each property addition.
• Mark an older entry superseded when a newer instruction replaces it.
• Keep uncertain information out of the confirmed table. Record it as requiring property validation instead.
• A conversational correction during one SOP run does not update this file unless the operator explicitly requests a permanent property-context amendment.
• Review website-derived facts before relying on them for a procedure where facilities, access, hours, charges or seasonal operation matter.

9. Sources

Internal sources:

• Positioning_And_Vision/Michlifen_Positioning_Statement.docx
• Positioning_And_Vision/MM_Vision_July_2026.pptx

Official public sources reviewed 13 September 2026:

• Michlifen Resort & Golf overview
• Michlifen resort facilities
• Michlifen frequently asked questions
• Michlifen Golf & Country Club

Website content may change. Treat the review date as a currency boundary.

MLR Property Context

property: Marchica Lagoon Resort
code: MLR
version: 1.0
status: Standing optional engine input
reviewed: 13 September 2026
owner: Deep Hospitality for Aleph Hospitality

1. Purpose and use

This file gives the SOP Engine compact context about Marchica Lagoon Resort. Use only the parts relevant to the SOP under review.

The engine can work without this file or without any property-supplied additions. Missing context does not prevent a run unless it is essential to a safe and faithful procedure. Where a local fact would improve the SOP but is not confirmed, use the appropriate property-validation label rather than inventing it.

This file does not override A, protected corporate wording, an approved operating instruction, legal requirements or the Runtime Contract.

2. Evidence status

Interpret entries using these labels:

• Property-confirmed: information supplied or approved directly by the property for operational use.
• Current public context: information published on the property's official website. Useful for relevance, but validate it before converting a variable service detail into a mandatory operating instruction.
• Approved positioning: the intended identity and guest-experience direction in supplied positioning material. Use it to guide proportionate tone and relevance, not to invent procedures.
• Strategic proposal: a future initiative, affiliation, programme or ambition. Never state it as current practice.

If sources conflict, prefer the most recent property-confirmed or formally approved operating source. Do not resolve a material conflict silently.

3. Current public context

• MLR is a five-star resort at Atalayoun in Nador, set beside the Marchica lagoon on Morocco's Mediterranean coast.
• The property presents a contemporary coastal setting that combines Mediterranean character with Moroccan hospitality.
• The official resort page lists 93 rooms and suites.
• The principal guest facilities include two restaurants, bars and lounges, a spa and wellness operation, indoor and outdoor pools, sports facilities, a Kids Club, event spaces and gardens.
• Leisure offers include the Marchica Golf Academy, water sports, tennis and fitness.
• The hotel caters for leisure guests, families, couples, weddings, celebrations, seminars and business events.
• The official website identifies some outlets as seasonal, including the Beach Club and Pool Bar.
• The official FAQ confirms that airport transfer is offered, while year-round opening and availability should be checked directly rather than assumed.

These facts identify potentially relevant SOP context. They do not confirm departmental workflows, service timings, staffing, systems, authority limits, charges, opening hours or seasonal availability.

4. Approved positioning

MLR's supplied positioning emphasises:

• a serene lagoon and coastal setting with views of the Atalayoun mountains;
• contemporary design, Mediterranean character and warm Moroccan hospitality;
• a balance of activity and relaxation, food and wellness, and land and water experiences;
• destination dining, local ingredients and Nador's land-and-sea identity;
• family leisure, couples, celebrations, meetings and retreats; and
• clear, conversational, thoughtful and professional guest communication.

For SOP use, translate this positioning into relevant colleague behaviour only when it improves the procedure. Do not insert promotional descriptions, theatrical gestures or generic luxury language.

5. Operational relevance cues

Use these cues only to locate relevant standing evidence or to test whether A needs a proportionate property-specific addition:

• Front Office and Guest Services: transfers, leisure bookings, family needs, events, water activities and seasonal outlet information.
• Rooms and Housekeeping: lagoon, pool and garden room categories, terraces, accessibility and family requirements.
• Food and Beverage: two restaurants plus bars and lounges, including seasonal venues.
• Spa and Recreation: spa, pools, hammams, treatment rooms, gym, tennis, golf academy and water sports.
• Events: weddings, celebrations, seminars, training and business retreats.
• Safety and Guest Information: water activities and seasonal facilities may require clear eligibility, availability and safety information from approved operating sources.

Do not infer a procedure, promise or fixed service standard from these cues alone.

6. Strategic proposals and aspirations

The supplied strategy includes possible international soft-brand affiliation, international luxury recognition, a new signature restaurant concept, shared collection programmes, cross-property talent initiatives, shared CRM and cross-selling, sustainability certification and potential casino development.

Treat all of these as strategic proposals unless a later authorised source confirms implementation. They must not create present-tense SOP requirements, systems, benefits, affiliations, facilities, roles or guest promises.

The positioning material describes MLR as a year-round destination. Because the current official website tells guests to confirm opening and availability, do not convert year-round positioning into an operational availability promise without property confirmation.

7. Property-supplied additions

The property may add current operational context here. The engine can continue to run when this section is empty.

Add only information that may materially affect an SOP. Do not use this table as a general property description or duplicate information already recorded above.

8. Update rules

• Record the effective date and source or approver for each property addition.
• Mark an older entry superseded when a newer instruction replaces it.
• Keep uncertain information out of the confirmed table. Record it as requiring property validation instead.
• A conversational correction during one SOP run does not update this file unless the operator explicitly requests a permanent property-context amendment.
• Review website-derived facts before relying on them for a procedure where facilities, access, hours, charges or seasonal operation matter.

9. Sources

Internal sources:

• Positioning_And_Vision/Marchica_Positioning.pptx
• Positioning_And_Vision/MM_Vision_July_2026.pptx

Official public sources reviewed 13 September 2026:

• Marchica Lagoon Resort overview
• Marchica resort facilities
• Marchica frequently asked questions

Website content may change. Treat the review date as a currency boundary.