PMS for hotels: what the team actually uses (and which ones are left unused)
In the actual operations of a hotel, especially a small or medium-sized hotel, the team does not use “the whole PMS”. They use few functions, but they use them intensively and under pressure: check-in, check-out, billing, room changes, incidents. The problem is not that there are more modules; the problem arises when everything is visible to everyone, without process or training, and that generates confusion, fear of “touching” and parallel work outside the system.
In LEAN, a practical way to reduce “ghost” functions is customisation by user group and by individual user: each person sees only the modules they need. When what you see is what you use, it lowers error, lowers the learning curve and improves continuity even with rotation.
Why many PMS “have it all” but the team uses only a 20%
This pattern often has very day-to-day causes: too many screens for one role, training that is not focused on the real process, diffuse roles (in small hotels one person does everything) and a culture of “better not to touch, in case I break something”. Added to this is duplicated work: Excel, WhatsApp and loose notes that seem quick, but take away traceability.
The cost is not just inconvenience. It translates into billing and folio errors, slowness at peak times, dependence on a person “in the know” and more incidents because information is scattered.
What a small hotel needs from the PMS
More than a catalogue, a small hotel usually needs a minimum viable core to operate without friction: reservations and availability, check-in/check-out, collections and folios, invoices and some basic reports (arrivals, departures, occupancy by date, daily collections). If the PMS also coordinates well with floors (even if only at room status level), the flow improves a lot because reception stops working “blind”.
Functions used by almost all the team
If you look at the actual week, there is a set of functions that almost always repeats itself: the occupancy calendar, the booking and guest record, room assignment and changes, internal notes to leave context between shifts, and payment/folio status. Added to that are the more operational: arrival and departure lists and last minute changes.
As a quick check, if your PMS allows you to operate well on a day-to-day basis, you should be able to: see arrivals/departures and pending, assign and change rooms without chaos, keep clear folios and know what is paid and what is not, and leave internal notes that another shift can understand.
What each role actually uses
Reception / Front desk
Reception lives in a few screens: check-in/check-out, modification of reservations, room assignment, billing and folio, and recording of incidents or notes. Occasionally it may play simple upsells or a quick report for management. What tends to be underused are advanced reports, configurations and complex templates, not for lack of interest, but because they should not be touched in daily operation or because they require a process that the hotel has not defined.
Revenue / management (in small hotels, often the same person)
This role uses the PMS to monitor the business: occupancy by date, booking evolution (if pick-up exists), ADR/RevPAR in the basics, performance by channel and, depending on the stack, review of rates and restrictions. What is often underutilised is fine segmentation when the data is not captured well and advanced dashboards when they are not converted into a concrete weekly routine. It's not that they “don't work”; it's that without discipline of use, they become pretty screens that no one looks at.
Housekeeping / floor supervision
If the PMS allows it, floors need to view and update room statuses, priorities and report issues that affect availability. Many hotels rely on a Housekeeping App to make this work in real time, because the PMS often falls short for allocation, tracking and photos. In this case, the PMS remains the core of availability and the front desk benefits from seeing reliable statuses.
Administration / accounting
Here the actual usage is quite stable: invoices, closings, basic reconciliation, receivables reports and exports. What is usually not used are high-level configurations if there is no internal manager to maintain them, which is normal in small hotels.
Functions that are often “not used”
Not using modules is not a failure. It can be perfectly normal if the hotel does not need them. The important thing is that what is not used does not get in the way or confuse. Often automations, integrations or complex reports are not activated because there is not enough time to parameterise, or because the process is not ready. The practical focus should be: the PMS should cover the critical and not add friction.
A clear sign that a module is “in the way” is when the team solves that task outside the PMS (in WhatsApp or Excel) because in the system “it's scary”, “there are too many clicks” or “we don't know where it is”. That's not an attitude problem; it's a view and process design problem.
The key to using what matters: customising the PMS per user and per team
The most effective lever in small hotels is often to reduce the visible per role. In LEAN, environments for groups of users and for individual users are customised: each person sees only the modules they need. This prevents a receptionist from getting lost in complex configuration screens or reports, and reduces errors from touching the wrong things.
Personalisation does not mean “we train less”. It means that each role works with focus and security. Front desk sees reservations, check-in/out and collections; management sees reports and control; floors see status and incidents; administration sees billing and export. When the environment is fine-tuned, onboarding is accelerated and the hotel is no longer dependent on “the expert person”.
How to decide which modules to activate in your hotel
A simple method is to start with processes, not modules. First list your actual processes (check-in/out, collections, floors, incidents, distribution), define who does what and which tasks are daily or weekly. From there, select the minimum modules that support those tasks and measure if they are actually used. If the team masters the core, then you expand.
A quick mini-audit (without consultancy) works well: in one hour, bring together reception, management/revenue and floors, and get everyone to say which screens they use in a week and what tasks they do outside the PMS. This almost always results in three clear improvements: simplify views by role, create a daily core checklist and set a weekly review routine.
Operational impact: less training, fewer errors, better continuity with rotation
With rotation and mixed shifts, continuity depends on simple systems. When the PMS shows only what is needed per role, new staff learn the basics faster and make fewer mistakes due to confusion. In addition, the hotel gains consistency: the process does not depend on a specific person, but on a repeatable operation.
Frequently asked questions
What minimum functions should a PMS for a small hotel have?
A minimum viable core includes reservations and availability, check-in/check-out, collections and folios, billing and basic reporting (arrivals, departures, occupancy and collections). It also helps if there is coordination with housekeeping at least at the room status level, so that reception does not manage blind assignments.
Why doesn't my team use many PMS features?
It is often due to too many visible modules, lack of process and practical training, blurred roles and fear of making mistakes. It also happens when the team works in parallel with Excel or WhatsApp because the PMS is not adapted to the real flow. The most effective solution is often to simplify views per role and standardise the daily core.
Is it bad that we don't use all the PMS modules?
Not necessarily. The important thing is that the PMS covers critical processes and does not add friction. Not using a module can be normal if your hotel does not need it or is not ready to operate it. The problem is when those modules get in the way, confuse or cause errors in operational roles.
How do I reduce errors and speed up training in a PMS?
It works well to combine role-based customisation, short SOPs/checklists and limiting the screen to what is needed for each job. In LEAN you can customise environments by user group and by individual user, so that each person sees only the modules they need, reducing confusion and speeding up learning.
What should a receptionist see on screen and what should not?
A minimum viable core includes reservations and availability, check-in/check-out, collections and folios, billing and basic reporting (arrivals, departures, occupancy and collections). It also helps if there is coordination with housekeeping at least at the room status level, so that reception does not manage blind assignments.
What should a receptionist see on screen and what should not?
A minimum viable core includes reservations and availability, check-in/check-out, collections and folios, billing and basic reporting (arrivals, departures, occupancy and collections). It also helps if there is coordination with housekeeping at least at the room status level, so that reception does not manage blind assignments.
How do I do a quick audit of PMS usage in my hotel?
Bring together reception, management/revenue and floors for 60 minutes. Have everyone list screens used and tasks they do outside the PMS. Identify what modules are left over for each role and what is missing for the actual flow. Close with three actions: simplify views per role, define a daily core checklist and set a short weekly review routine.
You may also be interested in
REQUEST YOUR DEMO TODAY
Discover how Lean Hotel System can transform your hotel business
Spanish
English
Italian
French
German
Portuguese