Hotel software in the classroom, and what students never touch.

1. The classroom already solved one problem

A decade ago most students met a property management system for the first time on the day they were hired. That is no longer true. Booking systems are taught properly now, and a graduate arriving at a front desk usually knows what they are looking at. That is real progress and it deserves saying.

2. But it is the same eight hours

Look at what a student practises. They take a reservation. They change a rate. They check a guest in, move a room, split a folio, run a night audit. It is the front desk — because a property management system is a front-desk product. That is what it is for, and teaching it well is not a criticism of anyone.

The problem is what the timetable implies. A graduate leaves believing that hotel software is the reservation screen, because that is the only hotel software they have ever opened.

What the rest of the building was doing

While the front desk was checking someone in, a housekeeper was working through a room list. An engineer was on a plant round that repeats every Tuesday. A duty manager was reading a handover written by someone who went home four hours ago. A supervisor was chasing whether 412 ever got its second towel set. None of that is in the PMS, and none of it was in the course.

3. The first shift

This is where it shows. A new hire who can drive the booking system still has to be taught, on the floor, in the first week:

• where to look to see what is ready and what is not, without walking the corridor
• how a job gets raised, who it goes to, and how anyone knows it was finished
• what the property's standard actually is for a room, a public area, a plant room
• who is allowed to see what, and why the answer is different for a supervisor
• what the hotel says to a guest before a person gets involved

Every one of those is learnable in a classroom. None of them needs a real guest or a real booking. They are simply not what a front-desk system was ever built to show.

4. The gap is operations, not reservations

A hotel is mostly not the front desk. Housekeeping, maintenance, the handover between shifts and the standards that hold them together are where most of the labour and most of the cost sits. It is also where a new employee is least useful on day one and takes longest to become useful.

So the useful question for a training centre is not "can my students learn the booking screen" — they can — but "can my students practise a shift". Building a hotel is a better exercise than booking a room into one. You cannot set up a property without deciding what the departments are, what each one is responsible for, how often the work repeats, and what "done" looks like. That decision-making is the job.

5. What we are offering, and what we are not

We are not replacing anything in your curriculum, and we do not teach reservations. Treema sits on top of the booking system a hotel already runs, so whatever you teach for the front desk, keep teaching it. This is the other half of the day, not a substitute for the first.

What we are offering is the other half of the day. A group gets its own workspace and sets up a property from nothing: buildings, floors, room stock and the back-of-house rooms a floor plan forgets; department standards turned into checklists that open on a schedule; the services page the hotel sells from; the roles and permissions that decide who opens what; and the automatic replies a guest gets before a person steps in.

At the end the student has not watched a hotel being run. They have set one up, and they can say why they made each choice. That is a different graduate.

6. If you teach this

There is nothing to buy and no contract. Write to us with the name of your centre, the course you teach and roughly how many students are in a group, and we will open one workspace per group. Inna will answer you herself.