Belt system

How to track BJJ belt promotions (without a spreadsheet)

Ossly · August 2026 · 4 min read

Every academy has a version of the same system: a spreadsheet, a notebook, or the professor's memory, holding names, belts, and roughly when everyone was last promoted. It works until it doesn't. Usually that's the day a purple belt asks "how far am I from my next stripe?" and nobody can answer.

Why the spreadsheet fails

• It doesn't count classes. Mat time is the real input to promotion decisions, and it lives somewhere else. Often nowhere.
• Only one person can read it. The student, the one person the data would motivate, never sees it.
• It rots. Promotions get written down weeks later, dates are guesses, and the history becomes folklore.

The system that works

You need three things connected: attendance, rank, and history.

1. Count every class automatically. Attendance should be registered by the coach in one tap when the class happens, not reconstructed later. Each attended class increments the student's count toward the next stripe.

2. Define the threshold and let the software flag readiness. Pick your number of classes per stripe. When a student approaches it, they should surface on a list. Promotion day becomes a review of a ready-made list instead of a memory exercise.

3. Make the promotion a single action that writes history. Award the stripe or the belt in one tap. The student's counter resets, the promotion lands in a permanent history with the right date, and a certificate is generated for the student to save and post.

What the student should see

All of it. Their current belt and stripes, a progress bar of classes toward the next one, their full promotion history. A student who watches the bar move after every class doesn't need a retention campaign. The bar is the retention campaign.

Edge cases your system must survive

• Students who arrive already graded. You must be able to set a belt without generating a bogus history.
• Backdated corrections. Promotions get re-dated. Counters should recompute from history, not drift.
• The professor's discretion. Thresholds guide, they don't decide. Software flags readiness; the professor promotes.