A booking confirmation is not always enough to meet your reporting duties. What guest details are mandatory depends on where the property is located, who is staying, the type of accommodation you provide, and which authority requires the information. For a host with one holiday let, that can feel unnecessarily complicated. For a manager handling dozens of properties, it can quickly become a daily operational risk.
The practical answer is simple: collect only the information your applicable rules require, collect it early enough to submit it on time, and keep an auditable record for the required retention period. The detail sits in knowing which fields apply to each booking.
What guest details are mandatory?
There is no single guest-data checklist that applies to every short-term rental across Great Britain and Europe. National rules, local authority requirements, tourism reporting systems and accommodation registers can all set different obligations. Requirements may also change according to whether a guest is a UK resident, an overseas visitor, an adult or a child.
In many accommodation-reporting systems, the required record starts with the lead guest’s full name, date of birth, nationality and arrival and departure dates. Authorities may also require a document type, document number, issuing country, place of residence, number of guests, property address or a booking reference.
Some jurisdictions require details for every person staying, not just the person who made the booking. Others accept a lead-guest record alongside the party size. A local tourist tax declaration may require the number of taxable nights and guest exemptions, while a police or immigration-related register may require identity-document information for certain international travellers.
That distinction matters. A field that is useful for your internal operations is not automatically mandatory for government reporting. Equally, a booking platform’s standard guest information may not be enough for an official guest book.
Separate booking data from compliance data
Most hosts already capture contact details to manage a stay. The guest’s name, email address, telephone number, payment status and arrival message are normal booking data. They help you communicate with the guest, but they may not meet a statutory reporting requirement.
Compliance data is the information a public authority specifically requires you to register, submit or retain. It may include identity, nationality, residence, travel dates and occupancy details. The exact fields and submission timetable are prescribed by the relevant scheme, not by your channel manager or online travel agency.
Keeping these two purposes separate helps you avoid two common problems. The first is under-collection: assuming an OTA reservation contains every field required by the local authority. The second is over-collection: asking guests for passport scans or personal details that are not necessary for your legal obligation.
Under UK GDPR, the principle is data minimisation. Collect information because you have a clear purpose and legal basis, not because it might be useful later. If your local rules require a passport number, record it securely. If they only require nationality and dates of stay, a passport image may create unnecessary privacy and security exposure.
The fields you may need to collect
Your required fields should be configured by property location and reporting regime. In practice, the information commonly requested falls into four groups:
- Guest identity: full legal name, date of birth, nationality and, where required, sex or place of birth.
- Travel document details: document type, number, issuing country and expiry date where the applicable authority requires these fields.
- Stay information: date and time of arrival, planned departure, number of nights, purpose of stay and party size.
- Property and reporting information: accommodation address, property registration number, host or operator details, booking reference and tourist-tax status or exemption.
Not every field in that list will apply to your property. For example, a rural cottage in one area may need only a guest-book entry and periodic occupancy declaration, while a city-centre serviced flat may have separate visitor-tax reporting. A portfolio spread across countries can involve several different data sets and deadlines.
Children need particular care. Authorities often require a count of minors, their age category or full guest details, but a child’s data should never be collected casually. Follow the fields set by the authority, make the purpose clear to the booking guest and restrict staff access to the record.
When should you request guest information?
The best time to request mandatory details depends on the submission deadline. If records must be filed before arrival, asking for data at check-in is too late. If the authority requires an arrival-day or next-day submission, a pre-arrival form gives you time to validate missing fields and send reminders.
For direct bookings, make the request part of the booking journey or automated pre-arrival process. Explain that the information is required to meet accommodation-registration obligations, specify who must complete it and state when it is needed. Clear wording reduces guest resistance and prevents awkward check-in conversations.
For OTA and property-management-system bookings, map the data you receive against the fields you must report. Online travel agencies often protect guest contact information or provide only lead-booker details until a defined point in the reservation. You may need an additional guest-registration step to fill the gap.
Do not rely on staff to spot missing information manually across emails, messages and spreadsheets. A missed document number, incorrect nationality or unconfirmed arrival date can stop a submission from being accepted and leave you chasing guests at the last minute.
Accuracy matters as much as collection
Mandatory data that is incomplete, mistyped or submitted late can still create a compliance issue. Build in simple checks: use required fields, date validation, country lists and document-number rules where relevant. Ask the guest to review their own information before they submit it.
It is also worth defining who owns the task when bookings change. Cancellations, no-shows, early departures, extensions and guest substitutions can all affect the record you need to submit. In a managed portfolio, the property owner, local co-host and central reservations team may each assume somebody else has updated the authority record.
A connected workflow avoids that uncertainty. Booking changes should update the guest record, trigger the relevant reporting action and leave a clear history of what was submitted and when. This is particularly valuable where different properties follow different local rules.
How long should mandatory guest records be kept?
Retention periods are set by the authority and can vary. In accommodation compliance, guest books and supporting records are commonly retained for three to five years, but you should confirm the rule that applies to your property and reporting scheme. Keep records no longer than required unless another legal obligation, such as tax or dispute management, justifies a separate retention period.
Secure retention is not just a storage question. You need to be able to find a record during an inspection, show that it was submitted on schedule and limit access to authorised people. A shared inbox, paper file or unmanaged spreadsheet makes that much harder, especially when staff change or a portfolio grows.
Use role-based access, encrypted storage and a defined deletion process. Keep an audit trail for changes, submissions and corrections. If you use a third-party system, check that it supports GDPR-compliant processing and that your records remain available for the full period you must retain them.
Make compliance part of the booking flow
The most reliable approach is to treat guest registration as a standard stage of every reservation, not an admin task saved for check-in day. Capture the right fields from direct bookings and connected channels, validate the information, submit it on the applicable schedule and archive the guest book automatically.
GuestAdmin is designed for this exact workflow, bringing reservation intake, guest data collection, authority submissions and secure records into one cloud-based process. That means less re-keying for independent hosts and clearer oversight for multi-property managers, without requiring a separate system for every booking source.
The right mandatory guest details are the details your property is legally required to report – no more, no less. Once those requirements are configured around each property, compliance becomes a controlled routine rather than a last-minute chase before every arrival.