How to Track Badges, Belts, and Award Schemes Without a Paper Register

A Bronze Duke of Edinburgh's Award asks a 14-year-old to keep going in three separate sections for at least three months each, with one of them stretched to six, before the expedition even counts. That is a minimum of 39 weekly entries per participant, spread across a year, held by volunteers who see that young person for two hours on a Wednesday. The requirement is not the hard part. The record is.

Why do award schemes break down at the record and not the requirement?

Because the requirement happens once and the record has to survive everything that comes after it.

Take a staged activity badge in a Cub pack. A Cub swims 25 metres in October in front of an assistant leader who volunteers twice a month. The swim is unambiguous. Whether it gets written down, whether the note survives a change of section leader in January, and whether anyone can find it when the badge is due in March, is where the scheme actually lives or dies.

Three failures show up again and again in clubs running any kind of graded scheme.

• The record sits with a person, not the organisation. A notebook, a phone photo of a sign-off sheet, a spreadsheet on one laptop. When that volunteer stops turning up, so does the evidence.
• The unit recorded is too big. Clubs tick the badge rather than the requirements inside it, which makes the record unauditable and forces a leader to reconstruct months of detail from memory.
• Nothing is dated. Time-based requirements are the most common kind in youth award schemes and the least often evidenced, because "she has been coming all year" is not a record.

Coaches and leaders we speak to often say a version of the same thing: "We know they did it. We just cannot prove which week they did it, and the assessor wants the weeks."

What should you actually record: the badge or the evidence?

The evidence, with the date attached, every time.

This is the one design decision that determines whether an award record is worth keeping. A tick against a badge name records that a decision was reached. It does not record what the decision rested on, so it collapses the first time a parent asks why their child has not been awarded something, or an external assessor asks to see the underlying detail.

Break each award down once, at the start of the year, into the smallest unit the scheme itself defines. In a dojo that is a syllabus line, a kata or a set number of sessions since the last grading. In a music school it is a scale group, a piece, or a theory paper. ABRSM makes the dependency explicit for its own graded exams: a candidate cannot enter Grade 6, 7 or 8 practical without first passing Grade 5 Music Theory or an accepted alternative, which is a prerequisite worth holding in the record rather than discovering in an exam entry window.

Once the units exist, the leader's weekly job stops being admin and becomes marking. In Bitir this is the assignment widget doing ordinary work: one requirement per assignment, a due date if the scheme sets one, and a per-member completion that carries the date it was marked rather than the date somebody got round to typing it up. The badge is then arithmetic.

One warning. Do not let the breakdown get finer than the scheme requires. A pack that turns a six-line badge into 40 tracked items has invented work that the awarding body never asked for, and volunteers will stop doing it by week three.

Should badge progress be visible to the whole group?

No, and this is the place where clubs most often get talked into the wrong thing by their own software.

Leaderboards, wall charts and shared progress grids are sold as motivation. They motivate the members who are already ahead. For the ones behind, and in most sections that means the members with the least support at home, a public ranking tells them weekly that they are losing at something they joined for fun. A young person whose family cannot fund a residential, or who misses three weeks because of a caring responsibility, has their circumstances published to the group as if it were effort.

We would argue for the opposite arrangement: private progress, public presentation. Each member's running total is visible to that member, their parent and the section leader. The group sees the award at the moment it is presented, in front of everyone, which is the celebration that was always doing the motivational work anyway. Our guide to celebrating milestones without it feeling forced covers how to make that moment land.

There is one honest exception. Team-wide targets that everyone contributes to, such as a pack aiming for 300 collective volunteering hours towards a group award, work well in public because nobody is ranked inside them.

How would this look in a real section?

Rowan Petrie runs a 34-strong Cub pack in Perth on Tuesday evenings, with four adult volunteers, two of whom help once a month. The pack has 11 badges live at any one time and, across the autumn term, 374 individual requirement lines to keep track of. Rowan set it up over one evening in September.

1. One private group for the pack, one for parents. The parent group carries logistics and award presentations. Cub-facing content stays in the pack group, with two adults in each, following the rules in our guide to safeguarding communication in youth groups.
2. Each live badge becomes a goal per member. Written in the member's own words where the scheme allows it, so a Cub knows what they are working on without reading a syllabus PDF.
3. Each requirement becomes an assignment. Marked on the night, by whichever leader saw it, with the date it was met.
4. Attendance is taken every week. It takes about 40 seconds and it does the evidencing for every time-based requirement in the scheme without anyone writing a separate note.
5. Assistant leaders get limited roles. They can mark attendance and complete requirements for their own six Cubs. They cannot see per-member notes or contact details, which protects them as much as the members.
6. Presentation night is a post, not a spreadsheet. Rowan posts the awards to the parent group the same evening, with names, and the individual progress stays private the rest of the time.

The change Rowan noticed first was not the admin time. It was that partially finished badges stopped being invisible. Two Cubs who were one requirement short of a staged badge had been one requirement short since May, and nobody had known.

What happens when a member moves up or a leader moves on?

Both are routine events that paper handles badly.

A member moving from Cubs to Scouts, or from one belt syllabus to the next, should carry their completed record with them rather than starting from a blank sheet in a new leader's notebook. Keep the per-member history attached to the member, not the group, so the receiving section can read what was signed off and when.

A leader moving on is the harder case, and it is the argument for not keeping any of this on a personal device. Volunteer turnover in youth organisations is high by design, since most leaders are parents whose own children age out. When the record belongs to the club, an outgoing leader's access ends on their last night and the section keeps everything they wrote. The same principle applies to progress tracking generally, which our guide to progress tracking for groups works through in more detail.

Set a retention period in writing while you are at it. Award evidence for a member who left three years ago does not need to be kept forever just because deleting it was nobody's job.

Related reading: how a Sheffield karate school replaced its paper belt register, and how a London piano school made grade progress visible to parents.