Hotel online check-in: what to ask guests before arrival

Hotel online check-in is a form or guest-app page a guest completes before arrival so the desk already has the arrival time, the names, the requests and the invoice details. It saves typing, not the identity check: under Turkish law (Law No. 1774), hotels must verify identity in person, and the specific legal requirements for document handling should be confirmed with your legal adviser. In practice the document is checked at the desk.

It is 23:40. The guest has already typed their name, address and company tax number into your pre-arrival form. At the desk they are asked for all of it again, because the answers went to an inbox nobody opened that evening. This happens in hotels every night, and it is a design failure, not a staffing one. After reading this you will know which questions to move before arrival, which checks must stay at the desk, and how to keep the whole form inside the law.

What can online check-in replace at the front desk, and what can it not?#

It replaces the questions, not the checks. A pre-arrival form moves data entry to the guest; the identity check, the key handover and the payment decision stay at the desk.

Define the thing once. Online check-in is a page the guest opens from a link or from the hotel's own guest app before arrival, fills in, and whose answers land on the reservation the desk already opens. That last part is the whole point: if the answers land anywhere else, an inbox, a spreadsheet, a PDF, the form has failed before the guest arrives.

What it genuinely replaces: typing a name letter by letter while a queue forms, asking when the guest expects to arrive, collecting invoice details, and capturing requests before rooms are assigned. What it does not replace: verifying the identity document in person, handing over the key, taking or confirming payment, and the conversation that sells an upgrade.

The trade-off is real. A long form shifts work onto the guest and increases the personal data the hotel holds; a short form saves less desk time but is easier to justify and easier to keep accurate. Test every field with one question: which question at the desk does this field remove? If there is no answer, the field is decoration and should be deleted.

The form must stay optional. A guest who did not fill it in, or filled it in wrongly, is still a guest, and the desk must be able to complete the arrival without it. A hotel that treats the form as a gate creates a queue at exactly the moment it was trying to avoid one.

The record duty survives the form. Under Law No. 1774 (Article 2) (opens in a new tab) (mevzuat.gov.tr, consolidated text, 2026), operators of hotels, motels, pensions, holiday villages, campsites and similar lodging places keep the identity and arrival-departure records of everyone who stays, local or foreign, day by day in the prescribed form, ready for inspection at any time. And in Türkiye every stay involves a payment, a fiscal document, a guest identity notification (KBS, misafir kimlik bildirimi) and personal data (KVKK); the form is a front end to those steps, never a way around them. If you are rethinking the whole arrival, not just the form, start with designing the guest journey stage by stage.

Which fields are worth asking for before arrival?#

Ask for what changes what the hotel does before the guest walks in, and for what the desk would otherwise type while the guest waits.

The expected arrival time is the most useful field, ideally as a window rather than a precise minute. It lets housekeeping sequence rooms and lets the desk plan the evening. It is also the field guests most often get wrong when asked too early, which is why the timing of the form matters as much as its content.

The names of everyone staying, typed by the guest, remove the letter-by-letter exchange at the desk. They do not remove the document check, which still happens in person for each guest. A phone number reachable on the day of arrival should be described as such: say plainly that it is for the arrival, not for marketing, and mean it.

Requests belong on the form only if the hotel can act on them: a cot, a high floor, a late dinner, a quiet room. Do not offer a free-text box that no team reads; an unanswered request is worse than an unasked one. Invoice details belong on the form because they are the field most likely to hold up a departure. A marketing choice sits separate from everything else and unticked by default, so that a guest can finish check-in without agreeing to anything.

Fields to leave for arrival#

Should you ask for billing details and payment before arrival?#

Yes for the invoice, and only through a secure payment link for the payment. Card numbers never travel by email or through an open form.

Billing details: personal or company#

Ask one question first: personal bill or company bill. If company, ask for the registered company name and tax details exactly as the guest's accountant will use them, because a wrong tax number means the invoice is reissued after the guest has gone. Keep the invoice block short: a company bill does not need a home address, and asking for one is data the hotel has no purpose for. Confirm the tax treatment and document types with your own accountant rather than promising them in the form.

Payment guarantee: a link, never a card number#

Payment or a guarantee goes through a link to a payment page run by a provider the hotel has a contract with. The hotel sees a result, not a card number, and the guest sees the provider's page, not the hotel's form.

Never ask for a card number, a security code or a photograph of a card in a form, an email or a messaging app. If a guest sends one unasked, do not store it; tell them it will not be used and send the link instead. Say what the link does in one sentence: whether it takes payment now or only guarantees the booking, and what happens if the guest does not complete it. Do not promise how long a hold lasts; that depends on the provider and the card.

The same rule applies to extras. An upgrade accepted before arrival goes onto the guest's bill as a charge, and the guest should be able to see that it did.

Does online check-in remove the identity check at the desk?#

No. Identity is verified in person at the desk, and the facility keeps the identity notification record.

The duty is on the facility, not on the guest's typing. Law No. 1774 (Article 9) states that those obliged to file identity notifications may not accommodate anyone who cannot prove their identity with an identity card or another valid official document (mevzuat.gov.tr, consolidated text, 2026 (opens in a new tab)). So the guest should be told, in the form itself, to bring the document they will check in with. One line, in the guest's language, saves an argument at midnight.

The guest identity notification (KBS) is prepared at check-in from the document in front of the receptionist. A name typed into a web form is not that document. Whether a remote or online identity capture could ever satisfy the duty is not something this article asserts; the safe operating assumption is that the document is checked in person, and any change to that should be confirmed with your legal adviser.

Do not build a habit of photographing or copying identity documents. Whether and how a copy may be kept is a question for your adviser, and the minimum-data principle applies to documents as much as to form fields. Train the desk on the sequence: greet, verify the document, confirm the details the guest already sent, hand over the key. The form shortens step three, not step two. For the full sequence at the desk, see a front desk checklist for guest identity at check-in.

How do you keep the pre-arrival form inside KVKK?#

Ask only what the stay needs, tell the guest what you will do with it, and keep the marketing choice separate from the notice.

KVKK (kişisel verilerin korunması kanunu, Law No. 6698) applies to a five-field web form exactly as it applies to the front desk. Article 4 requires personal data to be processed for specified, explicit and legitimate purposes and to be relevant, limited and proportionate to those purposes (mevzuat.gov.tr, Law No. 6698, 2026 (opens in a new tab)). Every field you deleted in the checklist above was also a data-protection decision.

Article 10 sets the notice: who the data controller is, why the data will be processed, to whom and why it may be transferred, the method and legal basis of collection, and the guest's rights. Short is acceptable; missing is not. Article 6 treats data on health, religion or belief, dress, and biometric and genetic data as special categories, prohibited except in the cases the law lists, such as the person's explicit consent. A dietary or medical note collected before arrival can fall into this group, so ask for it only if the kitchen will act on it, and handle it deliberately.

The Personal Data Protection Board's decision 2026/347 (Official Gazette 24 March 2026, No. 33203) requires the privacy notice and any explicit-consent text to be prepared separately: one page, different headings, one below the other, with separate declarations. No consent text where processing rests on another legal ground, and nobody is asked to approve the notice itself.

Notice, consent and the marketing box#

Marketing is its own box, unticked, and never a condition of check-in. A guest who leaves it empty is still checked in, and the form should say so. Decide how long the answers live and make the system delete them; a form that keeps everything forever is a liability with a nice interface. Confirm the retention periods with your adviser. Keep the notice in the guest's language or provide a version they can read; a notice nobody understands is not a notice.

When should the form go out, in which language, and what does the desk see?#

Send it once, early enough to be acted on and late enough to be accurate, in the language the guest booked in, and make the result one line on the reservation the desk already opens.

Timing is a trade-off, not a setting. Sent too early, the arrival time is a guess; sent too late, housekeeping cannot use it. Tie the form to the booking confirmation and add one reminder close to arrival, rather than three messages nobody opens. If you are building the surrounding message sequence, what to send in pre-arrival emails and when covers the timing in detail.

Use the language of the booking, not the hotel's default. A form the guest cannot read collects wrong data and generates a support message in a language your team may not cover. One link, no account: a guest should not create a password to answer five questions, and every extra step loses answers.

What the desk sees matters more than what the guest sends. A short summary on the reservation card, not a PDF in a shared inbox; if the receptionist has to open a second system to find the arrival time, the form has failed. The desk still owns the arrival: greet, verify the document, confirm the requests were understood, hand over the key. The form should make that sequence faster, not remove the human from it.

Measure one thing: how many arrivals still need a question answered at the desk. That single count tells you whether the form is doing its job, and it needs no dashboard.

What to do next#

Print your current pre-arrival form, or the one you are about to build, and write next to each field the desk question it removes. Delete every field that has no answer. Then check that the notice and any consent text sit separately, under different headings, and that the marketing box is unticked. That single pass connects everything in this article: the form is a short list of questions moved earlier, the identity check stays at the desk, and the data you collect is only what the stay needs.