Team Activity RSVP Form Template
A team outing RSVP that settles the what and the when — availability windows, a ranked activity vote, and food notes for the group order.
We're getting the team out of the office — but democracy first. Say if you're in, rank the options, and flag the dates that work.
Team outings die in the planning channel. Someone posts "should we do something Friday?", four people react with emojis, two propose conflicting activities, and the thread scrolls into oblivion until the quarter ends. The failure is structural: a chat can host enthusiasm but cannot count it. This template is the counting machine — one link that captures who is in, which activity actually wins, and which dates survive contact with everyone's calendar.
Why these fields. The status question offers three real answers, because "depends on the date" is the most common truth on any team and forcing it into yes/no produces phantom headcounts. The activity vote uses a ranking block rather than a single choice, and that distinction decides outings: with four options and twelve voters, first-place votes usually split into a four-way tie, while rankings surface the option everyone ranked second — the true consensus pick that a simple poll structurally cannot find. The date question is a multi-select of concrete windows, not an open "when are you free?" that invites essays. Food notes appear only for people who are in or date-dependent — a logic rule spares the sitting-out crowd a question about a meal they will not eat — and the opt-outs get their own ending that thanks them without guilt, because the fastest way to kill future participation is to make "no" feel expensive.
What we left out. Budget questions (the company pays or it does not; either way it is not the form's business), venue suggestions as free text (options are votable, essays are not), and manager-visibility toggles — this is a social instrument, not a performance record.
Who uses this. Team leads and office managers planning quarterly outings, remote teams coordinating an on-site social day, sports and hobby clubs picking their next session, and the one organized friend every group deputizes by default.
Make it yours. Swap the activities and date windows for your real candidates — three to five of each keeps ranking meaningful. Add a webhook so each vote posts to the team channel as it lands; visible momentum reliably pulls in the stragglers. Close the form at your decision deadline, then export the CSV and tally first choices (or weight the rankings) — with twelve people the winner is usually obvious from the first column.
Democracy, then dinner. The form ends arguments by making preferences legible: the activity that wins deserved to win, the date that survives was actually possible, and the group order already knows about the shellfish allergy. All that remains is showing up. Run it once and the next outing plans itself — people start asking for the link before you post it.
Frequently asked questions
How does the ranked vote get counted?
Each response records the full order. Export the CSV and tally first choices — or weight rankings — in a spreadsheet; ties break on second choices.
Why do only some people see the food question?
A logic rule shows it to people who are in (or date-dependent) and skips it for those sitting out — their ending comes right after the vote.
Can results post to our team channel?
Add a webhook and every reply POSTs in real time — a simple workflow can announce each vote as it lands, which visibly boosts turnout.
What if someone changes their availability?
They resubmit — it takes thirty seconds. Timestamps in the responses view make the latest answer obvious when you lock the date.