The guest arrival form asks the wrong questions to the wrong person

Most guest arrival forms are designed for the host's back-office.

The guest who opens that link, three days before the trip, isn't there to fill in a form. They're there to figure out what happens on arrival.

On r/airbnb_hosts someone was looking for a replacement PMS and listed the must-have features. A customizable Guest Arrival Form was at the top: collect every guest's name, expected arrival time, phone number, email, plus any need for cribs or sofa-bed sheets.

Reasonable list. Standard feature. Every serious PMS has it.

And yet, reading it, a different question naturally comes up: that form answers the host's questions. But what are the guest's questions in the 72 hours before check-in?

What the arrival form actually optimizes

The arrival form solves a real problem for the host: collecting information before arrival.

What time is the guest arriving? Who's in the group? Do they need anything specific? What's the best number to reach them?

This information is useful. Knowing the arrival time avoids waiting around all afternoon. Collecting names can help with internal management or local obligations. Asking about a crib or extra bed lets you prep the property in advance.

The problem isn't what the form collects.

The problem is what it assumes about the person filling it in.

A guest three days out from a trip is curious, maybe a little anxious. They're picturing the place. Checking times. Trying to figure out whether they've got everything under control.

Their questions are very concrete:

• how exactly do I get there?
• where do I park?
• what time can I really arrive?
• is there anything I need to bring?
• how does check-in work?
• will someone be waiting, or do I let myself in?
• what do I do in the first five minutes after I arrive?

The form answers none of this.

It asks the guest to provide information without giving back the information they're looking for.

Two different jobs at the same moment

Pre-arrival communication has two distinct jobs that are often confused.

The first is data collection.

It serves the host: expected time, group composition, special needs, primary contact. It's operational work and, in many cases, necessary.

The second is orientation.

It serves the guest: real directions, parking, access, hours, essential rules, what to do if they arrive and no one is there, what to expect in the first minutes.

To the host, both feel like part of the same moment: "pre-arrival".

To the guest, though, they're completely different experiences.

Filling in a form is a task.

Receiving clear directions is a relief.

When everything is squeezed into a single link that asks for data but doesn't orient, the guest gets only half the experience. And often not the half that matters most to them.

What happens when orientation is missing

The symptom is familiar to anyone who has handled even a handful of bookings.

The WhatsApp message at 6pm:

Hi, just wanted to confirm — where exactly is the entrance?

Or:

Quick question for tomorrow: is there parking near the property?

Or again:

What time can I arrive? The portal says from 3pm, but I'll be in the area from noon.

These aren't hard questions. They're not strange requests. They're not distracted guests.

They're the natural result of pre-arrival communication that asked the guest to provide information without giving them enough orientation.

The guest has a mental checklist that runs before the trip: time, route, parking, entrance, keys, access, contacts.

If those questions don't get answered proactively, they get answered reactively.

Usually the evening before arrival. Usually via WhatsApp. Usually when both host and guest have something else to do.

For anyone running multiple properties — or just multiple back-to-back arrivals — this traffic piles up fast. And it concentrates at the worst moment: the day before check-in, when there are already cleanings, access, schedules and surprises to coordinate.

The sequence that actually works

The problem isn't the arrival form itself.

The problem is what surrounds it.

A form that asks for arrival time and group composition can be useful. But the same form, embedded in an experience that first orients the guest, becomes much more effective.

The pre-arrival sequence that works looks like this:

• A personal link sent to the main guest a few days before arrival.
• Inside the link, the information the guest actually looks for: directions, parking, hours, access, what to do on arrival, any important notes.
• Only then, the questions the host needs: expected time, special needs, best contact, any operational data.

The form doesn't disappear. It just stops being the entire interaction.

The guest fills in what's needed more willingly, because they've already received something useful first. They don't feel they're facing an obligation. They feel accompanied.

The rule is simple:

Information first, data collection after.

The QR code on the fridge arrives too late

Many properties already have a digital guide, a PDF or a QR code printed inside the apartment.

Better than nothing, sure. But for pre-arrival it isn't enough.

The QR code on the fridge gets seen when the guest has already arrived. By then they've already found the way, parked, looked for the entrance, picked up the keys, maybe sent a message, sorted out their doubts.

To actually orient, the guide has to arrive earlier. Not when the guest is already inside.

Good pre-arrival communication isn't just "where do I find the information?". It's "when do I receive the information?".

Two or three days before check-in is often the right moment: close enough to be relevant, early enough to be useful.

How it works in StayFast

StayFast approaches the pre-arrival moment starting from the guest's orientation.

With the personal stay link, the guest doesn't just get a generic property guide. They get a Stay Hub tied to their stay: useful information, arrival, access, parking, operational notes and relevant content before they set foot on site.

That's the heart of the Fast and Boost plans: giving the guest one clear place to orient themselves before and during the stay.

Not a scattered PDF. Not a QR code seen too late. Not an endless WhatsApp message.

A personal link the guest can open while they're actually preparing the trip.

For hosts who also need to collect structured check-in data, documents or compliance information, that's a different job and belongs to the Flow tier. It's important not to mix the two.

Fast and Boost mainly help to orient the guest and make the stay smoother. Flow adds digital check-in and compliance when needed.

The sequence stays the same: first the guest needs to understand what to do. Then, if the process requires it, they can also complete the necessary data.

What changes for the host

When the guest arrives already oriented, the host's job changes too.

Fewer repetitive questions come in. Key information doesn't depend on the host's memory or hand-copied messages. The personal link becomes the reference point for the stay.

When the guest asks "where do I park?", "how do I get in?", "what time can I arrive?", the answer doesn't have to be rebuilt every time. It's already there.

This doesn't remove the human relationship. It improves it.

The host can focus on real requests, on surprises, on hospitality and service opportunities. Not on the same explanation repeated ten times.

Where to start

If you want to improve pre-arrival communication without changing everything at once, you can start with four simple actions.

1. Write down the three questions you receive most often before arrival

They're almost always the same: parking, time, entrance, keys, distance, essential rules.

Those questions are a map of the gaps in your current communication.

2. Write instructions for someone who's never been there

A lot of instructions are only clear to people who already know the place.

"Park in front of the green gate" can feel obvious to the host. But the guest might be arriving in the evening, with little light, on a street where there are three green gates.

Pre-arrival instructions need to be written for someone arriving tired, with their phone in hand and no familiarity with the area.

3. Send the information in advance

The right moment isn't when the guest is already in the car.

Two or three days before check-in, the guest is still organizing the trip. That's when the information is actually useful.

4. Keep the data collection short

The more fields you ask for, the lower the chance the guest completes everything.

Ask only for what really helps you prepare arrival. The rest can wait, or belong to a separate process if you have specific obligations around digital check-in or compliance.

The question that avoids almost all the mistakes

Look at your arrival form, your pre-arrival message or your current guide and ask yourself:

Does it give the guest more than it asks of them?

If the answer is no, that's the thing to fix.

The form isn't wrong. It just needs a counterweight: the information the guest is looking for, delivered before they have to ask.

A guest who arrives informed is a different guest from one who arrives with questions. The stay starts better. Reviews reflect it. And the host has one less message to handle at the most awkward moment.