Why PMS projects run late, and how to go live in about four weeks
Most PMS projects fail before go-live day. What goes wrong, what to prepare, and how Newhotel takes each hotel live in about four weeks.
In this article
Ask any hotel manager about their last PMS change and you'll hear the same words: "painful", "late", "the first week was chaos". The software is rarely the reason. The way the project is run is.
The problem: where implementations go wrong
Newhotel has completed more than 4,000 implementations. These are the traps I see most often:
- Too many hands. The vendor sells, a partner implements, another partner supports. Knowledge is lost at every handover.
- Third-party documentation arrives late. Door locks, telephone (PBX), PayTV, accounting and payment gateways all need specs from other suppliers. When they arrive late, go-live slips.
- Configuration decisions nobody made. Rates, contracts, allotments, room types and reports are defined during the project instead of before it.
- Generic training. Everyone sits through the same course, so nobody really learns their own job.
- Staff left alone on day one. The consultant leaves the night before go-live.
How the Newhotel Cloud Suite solves it
- Implemented directly by our head office team, without subcontracting, for groups and large accounts. The people who know the product are the people in your hotel, and the standard is the same from one hotel to the next.
- About four weeks per property (20 to 30 working days), depending on scope and on how available your team is.
- Group first, then hotels. We first create the group's central database in the data centre. Then we bring each hotel onto it, one by one, with a quick setup.
- Department-by-department setup and training: reservations and sales, front desk and night audit, billing, housekeeping and maintenance, meetings and events, POS, and management reports. Each team learns its own work.
- Mobile apps and guest experience included in the plan: the housekeeping app, mobile POS, digital menu and guest experience tools are configured and trained as part of the project.
- We stay with you after go-live. For the first week of live operation, our team is on site or on call to support your staff.
Practical takeaway: your pre-implementation checklist
These tasks are on your side, and they decide whether the project finishes on time:
- Request third-party interface documentation now: door locks, PBX, PayTV, internet access control, accounting/ERP and payment gateway. This is the most common cause of delays I see.
- Name one key user per department. They get the deepest training and become your internal champions.
- Prepare your commercial data: contracts, allotments, rates, companies and travel agents, in one clean file.
- List your reports by priority. Choose the 5 you need on day one and the 15 that can wait a month.
- Choose your pilot hotel carefully. Pick a property with a strong team, not the most complex one.
- Block the dates. Protect the key users' time during training weeks.
Planning a rollout across several hotels? Ask us for a sample implementation plan for a group like yours.
Talk to our hotel groups teamRead next: Choosing a PMS for your group: lessons from 1,079 RFP requirements and Uptime, support and SLAs: what a hotel group should demand.



