Rosterra
All writing
Belt & progressionJune 2, 20268 min read

How to run a belt test in one day instead of two weeks of prep

Belt test prep should be a Saturday. Most schools spend two weeks on it. Here is where the two weeks goes and which parts you can automate without losing rigor.

Belt test prep should take a Saturday. Most schools spend two weeks on it. The good news: roughly 80% of that time is on things that can be automated without lowering the bar.

Where the two weeks goes

Most schools who tell us "belt test prep takes two weeks" are actually doing some version of this:

  • Week 1: Cross-checking the spreadsheet against memory and notebooks. Who is actually ready? Who thinks they're ready but isn't?
  • Mid-week 1: Conversations with parents about whether their kid will test. Some are awkward.
  • Late week 1: Chasing test fees. By email, by phone, by hallway conversation.
  • Week 2: Rechecking the spreadsheet, because the head instructor wants to know who's on the test before announcing it.
  • End of week 2: Printing certificates, sometimes with a typo, sometimes without.

The actual test takes a few hours. The prep is what eats the calendar.

What can be automated (without losing rigor)

1. Eligibility

If your system tracks attendance, skill signoffs, and time-in- rank, the eligibility view is computable. You shouldn't be maintaining a "ready / not ready" column by hand. The instructor's judgment is still in the loop, as a required signoff, but the input data is automatic.

2. Test fee collection

The list of "who paid" should not be a column you maintain. The test fee should be a line item that auto-charges the family on file when eligibility is confirmed, with a one- click pay link as the fallback. If a family hasn't paid 72 hours before the test, the system should surface that to your inbox, not the other way around.

3. Parent communication

When a student is added to the test roster, the parent should know. Same day. Same screen the instructor uses to confirm. Don't send a separate email by hand. Don't text ten parents.

4. Certificates

Certificate generation is a templated PDF. Configure templates once per rank. Run them in bulk after the test. The hour you spend on this should be spent on signatures and ceremony, not mail-merge.

What should stay manual

Three things you don't want the system to do for you:

Instructor signoff

A student is ready when an instructor says they're ready. The system can show you that all the boxes are checked, but the final call is a human one. Keep it that way.

Edge-case conversations with families

If a student is borderline, the conversation with the parent happens before the test, not after. The system can flag borderline cases; the conversation is yours.

The test itself

Don't try to automate the test. It's a ritual. The whole point is that students earn the belt in front of the instructor, their peers, and (often) their family. Software has no business in the room.

Automate the bookkeeping, not the test.

The cohort effect

One subtle benefit of automating prep: you stop limiting the test to the students who happened to be obvious. When the eligibility view shows you everyone who's ready, it usually includes two or three students who would've slipped through the cracks. They get tested. They earn the belt. They stay longer.

Across a year, three extra promotions per quarter is twelve students who feel seen and progress. That's a real retention lever.

A day-of runbook

The Saturday version of a belt test, assuming the prep above is automated:

  • T-7 days: Generate the test roster from the eligibility view. Send parent confirmations. Auto-charge test fees.
  • T-1 day: Pull the roster again. Check for any new payment issues. Print certificates in advance.
  • Test day morning: Attendance, warm-up, test in cohorts by rank.
  • After the test: Bulk promote in the system. Belts update everywhere: roster, parent portal, mobile app. Hand out certificates.
  • Evening: Send a recap to families. Include the next test date so students who weren't ready have a target.

If you're still doing the two-week version

Pick the part that hurts most. Most schools start with eligibility (the spreadsheet bit) because that's where the actual stress is. Test fee collection is a close second. Certificates are a one-quarter project that pays off forever.

The first test you run with eligibility automated feels unsettlingly calm. That's how it's supposed to feel.

Run your next belt test in a day.

Rosterra handles eligibility, fees, parent confirmations, bulk promotion, and certificates. Book a 20-minute demo with your real ranks.