The Scenario: The Company Has a Booth. Nobody Agreed on Anything Else.
DataStream's engineering team had a 10×10 booth at Austin Tech Week. Conference dates: fixed. Booth assignments: shared doc. Everything else — hotel blocks, which breakout sessions to attend as a team, the client dinner with three enterprise prospects, the internal retrospective — was completely uncoordinated.
David, the engineering manager, got voluntold to "figure out the logistics." The team was spread across Seattle, New York, Austin (the two locals), and one remote engineer dialing in from Berlin. The conference ran Thursday to Sunday. Berlin was 7 hours ahead. Finance needed expense reports within 5 business days. Three different department heads wanted face-time with the team at different meals.
The constraints:
- Two engineers had standing on-call rotations that couldn't be fully cleared
- The client dinner had to land on Friday — the only night all three external guests were free
- The company had a $250/person/day meal cap on reimbursable expenses
- One teammate keeps kosher; another is vegetarian
- The team wanted to vote on which evening activities to attend together vs. split up
Part 2 — How SquadPlan Ran the Coordination
Building the Event and Onboarding Twelve People in One Link
David created the "Austin Tech Week" event and sent a single invite link to all twelve participants. Within an hour, eleven had joined; the Berlin engineer joined 6 hours later after waking up. From that point, all communication happened in the event — no "reply-all" threads, no pinging people on Slack.
One invite link. Email invites for the two non-SquadPlan users auto-sent with a join link. Everyone's in within the hour.
Polls to Settle Every Group Decision Fast
Rather than putting decisions in Slack threads where they'd get buried, David used SquadPlan polls. "Which evening do we do the team dinner?" got six options with a 24-hour deadline. "Which keynotes should we attend as a full group?" used a ranking poll — attendees sorted options by preference; the system aggregated the rankings and highlighted clear consensus.
Creating a ranked-choice poll for session selection. Deadline enforced automatically — no more waiting for stragglers to vote.
All polls in one view. Three decisions resolved in the first 24 hours before anyone landed in Austin.
The Shared Itinerary Replaced Four Shared Docs
The conference schedule, booth coverage assignments, client dinner details (The Driskill Grill, 7:30pm, 15 East 6th St), and the Saturday night team dinner reservation at Uchi — all in the shared itinerary. Each item had a start time, end time, location, and notes field. Attendees could add their own items without overwriting anyone else's.
The living itinerary. Booth coverage shifts, client dinners, team sessions — visible to everyone, editable by organizers, and exportable to individual calendars with one tap.
Adding the Friday client dinner. Location, time, notes about dietary requirements, and an attached link to the reservation — all in one item.
Expense Tracking for Reimbursement-Grade Records
With a $250/person/day cap, tracking mattered. The group charged meals to individuals (not a corporate card), with the understanding that SquadPlan would handle the reconciliation for the expense report submission.
Finance loved this: The expense export gave each participant a per-day breakdown with the team total — exactly the format their reimbursement portal required. Three engineers submitted and got approved same week.
Conference expenses tracked by day and participant. The team's $3,100 in combined expenses settled to individual balances in minutes after the last dinner.
The retrospective happened. The client dinner was a success. The Berlin engineer joined the Saturday team dinner via FaceTime — slightly awkward but fully informed because he'd been watching the itinerary all week.