All documents

Aparthotel, guest house, small hotel: what changes in the operations

How the operational work of a small property differs from a large one, what changes when stays are long, and how it works when there is more than one property.

Published

The difference between a hundred-room hotel and a six-room guest house is not how much happens. It is how many people know about it.

A large hotel has a department, a shift, and a handover. A small property rests on one or two people, and the administrator’s first bout of flu carries off half the knowledge of what is going on at the property. Which is exactly why a small property needs a system more, not less.

Below is what the shape of a property changes in the operations, and what it does not change at all.

What never changes

Checkout cleaning is raised by a confirmed departure and gets a named assignee and an exact hour. Cleaning is accepted by somebody who did not do it. A room’s readiness is derived from accepted work, and nobody has a switch.

Those rules are the same for six rooms and for a hundred. They do not soften on a small property — and that is their value: the administrator of a guest house is usually the very person who would flip a state by hand ‘just this once’.

Long stays: a rhythm instead of a departure

Aparthotels and guest houses live on long stays, and cleaning in them is tied to a rhythm rather than to a checkout.

  • Planned stay
  • In house
  • Checked out
  • Cancelled
A stay's states: booked, in house, closed and cancelled.

The in-stay cleaning interval is set for the property, and can be changed for a particular stay where the guest has agreed something else. After that the cleanings appear on their own.

One detail that matters on a property where nobody watches the calendar daily: if several intervals are missed, ATQAR does not produce a stack of overdue tasks. One missed cleaning appears. A stack of overdue work is a way of making sure the list stops being read.

Several properties: one organisation, one team

Properties live inside one organisation. A new property appears for the whole active team automatically — nobody has to be entered a second time.

An employee, meanwhile, sees their work rather than the properties: their list is their tasks across every property in the organisation at once, not a separate way in to each building. For somebody who cleans in one building in the morning and another in the afternoon, that is the difference between one screen and three.

The owner sees everything across all of their properties at once.

What to do when opening a new property

Create the property. Enter every room and check that the names match the plates on the doors — that is the one place where a mismatch is expensive: an employee finds a room by eye, not by an identifier. Check the in-stay cleaning rules. Check the employees’ roles. Confirm the first departure — the first preparation cycle starts from it.

There is nothing to migrate and nowhere to migrate it: a property’s history begins at the first confirmed departure.

What ATQAR does not take on, at any property

It does not sell rooms, does not hold rates and does not take payment. A stay carries dates, a guest and, where needed, a booking reference from your own system — the rest stays where you already run it.

More: Properties and rooms, Bookings and stays, Your first sign-in.