Mobility

Measuring the Quality of Your Hotel's Transfers Without Complicated Tools

A few questions asked after each ride, a written record and a regular review with the transport company are enough. Here are the indicators to track, how to collect them and how to turn them into decisions.

Row of white minibuses parked in the shade of palm trees

Many hotels think they need a dashboard to talk about quality. In practice, what is almost always missing is not the tool: it is a shared definition of what a good transfer is, and a record of what actually happened. This guide gives you both.

Start by defining a “good transfer”

Before measuring, write down in a few lines what you expect, then have your transport company confirm it. Without this, every delay turns into a debate over interpretation.

  • The meeting point: where the driver waits, and from when they are present relative to the guest's arrival. Agree on it with the transport company; don't assume it.
  • Compliance: vehicle type, number of travelers and luggage, all matching the request.
  • Guest information: what the guest receives before arrival (meeting point, driver's identity, vehicle).
  • Handling the unexpected: who informs whom, and in what order, in case of a delay, a no-show guest or a change.
  • The drop-off location: for a riad, only the riad confirms where the guest is dropped off. This point is checked with the riad, not deduced.

Some of these points relate to trust between the parties involved: you will find them on the Safety, privacy and trust page.

The useful indicators, and only those

Stick to questions that can be answered with yes or no, or with a short note. An indicator that the front desk cannot record in a few seconds will not be maintained.

Transfer tracking indicators: what to record, where, when
IndicatorQuestion askedWhere to record itWhen
Presence at the meeting pointWas the driver there at the agreed time?Feedback from the driver or guest, message from the transport companyThe same day
Compliance with the requestWere the vehicle, travelers and luggage as requested?Front desk observation, guest feedbackThe same day
Guest informationHad the guest received the meeting point and the driver's identity?Ride record, conversation with the guestBefore arrival, then a check afterwards
ChangesWas the request modified? By whom, and when?Request historyWhen the ride is closed
IncidentsDelay, guest absent, wrong location, unsuitable vehicle?Free one-line note, with the presumed causeThe same day
Guest feedbackDid the guest leave a comment, positive or negative?Conversation at the front desk, any reviewsAt check-out or after the stay

Don't look for an average or an overall score at the start. A few readable lines are worth more than a rating nobody can explain.

Setting up the tracking, step by step

  1. Choose a single place for the record: a shared spreadsheet or, if you use a management tool, the history of each ride. One place, not three.
  2. Create one row per transfer with the same columns as the table above. Add the date, the transport company and the nature of the service.
  3. Decide who fills in what: the front desk at closing, the concierge for guest feedback. Specify that “nothing to report” must be written down, to tell the absence of an incident from an oversight.
  4. Sort each gap by cause: incomplete request on the hotel side, information not passed on, execution error by the transport company, external unforeseen event. This sorting is what makes the measurement useful.
  5. Schedule a regular review with the transport company. Bring cases, not impressions: date, what was requested, what happened.
  6. Decide on one action per review: change an instruction, complete a template message, train a team, or adjust the relationship with the transport company.
  7. Reread your own columns from time to time: if a question is never used to make a decision, delete it.

Who sees what: a record shared by the team

Quality is often lost between the morning team and the evening team. If only one colleague knows about yesterday's incident, it will be neither noted nor corrected. The same file must be accessible to both the front desk and the concierge, with the same information on the request, the assignment of the driver and vehicle, and the stages of the ride.

To see how a hotel organizes this record day to day, see the page on guest transfer management for hotels, riads and concierge services. To understand how a ride unfolds from the driver's side, read a driver's day, step by step.

Common cases and how to read them

  • The guest says the driver wasn't there. Before concluding the transport company was at fault, reread the meeting point that was sent. If it was vague, the cause lies in the request.
  • The vehicle was too small. Check whether the luggage had been specified. If so, it is an error by the transport company. If not, add the question to your request form.
  • The guest arrived not knowing who to look for. Check what was sent to them and when. The gap is on the information side.
  • The same incident keeps recurring with the same transport company. This is the time for a formal discussion, with the dates in hand.
  • No incident for a long time. Check that the recording is actually being done before concluding that everything is fine.

Common mistakes

  • Measuring too many things and giving up after a few days.
  • Recording only incidents: you then have no basis for comparison.
  • Looking for someone to blame instead of a cause: the tracking becomes defensive and teams stop reporting.
  • Defining “late” after the fact, at the moment of a dispute.
  • Keeping feedback in private conversations, with no shared record.
  • Never sharing the findings with the transport company.

Tracking checklist

  • The criteria for a good transfer are written down and shared with the transport company.
  • A row or a record exists for each ride.
  • Each row says “nothing to report” or describes the incident in one sentence.
  • Each gap has a categorized cause.
  • The initial request and its changes can be consulted.
  • A review with the transport company is scheduled at a fixed interval.
  • Each review leads to a named action, with someone responsible.

Template message to the transport company for the regular review

To see how the hotel, transport company and driver fit together, go to how the service works.

Frequently asked questions

Do you need software to track transfer quality?

Not to get started. A shared spreadsheet with identical columns for each ride is enough, provided the front desk fills it in consistently. A tool becomes useful when volume makes manual recording difficult or when several people need to follow the same requests.

How many indicators should you track?

As few as possible. Choose those that answer a concrete decision: compliance, presence at the meeting point, guest information, changes, incidents. If an indicator never changes a decision, remove it.

How do you set what counts as a delay?

Agree on it with the transport company before tracking begins, in writing, specifying when the driver must be at the meeting point. No universal rule replaces this agreement between you.

What should you do when the guest complains but the record shows an incomplete request?

Fix your own process: add the missing question to your form or to your message to the guest. Raise the case with the transport company as a shared improvement point, not as a reproach.

How often should you hold a review with the transport company?

At a pace you can sustain and that stays regular. During busy periods, a shorter and more frequent exchange helps correct things quickly. What matters is that each review relies on dated cases.