Can you handle short-notice itinerary changes during a live project?

Yes. We manage booking amendments, cancellation handling and updated itineraries as part of the travel file, so the client does not have to restart the process each time plans shift.

Do you work with travellers from more than one South African office?

Yes. We regularly coordinate travel for teams moving from Sandton, Pretoria, Midrand, Rosebank and other business areas across South Africa.

Can you support reporting and invoice checks after the trip?

Yes. We handle travel reporting and invoice reconciliation so accounts teams can match costs to the correct project and traveller.

Rosebank Consulting Sprint

Client brief: two-city workshop travel with very little slack

The client was a Sandton based consulting team sending senior advisers between workshop venues in Johannesburg and Cape Town over a short project window. The brief was simple on paper and quite demanding in practice: book fast, keep every traveller on the same rhythm, and make sure each return leg lined up with the next meeting without wasted hours in transit.

They needed a supplier who could deal with changing headcounts, late approvals, and the usual pressure that comes with client-facing work. Some consultants travelled solo, others moved in pairs, and the workshop dates shifted once the meeting rooms were confirmed. We had to keep the plan practical, cost-aware and ready for last-minute changes, especially where same-day returns and early-morning departures were involved.

The project covered eight travellers across two cities and required one central point of control. The client wanted fewer messages going back and forth, clearer approvals, and proper visibility on who was travelling, where they would sleep, and when they would be back at their counters, sorry, back at work the next morning.

Constraints that shaped the itinerary plan

We had three main limits to work around. First, the workshop timings were fixed by the end client, so the travel had to fit around those slots rather than the other way around. Second, the team was split between Johannesburg and Cape Town offices, which meant some people joined from Sandton while others came in from Pretoria and Midrand. Third, the client needed a clean approval trail and accurate invoicing for each traveller, since costs were being recovered by project code.

Travellers needed same day or next day return options where possible
Check-in and check-out times had to fit workshop start times
Some team members required extra baggage for presentations and samples
After hours support was needed for schedule changes during load-shedding delays
Hotel selections had to be practical, close to meeting venues, and suitable for early departures

We also had to account for the usual South African travel issues that can upset a tight schedule, including traffic around Rosebank and the M1, airline time changes, and short-notice room changes at the accommodation side. The plan had to hold together even if one piece moved.

What we supplied for the Rosebank consulting sprint

Our team handled the full booking cycle. That included fare searches, hotel options, approval support, rooming lists, document checks and travel reporting. We kept the travel file tidy so the project lead could see each booking at a glance, rather than chase separate confirmations from multiple people.

Return flight bookings for consultants travelling between Johannesburg and Cape Town
Hotel bookings close to the workshop sites, with flexible arrival and departure times
Booking amendments when workshop timings changed
Cancellation handling for one traveller who was moved off the trip at short notice
Delegate arrival tracking so the client knew who had landed and checked in
Invoice reconciliation split by traveller and by project phase

We also checked each traveller profile before ticketing to make sure names, ID details and loyalty information where applicable matched the booking file. That saved time later and reduced the risk of reissue fees. For the accommodation side, we looked for rooms with reliable backup power and working business facilities, since a few team members still had to send notes after hours and before breakfast.

Timeline and working rhythm over two weeks

The project ran over two weeks from first enquiry to final reporting. In week one we confirmed the travel windows, gathered traveller names, checked approval rules, and issued the first round of flights and accommodation. By the end of that week the main workshop movements were already locked in, with one standby option held where the client expected a possible change.

Week two was all about movement control. We monitored departures, updated the client on arrivals, and handled one same-day change when a consultant’s client meeting ran late in Johannesburg. That change meant moving the return flight and adjusting the hotel checkout by one night. We processed it quickly so there was no scramble at reception or at the airport.

The coordination worked best because everyone knew the process. The consultant team sent changes through one channel, our travel support kept the record current, and the accounts side had a clear summary at the end. No one had to guess which version of the itinerary was current.

Practical results for the client team

The main result was time saved. The consultants were able to focus on the workshops instead of checking flight times, phoning hotels, or comparing invoices line by line. The project lead had one version of truth for travel, and the accounts team received a cleaner reconciliation file once the trips were completed.

All scheduled workshop travellers arrived on time
One short-notice amendment was handled without disrupting the programme
Hotel check-ins were completed before evening client sessions
The client received a clear travel report with arrival and departure status
No missed workshop starts caused by transport issues

Just as important, the travellers said the travel plan felt predictable. That matters when people are moving between client sites, because even a minor delay can throw off a whole day. The client had enough visibility to plan meetings around real arrival times instead of estimates.

What we would repeat on the next consulting move

If we were handling this again, we would use the same structure: one lead point of contact, early traveller profile collection, and a firm approval workflow before anything is ticketed. For consultancy work that jumps between cities, this keeps the admin light and the travel file clean.

We would also keep the same approach to arrival tracking and after hours support. In South Africa, a flight delay, a traffic hold-up, or load-shedding at a hotel can change the day quickly. Having someone available to manage the booking changes, and to do it without drama, makes a real difference.

For future projects of this type, we would again recommend using split reporting by traveller, clearer rooming lists for the hotel, and a short pre-trip check on all document details. It saves the team from avoidable fixes later and gives the client a steadier booking process from start to finish.

Key facts

Project type	Business travel coordination for consulting workshops
Client type	Professional services team based in Sandton, Johannesburg
Travel scope	Johannesburg and Cape Town with rapid return legs
Timeline	2 weeks from first brief to final reporting
Travellers	8 consultants across staggered workshop dates
Services used	Flights, hotels, amendments, duty of care, reporting and invoicing

Rosebank Consulting Sprint

Client brief: two-city workshop travel with very little slack

Constraints that shaped the itinerary plan

What we supplied for the Rosebank consulting sprint

Timeline and working rhythm over two weeks

Practical results for the client team

What we would repeat on the next consulting move

Key facts

What our Business Travel customers say

Questions we get asked

More trips planned

Pretoria Board Meeting

Umhlanga Executive Stay

Bryanston Sales Launch

Planning something? Send the team a message.