The map
The systems map a hotel estate audit draws before judging anything
List what you actually run in each group, then draw the lines: which systems exchange data automatically, which are re-keyed by staff, and which do not speak at all. The re-keying lines are where labour and errors live.
The PMS and what feeds it
- Property management system
- Booking engine
- Channel manager
- Payments and folio
- Rate and revenue tools
The guest-facing surface
- Website and direct booking
- Guest wifi
- In-stay messaging
- Keys and door access
- In-room entertainment
The back office
- Accounting
- Procurement
- Housekeeping and maintenance
- Staff rota
- Point of sale
The data and contract layer
- CRM and guest profiles
- Analytics and reporting
- Marketing tools
- The contract register itself
Data ownership
Guest data a hotel cannot export is data it does not own
A hotel's guest history — stays, preferences, spend, complaints, consent — is scattered across the PMS, the booking engine, the CRM, the wifi provider and the messaging tool, each holding its fragment under its own contract. The audit question is blunt: for each system, can your own staff export the guest data, in a usable format, without a services fee and without asking permission? Where the answer is no, the vendor owns that fragment in practice, whatever the contract's ownership clause says, and every future decision — a new CRM, a loyalty programme, a property sale — pays a tax to that dependency.
The register that fixes this is short: one row per system, naming what guest data it holds, whose name is on it contractually, how it exports, and what an export costs. Building it usually takes a few phone calls and produces the audit's most uncomfortable findings — which is exactly why vendors rarely volunteer the information and why the calls are worth making before the next renewal, not after.
The calendar
The renewal calendar is the cheapest negotiating position a hotel owns
Most hotel technology contracts renew automatically, and the notice window — often a quarter before the date — is the only time the hotel holds any negotiating position at all. Miss it and the price, the terms and the data conditions are fixed for another cycle; worse, systems whose renewals were never tracked renew silently on terms nobody has read in years. The calendar is a single page: every contract, its renewal date, its notice deadline, its cost, and the decision owner. The audit builds it once; keeping it current is minutes a month.
The calendar also sequences everything else. A hotel that knows its channel manager renews in five months can run that procurement properly — with the systems map showing what the replacement must integrate with and the data register showing what must come out of the incumbent — instead of signing another cycle under deadline pressure. Renewal dates, read together, are a technology roadmap the estate wrote for you.
Before adding
Five questions a hotel asks before adding any new system
Run these against every pitch, including ours. A system that fails them does not become worthwhile because its demo was impressive.
1 · Which number does it move, and who owns that number?
Direct bookings, staff hours, review scores, energy cost — name the metric and its owner before the pilot, or the system will be judged by impressions. A metric, a baseline and a named owner, written before signature.
2 · What does it talk to — verified against your PMS, not a logo wall?
An integrations page listing your PMS brand proves little; versions, editions and interface fees decide reality. Require a written confirmation for your exact system and version, and a reference hotel running that same pairing. Integration confirmed in writing for your estate as it is, costs included.
3 · Whose name is on the data it creates?
Every new system becomes another row in the data register on day one — what guest data it will hold, its export path and its export cost, agreed before the contract rather than discovered at exit. Ownership and export terms in the contract, matching the register's standard.
4 · What does leaving it look like?
Notice period, data return, deletion confirmation and what stops working at the estate's edges when it goes. A system that is easy to leave is, not coincidentally, usually one run by a confident vendor. Exit terms read before signing, not at the first dispute.
5 · What does it add to the calendar and the training load?
One more renewal to track, one more interface for reception to learn, one more night-audit step. The estate's carrying cost grows with every addition, and the audit exists so that cost is chosen, not accumulated. The full carrying cost on the table beside the licence fee.
Our role
How we audit a hotel estate without arriving with a product to sell
- 01
The three documents, built with your team
We run the mapping, the data-register calls and the contract review with your people, so the documents stay maintainable by the hotel rather than becoming a consultant's appendix.
- 02
Engineering where the map shows re-keying
Where the map shows staff copying data between systems, we build the integrations — including around ageing PMS platforms — because removing a re-keying line is usually worth more than adding a system.
- 03
A neutral seat at vendor conversations
We sit on your side of renewal and purchase conversations as engineers, on fees you pay — we take no commissions from hotel technology vendors, which is what lets the advice stay advice.
What the estate should become is a commercial judgement that belongs to the property; the audit's job is that the judgement is made over a map, a register and a calendar instead of over a vendor's slides.
Common questions
What buyers ask
Why does a hotel technology audit start at the PMS rather than the website?+
Because the PMS is the system of record the rest of the estate orbits: reservations, room state, folios and most guest history either live in it or must reconcile with it. Start the map anywhere else and every line eventually leads back there anyway — the booking engine writes to it, the channel manager syncs against it, housekeeping and the night audit run on it, and half the integration fees in the estate are charged for the privilege of talking to it. Starting at the centre also surfaces the estate's real constraint early: the PMS's age, edition and interface openness decide what every other system can and cannot do, which is information you want before evaluating anything new, not after. The website matters — it is the storefront — but it is a satellite of the record, not the record.
What should a hotel's contract renewal calendar record?+
One row per contract, six columns: the system and vendor; the renewal date; the notice deadline, which is the date that actually matters; the annual cost including the interface and support fees that sit outside the headline price; the decision owner; and the current intention — renew, renegotiate, retender or exit. The notice deadline deserves an alarm well ahead of itself, because a negotiating position needs preparation time: reading the contract, checking the data register for what must be exportable, and looking at the systems map for what a replacement would have to integrate with. Hotels that maintain this one page stop discovering renewals in the accounts payable report, which is where auto-renewed contracts are usually noticed — one cycle too late.
How often should a hotel redraw its systems map?+
Redraw is the wrong model; maintain is the right one. The map changes on events, not on a schedule — a system added or retired, a PMS upgrade that changes interfaces, a vendor acquired and replatformed, a new property brought into the group. Make updating the three documents a closing step of every such event, owned by whoever owns the change, and the map stays current at almost no cost. A sensible rhythm on top of that is an annual review, ideally timed before the heaviest renewal season on the calendar, where the map, register and calendar are read together and the year's technology intentions are set. What ages a map into uselessness is not time but untracked change — and a map that has drifted from the estate is more dangerous than no map, because decisions still trust it.
In this cluster
Review your estate with us
A walk through your three documents once they exist — what the map, the register and the calendar say your next technology decision should be.
Start the conversation
