Vantly Get a custom quote

Hybrid and Remote Teams: How to Run an Offsite That Doesn't Leave Remotes Behind

By the Vantly team · Research checked October 2026

When a remote or hybrid company gets together, the offsite is often the most expensive thing the People team runs all year. It is also the event most likely to create two classes of employee: the people who were in the room, and the people who heard about it afterward. That split rarely comes from bad intent. It comes from a few quick decisions: who is "expected," who pays for the flight, whether travel days count as work, and whether the remote option is a real seat or a laptop at the end of the table. Together they decide whether remote colleagues come home feeling closer to the company or further from it.

Get a custom quoteSee sample events
Colleagues share a working lunch around a wooden table.
Photo: Artem Podrez / Pexels

When a remote or hybrid company gets together, the offsite is often the most expensive thing the People team runs all year. It is also the event most likely to create two classes of employee: the people who were in the room, and the people who heard about it afterward.

That split rarely comes from bad intent. It comes from a few quick decisions: who is "expected," who pays for the flight, whether travel days count as work, and whether the remote option is a real seat or a laptop at the end of the table. Together they decide whether remote colleagues come home feeling closer to the company or further from it.

This guide walks through those decisions in order, for People Ops and HR leads and the chiefs of staff and managers who plan alongside them. For the wider inclusion picture (venue access, food, alcohol norms, caregivers and opt-outs), see our inclusive company retreat playbook. This guide goes deeper on one question: how to make the offsite fair for people who live far away, work remotely, or cannot travel at all.

Start with purpose: what actually needs a room?

Before you decide who flies, decide what the gathering is for. Remote teams already do a lot well over video: status updates, presentations and anything that is mainly one person talking to many. Flying everyone in to watch slides is the fastest way to make people resent the trip.

What tends to be worth a room is the work that video does badly:

  • Building trust and relationships, especially across teams that rarely overlap.
  • Hard conversations and trade-offs where tone, body language and side conversations matter.
  • Open-ended problem solving, such as whiteboarding, mapping and messy early-stage strategy.
  • Onboarding and integration of new hires, new leaders or a merged team.
  • Unstructured time: meals, walks and the conversations nobody schedules.

A quick test for every agenda block: could this happen just as well on a normal video call next Tuesday? If yes, move it out of the offsite, or run it before or after as a remote session everyone joins the same way. What remains is the real reason to gather, and it should shape everything that follows.

Agenda block | In person? | Remote-friendly alternative

Company update, metrics, roadmap walkthrough | Usually not needed | Pre-recorded or live call the week before

Strategy workshop with trade-offs | Strong case | Smaller remote session with pre-reads and async input

Team bonding, meals, free time | Strong case | Hard to replicate; plan a separate remote moment

Cross-team problem solving | Strong case | Remote breakout with a shared digital board

Training or demos | Depends | Often works as well, or better, remotely

Who must attend in person, and who is optional

Once the purpose is clear, sort people into three groups and write the list down before anyone books travel.

  1. Expected in person. The people the core work depends on. If they are missing, the offsite does not achieve its purpose.
  2. Invited in person. Everyone you would like there, who can choose to come.
  3. Remote by design. People who join specific sessions remotely, on purpose, with a plan for how they take part.

Then be honest about what each label means. If the offsite is optional, say so plainly and make sure managers treat it that way. If it is expected, say that too, and give people the notice and support to make it possible. The worst outcome is a retreat that is "optional" on paper while everyone senses that skipping it will be noticed.

Write down, in the planning doc:

  • The purpose, in one sentence.
  • Who is expected, invited and remote by design, and why.
  • Who can approve an exception, and that people do not need to share personal reasons (health, care, visa, money, safety) to get one.
  • What anyone who cannot attend will receive: a recap, a follow-up session, a seat in key decisions.

Some people cannot travel for reasons they may not want to explain, from health or caregiving to immigration status or safety concerns about a destination. Build the exception path so nobody has to disclose any of that to use it.

Travel: pay for all, or for none

Travel cost is where fairness gets tested first. A common pattern goes wrong like this: the company covers flights for some people (often leaders or those "required") while others are told the trip is optional and self-funded. Or the company pays a flat amount that covers a short drive for one person and a fraction of a long-haul flight for another.

The simplest rule to explain is pay for all or pay for none, within the group you have invited in person.

  • If you invite someone in person, cover their reasonable travel. Flights or trains, ground transport, lodging and meals during the offsite. Distance should not decide who can afford to come.
  • If you cannot fund travel for everyone invited, shrink the in-person group or change the format, rather than asking some people to pay their own way to a work event.
  • Publish the travel policy before invitations go out. Class of travel, booking window, who books, what is reimbursed and how quickly. Ambiguity favors people who are comfortable asking.
  • Book centrally where you can. Asking each person to book and claim back pushes cost onto people's personal cards and turns one colleague into the team's unofficial travel agent. Central booking, or at least a named owner for travel questions, keeps the burden off attendees.
  • Plan for the people furthest away. Check door-to-door time for your longest journeys, not just the average, so the location does not simply reward whoever lives closest to HQ.

Expenses, per diems and reimbursements follow your company policy and local rules, so align the details with finance before you announce anything.

A note on perks that don't land equally. Some benefits feel generous to one group and irrelevant to another: a destination that is a short hop for the HQ team and two flights plus a layover for everyone else, or a "bring your partner" option that only works for people without care duties. You cannot make every perk equal, but you can say openly what it is and is not, and offer a reasonable alternative where the gap is large.

PTO and time: is the offsite work?

Remote employees often lose personal time to attend an offsite in ways office staff do not: longer journeys, extra nights away, travel on weekends to catch a cheaper or only available connection. If that time is quietly treated as "your own," the people who live furthest away pay the most.

Decide and publish the rules:

  • Offsite days are work days. Nobody should use PTO to attend a work event they were asked to join.
  • Recovery time is planned, not begged for. If someone crosses several time zones or travels over a weekend, consider giving a lighter day or a day off afterward, set as policy so nobody has to ask.
  • Extending the trip is optional and clearly separate. If people want to add personal days before or after, explain how that works (who pays for what, how PTO is logged) without making it the default.

The goal is that a colleague four time zones away and a colleague who lives near the venue both end the week having given the company the same amount of their own time.

Hybrid facilitation: the pitfalls

If anyone joins remotely, you are running a hybrid event, and hybrid is harder than either fully in person or fully remote. The room naturally drifts toward the people who are physically present. Without deliberate design, remote attendees end up as an audience instead of participants.

Common pitfalls

  • The laptop at the end of the table. One camera, one mic, a dozen people in the room. Remote people cannot hear side comments or see the whiteboard, and soon stop trying to speak.
  • Room-first conversation. People in the room talk over each other, laugh at things remote people missed and make decisions in the break.
  • Physical-only materials. Sticky notes and flip charts that nobody captures digitally.
  • Ignoring time zones. Sessions scheduled for the venue's afternoon land in someone else's late evening.
  • No one watching the chat. Questions and objections from remote attendees go unseen.

What helps

  • Decide the mode per session. Some blocks are fully in person, some fully remote (everyone on their own laptop, even in the room), and only a few are truly hybrid. Fewer hybrid blocks, done well, beat a hybrid agenda done badly.
  • Name a remote advocate. Someone in the room whose job is to watch the screen and chat, bring remote voices in, and call out when the room is drifting.
  • Get the AV right. A camera that shows the room at eye level, microphones that pick up everyone, a screen big enough that remote faces are visible to the room, and a WiFi connection tested in the meeting room under real load. Our guide to checking venue WiFi covers the test.
  • Go digital-first for collaboration. Use a shared digital board everyone edits, instead of paper that only the room can see.
  • Call on remote people first. In discussions, start with the remote participants before the room warms up and dominates.
  • Keep hybrid sessions short. Remote attention fades faster. Build in breaks and share materials ahead.
  • Respect time zones. Put hybrid sessions in a window that is reasonable for remote attendees, and record or summarize anything they cannot attend live.

Before the day, run a short tech rehearsal with at least one person joining remotely, from the actual room, with the actual equipment.

For people who can't come: a real alternative, not a consolation prize

Some people will not attend, by choice or by circumstance. What they receive afterward signals whether they still count.

  • Share the outcomes, not just photos. Send a clear written recap of decisions, open questions and next steps within days. A channel full of group selfies without context mostly tells people what they missed.
  • Give them a voice in the decisions. Collect input before the offsite through a short survey or async doc, and hold a follow-up session where people who were not there can question and shape what was decided.
  • Plan a parallel moment. A remote social hour, a local meetup for people in the same city, or a small budget for a meal with nearby colleagues while the main group gathers. Keep it simple and genuinely optional.
  • Send something thoughtful, if you send something. A gift box can be a nice gesture, but it should not be the only thing. If you send one, send it to everyone who could not come, not only those who asked, and make sure it arrives in time and works for their dietary needs, location and customs rules.
  • Watch the follow-up. In the weeks after, make sure people who were not in the room are not quietly left out of projects that formed there.

The test is simple: three months later, could you tell from someone's work whether they attended?

A short planning checklist

  • Purpose written in one sentence; Zoom-replicable blocks moved out.
  • Expected, invited and remote-by-design lists agreed, with reasons.
  • Exception path that requires no personal disclosure.
  • Travel policy published before invites: covered for all invited in person.
  • Central booking or a named travel owner; no reliance on personal cards.
  • Location and dates checked against the longest journeys and time zones.
  • PTO and travel-day rules published; recovery time planned.
  • Session modes decided (in person, remote, hybrid) and a remote advocate named.
  • Room AV and WiFi tested under load, with a remote rehearsal.
  • Recap, follow-up session and parallel moment planned for those not attending.
  • Post-offsite pulse survey that compares remote and in-person experience where group size allows.

When multi-city logistics exceed in-house capacity

Many People Ops teams run a single-location offsite themselves without trouble. It gets harder when attendees fly in from several cities, arrivals spread across a day, the destination is new to you, and the venue must carry a properly hybrid session. Then flights, transfers, rooms and AV become a project of their own.

That is the work of a local event designer who knows the destination: which venues have meeting rooms and WiFi that hold up for hybrid sessions, enough private bedrooms for your group, sensible arrival logistics, and spaces for both focused work and unstructured time. At Vantly, local event designers shape a tailor-made team retreat or company offsite around your purpose and your group, and confirm venue details in writing rather than relying on listings. One point of contact and one invoice is how we aim to work. Our sample events show what designers have shaped for other teams; treat them as starting points a designer tailors, not fixed packages.

When you want real options for your dates and your group, you can get a custom quote.

FAQ

Who should attend a hybrid team offsite in person?

Start from the purpose. Expect in person the people the core work depends on, invite others who can choose freely, and design specific remote sessions for everyone else. Say clearly what is optional, and offer an exception path that needs no personal explanation.

Should the company pay travel for remote employees attending an offsite?

A simple, defensible rule is to cover reasonable travel for everyone you invite in person, or reduce the in-person group. Self-funded travel or flat amounts that favor people nearby tend to feel unfair.

Should employees use PTO for travel to a company offsite?

Generally no. Treat offsite days and travel days as work time, including weekend travel, and plan recovery time for long journeys. Make any personal extension optional and clearly separate.

How do you include remote attendees in a hybrid session?

Use fewer, shorter hybrid sessions, name a remote advocate in the room, set up a camera at eye level and good microphones, use a shared digital board, call on remote people first, respect their time zones and rehearse the tech with someone joining remotely.

What should you do for employees who can't travel to the offsite?

Collect their input beforehand, send a clear recap of decisions, hold a follow-up session where they can shape outcomes, and offer a parallel moment such as a local meetup or remote social. A gift is a nice gesture, not a substitute for being part of the decisions.

What work should an offsite be used for, versus video calls?

Use in-person time for what video does badly: trust building, hard trade-offs, open-ended problem solving, onboarding and unstructured time. Updates and demos usually work as well on a call.

Sources

Thread topics are taken from the URLs. No comment text is quoted or paraphrased; the four remaining threads returned 403 (network block) on a recheck on 6 Oct 2026 and still need browser re-verification before publish.