A company retreat invitation has two jobs: make people want to attend, and turn their replies into numbers an organizer can plan from. The second job is the harder one, because a yes still leaves open how many nights that person needs, when they land, whether they want the shuttle, and what they eat. This guide gives you three invitation templates, a map of which facts belong where, ready-to-adapt RSVP questions, a worked headcount example, and the message sequence from first date hold to final arrival note.
What a Company Retreat Invitation Has to Include
Whatever the retreat's shape, the invitation has to answer the same questions before anyone can reply usefully:
- Who is hosting and who is invited: everyone, one department, or a named list.
- Program dates and times, with the venue's time zone, stated separately from travel days. "Programming runs Tuesday 9:00 a.m. to Wednesday 3:00 p.m." is not the same as "block Monday through Wednesday."
- Venue and arrival or departure expectations: where to be by when, and when people are released.
- A reason to come, in one concrete sentence, plus the meals and activities provided.
- Attendance expectations and any guest allowance, stated plainly.
- A monitored contact that answers questions.
- A reply route and an RSVP deadline, set early enough to leave working days before any booking cutoff.
Anything beyond that belongs in the details panel rather than on the card. On a Greenvelope invitation the panel is enabled under Details, then Information, then the Enable Event Details toggle, and it holds the address, agenda, parking, attire and policy links.
Which Retreat Template Do You Need?
The three retreat shapes and what each invitation must settle; the RSVP questions for each are further down
| Retreat shape | What the invitation must settle |
|---|
| One-day local offsite | Arrival window, transport to the venue, whether the day replaces normal work hours |
|---|
| Overnight, organizer books rooms | Program dates versus travel days, which nights are covered, a reply deadline set ahead of the hotel's cutoff |
|---|
| Distributed team, employees book | Who pays, the approved booking method, a booking deadline after the reply deadline |
|---|
Each template is the full invitation message in two labeled parts: the card wording guests read first, and the details panel content that travels with it. Square brackets mark replacement fields; lines about who pays or what is expected are placeholders for your own policy.
Template 1: One-Day Local Team Offsite
No overnight stay, so the card stays short: the arrival window, the end time, and one reason to come.
Email subject line: [Team name] offsite, [day and date] at [venue]
Card wording:
[Company or team name] invites you to our [season or purpose] team offsite.
[Day, date]
Doors open [time]; programming [start time] to [end time], [time zone]
[Venue name], [city]
Join us to [reason for the day, in one sentence]. Breakfast, lunch and afternoon coffee are provided.
[Attendance expectation.]
Please RSVP on this invitation by [RSVP deadline]. Questions: [monitored contact name and address].
In the details panel: the address with a map link, parking and transit directions, the agenda, attire, and building access instructions if people need a badge.
Write the attendance expectation as one plain sentence of your actual policy, and name who to talk to about a conflict. For the reason line, one concrete draw beats a slogan: a first look at next year's plan, a guest speaker, or a working session the team has been asking for.
Template 2: Overnight Retreat Where You Coordinate Rooms
Two common problems with overnight invitations are travel days collapsed into program dates, and deadlines that run in the wrong order. Room requests arrive through the RSVP, so the reply deadline comes first, with working days after it for review and follow-up before the hotel's room block closes. Say both dates and why the first is firm.
Email subject line: [Company name] [year] retreat, [month dates] at [venue]: please reply by [date]
Card wording:
[Company name] [Year] Team Retreat
Programming: [day, date] [start time] through [day, date] [end time], [time zone]
Travel days: arrive [day] by [arrival deadline]; depart [day] after [release time]
Where: [Venue name], [city and state]
We have [number] days together to [reason, in one sentence]. All meals from [first meal] through [last meal] are provided, with a closing dinner on [evening].
[Attendance expectation, in one line.] [Guest allowance, in one line.]
Please RSVP on this invitation by [RSVP deadline]. The reply form asks which nights you need a room and about the shuttle; our room block at [hotel] closes on [hotel booking cutoff], so the deadline is firm.
Questions, or anything you would rather not put in a form: [monitored contact name and address].
In the details panel:
- Lodging: [Company name] is holding a block of rooms at [hotel] and covering [which nights]. We request your room from your reply; [hotel or travel contact] confirms it once it is booked.
- Getting there: [Who pays, and how travel is arranged.] A shuttle runs from [airport] on [arrival day]. Programming ends [end time] [time zone]; book departures no earlier than [earliest realistic departure], to allow for the ride back.
- Attendance and guests: the fuller version of the card's policy line: who to talk to about a conflict, and which parts of the program a partner may join.
- The agenda by day, what to pack for [activity], the shuttle schedule, the expense policy link, and the accessibility contact.
If partners are welcome at the closing dinner only, say so in the guest allowance line and note that a separate dinner invitation will follow; the workflow is under the message sequence. If the company covers only some nights, the lodging sentence is where that lives.
Template 3: Distributed Team, Employees Book Through the Approved Process
When people book their own travel, the invitation points at the policy rather than restating it. The deadlines run in sequence: reply first, then book before the negotiated rate or the policy window expires.
Email subject line: [Company name] all-team retreat, [month dates], [city]: reply by [date], book by [date]
Card wording:
[Company name] is bringing the whole team to [city] for [number] days.
Programming: [day, date] [start time] through [day, date] [end time], [time zone]
Suggested travel: arrive [day] evening; depart [day] after [earliest realistic departure]
Where: [Venue name], [address or neighborhood]
[Reason for the retreat, in one sentence.] Breakfast and lunch are provided each program day, plus a team dinner on [evening].
[Attendance expectation, in one line.] [Guest allowance, in one line.]
Please RSVP on this invitation by [RSVP deadline], then book your travel through [approved travel process or tool] by [booking deadline].
Questions, accessibility needs, or travel exceptions: [monitored contact name and address].
In the details panel:
- Booking your travel: book flights and your room through [approved travel process or tool] under [cost center or code] by [booking deadline]. [Company name] covers [what is covered]; anything outside that follows [expense policy]. Your booking is confirmed by [travel tool], not by your reply to this invitation.
- Attendance and guests: the fuller version of the card's policy line: who to talk to about a conflict, and which parts of the program a partner may join.
- The recommended hotel and any negotiated rate code, the agenda, ground transport options, and the expense submission deadline.
The suggested departure time matters more than it looks: programming that ends at 3:00 p.m. two hours from the airport quietly rules out any flight before early evening.
Where Each Fact Belongs
Retreat invitations get crowded when every fact lands on the card. Sort each one into four places before you write.
An information map for retreat communications
| On the card | In the details panel | Asked in the RSVP | Confirmed in the booking process |
|---|
| Host, audience, reason | Full address and map | Attending or not | Flight bookings |
| Program dates and times | Agenda by day | Nights requested | Room assignments |
| Travel day expectations | Hotel and rate details | Arrival window | Rate codes and billing |
| Meal and activity context | What to pack, attire | Shuttle interest | Shuttle seat roster |
| Attendance and guest policy | Expense policy link | Meal needs | Policy exceptions |
| RSVP deadline, booking cutoff | Accessibility contact | | Final rooming list |
The RSVP Questions, Ready to Adapt
On a Greenvelope invitation the third column is built with Survey Questions, added under Details, then RSVP Page, then Add a New Question, in four formats: dropdown, multiple choice, checkbox and write-in. They appear on the guest's RSVP page after the guest selects a response. A working set for the overnight template, with specific nights rather than a count:
Suggested survey questions for an overnight retreat
| Question as guests see it | Format | Answer options |
|---|
| Which nights do you need a room? | Dropdown | [Monday, June 8] only; [Tuesday, June 9] only; Both nights; No lodging needed |
| When will you land at [airport]? | Multiple choice | [Day] afternoon; [Day] evening; [Next day] morning; Traveling directly to the venue; Not yet known |
| Do you want a seat on the [airport] shuttle on [arrival day]? | Multiple choice | Yes; No, making my own way; Not yet known |
| Any dietary requirements we should pass to the caterer? (optional) | Write-in | Guest-written response |
Tailor the set to the retreat's shape: a one-day offsite usually needs only the dietary question and whether anyone needs a ride, and the distributed template drops the lodging question when rooms go through the travel tool. The lodging question is a dropdown so one answer cannot both request a night and decline lodging.
A shuttle yes records interest, not a seat; confirm the roster with the arrival instructions. "Not yet known" answers are your follow-up list. For this workflow, verify booking status against the hotel's confirmations or the travel tool's report, checked against your export, rather than relying only on a self-reported answer. A blank answer to the optional dietary question does not establish that someone has no restrictions, so reconfirm against the caterer's list closer to the date.
Keep payment details, passport or ID numbers and medical information out of these fields; the dietary question asks what catering needs to know, nothing more. Anyone needing an accommodation, a particular room, or a travel exception goes to the monitored contact instead, privately.
A Worked Headcount Example
One attendance total cannot determine every booking, which is why the replies have to carry more than yes or no. Take a two-night retreat with 48 people invited:
- 39 replied yes. All 39 attend the sessions, both provided lunches, and the closing dinner.
- 31 requested a room. The other eight live locally and drive in each morning.
- 55 room-nights. Of the 31, 24 asked for both nights and 7 for the first night only. Occupancy assumption, stated before anyone converts people into rooms: one room per person requesting lodging, single occupancy. That is 31 rooms on the first night and 24 on the second.
- 22 shuttle seats requested. All 22 asked for the same journey, the [airport] pickup on arrival day. Nine of the overnight group are driving themselves, and the eight locals never needed it.
- 43 at the closing dinner. The 39 attending employees plus four partners, whose attendance came in through replies to the separate dinner mailing described below, and who attend nothing else.
Five different totals from one retreat. Change the occupancy assumption to shared doubles and the room number moves again; write the assumption down first.
The handoff runs like this. Export the guest list and responses from the Track step using the download icon at the bottom of the guest list. Sort the spreadsheet by the lodging question to build a requested rooming list, send that to the hotel, and treat what the hotel confirms as the confirmed rooming list. Submitting an RSVP or a lodging request does not itself confirm a reservation: rooms and flights are confirmed in the hotel's, airline's or travel tool's records, and shuttle seats are confirmed by you or the shuttle provider against the roster. Re-export before the rooming list goes out, compare against the previous version by hand, and work the changes individually.
Product details checked October 22, 2026.
The Message Sequence
Retreat communication runs in four stages, with who receives each one varying by purpose rather than by one fixed list: the hold and the invitation may reach the same people, the follow-ups go to subsets, and a partner dinner adds its own mailing.
- The early hold. Once the dates and city are confirmed, send a save the date or announcement so people can protect the time. Three to six months ahead is a useful starting point for a larger corporate event, with more notice when there is travel or a multiday program. Our corporate save the date wording guide and business save the date email templates cover that send.
- The full invitation. The template above, sent as an invitation mailing: on Greenvelope, RSVP functionality comes with invitation mailings, and save the dates, announcements and cards do not collect attendance RSVPs.
- RSVP reminders and booking follow-ups. Scheduled RSVP reminders go only to contacts who have not responded, which makes them the tool for chasing replies before the deadline. People who said yes but have not booked will never appear on that list; build theirs from the export checked against the hotel or travel tool confirmations, and follow up with them directly before the booking cutoff.
- Final arrival instructions. Event reminders go to contacts whose RSVP status is attending, so the arrival note, the confirmed shuttle roster and the first session location reach the people who are coming without landing on anyone who declined.
Partners and other partial-audience activities deserve their own send. Permission is your policy. The plus-one settings on whichever mailing invites the partner control the allowance and which companion details are requested. The guest supplies the name and attendance when they respond. And what anyone may attend is decided by which mailing they are on, never by a survey answer or a contact tag. For dinner-only partners, pair the employee retreat mailing with a separate closing-dinner mailing carrying a plus-one allowance. Our guide to adding custom questions to an online RSVP covers what survey answers can and cannot do.
Designs Built for This Send
A retreat invitation reads better when it looks like it came from the company rather than from a calendar app. Two current designs in the company retreat collection: Painted Grove by Ani Somi, which suits an outdoor or lodge venue, and Refined Details by Jen Montgomery for a more formal program. Wording, fonts and preset colorways are editable in the Greenvelope editor, though what can be changed varies by design and some elements are adjustable only through the optional paid design service. For templates, explore the full company retreat collection and pick the one that matches your venue.
Pricing works as it does for any other mailing: single mailings start at $19 for a guest list of up to 20 people, with pricing based on list size and no subscription required. The invitation is its own mailing even when it reuses the same contacts as the hold, and so is a separate dinner mailing.
Frequently Asked Questions
What should a company retreat invitation include?
A company retreat invitation sent through Greenvelope should name the host and audience, state the program dates and times with the venue's time zone separately from the travel days, give the venue with arrival and departure expectations, offer one concrete reason to come plus the meals provided, state the attendance expectation and any guest allowance, name a monitored contact, and close with a reply route and an RSVP deadline. The agenda, parking, attire and policy links belong in the details panel.
How do you word an invitation for an overnight company retreat?
Lead with the programming window, then list the travel days underneath as a separate line so nobody books the wrong flight. State who is covering lodging and how rooms get booked, in your own policy wording. Ask which specific nights each person needs, and explain that the reply deadline is firm because the hotel's room block closes after it. A Greenvelope invitation mailing collects those answers as survey questions at the same time the guest replies.
What is the difference between the RSVP deadline and the booking cutoff?
The RSVP deadline comes first: replies, including room requests, are due early enough to leave working days for review and follow-up. The booking cutoff is when rooms or flights must actually be reserved, by the organizer submitting the rooming list before the hotel releases the block, or by each employee booking before a negotiated rate expires. State both, and make clear that replying is not the same as being booked.
What questions should you ask on a company retreat RSVP?
Match the questions to the retreat's shape. An overnight retreat with organizer-booked rooms asks which specific nights a room is needed, with a no-lodging option, plus an arrival window, shuttle interest and an optional dietary question, offering a not-yet-known answer where guesses would hurt. A one-day offsite usually needs only the dietary question and whether anyone needs a ride. In Greenvelope these are survey questions added under Details and then RSVP Page, in dropdown, multiple choice, checkbox or write-in format. Keep payment details, passport or ID numbers and medical information out of the form.
How far in advance should you send a company retreat invitation?
Send the early date hold once the dates and city are confirmed, with three to six months ahead as a useful starting point for a larger corporate event and more notice when there is travel or a multiday program. The full invitation follows once the venue, agenda and travel policy are settled, far enough ahead that people can still reply and book inside its deadlines. Both are planning guidelines, and a venue or airline deadline can move them.
Is attendance at a company retreat mandatory?
That is a question for your own policy, and the invitation should state the answer plainly rather than leave people guessing. If attendance is expected, say so and name who to talk to about a conflict. If parts of the program are optional, label them separately so they do not read as expectations. Vague wording here produces replies that are hard to plan from, because people hedge when they are unsure whether they may decline.
Can employees bring a partner to a company retreat?
Only if your policy allows it, and the invitation should say which parts of the program a partner may join. Three things stay separate: permission comes from your policy; the plus-one settings on the mailing that invites them control the allowance and the companion details requested, which the guest supplies when responding; and what they may attend is decided by which mailing they are on. A survey answer or an allowance does not by itself limit anyone to one activity. For a dinner-only arrangement, send the retreat mailing to employees alone and a separate closing-dinner mailing with a plus-one allowance.
How do you send final arrival instructions only to guests who are attending?
Use the two reminder types for their two audiences. In Greenvelope, scheduled RSVP reminders go to contacts who have not yet responded, the tool for chasing replies before the deadline. Event reminders go to contacts whose RSVP status is attending, the tool for the arrival note, the shuttle roster and the first session location. Sending logistics to the whole invited list means people who declined receive instructions for a trip they are not taking.
Related Resources