Hotel technology

A named owner for every hotel system: PMS, channels, Wi-Fi, locks and cameras on one page

A hotel system owner list names one person, a deputy and vendor contacts for each critical system. This guide shows how to build the page, secure logins and keep it current.

  • 9 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

Contents

Key takeaways

  1. One named person, not a department, is what makes a system owner list usable at night.
  2. The deputy matters as much as the owner: a page that stops at one name fails on the first holiday.
  3. Support hours belong on the page in the hotel's own time zone, next to the contract that pays for them.
  4. A shared password vault with a sealed break-glass copy beats a spreadsheet on the front desk PC.
  5. A quarterly review, plus a review after every staff change and every incident, keeps the page true.

A hotel system owner list is a one-page register that names, for each system the hotel depends on, one internal owner, a deputy, the vendor contact with support hours, where the logins and contract are kept, and the date of the last review. It answers one question at any hour: whom do we call, and who decides.

The door lock system stops accepting cards at 11 pm on a Saturday, and the front desk has three phone numbers, two of which belong to people who left last year. The question is not technical. It is whether anyone wrote down who owns that system, who covers for them, and whom to call when the vendor's office is closed. This guide shows how to build that page: which systems earn a row, who the owner and deputy are, what goes in the vendor column, where logins and contracts live, and how to keep the whole thing true.

What is a hotel system owner list?

It is a single page that gives every system the hotel depends on one named internal owner, a deputy, a vendor contact with support hours, the place where logins and the contract are kept, and the date it was last reviewed.

One row per system, written in the words the hotel uses: door locks, Wi-Fi, channel manager, not the vendor's product name. The page is a decision tool, not an inventory. It exists so that anyone, at any hour, can find who decides and whom to call. Keep it to one page and one screen; a list that needs scrolling gets printed once and never updated.

Separate three things in every row: who is accountable, who operates the system, and who approves the spending. They are often three different people. Write the role beside the name, so the page survives a promotion and shows at a glance when it has gone stale. Keep a printed copy at the desk for the night team and a shared file for everyone else, with the same content. A row without a date is a guess: the last-reviewed column is what turns the page into a habit.

SystemOwner and deputyVendor contact and hoursLogins and contractLast reviewed
PMS (reservations, front desk, billing)name, role · name, roleaccount manager, support line, hours in hotel timevault entry, contract folderdate
Channel manager and booking enginename, role · name, roleaccount manager, support line, hoursvault entry, contract folderdate
Wi-Fi and networkname, role · name, roleprovider, support line, hoursvault entry, contract folderdate
Door locks and key card encodername, role · name, roletechnician, support line, hoursvault entry, contract folderdate
Cameras and recordername, role · name, roleinstaller, support line, hoursvault entry, contract folderdate
Telephony and point of salename, role · name, roleprovider, support line, hoursvault entry, contract folderdate

Which systems belong on the page?

Any system whose failure a guest would notice within the hour, or that holds money, personal data or physical safety, belongs on the page.

Start with the five that stop the hotel: the property management system, the channel manager, Wi-Fi and the network, door locks, cameras. Add what holds money or fiscal records: the payment terminal, the fiscal device at each outlet, invoicing, the guest bill. Add what holds personal data: the guest database, the reservation inbox, the camera recorder, the marketing list. Add what the building runs on: energy management, the phone lines, any lift or access system that depends on the network.

Apply the night test: if a colleague would phone you about it after midnight, it earns a row. Cap the first version at eight to ten rows; a page of forty rows is a wish, not a plan. When a system is retired, its row leaves the page the same week, together with its logins and its contract reference, as covered in retiring old hotel equipment and wiping its logins before it leaves.

Does this system earn a row?

Checklist

  • A guest would notice its failure within the hour
  • It holds money or a fiscal record
  • It holds personal data
  • It controls physical access or safety
  • The hotel cannot trade without it for a full day
  • Someone outside the hotel must be called when it fails
  • It has a login that someone in the hotel holds

Who owns a system, and who is the deputy?

The owner is the person accountable for access, contract and escalation on that system, not necessarily the person who operates it every day.

Accountability has four parts: the owner knows the contract, approves who receives a login, decides when to call the vendor, and signs the quarterly review. Name a person, never a department. A department cannot answer a phone at 11 pm.

The deputy must be able to act, not just relay: same access, same authority to call the vendor, and a stated limit for approving an emergency call-out. Where the hotel is large enough, keep the owner and the budget approver separate: the owner proposes, the manager approves. Do not let one person own every row; if the whole page carries one name, the page has a single point of failure.

Give the owner a small, explicit duty: a ten-minute check each quarter and a note in the shared file. Write the role next to the name, so a departure leaves a visible gap rather than a silent one.

What belongs in the vendor contact and support hours column?

A named account contact, the support channel the hotel is actually entitled to use, the hours converted into the hotel's own time zone, and the contract that pays for them.

Record the channel the contract covers: a phone line, a portal, an email address. A portal nobody has ever logged into is not a support path. Write the hours as the hotel experiences them, and mark the gaps: nights, weekends, public holidays. Note what the contract calls an emergency and what response time it promises, using the vendor's own wording rather than a summary.

Add the second step: the account manager's direct contact and the person above them, for when the first line does not answer. Note whether after-hours calls are included or charged, and who in the hotel may authorize a charge. Keep the contract number and the renewal date in the same row, so a support call never begins with a search through email.

Watch outOffice hours are not a night path

A support line answered only in office hours does not cover a Saturday failure. Write the real hours on the page and plan the night separately, rather than assuming cover the contract does not give.

Where should logins and contracts be kept?

In one shared password vault with named access, plus one sealed break-glass copy for the night team, and in a single contract folder organized by system with renewal dates visible.

One vault, one folder, one rule: no system login lives in an email thread or on a note stuck to the desk. Give vault access by name and remove it the day a person leaves; the vault's own log shows who opened what and when. Seal the break-glass credentials in an envelope or a vault entry that alerts when opened, and re-seal it after every use.

Keep contracts, order forms and renewal dates in one folder named by system, not by vendor, so the page and the paperwork match. Mark which logins are personal and which are shared; shared logins should be few, and each one still needs an owner. Test retrieval once a quarter: can the deputy find the door lock login in under five minutes without asking anyone? A related question is who can reach your hotel systems through vendor remote access and API keys, which the same review should cover.

Key pointThe page and the vault do different jobs

The page tells you whom to call, the vault tells you how to get in. Both must be reachable by the deputy without the owner's phone.

What happens at 11 pm on a Saturday?

The night team follows a short written path: what they may do alone, whom they call next, and how the hotel keeps operating while the system is down.

Write two lists per critical system: actions the night team may take without asking, such as a restart or switching to the manual procedure, and actions that wait for the owner. Keep a manual fallback ready for each critical system: a registration form, a mechanical key or a manual encoder procedure, a backup connection. Give the night manager one phone number per system, in order, with a stated wait before moving to the next.

State in writing who may approve an emergency call-out charge and up to what limit, decided before the weekend rather than during it. Log every incident in one place: time, system, who was called, what was done, when it ended. The log is what makes the quarterly review real. Debrief within a week while the details are fresh, and change the page if the path failed. For the vocabulary of downtime itself, see recovery terms for hotel systems: RTO, RPO and what they mean at the desk.

TipPrint the night page

Laminate it and keep it at the desk with the fallback forms. A page that needs a login to read is not available when the network is the thing that failed.

How often should the page be reviewed?

Once a quarter, and again after any staff change, new system, contract renewal or incident.

The quarterly check is short: are the names still employed, do the numbers still connect, are the support hours still true, has a contract renewed? Check access at the same time: remove logins for people who left, confirm each deputy still holds theirs. Compare the page against the invoices; a system nobody owns is often a system nobody is watching.

Record the review date and the name of the person who did it. An undated page is a guess. Fold the review into the budget cycle so licences, support contracts and renewals are seen together rather than one call at a time, the way a hotel IT budget built from devices, licences and renewals is meant to work. After an incident, review the single row involved within the week, not the whole page.

ChecklistQuarterly review checklist

  • Every name still employed
  • Every deputy confirmed and reachable
  • Support hours re-checked against the contract
  • Renewal dates updated
  • Vault access list matches the page
  • Break-glass copy still sealed
  • Night page reprinted and dated
  • Last incident log read

What to do next

This week, take the five systems that stop the hotel, write one name and one deputy beside each, add the vendor's real support hours, and print the page for the desk. Then walk the night path once, in daylight, with the night manager reading it aloud: the gaps show up immediately. The page is not documentation for its own sake. It is the difference between a hotel that knows whom to call and one that finds out at the worst possible moment.

Frequently asked questions

Should the system owner be the person who uses the system every day?

Not necessarily. The owner is accountable for access, the contract and escalation; the daily user is the operator. In a small hotel the same person can hold both roles, but then the deputy must be someone else, and the owner still signs the quarterly review.

Can one person own more than one system?

Yes, and in a small hotel they usually will. Cap it deliberately, name a deputy for each row, and never let one person own every system, because that recreates the single point of failure the hotel system owner list is meant to remove.

What if the vendor only offers support by email?

Write that on the page as it is, add the account manager's direct contact as the second step, and plan the night around a manual fallback rather than around a reply. Check what the contract promises for response, and note whether after-hours help is charged.

Do we need a printed copy of the page?

At least the night page, yes. The failure that matters most is often the network itself, so the contact list, the fallback procedures and the escalation order should be readable without a login, kept at the desk and reprinted after every review.

How do we keep the page current when staff turnover is high?

Write the role beside every name, tie vault access to the row, and make a departure, a new system, a renewal and an incident each trigger a review of the affected rows. A dated quarterly review catches whatever those triggers miss.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

We can brief you on this topic.

If this topic touches your work, we can walk you through what is built and what is designed.

Request a briefing