Date changes into the PMS and channel manager, once

The question this file answersHow many hours a day does my front desk spend moving nights around in the PMS and re-sending confirmations?

Fits: hotels and small groups where 15–25% of bookings come back modified (hospitality playbook) and changes still arrive as free-text email or OTA messages; in the composite, a group of five properties.

Not for: properties where guests already change and cancel through a self-service link tied to the PMS — the desk retype is not your cost.

Typical day

What the desk looks like today

Typical, from the hospitality playbook — not a client's day. Somewhere between one booking in six and one in four comes back changed: a night moved, a cancellation. The guest writes by email or through the OTA inbox; whoever is on the desk checks availability, reads the rate plan's cancellation terms, changes the reservation in the PMS, updates the channel manager and sends the confirmation. It hurts in high season, and more once the receptionist who knew the rate plans by heart has left — in hospitality, that is common.

What changes

What Monday looks like after

The morning after a full weekend. The desk opens a short list — a wedding party moving a block of rooms, a guest wanting a refund the rate plan does not allow, a name your manager flagged — instead of an inbox where every subject line begins "can I change". The straightforward date moves were made in the PMS overnight; the channel manager shows the same availability; confirmations sent. Receptionists are at the counter with the people in front of them — what left is the retyping, not the staff. Hospitality Technology (2023) puts cancellations and changes at 2–3 staff hours a day; expect that to be where the time comes back.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~35–50%

less front-desk workload — Cloudbeds (2023)

Before: front desks report 2–3 staff hours a day on cancellations and changes (Hospitality Technology, 2023). After: Cloudbeds (2023) reports 35–50% less of that workload with automated modifications — groups and comps stay a person.

Where this number comes from

Cloudbeds "Property Management" (2023) reports that automated booking modifications reduce front-desk workload by 35–50%; Hospitality Technology "Lodging Technology Survey" (2023) puts cancellations and changes at 2–3 staff hours a day. Industry figures, not our measurement. Playbook range for this process: 40–60%.

What we install

What we put in front of the systems you already run

Your PMS stays where it is — Opera, Mews, Cloudbeds, Protel or the one you run — and so does the channel manager: SiteMinder, RateGain, D-EDGE or equivalent. Between them and the inbox we put a checking step:

each message is sorted — date change, room change, cancellation, other
the request is checked against live availability in the PMS and the rate plan's cancellation terms
a change that passes both is written into the PMS through its API and pushed to the channel manager, confirmation in the guest's language
anything outside policy — a group, a compensation request, a flagged guest — goes to a person with the thread and the broken rule.

First scope: the change types your desk sees most.

What stays human — and what this will not do

Anything outside policy. Group changes. Compensation — deciding what a guest is owed. The guest whose name your manager knows.

What can go wrong — and what we do about it

If the cancellation terms live in people's heads rather than per rate plan in the PMS, the first weeks go on writing them down: audit work. Smaller properties often run the channel manager by hand; without an API on either side, changes reach the PMS by the vendor's own import or by a screen-level bridge; that is slower and needs IT time. Two guests asking for the same last room is a race the system must lose — it holds and asks. The Cloudbeds 35–50% is front-desk workload; groups, compensation and high-value guests sit outside it.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we gather a month of changes and cancellations, count them by channel and rate plan, and check whether your PMS and channel manager expose an API the vendor allows. Pilot, 3–5 weeks — medium complexity in the hospitality playbook (€10–20K): one property, in-policy date and room changes only, every automatic change visible to the desk the same day. Production: the other properties, then cancellations with refunds. From you: the cancellation terms per rate plan, written down.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…

Do date changes and cancellations reach you as free-text email or OTA messages?
Does someone retype each change into the PMS and then again into the channel manager?
Are your cancellation rules written down per rate plan, not remembered per receptionist?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map an ops process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Ops.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files