An event brief that says “120 people, three offices, one shared experience” leaves most of the important decisions open. Are the offices joining at the same time? Does each location have a suitable room? Who can change the plan locally? What happens when a satellite office cannot use the format chosen by headquarters?
Multi-city team building needs both a shared design and a workable local plan. This guide explains how to build them together. It includes a copyable office matrix, a consistency checklist, a hypothetical rollout and a readiness review. It is a planning method, not a statement that every provider offers every delivery model or city.
For the wider sequence from goals to follow-through, use the complete team-building event planning guide. This article focuses on the decisions that change when people are distributed across offices.
What multi-city team building means and which format you need
Multi-city team building is a coordinated program for employees in two or more locations. Teams can participate simultaneously, in scheduled waves or through local sessions connected by the same purpose and follow-up. A useful rollout has named local owners, a shared brief and explicitly agreed adaptations for each office.
A multi-city brief should distinguish simultaneous app-based activities with a remote briefing and shared results from separately facilitated local events. Before comparing proposals, specify which experience you need, who leads each location and how the offices will connect.
Compare simultaneous, staggered and local delivery
No model is automatically better. If the purpose is for colleagues from different offices to work together directly, parallel local activities alone do not create that interaction. Add a meaningful cross-office task or choose another format. If the purpose is local connection around a shared company theme, separate sessions can be appropriate without pretending the offices are collaborating live.
Start by writing the interaction you want people to practice. “Improve collaboration” is broad. “Each office explains what a complete request looks like and agrees how to acknowledge a cross-office handoff” gives the designer something concrete to work with.
Build the office-by-office rollout matrix
Treat each office as a delivery location with its own dependencies. A single total headcount cannot tell a provider how many spaces, local contacts or material deliveries are needed. Ask each local owner to verify their row rather than having a central planner guess.
Copy this blank location record
Repeat this compact record for every location. Keep the working version in a shared planning document and put confidential personal information in a separate restricted channel.
Avoid requesting diagnoses in this sheet. A local owner generally needs to know what participation arrangement must be supported and who will coordinate it privately. They do not need a widely circulated account of why someone requested it.
Use a filled matrix to expose dependencies
The following is a hypothetical planning example. Counts illustrate the organizer's requirements; they do not establish FullTilt staffing, capacity or availability.
The total is 60 + 36 + 24 = 120. That arithmetic helps organize a brief, but does not prove that the proposed rooms or activity can support those numbers. Ask the provider and relevant venue contacts to approve each working layout and format.
A status of “awaiting confirmation” is useful. A green cell based on an assumption is not. Before committing, make the unresolved room, equipment or participation question visible to the person who can answer it.
Decide what stays consistent and what may change
Consistency should protect the purpose without forcing every location to copy headquarters. Different rooms, languages, working hours and participation needs can require different arrangements.
Agree the boundaries before local owners book alternatives. Use three categories: required everywhere, local choice within agreed limits, and changes that require approval. This prevents a local adjustment from quietly changing what the company bought.
For example, every office could produce one handoff agreement using the same four fields: request owner, required information, acknowledgement and escalation. Local teams can use different realistic examples. The shared output makes discussion possible without claiming the activities produce identical experiences or business outcomes.
Do not use a central leaderboard by default. It can be appropriate for an approved activity, but scores across different conditions are not automatically comparable. Ask whether different rooms, timing, task versions or facilitation would make the comparison misleading.
Choose simultaneous or staggered delivery across time zones
Look for an acceptable local working window at every location. Record the actual event date and named time zone, then verify the conversion for that date. Daylight saving changes and overnight date differences make permanent city-offset assumptions unreliable.
If one common window consistently places the burden on a small office, consider waves. Describe how the waves connect: the same introduction, comparable task, common debrief question and shared recap can create continuity. A forced live connection is not the only way to create a coordinated program.
Protect later waves from spoilers
If solving a challenge is part of the activity, decide what can be shared before all waves finish. A company-wide photo or answer-filled recap can spoil a later session. Give organizers a specific release time for solution material and an approved alternative message they can share earlier.
Keep practical information flowing even when task details are restricted. Later offices still need arrival instructions, participation choices and local contacts. “No spoilers” should not become a reason to withhold essential information.
For colleagues joining remotely, agree an actual role. A camera pointed at a busy room is not a complete participation design. Confirm which tasks they can contribute to, who includes their input and what alternative route exists if the live arrangement fails.
Confirm the delivery scope before requesting proposals
Use one common brief with a site appendix for each office. Ask suppliers to explain which elements they can deliver, which require local support and which remain subject to confirmation. Our team-building RFP template supplies the outgoing request; the matrix above becomes its location appendix.
Ask separately about shared design and location-specific delivery. Who briefs local contacts? Who facilitates each session? Who supplies, ships, receives and stores materials? Who confirms venue permission, access and sound? Is a remote platform needed, and who supports it? What happens if a location must change dates?
Require written assumptions for travel, venue, materials, shipping, taxes, currency, cancellation and headcount changes. These are scope questions, not automatic inclusions. Do not assume that one contract, one price or a phrase such as “nationwide” resolves every location's responsibilities.
Use the team-building cost guide to organize cost questions, not to multiply an assumed per-person rate across offices. FullTilt's starting budget is $3,000+ for a total event; per-person pricing varies. That starting point is not a quote for a multi-site rollout or a promise that all locations fit within it.
Work through a three-office rollout example
Hypothetical planning example: not a client case, delivered program or FullTilt quote. A company plans for 120 colleagues across Offices A, B and C. It wants teams to practice a clear handoff between local operations and a shared support function. Each office will leave with one draft agreement, which the operations sponsor will review after the event.
Offices A and B have a workable common window. Office C does not. The planner chooses two waves, subject to provider confirmation, and records the shared brief plus local responsibilities. The organizer does not describe this as a single simultaneous experience.
Turn a venue problem into an approved change
Office B loses its booked room. The local owner proposes a smaller replacement. Instead of simply changing the address in the invitation, the planner asks the provider and venue whether the layout, participation options, activity mechanics and access window still work.
If the alternative is unsuitable, the options include another venue, an approved different format or another date. The aim is a workable commitment, not preserving the original calendar at any cost. Publish participant instructions only after the local plan is settled.
Run a readiness review before each location starts
A shared start time does not mean every office is ready. Complete a local review and give the overall decision owner a clear status. This is a planning check, not safety certification or a substitute for venue requirements.
Each local session also needs its own operating sheet. Use the team-building run-of-show template to turn the approved plan into timed actions, readiness conditions and handoffs.
Connect the offices after the event
Ask the same core debrief questions while allowing local examples: What information helped the team act? Where did a handoff become unclear? What would we try in an actual cross-office request? Capture observations without diagnosing individuals from game behavior.
Choose one small working agreement with an owner and review date. For example: “The requesting office includes a decision owner and needed-by date; the receiving team acknowledges receipt through the agreed channel.” At review, examine whether the teams tried the agreement and what needed adjustment.
Participant satisfaction, completion of a worksheet and later work behavior are different forms of evidence. None alone proves financial return or that the event caused a wider business change. For an ongoing cadence, connect the review to your year-round team-building plan.
Multi-city planning mistakes to avoid
Avoid treating the headquarters plan as universally workable, hiding local counts inside one total, assuming every extra cost is included, and using remote attendees as spectators. Also avoid introducing a new city or format through an informal message after the scope has been approved.
The practical safeguard is straightforward: one shared brief, a verified record for each location and a named owner for every change. Ask for delivery scope in writing before describing the program to employees as confirmed.
Frequently asked questions