I'm In!

Organizer Guide

Best practices and deeper concepts for creating and managing events.

Event model

Events are identified by a short user code and a URL-friendly event slug. The public page lives at /{user_code}/{event_slug} and shows details, slots, and comments.

Single-day vs multi-day

  • Single-day: event has starts_at and optional ends_at.
  • Multi-day: the system creates occurrences (one per date). Slots can be linked to an occurrence.
  • Optionally keep the same time and/or slots across all days.

Slots and capacity

  • Name your slots clearly (e.g., “Volunteers – Setup”).
  • Set capacity; participants see remaining spots in real time.
  • Types supported: people, item, or time-based slots.

Sharing & preview

  • Use the provided share link on the event card to invite participants.
  • Preview the public page from your Dashboard before sharing widely.
  • Send reminders from the participants panel in your Dashboard; automated reminders may also be sent.

Managing sign-ups

  • Track who’s signed up and remaining capacity from the dashboard.
  • Cancel a signup if necessary; capacity updates automatically.
  • Use comments for simple coordination visible to participants.

Technical notes: The app uses Firestore with collections for events, occurrences, slots, signups, and comments. Multi-day events leverage occurrences for per-date customization.