> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/getting-started/daily-workflow.md).

# Daily shift workflow

## Start of shift

1. Sign in with your own account and confirm the selected property.
2. Read urgent and ongoing tasks on the Reception Notes board.
3. Check dirty, out-of-order and renovation units on the Room Status Board.
4. Review today's arrivals and departures in the Stay Calendar and reservation list.
5. Consider late departures together with rooms scheduled for another arrival on the same day.

## During the day

Record new bookings using the [reservation workflow](/en/daily-operations/reservations.md). Check arriving guests into their existing reservation instead of creating a second booking. Use the reservation's room-change operation when moving guests. Add extra services to the correct reservation folio.

Update the cleaning status when cleaning is complete. Never mark an unprepared room as Clean merely to get past a validation message.

## At departure

1. Open the [pre-check-out folio](/en/daily-operations/check-in-out.md).
2. Review accommodation and service charges, payments received, refunds and security deposits separately.
3. Complete any required records within your permissions.
4. After confirming check-out, verify the stay and room status.
5. Leave a reception note if the room needs preparation.

## Handover

Clearly record unfinished tasks, expected arrivals and balances requiring follow-up. If you have access to shift and cash reports, compare recorded cash movements with the cash actually counted. Sign out when your work is finished.

Related guide: [Reception notes](/en/daily-operations/reception-notes.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.interaktifotel.com/en/getting-started/daily-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.