Knowledge base
DC Registry
Every codex on Be A Top Host names its documents with a short DC, a Codex Document Code, built from small parts like SOP or SH. This page is the registry those codes are built from.
One registry, every codex
Once a code is registered here, it carries one meaning across every organization's codex on the platform, whether that codex belongs to BATH, HLH, or any other organization we work with. No two offices, teams, or document types share a code with different meanings.
A document code strings a few of these parts together, for example GR-RV-SOP-SH-01: an office, a team, a document type, a scope, and a running number. The groups below are that same registry, organized so it can be browsed rather than looked up one code at a time.
Office
Which office or department a document belongs to.
The office handling reservations and booking operations.
The office handling cleaning operations.
The office handling day-to-day coordination across teams.
The executive committee overseeing the organization.
The office handling guest relations and guest experience.
The office handling business growth and expansion.
The office representing organization-wide headquarters functions.
Retired token, superseded by KE (Keys).
The office handling laundry operations.
The office handling overall management.
The office handling procurement of supplies and vendor costs.
The office handling the technology platform.
The project management office coordinating work across teams.
The office handling pricing strategy.
The office maintaining the operator and assistant persona definitions used across automated communications.
The service-provider roster, tracked under the office segment.
The office handling repair and maintenance vendors.
The office handling revenue operations.
The office handling sales.
The office handling service providers such as cleaners and vendors.
The office setting organization-wide standards.
The office handling cleaner certification and training through the Philippines' TESDA program.
The office handling external vendors.
Team
Which team or function inside an office a document belongs to.
The Airbnb booking channel.
Air conditioning servicing and technicians.
Guest arrival and departure logistics.
Guest-facing property amenities.
Optional paid add-ons guests can purchase.
Broadcast-style announcements sent to a wide group.
Job candidates in the recruitment pipeline.
The booking and communication channels a property is listed on.
General communications.
Parking and carpark management.
Regulatory and policy compliance.
Cleaning staff and contractors.
External contractors.
Custody of keys, devices, or other property items.
Converting inquiries into confirmed bookings.
Dispatching staff or service providers to a job.
Front-desk operations.
Web domains and related digital assets.
General documentation.
Escalated issues that need higher-level attention.
Demand and revenue forecasting.
Foundational reference material.
Fees and payment processing.
Planned future work that is not yet active.
Follow-up actions after an interaction.
Direct communications with guests.
Google Workspace tools and integrations.
The Hostaway property management platform.
A staff or operations handbook.
Handover of a task, shift, or property between parties.
Care and support provided to guests during their stay.
Technical and operational infrastructure.
Keys and building access management.
The internal knowledge base.
Physical keys and key management.
Scheduling of key handoffs.
Lost and found items left by guests.
Property maintenance.
Messaging platforms and threads.
A grouping of related property listings or units.
New business development.
Onboarding new staff or service providers.
Operations work, and separately optimization work; two related uses of this token still being reconciled into one.
Staff and personnel records.
Property and listing photography.
Parking arrangements for guests.
The recruitment or sales pipeline.
Backend records and systems.
Hiring and recruitment.
Risk management.
The roster of cleaners assigned to properties.
Repair vendors such as glaziers, plumbers, and electricians.
Routing of tasks, messages, or requests to the right person.
Guest reviews.
Staff and task scheduling.
Consumable supplies for properties.
Turnover between one guest's stay and the next.
A geographic territory or coverage area.
Upsell offers made to guests.
Retired token, superseded by VE (Vendors).
The WhatsApp messaging channel.
The WeChat messaging channel.
Water heater equipment and servicing.
Subtype
An extra layer some platform documents use between team and type.
A calendar-related document.
Retired token, superseded by CH (Channels).
A document related to shared file storage.
A manual-type reference document.
A reservations-related document.
A sidebar-related document.
A document that serves as the authoritative record for its topic.
Type
What kind of document it is, such as a policy, a template, or a playbook.
A step-by-step checklist document.
A large body of reference source material.
A document laying out a guiding principle or philosophy.
A glossary defining terms used across the documentation.
An index document that helps navigate to other documents.
A short, informal notes document.
A playbook giving step-by-step guidance for handling a specific situation.
A policy document stating a rule or standard.
A protocol document defining a formal procedure.
A reference document providing background information.
A registry document tracking a structured list of items.
A document with step-by-step instructions for a recurring task.
A reusable template document.
Scope
How broadly a document applies, from one property to the whole organization.
Applies to properties in the Docklands area.
Applies to a defined set of Melbourne apartment buildings.
Applies across the whole organization, not to one property or team alone.
Citation tier
How settled a document is, from an open question to a fully ratified rule.
A placeholder entry that flags a known gap, sketched out but not yet resolved.
An entry whose structure is in place but whose content is still thin.
An entry that is clear but has not yet been formally approved.
An entry that is clear and has been approved or has a working precedent.
An entry that is clear and backed by multiple worked precedents.
An entry that is formally approved, load-bearing, and kept current.
Status
Where a document stands in its lifecycle, from planned to current to retired.
A flag marking a bundled document that should be split into separate, single-topic documents.
A document that is live, accurate, and needs no rework.
A document that has been written but not yet formally approved.
A flag marking a document that is too thin and needs more detail.
A flag marking a document that is outdated and needs to be rewritten.
A flag marking a document filed under the wrong category, pending recoding.
A flag marking a case where two versions of a document exist and need to be merged.
A flag marking a document that should be removed from active use.
A flag marking an older document that needs to be reviewed, repointed, or retired.
A document whose structure is in place but whose content is not yet written.
A document that has been named or planned but not yet written.
A document that is provisional and may not survive review.
Composition
How many ideas a document bundles, from a single rule to a large multi-topic bundle.
A document covering a single idea or a single enforceable rule.
A document bundling a few related ideas together.
A large document bundling many topics together.
Looking for guides on using the platform instead? Back to the knowledge base