Skip to content
EntryWick documentation

For somebody about to start an event and deciding which event template to start from.

The six event templates — what each one assumes

Who opens this: somebody about to start an event and deciding which event template to start from. What they came to do: pick the one whose shape is closest to their event, so they are editing rather than building. True when they leave: they know what each event template assumes about who comes, how people are counted, and what gets sent — and which one to pick.

An event template is a whole event in a file: its days, its kinds of attendee, its check-in points, its forms, its copy, its schedule of emails and its checklists. Importing one makes a draft event with all of that in it. Nothing is locked afterwards — every object is yours to rename, rewrite or delete. The event template is a starting position, not a cage.

The format is in docs/EVENT_TEMPLATE_FORMAT.md; the import wizard is event-template-import.md and the library screen is event-template-library.md.


Community Celebration — community-celebration

The one everything else was learned from. A two-day event for thousands of people who come as families, from congregations spread across a region, checked in at their own congregation early in the morning and again at the venue.

  • Counts people twice on purpose. A satellite point at each congregation pre-checks a family at 3:30 AM local; the venue gate is the count that decides how full the hall is.
  • Households. One email can carry every ticket in a family, and a youth's ticket can be shared with the adult bringing them.
  • Print track. Anybody with no email gets a printed ticket handed out at their congregation, and is never second-class for it.
  • Pick it when people arrive in groups from places you also run, and the venue is not where the day starts.

School Field Trip — school-field-trip

One day, one bus, three counts: on at school, in at the venue, back on before the bus moves. Students are registered by a guardian, never by themselves.

  • The permission slip is the gate. A student with no signed slip does not travel, and the form refuses to be sent without it.
  • One adult per five students, checked as the form is sent rather than the morning of the trip.
  • Medical and dietary answers go to the class teacher and the chaperone riding with that class, and are printed on the bus list so they survive a dead phone.
  • Pick it when minors travel with your staff and you are legally responsible for a head count.

Volunteer Day — volunteer-day

Shifts with capacity, a team lead per group, and hours that come from a pair of scans: sign in at the start of a shift, sign out at the end.

  • A lone sign-in is an unrecorded hour, which is why check-out is its own point and the gate training says so.
  • Under 18 asks for a guardian's name and their agreement to the waiver, and refuses the sign-up without it.
  • Full shifts take a waitlist rather than turning people away; waitlists move every year.
  • Pick it when people give you time rather than money, and somebody needs their hours in writing afterwards.

Conference — conference

Three days, several rooms, one badge. A delegate is scanned once at the registration desk, where the badge prints; every room door after that is a capacity count.

  • Every slot is booked in advance, and a door only knows what you booked. Changing rooms happens at the desk, never at the door.
  • Early-bird pricing is a rule with a date, so the discount ends by itself.
  • Invoice bookings hold a place and wait for payment; the badge is issued when the money arrives.
  • Access and dietary answers reach the venue team and catering, by name, before anyone travels.
  • Pick it when people pay to come, choose what to attend, and rooms are the constraint.

Sports Tournament — sports-tournament

A weekend of matches. A coach registers a roster once; players, coaches, officials and spectators are all scanned at the field gate.

  • The waiver is the hard line. Every player's guardian agrees to it themselves; a player without one does not play, and that argument is had before Saturday.
  • The age bracket comes from the date of birth, not from the team's name.
  • A team tent checks a whole roster in early so the gate moves quickly.
  • Spectator tickets are per day, and a Saturday ticket at Sunday's gate goes red rather than being waved through.
  • Pick it when people arrive as teams and paying spectators arrive alongside them.

Corporate Offsite — corporate-offsite

One to three days away from the desk. Employees register with single sign-on, so the company fills in what it already knows and only asks what it does not.

  • The ticket opens the venue, the dinner and the activity you chose — and a guest's ticket opens the dinner only, by design.
  • Dinner and activity scans are the counts the caterer and the suppliers are given.
  • Dietary and access answers go to the venue, not up the reporting line, and the form says so where it asks.
  • The RSVP closes itself so the venue gets numbers on the day it was promised them.
  • Pick it when the audience is your own staff, the venue needs numbers, and the questions are practical rather than about eligibility.

What every one of them carries

A public page Hero line, the event's own description, the schedule from its days, what to bring, an FAQ written for that vertical, and the register button. Sections with nothing in them are not rendered.
Forms One per way in — public, on-behalf, invitation, import — with consent, dietary and access questions where the vertical needs them, and conditional logic that hides what does not apply.
Templates Confirmation, ticket, reminder and thank-you emails, a ticket page, a badge and a print sheet, in that vertical's voice. Their codes are prefixed (trip-, conference-, …) so they arrive alongside the generic copy your organization is seeded with rather than being refused as duplicates.
Schedules Confirmation on confirmation, tickets a set number of days out, a reminder the day before, a thank-you after. Every one of them is yours to move or switch off.
Checklists Pre-event, by day. Gate training, in the words somebody reads to a volunteer at 7 AM. Group-lead notes for whoever runs one class, one team, one shift or one track.
An example group tree Offered on the wizard's group step: match them to groups you already have, let the import create them, or ignore them.

What a plan changes

Nothing in an event template ever fails an import. Anything your plan does not cover is imported switched off with the reason, or, where a count limit is already full, not created and recorded so it can be added after an upgrade. The wizard's last screen says which. See docs/PRICING_ENTITLEMENTS.md §7 for the keys, and each event template's requires block for what it asks for.