Journal

Stories from the desk.

Real arrangements, lightly anonymised: a record of how requests actually get handled, one trip at a time.

We publish sparingly. Entries are desk notes or anonymised trips we ran — not city-page filler written for search engines. If there is nothing honest to add, the page stays quiet.

A trip we ran

Four days, arranged around a single phone call.

Day 1 — Arrival

A private transfer met the family at the runway; the villa was stocked to their preferences before the car arrived.

Day 2 — On the water

A yacht and crew were secured for the day, with lunch arranged at a cove reachable only by boat.

Day 3 — A change of plan

A late request for a table that evening was placed and confirmed within the hour, no questions asked.

Day 4 — Departure

Bags were collected ahead of time and the return flight was tracked in case timings needed to shift.

A week we ran

Updated August 2026 · Lightly anonymised

Basel fair week, held together from Zürich.

Before the fair

Rooms were secured early on clear terms; cars and evening tables were sketched against a packed viewing calendar, not against hope.

Cross-border timing

Arrivals via EuroAirport were planned with the correct border side confirmed before drivers moved — no improvisation at the kerb.

A mid-week shift

When a dinner moved by ninety minutes, the same contact re-cut the evening without involving the client in vendor calls.

Out again

Departure to Geneva for the next chapter used the same file — preferences already known, no re-briefing at the airport.

A weekend we ran

Updated August 2026 · Lightly anonymised

Lugano lakeside, with Milan timed cleanly.

House and lake

A lakeside house was confirmed with staffing and provisioning notes taken from the client file, not from a generic checklist.

Saturday across the border

A lunch in northern Italy was arranged with papers and timing agreed the day before — the car never waited on a guess.

Sunday return

Malpensa departure was tracked; a short delay at security triggered one message and a revised curb time, nothing more for the guests to manage.

A desk note

August 2026 · Operational, not a trip log

What we confirm before a Swiss private transfer.

Partners and clients often ask what “arranged” means on the day. Before a driver moves, the desk locks five points. Missing any one of them is how curb chaos starts.

Terminal and side

Commercial vs private / FBO, and which side of a dual-border field when that applies — written into the job, not left for the chauffeur to invent.

Name on the board

Meet name, flight or tail number, and who may receive the party. Preferential wording is agreed when discretion requires it.

Bags and child seats

Soft vs hard luggage, golf or ski gear, and seats by age — confirmed the day before, not at the kerb.

Live delay path

Who the driver messages if the aircraft is late, and who the client hears from (one desk contact — not three vendor threads).

Drop and next leg

Exact address, door code or concierge desk, and whether the same car holds for a next movement. No “somewhere in Zürich”.

This is ordinary desk hygiene. It is also why same-day changes stay calm: the file already knows the constraints. Operators who work with us can use the same checklist on their side.

From the desk

We add entries when there is something real to say.

Trip logs when a file closes. Desk notes when the ops lesson is useful. Nothing invented to fill a calendar.

Start your own