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.
Start 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.
Take the register as normal
On the night, it's the same register as always — mark who's present, and a Left early checkbox with a time catches anyone who didn't stay the whole session.
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.
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.