Launch brief for a fast-moving sales team
The client was a mid-sized sales team based in Johannesburg, with delegates travelling in from Cape Town, Durban, Pretoria and Gqeberha for a regional product event in Bryanston. The launch had a short lead time, a fixed event schedule and a few senior attendees with separate travel approvals, so the booking plan had to be neat from the start.
Our role was to pull the trip into one working file, match the right travel times to the event programme and keep the team informed without creating admin for their internal managers. We handled flight options, room blocks, arrival timings and change tracking so the client could focus on the launch itself.
- Team size: 18 delegates
- Origin cities: 5 South African centres
- Event area: Bryanston, Sandton
- Planning window: 2 weeks
What made this trip tricky
The main constraint was timing. Several attendees were travelling on different dates, and the event had a morning start with a pre-launch briefing the day before. That meant flight arrivals had to be spread carefully, not just booked at the cheapest fare. We also had to work around school holiday traffic in some departure cities and reduce the risk of late arrivals from weather delays and peak-time congestion.
Because the group included sales managers, account leads and support staff, approval workflow mattered as much as the bookings themselves. We set up a clean list of traveller names, ID details and fare classes, then checked changes with the client before confirming. It saved time later when one delegate needed to move from a morning flight to a later departure after a meeting ran over.
- Staggered departures across 3 days
- Mixed fare classes based on approval level
- One late itinerary change before ticketing
- Co-ordination between travel, approvals and finance
Flights, rooms and event movement planning
We arranged the full travel pattern rather than just the air tickets. For the Johannesburg and Pretoria travellers, same-day movement was possible, but we still recommended earlier departures to avoid rush-hour pressure on the N1 and M1. For the Cape Town, Durban and Gqeberha delegates, we booked flights that arrived before 16:00 where possible, giving enough time for check-in and a proper rest before the launch briefing.
Accommodation was selected close to the Bryanston event venue to keep transfers short and predictable. We looked for practical room standards, reliable lighting for load-shedding, stable Wi-Fi for last-minute deck updates and easy access for evening return travel. The brief also asked for clear invoice handling, so room charges and incidentals were tracked separately from flight costs.
- Flights arranged from 5 cities
- Accommodation near the event venue
- Transfer timing matched the event agenda
- Separate cost lines for flights, rooms and changes
How we managed approvals and documents
Corporate travel often slows down when approval steps are not clear. In this case, we built a simple traveller list and worked through the approvals in sequence so that finance and line managers were not chasing separate updates. Every booking was checked against the event register, traveller profile and ID details before issue. That reduced errors and kept the group file clean.
We also checked travel documents for each delegate, including names on tickets, identity numbers and any special requirements for check-in. A few travellers needed support with updated profile details, and one attendee had a surname spelling difference on internal records, which we sorted before ticketing. Small fixes like that matter, because they prevent boarding delays and awkward phone calls at the airport.
- Traveller profile checks completed before issue
- Document matching done for every delegate
- Approval notes shared with the client team
- One name correction fixed before ticketing
During the launch week
The launch week needed active monitoring. We kept an eye on departure times, checked for schedule changes and managed one booking amendment after a meeting extension in Cape Town pushed a delegate into a later flight. Because the group was travelling into a busy business area, arrival times were set with traffic in mind, not just the flight timetable.
After hours assistance was important once the event had started. When one Durban traveller reported a missed bag on arrival, we logged it immediately, checked the flight record and passed the details through so the client’s internal team could move on with the programme. We also monitored delegate arrivals, which helped the event coordinator confirm who was on site and who still needed transport from the hotel.
- One same-day booking amendment handled
- Delegate arrivals tracked against the event schedule
- After hours support used for baggage follow-up
- Travel changes communicated to the client team quickly
Results, reporting and what we would repeat
The outcome was a launch that stayed on time and organised, with delegates arriving in a workable order and the event team not having to manage travel noise through the day. There were no missed bookings, no duplicate room issues and no last-minute confusion around who was arriving when. The client also had a clear post-trip report showing flight spend, room totals, amendments and any follow-up actions.
If we were doing the same project again, we would apply the same structure: fixed approval flow, staggered arrival planning and clear rooming list control from the start. For a sales launch in Bryanston, that approach works well because it keeps the team moving and avoids the usual scramble that comes with mixed-city business travel.
- Trip delivered within the 2 week planning window
- Zero missed bookings on the final manifest
- Clear reconciliation for flights and accommodation
- Repeatable format for future regional events
Key facts
| Client type | South African sales team preparing for a regional product event |
|---|---|
| Project location | Bryanston, Sandton |
| Planning timeline | 2 weeks |
| Travel origins | Johannesburg, Cape Town, Durban, Pretoria and Gqeberha |
| Core services used | Flights, accommodation, itinerary management, amendments and reporting |
| Project size | 18 delegates with staged arrivals and approved rooming lists |
