Knowledge bases.
Department procedures your staff and your agents read from the same copy, answers that cite their source, and what makes a procedure findable at 02:00.
What a knowledge base is
A knowledge base is a department's written procedures, held in one place and assigned to the properties they apply to. Housekeeping has one. Maintenance has one. Front desk has one. A new workspace is seeded with 14 department knowledge bases, and housekeeping arrives with 69 procedures already written — the standard ones, the ones every hotel has somewhere and few hotels can produce on demand.
Two audiences read the same copy. A person opens it to check a step. An agent reads it to answer a question, and shows which procedure it used. There is no second, agent-only version of your standards, which is the entire point: when the procedure changes, it changes once.
Scope: who a procedure applies to
Every base is owned by a department and assigned to properties. A procedure written for the UAE cluster reaches Marina Bay Hotel and Palm Suites and stops there; Riyadh Central keeps its own. Where a standard genuinely is group-wide, assign it everywhere and stop maintaining four copies that drift.
Members and Groups organises staff into 9 departments, and a person reads the bases their department and their properties cover. This is not only a permissions question. A front-desk agent whose every search returns housekeeping procedures has been given a worse tool than a folder.
How an answer gets cited
- 01/04Someone asks
The question is asked in the surface the work is already in — inside a task, in a chat, in the inbox — not in a separate place a person has to remember to go.
- 02/04Retrieval
The question is matched against the procedures the asker's department and property give them. Matching is on meaning, not on exact words: "the kettle in 412 is dead" finds the in-room equipment procedure without containing the word equipment.
- 03/04An answer with its source attached
The answer names the procedure it came from and links to it. One click and the person is reading the standard itself, which is where they should end up if the answer is at all consequential.
- 04/04Or an honest miss
If nothing clears the relevance bar, nothing is invented. The answer is that the procedure is not there. That is a finding: it means the next person will not find it either, and it is worth writing.
The citation is the feature, not the decoration. An answer nobody can check is worth less than the two minutes it saved, because the first time it is wrong, the staff stop trusting all of them.
What makes a procedure retrievable
- One task per document. "Deep clean a suite bathroom" is a procedure. "Housekeeping" is a folder.
- A title that says the task. Someone searching types what they are doing, not what the document is called internally.
- Numbered steps in the order they happen, with the equipment and the room type named. A model number in the text is what lets an agent find the right manual later.
- The exception written down. Most questions at 02:00 are exceptions: what to do when the guest is in the room, when the part is out of stock, when the supervisor is off site.
- An owner and a revision date at the top, so a reader can judge how much to trust it.
Keeping them current
Where the knowledge base gets used
It is not a separate destination. It is read from the places work already happens:
- A task carries the procedure that applies to it, so the person doing the job is not asked to go and find it.
- A flow that proposes a fix cites the manual or the procedure it read.
- A drafted guest reply is answered from the department's base, so what the guest is told matches what the staff were told.
Where to go next
- Flows — the runs that read these procedures.
- Shifts and tasks — where a cited procedure lands in someone's day.