Running a delegation in Davos week: what the delegation lead actually does

A delegation lead runs Davos week as an operation: a small team with named roles, a daily rhythm that starts before the first breakfast and ends after the last nightcap, a meeting pipeline built weeks in advance and re-sequenced every evening, and a briefing book that tells the principal who they are meeting, why, and what to ask. The official programme, where the delegation holds accreditation at all, is a fraction of that week. The independent calendar of breakfasts, roundtables and dinners around it is where the lead spends most of the effort. This is the playbook for the person who runs it.

It is written for corporates, institutions and family offices sending a team rather than a single person. The individual version of the same discipline is set out in arriving with intent.

The roles in a Davos delegation

Every delegation, whatever its size, needs the same five functions covered. The only question is how many people carry them.

The principal is the reason the delegation exists: the chief executive, the founder, the minister or the head of the family office whose presence opens the rooms. In Davos the principal's job is the conversations, and almost nothing else.

The delegation lead, often the chief of staff, owns the plan. The lead holds the objective, makes the trade-off when two good meetings collide, decides who goes to which dinner, and is the person the rest of the team answers to during the week.

The scheduler keeps the pipeline current: confirmations, changes, locations, walking times, and the meetings that are held but not yet confirmed.

The communications lead owns what is said: the messages, the briefings for any appearance, what is on and off the record, and the link to the communications team at home.

Logistics covers the physical week: accommodation, transport, the Secure Hotel Badge for everyone who needs one, and the contingency when weather or security changes the plan.

In a large corporate delegation each function has its own person, and some have several. In a small one they combine. The minimum configuration that works is two people: a principal, and a chief of staff who carries the lead, the schedule and the logistics, with communications held by the team at home. A two-person delegation is not a smaller version of a large one. It is a different shape, built almost entirely on preparation, because there is nobody spare to fix things during the week. How we design a corporate team's week as one engagement is on our page for corporates, and the version for principals travelling with advisers is on our page for family offices.

Before the week: objectives, the target list, the pipeline

The individual preparation, one objective and a pre-booked calendar, is set out in our first-timer's guide to the Davos week. The team version adds coordination.

Start with one objective for the delegation and one for each member, and make sure each personal objective ladders to the delegation's. A delegation whose members pursue unrelated agendas reads, in the rooms, as an organisation without a position.

Then the target list. For the principal, the fifteen to twenty-five people or organisations whose direct contact would change the year; for each other member, a shorter list of their own. For every target, three working notes: where they are likely to be that week, who connects you, and what the principal would ask with ten minutes.

Then the pipeline: every target with a status, whether requested, introduced, held or confirmed. The pipeline is a living document from the autumn onward, because the calendars of the people you want to meet fill before the week begins. A meeting proposed in December is easy to place. The same meeting proposed on the Tuesday of the meeting competes with a full schedule.

The long-lead items run in parallel: accommodation in the spring and summer, Secure Hotel Badge applications in the autumn, and the calendar of independent events the delegation will attend, the breakfasts, roundtables and dinners, as it firms up through November.

The daily operating rhythm

The public shape of a Davos day is predictable: breakfasts from around seven, open programming and meetings through the late morning and afternoon, roundtables and lounge conversations in the late afternoon, and dinners from around seven that run long, as set out in Davos 2027 dates and how the week works. The lead's day wraps around it.

• The morning sync, before the first breakfast: fifteen minutes with the whole delegation on today's calendar, what changed overnight, who covers what, and the one or two meetings that matter most.
• The breakfast, often the most focused meeting of the day.
• The midday re-sequence. By late morning the day has moved: a meeting has slipped, an introduction has landed, an invitation has arrived. The lead and the scheduler re-cut the afternoon and the evening.
• The afternoon block of meetings, roundtables and House sessions, with margin between them for the walk and the security checks at venue entries.
• The evening, when the delegation may split across dinners so that each room is covered by the right person.
• The debrief, after the last commitment: notes from every meeting captured while they are fresh, follow-ups logged with an owner, tomorrow re-cut, and the principal's brief for the morning updated.

The sync and the debrief are the two fixed points of the day. Everything between them can move. They should not.

A delegation that skips Tuesday's debrief spends Wednesday working from Monday's plan.

The meeting pipeline, re-cut every evening

The pipeline is the delegation's single source of truth, and it pays to keep it simple. Three states cover almost everything.

Confirmed meetings have a time, a place, a brief and an owner. Held slots are protected time, reserved for a meeting that is likely but not yet fixed, or for the unplanned conversation that so often turns out to matter most. Floating meetings are wanted but unplaced, and they move into the calendar as space opens.

Every evening, the lead re-cuts the next day. Floating meetings move into released holds, new requests from the day's conversations are slotted or declined, and anything that no longer serves the objective comes out. Every morning, the sync confirms the cut.

Capacity is the constraint, and it is the principal's day rather than the delegation's. Build the principal's day for depth: a handful of substantive meetings with real margin between them, and room for the conversations nobody planned. The delegation can cover more ground by splitting across rooms; the principal's calendar should not try to. The town will eat any schedule built without that margin.

How introductions are brokered

Introductions at Davos move through three channels, and a delegation lead works all three.

Through hosts. The host of a dinner or a roundtable decides who sits next to whom, and a good host seats people who should meet. Being in the right rooms is the first source of introductions, which is why the calendar of independent events matters as much as the meeting list.

Through networks. Someone who knows both sides explains why the meeting is worth having. That is what a warm introduction is: not a forwarded email, but a named person putting their judgement behind the meeting. Cold requests rarely work in Davos, and warm ones often do.

Through a programme. A concierge with its own programme of events and its own network can make introductions within that network and seat a principal in rooms designed around a theme.

What none of these can do is guarantee a meeting with a specific named person, and nobody credible promises one. The work is to position the principal where the right people are, prepared with the right context, and to make the conversation natural when it happens. The longer-term pathways, including how standing builds across several years, are set out in how to get invited to Davos.

The briefing book

The briefing book is the document that holds the week together. The delegation lead owns it, the team contributes to it, and the principal reads it in the minutes before every important conversation.

A good book contains:

• The objective and the delegation's messages for the week, on a single page.
• The calendar, with locations, the walking time between them, and who attends each commitment.
• A one-page brief for each priority meeting: who they are, what they have said recently in public, why the meeting makes sense from their side, the ask, and what not to raise.
• A note for each dinner and event: its purpose, its host, and the kinds of guests it draws.
• The logistics: badges, transport, accommodation, contacts and the contingency plan.

It is written in the weeks before the meeting and refreshed every evening during it, after the debrief. Its test is simple. Could the principal walk into any room on the calendar, with two minutes to read, and know exactly why they are there?

Credentials across a mixed delegation

Most delegations are mixed. A principal may hold official accreditation through the organisation's membership or partnership, while advisers and staff do not. Where the principal carries official accreditation and the others do not, the rest of the delegation is credentialed through Secure Hotel Badges, so that everyone can move through the secured-zone hotels where much of the independent programme takes place.

The lead's job is to map who can enter where, and to build the calendar so that the principal is never stranded inside the Congress Centre while the rest of the delegation works the town, or the reverse. The badge applications run to autumn deadlines and depend on a confirmed hotel reservation in each applicant's own name, so they belong in the plan from its first month. The mechanics are in the Davos Hotel Badge, explained.

Movement and geography

A delegation moves more slowly than an individual: more people, more luggage, more meetings in more places. Two rules keep it workable.

Base the delegation centrally, ideally in a single property, so that the briefings, the breakfasts and the debrief happen under one roof and the principal can walk to most commitments. Our guide to where to stay during the Annual Meeting week covers the choice, including when a chalet suits a group better than a block of hotel rooms.

Plan the movement as part of the calendar rather than as an afterthought: who walks, who takes a car, and how the delegation reunites for the evening. The routes in and the meeting-week traffic rules are set out in getting to Davos in January.

After the week: the debrief and the follow-up calendar

The week creates the opportunities and the follow-up converts them. For a delegation, the discipline is the same as for an individual, with owners attached.

In the days after the meeting, the delegation holds a full debrief: every meeting, what was discussed, the next step, and who owns it. Every follow-up goes out promptly, while the context is fresh, and says something specific rather than thank you. Every meaningful conversation gets a date for its next contact. Six months on, the lead reviews what the week produced against the objective it was built for, which is the only honest basis for deciding about the following year.

The research is a useful corrective. A study of corporate attendance from 2009 to 2018, summarised by its authors in a VoxEU column, found no evidence that attending improved firms' stock market performance or credit ratings, beyond an economically modest effect on ratings for first-time attendees. Whatever the week returns, it returns through relationships and decisions, and those count only if someone tracks them. A scorecard for doing so is set out in how to measure what Davos week returned.

How The Davos Cabinet supports a delegation

We build a delegation's week as one engagement. The calendar is coordinated across the team, briefings are tailored to each executive's portfolio and reconciled with the in-house communications function, and movement, meeting space and the daily review are run by a single dedicated team.

The Principal adds a dedicated one-to-one concierge throughout the week, introduction requests supported by our team within our network, and personal briefing notes delivered each evening. The Delegation extends this with plus-one and delegation companion options across our programme, dedicated introductions within our network, a custom briefing book prepared for the delegation in the weeks before Davos, and a six-month post-Davos engagement covering follow-up coordination and quarterly briefings. Members of the delegation are invited to the dinners hosted within our programme, which draw senior leaders from government and business.

The Secure Hotel Badge is handled end to end for every member who needs one: the application, the police verification paperwork, collection in person with a passport at the official pickup point in Davos, and help on the ground through the week. Everything we host is organised independently by The Davos Cabinet. It is not part of the official Annual Meeting programme and does not include access to the official meeting, its sessions or its delegates. The structure is set out across our tiers.

Common questions

The questions delegation leads and chiefs of staff ask us most often about running the week. Full responses sit in the accordion below.

Begin your conversation

A delegation's week is built in the months before January. The earlier the roles, the pipeline and the badges are in motion, the better the week. The conversation begins by application.

For the individual version of this discipline, read arriving with intent and the first-timer's guide to the Davos week. For a public official's office, the specifics of the mandate, protocol and security are in briefing a public official for Davos week.

Frequently asked questions

1. 01What does a delegation lead do at Davos?↓

   Runs the week as an operation. The lead owns the objective and the calendar, assigns the roles, keeps the meeting pipeline current and re-sequences it every evening, makes sure every important meeting has a brief, and runs the morning sync and the evening debrief. The lead decides the trade-offs so the principal can spend the week in conversations.

2. 02How big should a Davos delegation be?↓

   As small as the objective allows. A principal and a chief of staff is the minimum configuration that works; larger delegations add a scheduler, a communications lead and logistics support. Every additional person needs a reason to be there, a credential for the rooms they must enter, and a bed in a town that is full that week.

3. 03How many meetings a day should a principal take at Davos?↓

   Fewer than most first-timers plan. Build the principal's day around a handful of substantive meetings with real margin between them, and let the delegation split across rooms to cover more ground.

4. 04Who writes the Davos briefing book?↓

   The delegation lead owns it and assembles it from the team's research, the principal's objectives and the week's calendar. It is prepared in the weeks before the meeting, with a one-page brief for each priority meeting, and refreshed every evening during the week after the debrief.

5. 05Can a two-person team run a productive Davos week?↓

   Yes. A principal and a chief of staff, with the calendar built before the week and the logistics handled, is the minimum configuration that works. The chief of staff carries the schedule, the briefs and the follow-up log, and the principal carries the conversations. What a two-person team cannot do is improvise the week on arrival.

The Davos Cabinet is not affiliated with nor endorsed by the World Economic Forum.