All Cadets

Cadet management for JROTC and ROTC programs.

One system for the roster, the chain of command, promotions, awards and taskings - built around how a cadet unit actually operates, not adapted from a generic school database.

Website · Support · Trust & Safety

All Cadets builds software for the instructors who run cadet programs.

A JROTC or ROTC unit is not a classroom. It has a chain of command, a promotion ladder, an awards system, a structure that changes every year, and cadets who hold real authority delegated by staff. Instructors have historically run all of it on spreadsheets, shared drives and paper - because the school's student information system has no concept of a battalion, a billet or a ribbon rack.

We built the system that does.

Roster of record. Every cadet, their course level, grade, assignment, rank and billet. Sortable, filterable, exportable, printable. Dropped cadets stay visible in the record rather than vanishing from it.

Unit structure. Build the hierarchy the way your unit is actually organised - battalions, companies, platoons and squads, each with its own mascot, motto, colours and guidon. Any structure renders as an org chart.

Chain of command that means something. Positions are the permission model. Promote a cadet into S-1 Personnel Officer and they inherit exactly what that billet may do; move them out and the authority leaves with the position, not the person.

Delegation with a final say. Cadet staff can be given real work - updating records, managing structure, running taskings - while every change they make without sign-off authority lands in an instructor's approval queue first. Cadets do the work. You keep the final say.

Taskings. A board of lists and cards with due dates, checklists and labels. Assign to a cadet or to a billet, so a recurring tasking follows the position through every turnover.

Awards and promotions. Branch-specific rank ladders and award catalogues, with the ribbon and insignia artwork built in.

A battalion is a wing is a ship, depending on who you ask. All Cadets does not flatten that. Echelon vocabulary, rank ladders, position categories and award catalogues are all branch-scoped, so the system speaks your service's language rather than making you translate.

Both program levels are supported, each with its own tailored experience: JROTC for high school programs, and ROTC for college battalions.

International support is on the roadmap - the branch and echelon model was built from the start to describe any cadet organisation, not only US ones.

You are holding minors' records on a school network. The controls are how the system is built, not options you have to configure:

• Units are isolated from each other at the database layer, not by a filter in the application.
• Cadets see their own view - their assignment, their billet, their taskings. Staff functions are absent from their app, not merely greyed out.
• Every change is logged to an auditable unit history.
• Sessions expire on idle with a hard cap, because units share computers.
• Safeguarding reports have a dedicated channel that is never routed to cadets, and escalated reports are visible only to platform staff.

Our Privacy Policy sets out our COPPA and FERPA commitments in full, including how the service operates under FERPA's school official exception and how a parent or guardian can access, correct or delete a cadet's information.

One price for the whole unit. No per-instructor licences, no modules sold separately.

You pay for the capacity you actually carry, and you can start without a card.

Instructors and SAIs - the roster, the structure and the approval queue, without the spreadsheet.

Cadet staff - real responsibility, scoped to the billet they hold, with staff oversight built into the workflow.

Cadets - a clear view of where they stand: their assignment, their rank, their taskings.

Districts and program directors - consistent records across every unit, with subscription and roster health visible in one console.

Engineering documentation lives in the main repository: README · Architecture and conventions · Local development

If you would rather talk to someone before deciding, the contact form reaches us directly.

Security researchers: please see our Responsible Disclosure policy before reporting.