Technology

Keeping Track of Changes to a Ride: Who Changed What, and When

A ride changed without a record turns into a dispute: who asked for the time, who accepted the vehicle? Here is the transport company's method for knowing who changed what, and when.

Van interior seen from the tailgate with bags, a map and water bottles

This guide is for the transport company: dispatcher, operations manager or owner of a small fleet. You receive changes from several contacts (hotel front desk, concierge, agency, sometimes the traveler) and pass them on to your drivers. That is where information gets distorted.

Why the record gets lost on a ride

A modified ride rarely goes through a single channel. The hotel calls, the traveler writes to the driver, the dispatcher corrects from memory. Everyone holds a piece of the truth.

  • **The change is given verbally**: on the phone, there is nothing to reread in case of disagreement.
  • **The change is buried in a conversation**: a time message lost between photos and thank-yous is found by no one.
  • **The change arrives through a parallel channel**: the traveler informs the driver directly, and the driver doesn't tell dispatch.
  • **The change is applied without a date**: no one knows whether it comes before or after the client's last message.
  • **Several people edit the same file**: two members of the hotel team, or two of your dispatchers, each make corrections on their own.

What to note for every change

A useful change record can be read in a few seconds. Here are the minimum fields, with an example wording.

Change record: the fields to fill in
FieldWhat you noteExample wording
SubjectWhat changes: time, meeting point, number of travelers, luggage, vehicle, driver, cancellationPickup time
Before / afterThe old value and the new one, side by sideOld: initial value. New: requested value
RequesterWho makes the request, with their establishment or roleHotel front desk, or agency, or traveler
Date and time of the requestThe moment you received it, not the moment you processed itDay and time of receipt
ChannelWhere the request came inWritten message, call, traveler link
AcknowledgmentWho, on your side, recorded and confirmed itDispatcher's name, confirmation sent
Driver informedWho told the driver, and how the driver acknowledged receiptDriver informed, receipt acknowledged or not

A rule for phone calls: a change received verbally is only valid once it has been read back in writing to the requester. “To confirm: pickup moved to such-and-such time, please reply OK.” The requester's reply is what counts.

The method, step by step

  1. **Set up a single file per ride.** Every change is attached to that ride, not to a personal conversation. If you use a tool that keeps a history of the ride (request, assignment, steps), check it before changing anything.
  2. **Designate who can make changes.** Agree with each client on who is authorized to request a change. A front desk with several people must identify the one who writes.
  3. **Record before you execute.** Note the old and the new value before informing the driver. Correcting from memory is the first source of error.
  4. **Confirm to the requester in writing.** Restate the change as you understood it. They validate or correct it.
  5. **Inform the driver with the same text.** The driver receives the validated wording, not a rephrasing. Ask for acknowledgment of receipt.
  6. **Flag the consequences.** A time change may affect the vehicle, the driver or the next ride. Note it on the record.
  7. **Reread before departure.** Before the ride, compare the latest written version with what the driver has in hand.

For the driver's view of these exchanges, see a driver's day, one ride step by step.

Reusable message templates

Confirmation to the requester

“Hello, we have recorded your change for the ride of [traveler's name or reference]. Before: [old value]. After: [new value]. Request received on [date, time] from [name, role]. Please reply OK to confirm, or correct us.”

Information to the driver

“Change to ride [reference]: before [old value], after [new value]. Requested by [establishment] and validated by us on [date, time]. Please confirm that you have read this. This version replaces all previous ones.”

Follow-up when two versions are circulating

“We see two versions of ride [reference]. Last written version we hold: [value]. Please confirm which one is correct before [deadline you set with the client].”

When several parties touch the same ride

Hotel, transport company and driver don't need to see the same information, but all must start from the same file. That is the principle of role-based access: everyone sees what is useful to them, in the same place. On the hotel side, several team members can follow the same requests, which makes it all the more important to know who wrote what.

For the general framework of trust between parties, see the page Safety, privacy and trust. For the transport company's role in the file, see the page dedicated to transport companies and how a ride works from start to finish.

Common mistakes

  • **Overwriting the old value.** Without the “before”, it's impossible to understand what changed.
  • **Dating only the processing.** Two requests can cross; only the date of receipt puts them in order.
  • **Accepting a change from an unidentified third party.** Check with the usual client before executing.
  • **Letting the driver confirm verbally.** A “yes, fine” at the wheel leaves no trace.
  • **Changing the vehicle or driver without telling the client.** That is also a change: it is recorded and communicated.
  • **Assuming access or the drop-off location.** If the location changes, only the establishment concerned, for example the riad, confirms where the client can be dropped off.
  • **Reopening a closed record to correct it discreetly.** Add a dated line rather than rewriting.

Transport company checklist

  • The change is attached to the right ride.
  • The old and new values are written down.
  • The requester is identified (name or role, establishment).
  • The date and time of receipt are noted.
  • The channel of arrival is noted.
  • The requester has validated in writing.
  • The driver received the same text and acknowledged receipt.
  • Related rides have been checked.
  • Only one version is considered valid, and everyone knows it.

With WAYLISS

  • Each ride keeps a viewable history: request, assignment and steps.
  • The information each party needs comes from the same file, according to its role and rights.
  • Several team members (front desk, concierge) can follow the same requests.
  • The transport company assigns the driver and vehicle; the property sees the driver’s first name, the vehicle and the plate.

Learn more: Safety, privacy and trust

Frequently asked questions

Frequently asked questions

How can I know who modified a ride when several people have access to it?

Require every change to carry the name or role of its author, the date and the channel. If your tool keeps a history of the ride, check it; otherwise keep a change record per ride and share it only in a form that is identical for everyone.

Is a change announced by phone valid?

Only if you read it back in writing to the requester and they reply. Agree on this rule with your clients before the first incident, not after.

What should I do if the traveler informs the driver directly of a change?

Ask the driver to pass it on to you without delay, then confirm it with the establishment that ordered the ride. The traveler is not always the one who ordered: the change is validated with the latter.

How long should the record of a ride be kept?

We have no source establishing a duration. Check the applicable obligations with your adviser or the relevant authority, and agree on a duration with your clients.

What should I do in case of disagreement about what was requested?

Go back to the written chronology: request, confirmation, driver informed. If a step is missing, that is where the rule needs to be strengthened for future rides.