I'd sat in on a handful of Boards of Review before I ran my first one solo, so I figured I had a decent read on how they worked. I was wrong, and it took embarrassing a First Class scout in front of three committee members to figure that out.
His name was Marcus. Sharp kid, quiet, the kind of scout who does the work without needing anyone to notice. He came in for his First Class review having genuinely earned every requirement. I had his advancement report, I had my list of "good BOR questions" printed off some forum, and I had, apparently, decided that my job was to catch him out.
I ran it like a pop quiz
I asked him to name all seven Scout Law points from memory, in order. He got five, paused, and started to sweat. I let the silence sit there — on purpose, because somewhere I'd absorbed the idea that a BOR should feel a little like pressure-testing. Then I asked him to explain the difference between the Scout Motto and the Scout Slogan, like it was a vocabulary exam. He froze up worse.
By the end, Marcus wasn't talking about his six months of patrol leadership or the cooking he'd done on three campouts. He was just trying to survive the next question. We passed him — of course we passed him, he'd met every requirement — but he left that room looking like he'd been through something unpleasant, not something he should be proud of.
A Board of Review is not a test of what a scout remembers. It's a conversation about what a scout has done.
What actually changed
One of our committee members, a longtime Cubmaster before she joined our troop committee, pulled me aside afterward. She didn't lecture me — she just asked, "What were you trying to find out?" I didn't have a good answer. That was the problem.
The official guidance is clear once you actually go looking for it: a Board of Review evaluates the scout's experience in the troop and reviews the requirements he's completed — it is explicitly not a retest of skills or knowledge. The BSA is emphatic that a scout who has been signed off on a requirement shouldn't be quizzed on it again at the BOR. I knew that, technically. I just hadn't let it change how I actually ran the room.
Here's what I do differently now, three years and probably eighty BORs later:
- I open with something that has nothing to do with rank requirements — a recent campout, a merit badge he's working on, something I noticed him do well. Get him talking before you ask him anything that feels like a test.
- Every question starts with "tell me about" or "what was it like," not "what is" or "name the." I want stories, not recitation.
- If a scout blanks on something, I treat it as a sign the question was bad, not that the scout is unprepared. I rephrase or move on — I don't sit in the silence to make a point.
- I ask what he's proud of. Every single time. It's the best question I have, and I stole it from that same committee member.
- I ask what's been hard. Scouts are more honest about struggle than you'd expect, and it tells you more about their growth than any requirement checklist does.
The part I still think about
Marcus is Life rank now, working on his Eagle project. His BORs since that first one have been completely different — he talks for ten minutes without me prompting him, because somewhere along the way he stopped bracing for a test that was never supposed to happen. I don't know if he remembers that first review as clearly as I do. I hope not.
If you're about to run your first BOR and you're tempted to build a list of gotcha questions to make sure the scout "really knows it" — don't. The requirement sign-off already happened. Your job in that room is to find out who this scout is becoming, not to re-litigate what he already proved.