One record from first class to black belt.

A focused release may include households, students, guardians, programmes, classes, enrolment, attendance, approved curriculum, prerequisites, instructor observations, test eligibility, test events, rank history, memberships, payments, communication, role access, and location reporting. The school defines instruction, assessment, promotion, safeguarding, billing, and records policy.

No. Software can show approved prerequisites, attendance, instructor observations, prior tests, missing evidence, and an authorised approval workflow. Qualified instructors own readiness, assessment, accommodations, safety, grading, promotion, and corrections. A calculated status should never replace instructor judgement.

Preserve programme, curriculum version, rank, prerequisites, evidence, instructor, test event, result, approval, effective date, certificate or reference, deferral, correction, transfer source, and prior history. Do not overwrite a past rank when curriculum or terminology changes. Make imported and verified records distinguishable.

One student record serves every location, with shared curriculum versions and location reporting on top. A student who moves schools carries verified rank history, including transfer source and prior history, instead of starting again or relying on a paper certificate. Programme and terminology differences between locations stay visible rather than being flattened into one list.

Waivers are digital, with parent or guardian signatures for minors, and permissions sit on the household and student records. Families see only their own students, and staff roles decide who can record attendance, edit ranks, or change billing. Safeguarding rules are set by the school, and the system enforces who can see and change what.

Memberships and payments sit on the same student record as classes and ranks, so the office stops reconciling a billing tool against an attendance sheet. Households group family members under one billing view, and each membership, pause, and payment is tied to the student it belongs to. Billing rules are agreed with the school before the first release.

Buy a maintained platform when it handles scheduling, attendance, belt tracking, and billing with reasonable setup and its pricing makes sense. Build custom when a grading, curriculum, or franchise workflow will not fit that platform, or when several locations need one shared rank record the product cannot give you. If the grading policy itself is still changing every term, wait and settle it first.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your school.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

No single number is honest for every school, so this page states no price band. Cost follows scope: how many locations, how many programmes and curricula, which connections to payment and accounting tools, and whether records need moving over from spreadsheets or an existing platform. The agreed phase is priced in writing before paid work starts, with the workflow, what 'done' looks like, and the exclusions named.