A single transfer has a start and an end. A circuit has several, and each involves different people: a hotel that releases the customer, a driver who takes them on, another property that welcomes them. Breaks almost always happen at these junctions. This guide is for agencies that assemble these legs for their travelers.
First decision: one vehicle for the whole circuit, or a relay in each city?
Before any sheet, settle on the model. It determines how you place orders, how you name the service and how you handle changes.
- **Same transport company and same driver throughout.** The traveler sees a familiar face. In return, the service looks more like a vehicle hire than a series of transfers: ask the transport company how it describes and invoices it. The difference is explained in our guide on [how to name transfer, vehicle hire and excursion](/en/blog/transfer-vehicle-hire-excursion-difference).
- **Same transport company, different drivers on different legs.** The company keeps the overall view and assigns its teams. Specify that the traveler must be told about every change of driver.
- **One transport company per city or region.** This is often the most flexible option for distant legs, but you become the only point of junction. This is where the sheet per leg is indispensable.
No model is right on principle. Choose according to the size of the group, the number of legs and what your transport company can genuinely deliver in each area. Ask them in writing.
The leg sheet: the central tool
One sheet per leg, always in the same format. The transport company, the driver and the receiving property can read it in a few seconds. Anything missing from it will be assumed, and on a circuit an assumption is costly.
| Field | What you specify | Why it is useful |
|---|---|---|
| Departure | Property or place, day, requested pickup time | The driver knows who releases the customer and when |
| Arrival | Property or place, and expected arrival time only if the transport company confirms it | Avoids promising the next hotel a time that nobody has validated |
| Travelers and luggage | Number of people, number and type of bags, special needs | The vehicle is chosen on these details, and they sometimes change from one leg to the next |
| Meeting point | Exact place confirmed by the departure property | A single point, known to both traveler and driver |
| Drop-off point | Confirmed by the arrival property, especially in a medina | Never deduced from the vehicle type or the address |
| Transport company and contact | Name of the company, person reachable on the day | Know who to call when the leg goes off track |
| Next leg | What depends on this one: a visit, a flight, another transfer | Measures the impact of a delay |
For the drop-off point in a medina, only the riad can confirm what is possible. The guide how to agree the drop-off point with the riad gives the questions to ask. For choosing the vehicle, see the sedan, van and minibus categories and name the category in the request rather than a model.
The steps to follow to chain legs cleanly
- **Map the junctions.** List every point where one party hands over to another: hotel exit, arrival in a city, change of driver, station or airport.
- **Ask the transport company for journey times, not a search engine.** They know the roads, the breaks and their drivers' constraints. Note their answer in writing on the sheet.
- **Build in a margin before any non-negotiable item**: a flight, a train, a visit at a fixed time. Agree the margin with the transport company rather than setting it alone.
- **Send one structured request per leg.** A request that bundles the whole circuit into a single message is hard to read and hard to confirm. The expected elements are detailed in the guide on [what a good transport company reply must specify](/en/blog/replying-to-hotel-request-what-a-good-transport-company-answer-must-specify).
- **Have each leg confirmed by whoever carries it out**, with the vehicle and driver as soon as they are assigned.
- **Inform the receiving properties**: estimated time, number of people, special needs, name of the agency contact.
- **Write the cascade rule** (see below) and send it to everyone involved before day one.
- **Do a check-in the day before each leg** with the transport company and, if needed, with the departure property.
The cascade rule: what happens when a leg moves?
This is the part agencies forget. A customer leaves a hotel late, a visit runs over, a driver is held up. The next leg is affected, then the one after. Without a rule, everyone calls everyone and nobody knows what was decided.
Agree the following points before the circuit:
- who decides on a postponement or a change: the agency, a tour escort, or the transport company within a defined scope;
- who informs the traveler, the receiving property and the next driver, and in what order;
- up to what time a leg can be changed without consequence for the transport company: ask for their conditions, do not assume them;
- what to do if the customer is absent at the meeting point: follow the logic described in [the waiting protocol between hotel and transport company](/en/blog/airport-no-show-waiting-protocol-hotel-transport-company).
Common cases on a circuit
A change of vehicle during the circuit
A group that grows or shrinks midway, extra luggage bought along the way: the vehicle planned for the next leg may no longer be suitable. Ask again for the number of travelers and bags at each departure, and pass them to the transport company before the day before.
A leg that ends in a medina
Never promise the traveler a drop-off at the door. Ask the riad for the drop-off point and any escort, then pass them on as they are to the driver and the traveler.
A leg that leads to a flight or a train
This is the least forgiving leg. Set the departure time with the transport company starting from the ticket time, and have the departure property confirm that time. Inform the traveler with a clear message.
A driver who changes between two cities
The traveler must know who is waiting, with which vehicle and where. A legible sign and a name known in advance avoid hesitation; the welcoming steps are described in the guide [on the driver's airport welcome](/en/blog/welcoming-customer-airport-driver-essentials).
What the agency can expect from a shared tracking tool
On a circuit, the difficulty is not placing the order but keeping the same file readable for several parties over several days. Whatever your method, require these capabilities: a structured request per leg, visible assignment, a clear traveler link and a history. To compare messaging, spreadsheet and platform, see the [comparison of transfer management methods](/en/blog/whatsapp-spreadsheet-platform-comparison-hotel-transfer-management). The general operation is presented on [the how it works page](/en/how-it-works).
Checking the transport company's framework
Road tourist transport in Morocco is governed by a set of specifications that sets, among other things, the conditions of access to the activity, its operating conditions and oversight, according to the Ministry of Tourism, Handicrafts and Social Economy. On a circuit where you entrust travelers to several transport companies, ask each one to confirm that it operates within this framework, and keep that confirmation with the file. For details of what is required, contact the ministry or the transport company itself.
Checklist before the circuit departs
- The model (one driver, one transport company or several) is chosen and written down.
- Each leg has its sheet, confirmed by whoever carries it out.
- Journey times and margins come from the transport company, in writing.
- Each meeting and drop-off point is confirmed by the property concerned.
- Legs to a flight or a train have a validated departure time.
- The cascade rule and the single contact have been sent to everyone.
- For each leg, the traveler knows where and how they will be picked up.
- Each transport company's operating framework has been confirmed.
- The file history is accessible to those who need it.
Common mistakes
- Sending a single message for the whole circuit and considering that "everything is confirmed".
- Promising an arrival time to the next hotel without the transport company's validation.
- Letting two people at the agency give contradictory instructions to the driver.
- Forgetting to ask again for travelers and luggage during the circuit.
- Assuming a vehicle can reach a riad because the previous one did.
With WAYLISS
- The property enters a structured request: flight, time, travelers, luggage and meeting point.
- The transport company assigns the driver and vehicle; the property sees the driver’s first name, the vehicle and the plate.
- The link shows the meeting point, then the driver’s first name, the vehicle and its plate once assigned.
- Each ride keeps a viewable history: request, assignment and steps.
Learn more: About WAYLISS
Frequently asked questions
Frequently asked questions
Do you need a single transport company for a whole circuit?
Not necessarily. A single company simplifies coordination, but several may cover distant areas better. Ask each one what it can genuinely deliver and decide according to the size of the group and the number of legs.
How do you warn the next hotel of a delay?
Go through the agency's single contact, who informs the receiving property and the next driver with an estimated time given by the transport company. Avoid multiplying crossed calls.
Who confirms the drop-off point in a medina?
The riad or receiving property, and nobody else. Do not deduce it from the vehicle or the address. Pass the answer on as it is to the driver and the traveler.
What records should you keep on a circuit?
Requests, confirmations, driver and vehicle assignments, and changes with their author. This lets you trace who decided what in case of disagreement.
To understand the platform's approach, see its about page. For receiving properties, see the page customer transfers for hotels, riads and concierge services.
Sources
- Transport touristique — Ministère du Tourisme, de l'Artisanat et de l'Économie sociale et solidaire (mtaess.gov.ma) (accessed 30 October 2026)
