Build guest reporting into your letting operation

Organise accommodation guest reporting through responsible roles, required information, accepted communications and privacy-aware procedures, using official sources.

Guest reporting is a separate operating responsibility from registering a tourist dwelling or publishing an online listing. It concerns the required information about bookings, stays and travellers, and the communication of that information through the relevant procedure. A clean property and a successful check-in do not demonstrate that the reporting work has been completed.

The starting points are the Interior Ministry’s accommodation portal and Royal Decree 933/2021. Apply their scope and instructions to the actual arrangement. Do not assume that every residential tenant must be processed as a holiday guest or that an occasional host has no reporting responsibilities simply because the activity is small.

Identify the activity and responsible person

Describe the accommodation service, operator and booking route. Decide who is responsible for each reporting task and who is authorised to act. If a manager or technology provider transmits information, document the arrangement and retain access to confirmation records. Do not assume that the booking platform, keyholder and cleaning company have silently divided the work between them.

The landlord preparation guide helps establish the operating roles. Ask the adviser or responsible authority to resolve any uncertainty about whether the accommodation falls within the reporting framework. Its professional and non-professional distinctions should not be replaced by a guess based solely on the number of properties an owner holds.

Set up the official route before the first stay

Use the official ministry destination for platform access and instructions. Check the establishment information and who controls the credentials. Establish a backup contact and a process for staff absence. Keep credentials out of shared guest documents and make sure a former manager’s departure does not leave the owner unable to access records needed for the continuing operation.

The ministry describes communications tied to reservation or contract events, cancellation and the beginning of the service, with an immediate communication requirement and an outer 24-hour limit for the relevant events. Build those events into the operating checklist. Do not design the process around a single weekly upload or assume that reporting is only a task at arrival.

Collect the required information without collecting everything

Map the fields in the current official procedure to the information you request from guests. Explain the purpose clearly and use a suitable secure channel. Do not create a broad form asking for unrelated information because it might be useful later. If the official system changes, review the form and staff instructions together rather than adding another informal data request.

The AEPD’s accommodation note says hosts should not request copies of identity documents for this purpose: copying a full DNI or passport collects excessive information. Verifying identity and collecting required details are different from retaining a document image. Review remote check-in software rather than assuming that every feature offered by a supplier is necessary or appropriate.

Make the booking-to-arrival handover explicit

Record the booking reference, responsible staff member and next reporting event in the operating workflow. Ask how changes in names, dates or guest numbers reach the reporting person. A change accepted by the reservations team must not remain invisible to the person maintaining the official record. Keep the workflow usable for a late booking as well as an ordinary advance reservation.

Connect the process with the inventory and arrival handover, but do not combine identity information with a general maintenance photograph folder. Staff checking a broken appliance rarely need access to guest identification details. Separating the records helps limit access while still allowing the people responsible to carry out their particular tasks.

Check submission results, not just the send button

Keep evidence that the relevant communication was accepted, together with a clear record of any rejection or correction. A screenshot showing a prepared form does not establish successful receipt. Decide who reviews failed submissions and how quickly an unresolved problem reaches the operator. Do not leave the task dependent on an unattended email account.

Suggested internal status labels are prepared, submitted, accepted, correction required and resolved. These are workflow labels rather than official legal categories. The landlord records guide helps organise the accompanying evidence. Avoid displaying personal details on a shared whiteboard or a spreadsheet circulated to people who only need to know that the administration is complete.

Plan for cancellations and changes

Agree how a cancellation, amended stay or replacement guest triggers a review of the relevant record. Keep the original event and subsequent correction understandable without retaining unnecessary duplicate data. If a booking is moved to another property, check that the information concerns the actual establishment and service rather than copying the previous address into a new form.

Where a supplier handles the transmission, ask how you can retrieve the acceptance and correction history. Test that route before a problem occurs. Do not treat the supplier’s invoice as evidence that every individual booking was communicated successfully. A clear reconciliation between bookings and relevant accepted communications provides much stronger operational oversight.

Retention depends on the applicable role

Article 5 of the decree sets a three-year retention period for the computerised register within its scope and an exception to those register and retention duties for non-professional activity, while retaining communication obligations. Obtain advice on the category and records applicable to the actual operation. Do not impose one guessed retention period on every dataset held by the manager.

The property data-protection guide helps frame access, purpose and record-management questions. Distinguish a statutory record from a commercial guest-contact list, a damage photograph and payment evidence. Information collected to comply with reporting duties should not automatically become a marketing database or be retained indefinitely because storage is cheap.

Check the service provider’s responsibilities

If a manager promises guest administration, specify which events and records that covers, who receives official messages and how errors are corrected. Ask about access controls, staff training and the end of the contract. The manager comparison guide gives a broader way to compare accountability. Obtain specialist advice on the appropriate data-protection terms for the arrangement.

Keep guest reporting separate from Andalusian tourism registration and the national registration framework. A number in one system does not show that traveller communications were made in another. Name the system and evidence whenever a manager reports that registration is complete.

Questions to test before going live

Can a new staff member identify the reporting person? Do booking changes reach that person? Can an accepted communication be found without circulating guest identity data? Is there a procedure for rejection, staff absence and loss of system access? Test those questions with a fictional booking and clearly labelled test material rather than using real guest records unnecessarily.

Does the booking platform handle everything? Establish the actual arrangement and applicable responsibilities. Keep evidence of the work performed instead of relying on a general platform description.

Should I email passport copies to make check-in faster? Do not use routine document copying as the solution. Follow the AEPD guidance and an appropriate method of verifying the required details.

Is this a substitute for current ministry instructions? No. Use the live official procedure for the required fields and events, and seek advice where the operation’s scope or role is uncertain.

An operating rehearsal

Use a clearly fictional reservation to rehearse who receives an enquiry, confirms the booking, records a change and checks the reporting status. Do not submit invented traveller information to an official production system. The rehearsal is an internal discussion of the workflow, or uses an explicitly authorised test facility if one is available. Include a late arrival and staff absence so the team can see where responsibility might be lost. Correct the operating instructions before relying on them for a real stay.