Team offsite invitation email: three copy-paste templates for the announcement, the logistics email and the final note

The templates below are written for the EA, office manager or People Ops lead who has been asked to "send something out" today. Each one has subject-line options, a send-when and sent-by line, fill-in brackets and a short "must include" check, and five optional inserts cover leadership, remote colleagues, conduct, quiet space and photos. This page is the email wording; designed invitation cards are a different job. The timing is rough guidance, so adapt it to your group size, the season and how far people travel. For the full planning timeline around these emails, see our first-time EA company offsite checklist.

Jump to the templates: Email 1, Email 2, Email 3.

The three emails at a glance

Each email has one job. If a detail does not help with that job, it belongs in the next email or on the shared page you link from all three.

The six-to-eight-week and week-before timings line up with the timeline in our first-time EA checklist. For a one-day event close to the office, you can often fold Email 2 and Email 3 together. For an overnight where people fly in from several cities, or a Hudson Valley retreat with a shuttle from Midtown Manhattan, keep all three.

Email 1: the announcement (copy and adapt)

Send when: as soon as the dates and region are held. Sent by: the leader, from their own account.

Subject line options:

• Save the dates: our team offsite, [dates]
• [Team name] offsite, [month]: dates and why we're going
• Hold [dates] for our offsite in [region]

Hi all,

We're taking the team away from [day, date] to [day, date] in [region or town]. [Travel day: we'll leave [city] on the afternoon of [date] and be back by [time] on [date].]

Why we're going: [one or two sentences on the purpose, for example "to agree our plan for next year and spend real time together outside the usual meetings"].

Who's invited: [everyone on the team / the leadership group / named teams]. [Attendance is expected for everyone who can travel / Attendance is optional, and we'd love you to come.] If the dates clash with something you can't move, tell [organizer name] this week.

What's covered: the company covers [accommodation for [number] nights] and [meals during the program]. [Transport between [city] and the venue — delete if not included.] [Lunch on travel days — delete if not included.] [Evening bar — delete if not included.] [Activities — delete if not included.] Travel and expenses follow our [travel policy link].

What happens next: [organizer name] will send a short registration form by [date]. You'll find everything in one place here: [link to the shared offsite page].

A calendar hold is on its way. Please accept it so we can plan numbers.

[Leader name]

Calendar hold to send the same day:

Title: [Team name] offsite, [region] (travel days included)

Day 1: [date], from [shuttle departure time or "travel from [time]"] so you can block the afternoon

Last day: [date], back in [city] by about [time]

Notes: Details and registration to follow from [organizer name]. Conflicts: tell [organizer name] by [date]. Shared page: [link]

If some attendees use another calendar app, that's fine: Google's Calendar help notes, "You can add anyone with an email address to your event, even if they don't have Google Calendar."

Must include: the purpose in the leader's words; the dates with travel days; the region or town (name the venue only once the contract is signed); who is invited and whether attendance is expected; only what is contracted under "what's covered"; the next step and its date; the calendar hold.

A few notes on the wording. Keep "what's covered" to what the venue quote actually includes, and delete any bracketed item that isn't contracted, so the announcement never promises something you will have to take back. Say whether attendance is expected using the policy your leadership and HR have agreed, and link the policy rather than restating it; the email should never set policy by accident. If your company hasn't published a travel policy yet, decide it first, as our guide to hybrid and remote inclusion recommends. How travel days count for paid time or for non-exempt colleagues is a question for HR or payroll, not for this email.

On subject lines: clear beats catchy. A subject line that carries the dates and the word "offsite" gets found again when someone searches their inbox three weeks later, which matters more than a clever phrase.

Email 2: logistics and registration (copy and adapt)

Send when: roughly six to eight weeks out for an overnight, once the venue is contracted. Sent by: the organizer, who also owns the replies.

Subject line options:

• Offsite registration: please reply by [date]
• [Team name] offsite: travel, rooms and one short form (due [date])
• Action needed by [date]: offsite registration

Hi all,

Here's what you need for [offsite name] on [dates] in [region or town], plus one short form. Please fill it in by [reply date]. This date comes from the venue's deadlines, so we can't extend it.

The form: [form link]. It asks for:

• [Your full name as it appears on your ID — if the company books flights or trains]
• Your departure city and whether you'll take the group shuttle or travel on your own
• Which nights you're staying, and if you'll arrive early or leave late
• Dietary needs and allergies
• Anything you need to take part fully, from access to the rooms to a quiet space or a private room need. Only [organizer name] will see these answers.
• An emergency contact

Getting there: [A shuttle leaves from [named street corner or building entrance] at [time] on [date] and returns from the venue at [time] on [date]. If you miss it, call [name and mobile] and we'll sort out a car or train.] [If you're driving: parking is at [location]; drop-off is at [entrance].] [If you're booking your own travel: please book under our [travel policy link] by [date].] More on the plan: [link to the shared offsite page].

Arriving: check-in opens at [time]. [Early arrival is possible from [time] — tell us in the form.] The first session starts at [time].

Accessibility and accommodations: [At the venue: list only the access features the venue has confirmed in writing.] If you need an accommodation to take part, tell [name, email, phone] by [date], or use the form. Asking early gives the venue time to arrange it.

Agenda: the draft is here: [agenda link, version and date]. It will change a little; the link always shows the latest version.

Questions? Reply to this email, so they all come to one place.

Thanks,
[Organizer name]

Must include: one form and one reply date; the travel and transport plan, including the pickup point, time and what to do if someone misses it; the arrival window and parking or drop-off for drivers; dietary and access questions in the same form; the agenda draft link; one reply-to address.

How to set the reply date. Take it from the contract, not from a guess. Find two dates: the date the venue or hotel needs your rooming list, and the date the kitchen or caterer needs the final count and dietary list. Use whichever comes first, then set the reply date a few days earlier so you have time to chase late replies. If a private chef is cooking, ask the chef for their date, because a private chef may need the final list earlier than a restaurant would. Our guides to hotel attrition and release dates and the food and beverage minimum explain why those deadlines decide what you pay for.

Rooms. The form asks which nights people are staying, when they arrive and whether they have a private access or room need. It should not imply that anyone will share. If your company's policy does pair colleagues in rooms, add a separate line about it that matches the policy; never plan for shared beds. Our guide to private rooms versus shared beds covers how venues count capacity.

Dietary and access, once. Ask both in the same form, with the cutoff the kitchen gave you, so nobody is asked twice. The dietary and allergy workflow covers the fields and the severity tag, and the venue accessibility checklist covers how to ask privately. A New York City government guide, useful well beyond New York, sets out what invitations and other promotional materials should say about access: "What accessibility features will be present, even absent a specific request." and "Who to contact to request an accommodation (name, email, phone)." That comes from the Mayor's Office for People with Disabilities' Planning an Accessible Event guide (May 2025). Its request deadline is written for City agency events open to the public, so for an overnight offsite, ask in the registration form, well before rooms and travel are booked.

Transport. For a group traveling together, the pickup point and time are the lines people need most, so name a specific corner or entrance rather than "the office". Our group transport guide covers the shuttle plan itself. The emergency contact you collect here feeds your event emergency action plan, which explains who should hold that information and how. For when to share the agenda with the venue and attendees, see the offsite agenda template.

Email 3: the final "know before you go" note (copy and adapt)

Send when: the week before. Sent by: the organizer.

Subject line options:

• Know before you go: [offsite name], [dates]
• See you [day]: where to be and what to bring
• Final details for [offsite name]

Hi all,

We're nearly there. Here's everything for [dates] in one short note.

Where to be: [Shuttle: meet at [named street corner or building entrance] at [time] on [date]; it leaves at [time].] [Driving or rideshare: the address to use is [address drivers and rideshare apps find]. Use the [group / main / side] entrance, not [the other entrance].] Check-in opens at [time].

First session: [time] in [room].

What to wear and bring: [dress code]. [We'll spend time outdoors, and evenings can be cool, so bring a warm layer and comfortable shoes for walking between buildings after dark.] [Bring your laptop for [sessions] / Laptops aren't needed.]

WiFi: we'll share the details when you arrive. [If phone signal matters to you, it's worth checking your carrier's coverage for the venue's area before you leave.]

On-site contact: [name], [mobile]. They're the person to call if you're running late, can't find the entrance or need anything during the offsite.

Agenda and safety: the latest agenda is here: [link]. The short emergency sheet is here: [link].

[For tips on traveling and making the most of the days, see our attendee guide: [link].]

See you soon,
[Organizer name]

Must include: the pickup point and time, or the address drivers can find and the entrance to use; the check-in time and first session; what to wear and bring for the setting; WiFi and laptop expectations; the on-site contact's name and mobile; links to the agenda and the short emergency sheet.

The on-site contact is usually the local coordinator at the venue or on the event team, not someone back at headquarters, so check whose mobile you print. Some inns and estates have a separate group or service entrance, so ask the venue which entrance drivers and rideshares should use. Keep WiFi passwords out of email. On signal, ask the venue rather than assuming; there's no need to warn people that coverage is poor unless the venue tells you it is.

This email gives attendees one contact, not the full call sheet. The call sheet lives in your company offsite day-before runbook, and the attendee version of the emergency plan comes from the event emergency action plan template. For the attendee's own checklist, you can link our company offsite attendee guide.

Optional inserts (paste into any email)

Each insert is one or two sentences. Use only the ones that apply, and follow the link for the full wording guidance.

Leadership or confidential offsite. "This is a leadership offsite, so please keep the details within this group for now. We'll share the plans with the wider team on [date]." Describe the venue in neutral terms ("we'll be staying at [venue]"). Avoid words that promise you'll have the place to yourselves, such as "private", unless you have a confirmed full-house buyout, because the words in the invite become the promise; our guide to true buyouts versus soft room blocks explains the difference.

Remote and non-attending colleagues. "If you're not joining in person, here's what you'll get and when: [the session you can join remotely / a recap by [date]]." Who is expected, invited or remote by design is a policy decision; see hybrid and remote inclusion.

Expectations and conduct. "Our usual standards apply throughout the offsite, including the evenings: [link to your conduct note]." For the full invite and pre-read language, use our code of conduct and alcohol norms guide.

Quiet space and optional activities. "[There will be a quiet room throughout the program.] [Activities marked optional really are optional.]" Our guide to quiet rooms and sensory breaks has the full invite wording.

Photos. "We'll take some photos during the offsite. If you'd rather not appear in them, let [name] know." The photo-consent section of the code of conduct guide covers how to handle it.

Who sends what, and why it matters

The leader sends the why; the organizer sends the logistics and owns the replies. When the purpose comes from the person who called the offsite, it explains why the dates matter in a way a logistics email can't. When the logistics come from one organizer, every question lands in one inbox instead of scattering across Slack threads and side conversations.

Keep one living page or document for the details, such as the shared offsite page in the templates, and link it from all three emails. Each email then stays short, and when something changes you update the page rather than sending a correction. Plain wording helps too. Digital.gov's plain language principles put it simply: "Have a topic sentence." "Use the active voice." "Organize the information." The templates follow that pattern, with each block opening on the thing people need to know.

The same split applies when you work with an outside planner: as our guide on how to brief a local event designer explains, invitations and the "why we're doing this" note usually stay in-house, while the logistics behind them come from whoever is running the event.

Five mistakes that cause a second email

1. Announcing before the dates, region or travel policy are set. Every unsettled detail turns into a correction email. Hold the dates, pick the region and publish the policy first, as our hybrid and remote inclusion guide recommends.
2. A reply date after the hotel's or kitchen's deadline. You end up guessing numbers or paying for rooms and meals nobody uses. Set it from the contract, as in Email 2, and see hotel attrition and release dates.
3. Asking dietary and access needs in two places. People answer one and miss the other. Use one form, per the dietary and allergy workflow.
4. Promising the whole venue when you have a room block. If other guests are at the inn, the invite has overpromised. Read the true buyout guide linked in the inserts above before you choose the words.
5. Leaving travel days out of the calendar hold. People book meetings over the afternoon the shuttle leaves. Put the departure time in the day-one hold.

If the dates themselves change after you've announced them, tell attendees once, with the new dates and what happens next; our guide to changing the event date after a deposit covers that message. Running a single-evening party rather than an offsite? The holiday party checklist has its own invitation steps.

Setting the templates up in Gmail or Outlook

Saving each email as a template means you can reuse it for the next offsite and keep the wording consistent. In Gmail, templates are switched on from the Advanced tab in Settings, and Google's help page on templates notes: "Important: You can only turn on and use message templates from Gmail on your computer." In Outlook, Microsoft's guide to email templates says "you can save templates using the Mail Templates built-in feature or the My Templates add-in, depending on the content and purpose of the template." Mail Templates suits full emails like these; the My Templates add-in suits shorter snippets such as the inserts. Microsoft adds that "To use Mail Templates and the My Templates add-in, your account needs to have a qualifying Microsoft 365 subscription." If you prefer, keep the three emails in a shared document and paste from there.

Where a local event designer helps

Your team keeps the invitations and the why. What those emails depend on is a set of logistics details that only come once the event is planned: the address drivers can find and the entrance to use, the shuttle pickup point and times, check-in and early-arrival options, the rooming-list and final-count dates, and the handoff of dietary and access needs to the kitchen.

A Vantly local event designer who knows the destination can supply those details and build a tailor-made plan around your dates, from the venue and meals to transport and the on-site coordinator people will call. Our intent is one vendor, one PO for the event, rather than a separate contract and deposit for every vendor. You can see sample events as examples a designer tailors to your team, or browse local event designers by destination. For the format itself, our company offsite, team retreat and corporate retreat pages are good starting points. When you're ready, get a custom quote.

Frequently asked questions

When should you send a team offsite invitation?

Send the announcement and a calendar hold as soon as the dates and region are held, so people can protect them. Follow with a logistics and registration email roughly six to eight weeks out for an overnight, and a short final note the week before. Adjust the timing for how far people travel.

What should an offsite announcement email include?

Why you're going, in one or two sentences from the leader; the dates, including travel days; the region or town; who is invited and whether attendance is expected; only what the company has contracted and covers; and what happens next. Send a calendar hold the same day, and name the venue once the contract is signed.

Who should send the offsite invitation?

Usually the leader sends the announcement, because the "why" should come from them. One organizer then sends the logistics and registration emails and owns the replies. One sender for logistics means one place for questions, and a single linked page keeps the details from scattering across email and chat threads.

How many emails should attendees get before an offsite?

Three is usually enough: the announcement with a calendar hold, a logistics and registration email with one form and a firm reply date, and a final "know before you go" note the week before. Add one polite reminder to people who haven't replied, rather than resending everything.

What goes in the final email before an offsite?

Keep it scannable: the shuttle pickup point and time, or the address drivers can find and the entrance to use; check-in and the first session; what to wear and bring; WiFi and laptop expectations; and the on-site contact's name and mobile, usually the local coordinator. Link the agenda and the short emergency sheet.

How do you word an invitation for a confidential leadership offsite?

Keep it short and factual, ask attendees to keep the details within the group, and say when the wider company will be told. Describe the venue in neutral terms, and don't suggest you'll have it to yourselves unless you have a confirmed full-house buyout, because the words in the invite become the promise.

When should the RSVP deadline be?

Take it from the contract. Find the date the venue or hotel needs your rooming list and the date the kitchen needs the final count and dietary list, use whichever comes first, and set the reply date a few days earlier so you have time to chase late replies.

How do you tell people whether the offsite is mandatory?

Say it plainly in the announcement, using the policy your leadership and HR have agreed: who is expected in person, who is welcome, and how to raise a conflict. Link the travel and expenses policy rather than summarizing it, so the email never sets policy by accident.

Ready to send the first email?

Share your dates, region and headcount, and a local event designer can put together a tailor-made proposal with the logistics details your emails need. Get a custom quote.

Related guides

• First-time EA company offsite checklist
• Offsite agenda template
• Company offsite day-before runbook
• Dietary and allergy workflow for company offsites
• Company offsite attendee guide

Sources

• NYC Mayor's Office for People with Disabilities, Planning an Accessible Event (May 2025), "Invitations and Publicity Materials", p. 17
• Digital.gov, Plain language principles
• Google, Gmail Help, Create a template in Gmail
• Microsoft Support, Create email templates in Outlook
• Google, Google Calendar Help, Invite people to your Calendar event

All sources checked October 2026.