Best practices for organizing sign-ups

Most broken sign-ups fail for boring reasons: a vague title, a capacity that was never the real room size, a public listing that should have stayed private, or two people editing two different events. These habits prevent that. They assume you already know how to create a sign-up.

Name the event the way people already talk

The title shows on the public page, in Search, on the team page, and in confirmation email. “Spring Fling Volunteers 2026” is searchable. “Help needed!!!” is not. Put the year in the title if this event happens every spring, or you will have last year’s page still circulating.

Slot titles should be jobs or items, not paragraphs. “Grill 5–6 p.m.” is a slot. “Please arrive 15 minutes early and wear closed-toe shoes if you can, thank you so much” belongs in the sign-up description or the slot description field.

One event, many dates — not many events

If it is the same group doing the same kind of work, it is one sign-up with many instances. A six-week class is one sign-up and six dates, or a weekly recurrence. A bake sale and a car wash on the same Saturday are two sign-ups. Mixing them makes capacity, descriptions, and later reports lie.

Recurrence is a generator, not a living series you can edit as one object after the fact. If the third Thursday moves, edit that instance. Do not rebuild the whole series unless you meant to.

Set capacity from the constraint that is real

Room holds 18? Default capacity is 18. Grill needs two people? Slot capacity is 2. Conference slot is one family? Capacity is 1. Do not set 100 because you “don’t want to turn anyone away” if the fire marshal or the parking lot will. There is no waitlist. When something is full, it is full. See capacity.

If you routinely run over, raise capacity on purpose and tell people, or add another instance. Silent overbooking on a spreadsheet is how you got here.

Decide listing before you paste the link

Public listing is a directory switch, not a permission system. Off: only people with the URL. On: Search, team page, creator page. Classroom parties, staff trainings, and anything with minors in the description stay off. Community workshops and volunteer days you want strangers to find stay on. Flip it in edit if you guessed wrong. Details: sharing.

Keep the roster in the product

Exporting to a sheet the night before, then taking walk-ups on paper, is how you get two sources of truth. Remove no-shows in the dashboard. When someone emails “take me off,” remove them or have them use the unregister link. The next visitor can take the open spot. Do not keep a side list “just in case” unless you are willing to reconcile it every hour.

Collect only what you will read

A custom form attached before registration is useful for shirt size or allergy notes. It is not useful for a twelve-question survey nobody opens. Every extra field lowers completion. If you would not act on the answer the morning of the event, do not ask.

Never put medical details, student last names, or door codes in the public description. Organizers see the roster; the open internet sees the page. Privacy choices covers what is visible.

Two organizers beat one hero

Invite a teammate before you leave town. Events belong to the team. If only your personal login can edit Saturday’s shifts, you have a single point of failure. Use the team page as the official calendar and your creator page only when people follow you, not the organization.

A short list you can reuse

• Title a stranger would understand.
• One sign-up per kind of work.
• Capacity from the real constraint.
• Listing off unless you want to be found.
• One roster, no shadow spreadsheet.
• A second person with access.