The Shape of the Library: Architecture Options

Where Hotels Usually Start

Having built and lived with Standard Operating Procedures (SOPs), policies and process libraries across many operations, we find most hotel companies sit in one of three places.

The shared drive. Everything lives in folders on OneDrive or Google Drive, shared as needed. Some departments keep theirs tidy, most do not, and the truth of any document depends on who you ask. This is the most common state in the industry, and nobody chose it; it accumulates.
Brand standards only. The property runs on its franchisor's standards and audit programme, with mystery shopping doing the checking. There are no SOPs of the company's own; the brand's book is the book. Fine while the flag flies, and nothing is left when it changes.
A structured library. The more deliberate operators build an intranet or knowledge base with a real taxonomy. The most sophisticated organise it around their processes themselves, sometimes on a recognised frame such as the American Productivity and Quality Center (APQC) process classification, separating the core process, managing the guest experience, from the support processes: people, finance, technology, procurement.

An estate the shape of Aleph's is usually a mix of all three at once, property by property, depending on flag and history. That is not a failing; it is the starting condition, and the design below treats it as one. Whatever is chosen must be a home that properties in different states can move into at their own pace, not a system that assumes everyone starts from the same place. The structures drawn in this paper follow shapes we have designed and run with operators from a single-city luxury group to a multi-brand international portfolio; the workshop sees worked examples of each.

Three Decisions Inside Any Option

Whichever option the room prefers, the same three decisions sit inside it. They are separable, and keeping them separate is what stops the conversation running forever.

The rings: who is bound by what

A non-negotiable core at the centre, applying to the entire estate. Around it, standards bound by brand or by tier, three-star, four-star, five-star. At the edge, the property-local variants. The factory already produces exactly this shape, a common spine with a property fit, so the rings describe what exists rather than impose something new. A change made at one property lives in its ring and cannot leak to another.

The map: how processes are organised

Flat by division is the simplest. One step up, the core process is delineated from the support processes, in the APQC manner. The fullest picture is the house: strategic processes at the top, the guest experience as the core in the middle, the support processes beneath. The house has one great virtue: it puts the whole company on a single page, which is precisely the picture this module owes its sponsors.

The facets: how a person finds things

Division, geography, document type and language. Document type follows what the factory makes: policy, process, step-by-step task, training session plan, group training session plan. Language is English and French as a fact of this estate. The facets do not compete with the map; they are the doors into it, all hyperlinked into one knowledge base so a reader lands on the current version from any direction.

The rings, drawn

The factory already makes documents in this shape: a common spine, a brand or tier layer, and a property fit at the edge. The rings are also the access model: a change lives in its ring and cannot leak sideways.

The map, drawn: three levels of ambition

Three drawings of the same estate, at rising levels of ambition. The house is the picture this module owes its sponsors: the whole company on one page, with every document in the library belonging to one visible place. Worked examples from operators we have built this with come to the workshop.

What the Best Actually Do: Two Worked Examples

Two structures we have worked inside, drawn here anonymised. They solve the same problem from opposite ends, and both did something the drawings above cannot show: they organised finding around the guest journey, pre-arrival to departure, inside or instead of divisions. The journey is a fourth way to draw the map, and it is the one a guest would recognise. The full structures come to the workshop.

The wheel: how a library stays alive

From the guest experience manual of a Dubai-born luxury group. The library is one station on a turning wheel: culture sets the bar, behaviour guidelines carry it, standards and processes write it down, training brings it to life, assessment checks it, improvement changes it, and the wheel turns again. Their manual is the starting point of the cycle, not the end of it; everything hangs off an intranet: step-by-steps, checklists, forms, templates, job profiles. This is the charter's living layer, drawn.

The register: governance carried in every row

From the operating brand standards of a multi-brand international group. Every standard is a numbered row that carries its own governance: what kind of standard it is, who owns it, its current status, where it applies, and when it takes effect, with a legend page expanding every code. The register, not the folder, is the truth, which is the invariant principle below already working at scale. Their map, notably, is the guest journey itself: pre-arrival and arrival, the room, the public areas, dining, spa, departure.

Five Options, and a Dial

The rings, the map and the facets fit inside every one of these. Options A to D sit on a dial of rising formality; Option E is different in kind, an artificial intelligence (AI) assistant that can attach to any point on that dial. What changes along the dial is how much structure surrounds the library, what that structure demands of Aleph, and what it gives back.

Option A

The disciplined drive

Keep the tools Aleph already owns and impose order: one agreed folder architecture, strict naming, a master index that is the single front door, and the taxonomy carried in the documents themselves.

Demands	Discipline and nothing else. No new platform, no new cost, no procurement conversation.
Gives	Order within weeks, on systems every property already runs.
To keep alive	Constant vigilance. Folder discipline decays without an owner; this is the option most dependent on people staying disciplined, because the structure cannot enforce itself.

Option B

The knowledge base

A structured, hyperlinked library with the taxonomy built in: the house on its front page, the facets as its navigation, the rings as its access model, every document reachable in seconds and cross-references that hold. Built on or beside what Aleph owns, handed over to run without us.

Demands	A real taxonomy decision up front, a named controller, and a change process with a record.
Gives	The single home the charter describes, the company-wide picture on one page, and structure that enforces itself rather than relying on discipline.
To keep alive	A steady, modest rhythm: requested changes, an approver, an audit trail. Governance by design rather than by effort.

Option C

The bought system

An off-the-shelf document management system: version control, approval workflow, read receipts and audit trails as product features rather than working practices.

Demands	Procurement, licensing, administration, and an owner inside Aleph for the system itself. It must also clear the estate as it is: split between Google and Microsoft 365, with hard restrictions at some properties.
Gives	The strongest built-in control of the four dial options, with the least designing.
To keep alive	Licence renewals and an administrator, indefinitely. A system nobody owns becomes the next abandoned portal.

Option D

The certified system

Document control run to the International Organization for Standardization (ISO) 9001 standard, independently certified: controlled documents, mandated review cycles, records, external audit.

Demands	A standing management commitment, not a filing exercise. Certification binds the whole operation to its own procedures, permanently and audibly.
Gives	External proof of control, credible to owners, brands and future partners.
To keep alive	Annual external audit and continuous internal upkeep. Named here honestly as the ceiling of the dial, so the middle options are chosen rather than defaulted to; it is a destination an operator grows into, not a starting point.

Option E

The knowledge bot: ask, do not browse

A tightly controlled AI assistant on the platform this programme already runs on. A team member asks a question in plain language, English or French, from any device including a phone, and the bot answers only from the approved library, quoting and citing the standard it drew from. The content behind it does not need to be elaborately structured, because retrieval does the finding; what it must be is tightly governed. Only approved documents enter the corpus, scoped by ring, so a property's bot knows that property's variants and nobody else's.

Variant one: bot-first

The corpus carries light structure only, the rings and the document-type labels, and the bot is the front door. The fastest route to phone access there is, and strongest exactly where the estate is hardest: a property whose information technology (IT) rules bar shared drives entirely still reaches every standard it is entitled to, because the bot is the door, not the drive.

Variant two: bot on the base

Option B plus the bot: the structured knowledge base for those who browse, the assistant for those who ask. The house stays the picture on the wall; the bot becomes the fastest corridor through it. This is the destination the recommendation below points at, and the two variants are a sequence as much as a choice.

Demands	Corpus governance above all: the same approval rhythm as any option, because the bot is only as trustworthy as what it is allowed to read. Licences on the programme's platform, access scoped per property, and honesty about limits: the bot quotes and points; the document remains the truth.
Gives	The fastest access of the five, on a phone at the front desk or in the kitchen. And the split estate stops mattering: the bot works the same whether a property lives on Google, on Microsoft 365, or on paper and PDF.
To keep alive	Exactly what keeps the library alive, no more. The corpus updates when the library updates; a stale library means a confidently stale bot, which is why governance comes first.

The One Principle That Is Not Optional

The taxonomy is the invariant; the platform is swappable. The identity, ring, classification and version of every document live in the document itself, never only in a platform's folder tree.

This estate runs Google in some houses and Microsoft 365 in others, with some teams reaching content only as PDF, on desktop and mobile alike. Any architecture that stores its intelligence in one platform's structure breaks the day a property cannot use that platform, which somewhere in this estate is already true, or the day the platform changes. Carried in the documents, the library survives any move. The knowledge bot makes this more true, not less: a bot is only as trustworthy as the corpus it reads, so the governance ring around the knowledge base is what makes "ask, do not browse" safe to offer. This is the lesson of every intranet that did not take, here and everywhere else, and it is the reason the options above are a dial rather than a fork: Aleph can start disciplined, become structured, add the bot, and formalise later, without ever rebuilding the library itself.

Where We Would Start, If Asked

Option B, approached through A, with the bot arriving early rather than last. Agree the rings, the map and the facets first, because they cost nothing to decide and everything downstream inherits them. Apply them immediately to what the factory is already producing, which is Option A in practice and useful from the first week. Let the knowledge base form around that taxonomy on platforms the estate can actually reach, and stand the bot up on the governed corpus as soon as it exists, because for the properties the estate serves worst, the bot is not a luxury at the end of the road; it is the first door that actually opens. The bought system remains available if the governance rhythm proves it is wanted, and certification remains the ceiling if Aleph ever wants control it can show to the outside world. Fit for purpose is the test at every step, and the room, not this paper, decides.

What We Need in Order to Decide Well

The estate map: property by property, who runs Google, who runs Microsoft 365, who may reach shared drives at all, and on what devices. One page from Fiona is enough.
What remains of the earlier intranet: content worth keeping, lessons worth honouring, and anything still running that people quietly rely on. We ask before we build over it.
The sponsor confirmed and the charter agreed, so the taxonomy workshop decides with authority.
The workshop itself: one working session, these options and the drawn structures on the table, Fiona and Abdellah as the guides, and a decision at the end of it.