Team Offsite Planning Checklist: Headcount First

What is a team offsite planning checklist, and why does it start with headcount?

A team offsite planning checklist is the ordered sequence of decisions you work through to run a company offsite: objectives, confirmed headcount, venue, travel, agenda, follow-up. The word that does the work there is ordered. Beds, transfers, catering and swag are all priced per person, which means every one of them is a bill written against a number you commit to in advance.

Most checklists you will find put the venue first and attendance somewhere near the end, filed under a line like "gather RSVPs". That ordering is backwards, and it is expensive. Once you have signed for a room block, you have already promised a hotel a number you do not yet have.

Headcount first means something specific. It means you do not sign anything priced per head until you can point at a list of names where each one has actively said yes, with a written rule for what silence counts as.

Quick summary: Lock a confirmed headcount before you sign anything priced per head. Work backward from the venue's minimum-guarantee date, set your internal RSVP deadline seven to ten days ahead of it, and chase non-repliers on fixed dates instead of waiting on them. That order is what keeps beds, catering and transfers from being billed against a number nobody actually confirmed.

That list is not the same thing as the invite you sent. Expect about a quarter of the team to stay silent unless someone chases them: across more than 70,000 tracked events, business invitations get a median response rate of 74.6 percent (Greenvelope, 2026). The gap between "I invited forty people" and "thirty-one have confirmed" is the entire difference between a trip that lands on budget and one that does not. Getting from the first number to the second is a process, not an assumption, and it is the same discipline that makes corporate event RSVPs manageable at any size.

Everything below is sequenced around locking that number before you spend against it.

How far ahead should you start planning an offsite?

Eight to twelve weeks is the lead time one retreat vendor publishes in its own planning guide (planretreat.com, 2023). That is one company's estimate rather than an industry figure, so read it as a floor. Anything involving flights, a venue with a small room block or a peak season pushes you further out.

The first two weeks are not about venues. They are about four decisions you cannot reverse later: what the offsite is for, the ceiling you are allowed to spend, the date window, and who is invited.

Write the invite list down as names in week one, even if it changes. You need a maximum to price against before you can shortlist anywhere.

What does an offsite actually cost per person?

One retreat vendor publishes a per-person range of $200 to $500 for a company offsite, alongside an 8 to 12 week lead time. Read that for what it is: a vendor's own 2023 estimate, with no methodology, no sample and no note on region or currency. It is a bracket to open the budget conversation with finance, not a benchmark to defend in a spreadsheet.

The useful part is not the number. It is which lines inside it move when your headcount moves.

Most of the money sits in the top four rows, and every one of them is billed against a number you commit to in advance. Get the count wrong by three people and you have not made a rounding error, you have bought three of everything for nobody. Budget structure and approval sequencing are covered in more depth in our guide to corporate event budget management.

What is a minimum guarantee, and why does it set your RSVP deadline?

A minimum guarantee is the number you promise the venue in writing by a stated date, and it is the number you pay for whether or not those people arrive. Hotels and conference venues use it because they buy food, staff shifts and linen against your figure. Most contracts let you revise the number upward after the cutoff, sometimes at a surcharge, and almost none let you revise it down.

Room blocks work the same way under a different name. An attrition clause says you have reserved a set number of beds, and if fewer are slept in you pay a percentage of the difference anyway.

So the date that governs your whole checklist is not the offsite itself. It is the final-numbers date buried in the contract, often somewhere between one and three weeks before arrival, and it varies by venue.

How do you set an RSVP deadline backwards from the venue's final-numbers date?

Work backwards, not forwards. Put the venue's final-numbers date at the bottom of a page and build the calendar upward from it.

1. Day 0: the guarantee date. The number you give the venue on this day is the number you pay for. Write it in the calendar as a hard stop, not a reminder.
2. Day −7 to −10: your internal RSVP deadline. This is the date you tell the team. The gap gives you a working week to reconcile replies, catch the people who answered in a thread instead of the form, and confirm dietary counts before the kitchen locks them.
3. Day −12 to −15: the second chase. Named, individual, and explicit: no reply by the deadline means you are counted as a decline in the number sent to the venue.
4. Day −18 to −21: the first reminder. A single group message with the link and the deadline in the first line.
5. Day −35 to −42: send the invitation. Anything earlier and people postpone answering; anything later and the chase window collapses into the guarantee date.

The two chase slots are the part most checklists leave out, and they are the reason the 7-to-10-day buffer exists. Without them your deadline and your guarantee date sit on top of each other, and every silent colleague becomes a bed you have already promised to pay for.

Keep the running count somewhere you can read at a glance rather than in a spreadsheet you rebuild every Monday. Tracking RSVPs without a spreadsheet covers the mechanics.

What should the invitation ask for besides yes or no?

A yes that arrives with nothing attached to it just moves the chasing to a later week. Ask for the rest while the person is already typing.

Five things belong in the same reply: dietary requirements and allergies, arrival and departure dates if travel is being booked centrally, whether they are willing to share a room or need a single, whether a partner is joining for the evening slot, and any accessibility need the venue has to know about in advance.

Sending a separate survey two weeks later means asking the same group to act twice, and the second ask reliably performs worse than the first. Worse, the answers land in a different place from the headcount, so the caterer gets one number and the kitchen gets another.

Keep it to those five. Anything you can decide without asking, decide yourself.

Invyt collects dietary requirements alongside the RSVP for free, and on Premium the dietary export pulls them out with the guest list, so the caterer gets one file instead of a reconstructed summary of three threads.

What counts as a confirmed head, and what does a non-reply mean?

A confirmed head is a guest who has clicked yes on the invite and whose name sits in the accepted column with a timestamp. Not a nod in the corridor, not a thumbs-up emoji on the Slack thread, not a manager saying "my whole team is coming." Those are intentions. The venue invoices against names.

Everything else is pending, and pending is the category that costs money, because it looks like a maybe and gets counted like a yes.

So write the rule down before you send the invite, and put it in the invite itself: if you have not replied by the deadline, and you have not replied to the two chases that follow it, you are counted as not attending in the number we send the venue. That sentence does more work than any reminder. It converts silence from an open question into a decision the non-replier has made by default, and it gives you something to point at when someone turns up expecting a bed.

Invyt holds each guest in one of three states, accepted, declined or pending, so the pending list is the chase list and nothing has to be reconstructed.

How do you chase the 20 to 30 percent who never answer the Slack thread?

The people who never answer are rarely refusing. They read the thread on a phone, meant to reply, and the message scrolled away. Treat chasing as a scheduled task with fixed dates rather than a mood that strikes you on a Thursday.

A sequence that works on a four-week reply window:

1. Day 0. Post the invite link in the channel and send the same link as a direct message. A channel post alone will reach roughly the people who were already going.
2. Day 7. Open the pending list and press the individual reminder on each name. One person, one nudge, no group shaming.
3. Day 12. Ask each team lead to raise it in their own standup. Peer pressure closes more gaps than any tool.
4. Deadline morning. Broadcast one reminder to everyone still pending, stating the cut-off hour and what silence will mean.
5. Deadline plus one day. Send the final message: "We send the venue our numbers tomorrow. If you have not replied by 5pm, you are going down as a no and there will not be a bed for you."

That last line feels blunt in a draft and lands as clarity in a channel. State the consequence once, in writing, and you never have to argue about it later.

What does each late drop-out and un-cancelled bed really cost?

Put a number on it and the argument ends. That same retreat vendor's $200–$500 per person range for a corporate offsite (planretreat.com, byline dated 2023, a vendor estimate with no stated method rather than an industry average) puts the middle of the bracket at roughly $300 per head, and the two failure modes below cost exactly the same.

$1,800 is a venue upgrade, a second facilitator, or the airport transfers for the whole group. It is not a rounding error on a 40-person budget.

The uncomfortable part is that the second row is the one people accept. A colleague who cancels politely two days before feels considerate. Financially they are identical to the person who ignored you for three weeks, because the hotel was promised the number before either of them spoke.

Which is why the deadline, not the invitation, is the thing that protects the budget.

What do you book once the number is locked?

Rooms go first. They carry the longest lead time and the earliest release date, and a room block held against a confirmed count is the one booking you rarely regret. If three people are still unconfirmed, hold three fewer rooms and ask the hotel what a late addition costs. Adding a bed is almost always cheaper than releasing one.

Transfers come next, because they price in steps rather than per head. A 16-seat coach costs the same for eleven people as for sixteen, so the confirmed number tells you whether you are booking one vehicle or two, and that decision is worth more than any per-person saving you will find elsewhere.

Catering is the last thing you commit, on the guarantee date itself, using the number your chase sequence produced.

Meeting space is sized to the group you have rather than the group you invited. A room set for forty with twenty-eight people in it kills the energy of every session you planned, and you paid extra for the feeling.

How should the agenda be built around the confirmed group size?

Group size changes the format, not just the room. At 12 confirmed, a single circle works for almost everything: one discussion, one facilitator, everyone speaks at least twice. At 30, whole-group discussion stops working after about twenty minutes because the quiet third never gets in, so you split into five or six groups and someone has to hold each one.

At 60, breakouts are the default and playback becomes the constraint. Ten groups reporting back for three minutes each is half an hour before you count the walking between rooms.

Do the arithmetic before you write the agenda. Divide your confirmed number by your ideal group size, that tells you how many breakout spaces and how many facilitators you need, and both of those are things you book, not things you improvise on the day.

Build the agenda after the number is locked, never alongside it. An agenda written for the invite list rarely survives contact with the group that turned up.

What do you do in the 48 hours after the offsite ends?

The invoice arrives against the number you guaranteed, not the number who ate. Pull the confirmed list up beside it and check the lines one at a time: beds, covers, transfers, any room you released before the cut-off. Billing errors are easiest to argue the week the event ends and nearly impossible to argue a month later.

Write down separately who actually turned up. An RSVP list records who said yes, not who walked through the door, and the gap between those two numbers is the single most useful thing you will carry into next year's guarantee.

Then send the follow-up while people still remember the room. Every action gets an owner and a date, and it goes to the same list you invited, so nobody has to ask what was decided.

What is the full week-by-week offsite checklist?

Here is the whole sequence in one place, anchored on the venue's final-numbers date rather than on the trip date itself. Counting backwards from the guarantee keeps the order honest.

Keep the list somewhere both you and your finance contact can open, not in a personal inbox. A shared RSVP tracker survives the week you are on annual leave.