Event Roster, Roles & Attendance

An event roster is the working list of who is actually coming, where they sit, and what job they hold for the trip. MySummitKeep keeps that organized in two connected places: a Roster tab on the event itself, where you sort Scouts into patrols and hand out leadership roles, and a dedicated roster page for taking real attendance on the day. This guide walks both.

RSVP vs. attendance vs. roster

These three words sound alike but mean different things, and the platform keeps them deliberately separate:

• RSVP / registration is the family’s promise to come. They sign up on the event page. See Event Planning for how registrations work.
• Roster is your organization of those registrants — which patrol each Scout is in, and who holds which youth leadership role for this event.
• Attendance is what actually happened: who showed up, who was a no-show, who left early. This is recorded on the day and never overwrites the RSVP.

Note

A Scout can be registered (RSVP’d), placed on the roster in a patrol, and still be marked Absent if they don’t show. All three records coexist so your participation history stays honest.

The “Consent missing” flag

When a Scout under 13 is registered for an event (by you, or by their parent) and no parent has recorded consent to the Children’s Privacy Policy, the registration still goes through, so nobody is turned away from the trip. The Scout’s registration shows an amber Consent missing badge on the event’s registrations list, and on the camp registration grid for summer camps, so you can follow up with the family. The badge disappears on its own as soon as consent is recorded for the Scout (a parent records it when they are linked to the Scout); there is nothing for you to clear. If a parent who is already linked asks how to record it, ask them to contact support. The event registrations list is the complete view; the camp grid only shows Scouts who already have camp schedule requests.

The one exception is a Scout under 13 trying to register themselves without consent on file. That is not allowed, and they are asked to have a parent or a leader register them instead.

Initializing the roster

Open the event, then choose the Roster tab. The first time you visit, the roster is empty and shows “Roster Not Initialized.” Click Initialize Roster to pull every approved registrant into the roster as an unassigned pool. You’ll see a confirmation like “Roster initialized with 14 members.”

If new families register after you initialize, re-running the roster picks them up — you won’t lose existing patrol or role assignments. Initializing and managing the roster requires the EventRoster.Manage permission, so most committee members can view but not edit.

Patrol assignments

Once initialized, the roster appears as a board: an Unassigned column on the left and one column per patrol. To place a Scout, drag their card from Unassigned into a patrol column — or move them between patrols the same way. The change saves immediately; there’s no separate “Save” step for patrol moves.

Tip

Patrol columns come from your unit’s patrols. If a patrol is missing, set it up first under Patrols, Dens & Divisions, then re-initialize.

The summary bar at the top tracks assigned to patrol vs. unassigned so you can see at a glance whether anyone still needs a home.

Role assignments and templates

Beyond patrols, you can assign youth leadership roles (positions of responsibility) for the event — a senior patrol leader, a quartermaster, a grubmaster, and so on. Assigning roles requires the EventRoster.AssignRoles permission (it is youth-prohibited, so only adults can do it). On a member card, click the small + (add role) button to open the Assign Role panel, pick a Position from the dropdown, add optional Notes, and click Assign. The role then shows as a chip on the card; click the small remove control on a chip to take it back off.

Each event type carries a role template that defines the standard positions an event of that kind should have, and how many of each are required. That template is what powers gap detection and auto-assign below.

Finding and filling gaps

When the roster is missing a role its template requires, a red Missing Required Roles banner appears at the top of the board. It lists each unfilled position in the form:

Quartermaster: 1 of 1 needed (0 filled)

Work down the list, assigning roles until the banner clears. The roster summary’s “filled role slots” count and the banner update as you go.

Caution

The gap banner only flags positions the event type’s role template marks as required. Optional roles won’t raise an alarm even if they’re empty — so glance over the full board, not just the banner, before a big trip.

Volunteer shift gaps

When any of the event’s adult volunteer shifts has fewer adults signed up than needed, an amber Volunteer shifts that need adults box appears on the Roster tab listing each short shift with its counts, for example Kitchen help: 1 of 3 (2 more needed). It shows counts only, never names. Fill the gaps from the Volunteer Shifts tab; see Event Carpools, Shifts & Duties.

Duty Roster

Who cooks, cleans, hauls water and tends the fire is set on the event’s Duty Roster tab, not here. It can be printed from there for the trip binder, and everyone in the unit who can open the event can read it. The same page explains the starter rotation.

Auto-assign

If your Scouts already hold permanent positions of responsibility, you don’t have to assign every event role by hand. Click Auto-Assign Roles (requires the EventRoster.AssignRoles permission). The platform reads the event type’s role template and matches it against members’ standing positions, filling the slots it can.

Auto-assign is additive and safe to re-run: it fills empty required slots without disturbing roles you set manually. If no role template exists for the event type, auto-assign reports that there was nothing to assign — set up a template for that event type first.

Taking attendance (roll call)

Attendance lives on the dedicated roster page. From the event, use the Roster quick-action (visible to leaders and admins), which opens /events/:id/roster. The page opens on the Attendance tab and lists everyone who registered.

For each person, tap Present, Absent, or Excused right from the row; expand a row to also reach Late and Left Early. To speed up a full turnout, use Mark All Present — it marks only the people still unmarked, so it won’t clobber an Absent you already set. The stat cards at the top tally Registered, Present, Absent, and Excused live as you go.

Tip

The No-Shows tab filters to everyone marked Absent and gives a one-click Follow-up link to message them. The Historical tab shows attendance rates over a date range and highlights perfect-attendance Scouts. For the unit-wide view, see Recording & Reviewing Attendance.

Check-in / check-out

For events where arrival and departure times matter — lock-ins, day camps, anything with a sign-out sheet — expand a member’s row on the Attendance tab. There you’ll find check-in time and check-out time fields plus a Notes box (for example, “arrived late due to traffic”). Set the times, then click Save Details to record them on that person’s attendance entry.

Recorded check-in and check-out times then appear inline on the member’s row (shown as “In:” and “Out:”), giving you a clean, auditable record of exactly who was on site and when.

Note

Marking attendance and editing check-in/out requires the event-management permission. Members without it can open the roster page but will see a read-only message instead of the marking controls.