---
title: "Checkout cleaning: who cleans the room, and at what time"
description: "How an administrator sees expected checkouts, confirms an actual checkout, and what happens to the resulting cleaning and its exact hour."
canonical: "https://atqar.com/en/docs/checkouts-and-cleaning/"
locale: en
language: en-GB
audience: administrator
published: 2026-08-03
updated: 2026-09-05
source: "https://atqar.com"
alternates:
  ru: "https://atqar.com/ru/docs/checkouts-and-cleaning.md"
  kk: "https://atqar.com/kk/docs/checkouts-and-cleaning.md"
  es: "https://atqar.com/es/docs/checkouts-and-cleaning.md"
  pt: "https://atqar.com/pt/docs/checkouts-and-cleaning.md"
  de: "https://atqar.com/de/docs/checkouts-and-cleaning.md"
  fr: "https://atqar.com/fr/docs/checkouts-and-cleaning.md"
  it: "https://atqar.com/it/docs/checkouts-and-cleaning.md"
  tr: "https://atqar.com/tr/docs/checkouts-and-cleaning.md"
  uz: "https://atqar.com/uz/docs/checkouts-and-cleaning.md"
  ky: "https://atqar.com/ky/docs/checkouts-and-cleaning.md"
  tg: "https://atqar.com/tg/docs/checkouts-and-cleaning.md"
---

This page is for administrators and owners. The day at a property starts here.

Checkout cleaning is carried out by a housekeeper — a cleaner, in everyday speech. In ATQAR that is a role rather than a job title.

## Before checkout: a safe forecast

The system creates a **checkout cleaning forecast** before an expected
checkout. It is neither a task nor a fact: it does not block the room, has no
assignee, and cannot be started. All housekeepers see forecasts across every
organisation property only for today and tomorrow: the room and expected time, with no position,
without the guest, stay, or booking reference.

If the checkout date is moved, the forecast moves to the new day without a
position.

During the property-defined period before an expected checkout, a **Confirm
checkout** task appears for a stay whose actual check-in has been recorded.
This is a persistent task, not a one-off message: it stays visible under
[**Important**](https://atqar.com/en/tasks/?view=attention) in Tasks until the checkout is
confirmed. An exact checkout confirmation resolves it.

## Confirm checkout

Checkout cleaning is created in only one way: by confirming checkout. It
is not created separately.

1. Find and open the relevant room under “Rooms”.
2. Select “Confirm checkout”.

The system immediately records the current server time and creates the
cleaning; no second confirmation is required. If checkout is being recorded
later and the actual time differs, select **“Checkout was earlier”** before
confirming. A future time is not allowed because checkout records something
that has already happened.

After confirmation, the forecast closes and one canonical cleaning is created.

ATQAR chooses an assignee and an exact hour for it straight away: a free
60 minutes inside a housekeeper's duty at that property. If the schedule has no
suitable hour, the cleaning is left without a time and says why.

> Product demonstration: Three answers to “when”: an exact hour, no duty to place it in, and work beyond the planning horizon.

Open the cleaning to review the plan. You can keep the chosen hour, or select
another employee and another slot by hand: the day and the hour stand in the
form as the **Date** and **Time** fields. A cleaning has no field of its own
for a deadline — this plan sets its time. There is no separate “urgency”
control on a task either: the mark appears automatically during the final two
hours before the deadline.

The card of assigned work looks like this:

> Product demonstration: Checkout cleaning: room, state, and assignee.

## If the cleaning already exists

Confirming checkout remains one action whatever state the room is in. If the
room already has an active preparation cycle, the system does not create a
second cleaning: it closes the named stay, records the confirmed departure on
that stay, and the room keeps waiting for the main cleaning already under way.
Open it. If blocking work takes priority on the card, find the main cleaning
in the room's recent task list. Do not create a second cleaning by hand;
change the assignee and the hour on the existing one.

## Where to assign work

There is no separate daily work order or Work order page. Open the cleaning
from the room card, task list, or calendar and review its plan. The deadline
and a guest preference remain separate task facts — the ‘Urgent’ mark appears
only during the final two hours before the deadline — and a card's visual place
in a list does not say which work to do first.

For a cleaning the assignee and the exact hour are one decision, not two. A
cleaning cannot be given to somebody with no duty covering that hour and that
property: change the [schedule](https://atqar.com/en/docs/duty-roster/) first. For every other
kind of work — a repair, an inspection, a replenishment — a duty restricts nothing.

If the schedule changes, ATQAR replans the cleanings it chose itself. A slot
picked by hand is never moved silently: that cleaning is marked as needing
attention so a person makes the decision.

The exact hour is planning rather than permission. It does not forbid starting
earlier, and it does not start the task by itself.

## Employees cannot see or select from a shared pool

There is no shared pool from which an employee claims work. A cleaning may
remain temporarily unassigned while an administrator allocates it. It becomes
that person's work only after it is assigned to them.

A housekeeper sees only their own tasks and shared safe forecasts for today and
tomorrow, without positions. Other people's work and unassigned work are hidden.

## Where to see the day's checkouts

See the day's checkouts in the [**Calendar**](https://atqar.com/en/docs/calendar/). Switch to
**Day** view and select a date to see that day's check-ins, checkouts, cleaning,
and other work.

## Cleaning during a stay

In addition to checkout cleaning, scheduled cleaning takes place during a
long stay. The system schedules it using the interval set for the property or
the stay itself (see [Stays and check-ins](https://atqar.com/en/docs/stays-and-calendar/)).

An administrator can also manually create a scheduled cleaning at a guest's
request or for a shared area. This is a task of the “Scheduled cleaning” type: it
has a work date, but is not part of a
particular stay's automatic rhythm. An assignee and an hour can be selected
immediately; if they are not, ATQAR chooses them from the duty schedule. A
manual task immediately receives the **“Ready to do”** status and does not wait
for automatic activation. It gets its exact hour by the same rules as a
checkout cleaning.

Such a cleaning can have a soft guest preference, such as a period from 10:00
to 18:00. It appears in the assignee's list and the task card,
but does not prevent work outside the period, is not a deadline, and cannot
make the task overdue. On the card for a cleaning that has not started, an
administrator can set a different period for that task only, remove the
preference, or restore the value from the stay. Changing the period on the stay
itself does not rewrite tasks that have started, are blocked, are under review,
or are complete.

An automatically created cleaning for a stay exists in advance as a regular
task in the administrator's **Scheduled** list. Once assigned, it appears
under the employee's **Upcoming** view
while its date is in the future, then under **Today** on and after its work date
until activation, cancellation, or loss of assignment. It cannot be started,
blocked, or submitted before automatic activation and is not overdue. However, **it does
not block the room**: the guest is staying there, and describing it as “not
ready” would be inaccurate.

Before an actual check-in is recorded, these cards remain plans only. If the
guest arrives later, the system recalculates the rhythm from the actual
check-in day: provisional dates before arrival are removed and do not become
“missed cleaning”. If several intervals are missed after check-in, they
collapse into one missed cleaning with the range displayed, rather than a
batch of old tasks.

The remaining future tasks stay **“Scheduled”** until the missed cleaning is first
submitted or explicitly cancelled as not carried out. The operational day of
that action becomes the new rhythm anchor. An administrator returning it for
rework does not create a second missed cleaning.

If background activation is delayed, the assigned employee sees the card as
temporarily unavailable and the administrator sees a persistent operational
alert. Do not create a replacement manually: wait for reconciliation or
investigate the displayed exception itself.

The **work date** says on which day the cleaning should be carried out. **“Due
by”** is a separate hard deadline. Its absence does not mean there is no work
date, and a guest preference does not become an overdue condition.

An administrator can move the **work date** of an automatically created
cleaning within the stay. The following cleaning tasks in the same schedule
that have not yet started move with it, while the assignee remains. If a
cleaning is missed, later dates are recalculated
once from the missed day, and after it is carried out on another day, from the
actual cleaning day. The system does not silently move work that has started,
is blocked, or is under review.

If a cleaning with a past work date is cancelled as not carried out, the system
retains the first day after its work date as the missed day. A late
cancellation does not shift the schedule again, and the cancelled task is not
restored automatically.

Background reconciliation after moving a cleaning or changing a schedule
usually takes a few seconds. If the system asks you to refresh data while
cancelling or reopening, refresh the page and repeat the action. This prevents
it from changing a stale schedule remainder.

## Close a stay when confirming checkout

If a room has an actually active stay or one awaiting resolution, the form
shows the **exact stay that will be closed**: the guest's name, the booking reference
when present, and the dates. This is not a formality. Even if checkout
is late and outside the planned dates, the system closes the specified record
instead of guessing from the calendar day.

A stay with the “In house” status cannot be cancelled: cancellation would
release nights while the guest is still in the room. If only the real check-in
time is wrong, use **“Correct check-in time”**. If the guest never checked in,
use the rare **“Guest did not actually check in”** action. If the guest actually
left, do not remove check-in or cancel the stay. Confirm checkout for the record
shown; a date warning does not block this action.

Checkout confirmation can close an active stay even when the administrator
forgot to record check-in separately. The checkout fact takes priority over a
missed arrival action.

Closing releases nights from the checkout day onwards: if the guest leaves
early, the room is available that same day. The recorded dates do not change,
so the discrepancy shows that checkout was earlier than planned.

If the wrong stay is shown or the details have changed, do not confirm another
record by guesswork. Refresh the room and correct the stay. The server requires
an exact identifier and will not create a cleaning while leaving the actually
active stay open.

Next: [Preparation cycles and correcting mistakes](https://atqar.com/en/docs/cycles-and-corrections/).