Scout SuiteHow-to guide
Programme to badge: signing off what actually got done
Link a badge requirement to a session once, and Scout Suite tracks who did it, who didn't, and who catches up later. Here's the whole path from planning to sign-off.
Watch this on its own pageStart the term and the session
Add a term under Programme → Terms: a name and two dates. Then create the session as a normal section event: a name, start and end time, nothing badge-related yet.
This is the detailed sign-off path for one session. Building a programme covers the whole term end to end: activity library, tagging, and a balanced-programme check included.
Link a badge requirement to the session
On the event, pick the badge and which requirement this session covers. From here on, attending counts straight toward that real badge requirement, no separate paperwork to fill in later.
Where a badge asks young people to choose, like "complete three of these five activities", you pick the activity this session covers, such as Discover or Experience. Each one attended counts toward the three they need.
Where the choice is between whole routes, like Air Researcher's Option 1 and Option 2, you pick a task within a route, such as "Option 1: Visit an airfield". Attending ticks that task and picks the route for anyone who hasn't chosen one.
A session linked to a whole "complete three" line can't tick anything, because that line is done through the activities under it. It's flagged on the session and on its register: remove it and link the activity the session covered.
Take the register as normal
On the night, it's the same register as always: mark each young person Present, Absent, Late or Excused. More on a row holds notes and a Left early time for anyone who didn't stay the whole session. Saving the register doesn't tick any badges by itself; that's the next step.
Auto sign off, and it knows who to skip
Sign off requirements → Auto sign off ticks the linked requirement for everyone who was present and stayed the whole time. Anyone who left early is skipped automatically, being there for part of a session isn't proof they finished it.
Each sign-off records the event's name and date, and anything you write in What did they do? about the session, so the young person's badges show where and how they did it.
Catch someone up later
If they finish it another way afterwards (at home, on their own), there's no need to redo the session. Open Sign off requirements again and tick their name individually.
Programme
More in this topic
Terms, badges, events, camp, and the reports that follow.