Guest ID registration Dubai operators assume Airbnb or Booking.com already handles — it doesn't. DTCM guest registration is a separate, ongoing obligation that sits with the DET permit holder, not the platform processing the booking. I run nine units across Dubai, and this is the compliance line item that's easiest to get right on unit one and quietly let slip by unit five, once check-ins stop being something you personally handle every time.
Why This Sits With You, Not the Platform
A booking confirmation from Airbnb or Booking.com tells you a guest paid and has dates. It doesn't tell DTCM who actually walked into the unit. Those are two different records, kept for two different reasons — the platform's is commercial, yours is regulatory. Licensed holiday home operators in Dubai are required to log guest identification for every stay under their DET permit, the same underlying principle hotels have operated under for years, extended to holiday home units. If your check-in process only produces a platform confirmation and nothing else, you don't have a guest registration record — you have a receipt.
What Actually Has to Happen at Check-In
Operationally, this means capturing passport or Emirates ID details — full name, ID number, nationality — for the guest at the point of check-in, not the point of booking. Across our nine units, six run self-check-in with a digital ID step built into the pre-arrival messaging, and three still do meet-and-greet, where we collect it in person. Both work. What doesn't work is treating it as optional for "just a quick trip" or a returning guest — the requirement doesn't have a frequent-flyer exemption.
The exact current portal, timing window, and submission mechanism are the kind of procedural detail that shifts, and getting that wrong carries real compliance risk. I'm not going to reconstruct that from a blog post — confirm the live process with DTCM or a licensed compliance consultant before you assume last year's steps still apply, especially if you're onboarding a new unit.
What to Actually Capture at Check-In
Whatever the submission mechanism turns out to be for your permit, the underlying data you need from the guest doesn't change:
- Full legal name, matching the ID document exactly
- Passport number (or Emirates ID number for UAE residents)
- Nationality
- Dates of stay for the unit
The mistake I see most often isn't missing fields — it's a name typed differently than it appears on the document, because someone rushed it standing in the doorway with luggage in the hall. Build the collection step so it happens before the guest is physically at the door, whether that's a pre-arrival form or a self-check-in kiosk step, and you remove most of the transcription errors along with most of the friction.
Digital Collection vs. Manual Collection
Both formats satisfy the same underlying obligation, but they hold up differently at scale. On our six self-check-in units, the ID step is baked into the same digital flow as the door code and the screening check — one link, sent once, before arrival. On the three units we still run meet-and-greet on, it's collected face to face and logged manually afterward. The meet-and-greet units are noticeably more exposed to the "we were busy, we'll log it later" failure mode, because "later" competes with turnover, guest messages, and everything else that day. If you're weighing which check-in style to run on a new unit, that's a real point in favor of self-check-in beyond the labor savings — it forces the compliance step to happen at a fixed point in the flow instead of depending on whoever's holding the keys that day.
Building It Into a Multi-Unit Check-In Flow
The failure mode I've actually watched happen isn't an operator deciding to skip guest ID collection — it's the process working fine when you're personally handling every check-in, then quietly falling apart once a cleaner, a co-host, or a third check-in agent is involved and nobody's confirming the step actually happened. That's exactly the same operational blind spot as guest screening — which is why we run both as one combined check-in step rather than two separate ones that each depend on someone remembering. If you're past two or three self-managed units, this is one of the first tasks worth handing to whoever owns your day-to-day operations, because "whoever's free at check-in" isn't a system.
How This Fits Into Your Wider DET Compliance Stack
Guest ID registration doesn't replace or reduce anything covered in our DET holiday home permit guide — it sits alongside it. The permit gets the unit licensed to operate; guest registration is part of staying compliant once it is, in the same bucket as the DET-compliant insurance most standard home policies won't cover. Owners tend to treat the permit as the finish line because it's the step with the certificate at the end of it. It isn't — it's the entry ticket to an ongoing checklist.
Where Extended Stays Complicate the Picture
This gets genuinely confusing once a booking stretches into medium-term-rental territory. A 21- or 28-night Airbnb stay still needs the same guest ID registration as a 3-night stay — the obligation doesn't taper off with length of stay. Where it gets more complicated is if that guest later wants to convert to an Ejari-backed contract, which is a different legal instrument with its own documentation requirements entirely. We cover that handoff — and where owners get exposed by treating a long booking and a proper MTR contract as the same thing — in our MTR conversion and Ejari guide.
Common Questions on Dubai STR Guest ID Requirements
Does Airbnb or Booking.com handle guest ID verification for me?
No. Platforms may run their own identity checks for account or payment purposes, but that's separate from your obligation as the DTCM-licensed operator to maintain your own guest registration records for the unit.
Do I need to collect ID for every guest, or just the booking lead?
Treat it as every guest, not just whoever's name is on the reservation. The specific scope for your permit type is worth confirming directly with DTCM rather than assuming from general guidance, since requirements can vary.
What happens if guest registration isn't maintained properly?
Beyond general risk to your permit standing, missing records tend to surface at the worst possible moment — a dispute, an incident, or an audit — rather than in the ordinary course of business. That's exactly why it's worth getting right before you need it, not after.
Does this apply to owner-operated units the same as management-company-run units?
Yes. The obligation sits with the DET permit holder, whether that's an individual owner running their own unit or a licensed operator managing it on someone else's behalf. Outsourcing the day-to-day check-in doesn't outsource the compliance responsibility.
How long do I need to keep guest ID records on file?
Retention periods are another detail to confirm directly with DTCM for your current permit type — this is not something to guess at, given the compliance exposure if you delete records before you're supposed to.
Does a medium-term or extended-stay booking need the same guest ID registration?
Yes — length of stay doesn't change the obligation. A 28-night booking still needs guest ID registration on the same basis as a 3-night one, separate from whatever happens later if that stay converts into an Ejari-backed contract.
What if a guest refuses to hand over ID at check-in?
Then you don't have a compliant check-in, and that's a conversation worth having before arrival, not at the door. Set the expectation in your pre-arrival messaging so it's never a surprise on either side.
Setting Up Your Check-In Process?
We build guest ID collection into the same check-in flow as our screening process across every one of our nine units — happy to walk through how we've structured it if you're setting this up for the first time or trying to fix it once it's already slipping. Get in touch here.
