A booking comes in for Friday. The guest has a new profile, you have the name on the reservation and nothing else, and the building manager wants a name list for every arrival. Or the opposite: a guest writes that Airbnb says their identity is not verified and asks what to do. Either way, you are now the person deciding what to ask for, when, and where it gets stored.
This guide covers what Airbnb verifies on its own, what it deliberately does not give you, and a checklist for collecting what your operation needs before arrival.
Why this keeps turning into a scramble
When you had three units, a guest's details came in over a couple of messages. At twenty units the same thing happens twenty times, across Airbnb, Vrbo, direct bookings and email. Documents land in a message thread, a phone gallery or a shared folder. Nobody can say at 3 p.m. on Friday which of today's arrivals have sent theirs. The problem is the growth of the operation, not the guest: the request is the same every time, but it lives in someone's memory.
What Airbnb verifies, and what you do not receive
Facts below are from Airbnb's help center article "Verifying your identity on Airbnb", checked on October 2, 2026. Airbnb can change its process, so recheck before you rely on it.
- Airbnb states that every host, new co-host and booking guest must be identity verified to use the platform.
- To verify, Airbnb asks for details such as legal name, address and contact information, and, if needed, a photo of a government ID (driver's license, passport or national identity card) and possibly a selfie.
- If a guest does not finish by the deadline, the reservation is not confirmed. The deadline is 12 hours after booking, or 1 hour if check-in starts within 12 hours.
- Airbnb says it does not share the guest's government ID with the host when they book. You see the verified badge, not the document.
- A host may request government ID after booking only for qualifying legal or compliance reasons, with the requirement and reason disclosed in the listing before booking.
Airbnb's off-platform policy, checked October 2, 2026, allows additional contact or identity requirements only if they are needed for legal or compliance reasons (it cites local laws, HOA rules and building security rules) and can be verified by the host if Airbnb asks.
Two practical consequences. First, "Airbnb verified them" and "I have what my building, insurer or local rules ask me to hold" are different things; the second is yours to collect. Second, if a legal or compliance requirement means you will need ID, say so in the listing before the guest books. A request that appears for the first time after booking is the one guests push back on.
This applies to Airbnb. We have not checked how Vrbo or Booking.com handle verification for this article, so confirm on their help centers before assuming the same.
A checklist that works without any software
- Decide what you actually need, per property. Check the documented requirements for each property. For Airbnb bookings, request additional contact or identity information only under Airbnb's legal or compliance exception, and be prepared to substantiate the requirement. Confirm the contact information Airbnb already provides rather than routinely asking guests for new contact details. Do not invent requirements; if you are unsure what the law in your city or state requires, ask a local attorney or the authority itself. This article does not give legal advice.
- State it in the listing. Say what you will ask for and why, in two sentences, so it matches Airbnb's conditions for requests after booking: a legal or compliance reason, disclosed before the guest books.
- Send one request, at one time. Pick a fixed point, for example right after booking is confirmed, with a link to a single form. Not three messages across three days.
- Say what happens to the data. One line: who sees it, where it is stored, and when it is deleted.
- Follow up on a schedule. If the form is not back two or three days before arrival, send one reminder. If it is still missing the day before, a short message with a deadline.
- Keep a single place to look. A list of today's and tomorrow's arrivals with a yes or no for "details received". If you have to open five threads to build it, it will not get built.
- Decide the no-response rule in advance. What do you do with a guest who never sends it? Write the policy now so you are not improvising on arrival day, and make sure it matches what the listing says.
- Delete on a schedule. Remove documents once their purpose is served, according to the retention you stated in step 4.
Store only what you need
Photos of IDs are some of the most sensitive data your business holds. Collect the minimum the requirement calls for, keep it where only the people who need it can open it, and avoid copies in personal phones and email attachments. If a document is not required for a booking, do not ask for it.
Collection is not verification
A guest sending a photo of a document means you have received a document. It does not confirm the person is who they claim to be, and it is not a background check. Treat the two as separate steps and be clear in your own process which one you are doing. Airbnb's verification covers its own platform; for direct bookings there is no equivalent unless you add one.
How InnSync handles the collection part
The sequence in steps 3 to 6 is repetitive and time-based, which is why it is easy to automate.
InnSync sends the pre-check-in form automatically and follows up with guests who have not submitted it. For each new booking, your team gets an alert with a permanent link to the day's arrivals and the documents attached to each guest, so the Friday question ("who has sent theirs?") has one answer in one place. Documents and agreements sit in the same flow as the replies and the cleaning and check-in routines, next to the PMS you already run.
What it does not do: InnSync's document workflow collects documents and alerts your team. It does not verify identity or screen guests. What you require and how long you keep it remains your decision.
If you use Guesty, Hostaway, Hostfully, OwnerRez, Lodgify or Hospitable
- Guesty: InnSync connects to Guesty; reservations, units and guests arrive from it.
- Hostaway: Keep Hostaway. InnSync runs the operation around it — the connection is set up with you during onboarding.
- Hostfully: Keep Hostfully. InnSync runs the operation around it — the connection is set up with you during onboarding.
- OwnerRez: Keep OwnerRez. InnSync runs the operation around it — the connection is set up with you during onboarding.
- Lodgify: Keep Lodgify. InnSync runs the operation around it — the connection is set up with you during onboarding.
- Hospitable: Keep Hospitable. InnSync runs the operation around it — the connection is set up with you during onboarding.
During onboarding, confirm how bookings will reach InnSync and which document requests, reminders and team alerts will be ready for your first arrivals.
In every case the PMS stays your system of record for bookings.
Next step
See how the document workflow works at tryinnsync.com/us/use-cases/guest-documents-id, or start with the US overview.