Martial Arts Studio Memory: Class Rosters and Belt Records for AI Agents
Store class rosters, belt progress and membership changes as company memory now, so a future AI agent can handle renewals and makeups with accurate history.

An AI agent for a martial arts school can answer parents about class times, offer makeups and flag memberships close to renewal, but only when it can see accurate records of who is enrolled, what each student attends and which belt they hold. Most studios keep those facts across a registration app, sign-in sheets, instructor notes and the owner's memory. The practical first step is to organize them as one maintained company memory that an agent can read today, before any agent is asked to act on it.
Key takeaways
- A renewal or makeup answer is only as good as the enrollment, attendance and rank history behind it, so check those records before any automation reads them.
- Keep facts (rank, enrollment, attendance) separate from policies (makeup windows, freeze limits, promotion minimums), and date each policy version.
- Start with read-only access, and keep refunds, rank changes and exceptions behind named staff approval.
- Define one observable success criterion, such as answers that match the record on file without a staff correction.
- Review permissions and rerun real front desk questions on a schedule, because rosters, memberships and instructors change constantly.
Why belt records are harder than they look
A belt is not a label. It is an event with a date, an evaluating instructor, a set of requirements and often a note about what still needs work. A student may train in two programs, move from a kids class to an adult class as they age, or share an account with a sibling. Each of these details changes what a correct answer looks like.
Membership data adds its own complications. A freeze, a pause for an injury, a transfer to another location and a plan change each have a start date and an end date. If a system records only the current plan, an agent cannot tell a parent whether a missed month was covered by an approved pause or simply missed. The gap is easy to overlook until a parent asks a direct question and someone has to check the answer by hand.
Good records do not require new software on day one. They require agreement on what each field means and who is allowed to change it.
What to store as company memory today
Think of company memory as the set of facts an agent would need to answer the questions your front desk handles every week. For most martial arts studios, that comes down to six groups of records.
- Student identity: one record per person, with guardians linked to their children and a contact preference for each.
- Enrollment: program, class schedule, start date, membership type, and every pause, freeze or transfer with its start and end dates.
- Attendance: each class attended or missed, with the instructor, the date and whether the session counts as a makeup.
- Rank history: each belt awarded, the date, the evaluating instructor and the requirements recorded as met.
- Policy snapshot: the makeup window, freeze limits, cancellation notice and promotion minimums, each with the date it took effect.
- Open items: scheduled tests, balances flagged by staff, and rank corrections waiting for instructor confirmation.
The policy snapshot is the easiest group to neglect. An agent that quotes a makeup window from an old handbook produces a confident, wrong answer. Store the current rule, its effective date and the person responsible for it.
A step-by-step plan for organizing the records
The work is mostly agreement and cleanup, not technology. The following sequence works for a studio of any size.
- Step 1: Write down the questions the front desk answers most often, such as whether a missed class can be made up or when the next belt test is.
- Step 2: Map each question to the fields it needs. A makeup question needs attendance, enrollment and the makeup policy.
- Step 3: Choose one source of truth for each field. If the registration app holds enrollment, do not keep a second copy in a spreadsheet that drifts.
- Step 4: Backfill the most recent full cycle of rank and attendance, then have an instructor check a sample of records against paper notes.
- Step 5: Name an owner for each field and a routine, such as a weekly review of pauses and transfers at the front desk.
- Step 6: Write the policy snapshot with effective dates and the staff member who approved each rule.
- Step 7: Test the memory with real questions before any agent is connected. The expected answers should come from the staff who handle those questions today.
The same discipline appears in other membership businesses. Compare how yoga studio memberships and waitlists depend on clear limits, or how climbing gym belay check logs depend on a dated record that someone can verify.
Illustrative scenario: a renewal and a makeup request
The following scenario is illustrative and does not describe a specific studio.
A parent writes on a Sunday evening asking whether her son can make up a Tuesday class he missed while traveling, and whether his membership renews at the end of the current term. An agent working from the memory described above reads the enrollment record, which shows an active plan with renewal scheduled for the end of the term. It finds the missed Tuesday in attendance and checks the policy snapshot, which allows makeups within a set window at the same rank level. It offers two open slots in a Thursday class taught for his belt, and it tells the parent that the renewal is scheduled and that staff will confirm the next billing date.
The agent does not decide anything beyond the policy. If the parent asks for the missed session to be waived, the request goes to the front desk queue with the attendance record attached. Staff reply the next morning. The parent gets an accurate answer, and the instructor sees a clear note rather than having to reconstruct the week from memory.
Decision guide: what the agent answers and what goes to staff
The boundary between answering and escalating should be written down before launch, not decided case by case at the counter.
- The agent may answer directly: class times, enrollment status, whether a session shows as attended or missed, the makeup window and upcoming test dates from the record.
- The agent may propose a makeup when policy allows it and an open slot exists at the student's rank level, then asks the student to confirm.
- Staff must approve refunds, fee waivers, freeze exceptions, transfers between programs and any request connected to an injury.
- Instructors must confirm rank awards, rank corrections and test results. The agent never writes a belt change into the record on its own.
- Any message that mentions a medical event, a safety concern, a custody question or a complaint about an instructor is escalated immediately to a named person.
Permissions, evaluations and sensitive data
Access should follow least privilege. The agent reads enrollment, attendance and policy records, writes only to a request queue, and cannot edit rank history or billing. The OWASP authorization guidance describes this pattern: each action is checked against the role and the specific record, not against the fact that a request came from inside the business.
Recurring evaluations matter as much as the first setup. Keep a set of real questions from the front desk, write the expected answer for each one from the record, and run them again after every change to the policy snapshot, the registration app or the agent's instructions. Anthropic's guidance on context engineering makes a related point: give the agent the smallest set of relevant information that answers the question, not the whole archive. For a studio, that means a student's attendance and rank history, not every message the family has ever sent. The NIST AI Risk Management Framework offers a useful structure for deciding which risks to measure and who reviews them.
Children's records need extra care. Collect only what the studio needs, limit who can see guardian contacts and medical notes, and confirm with an advisor how consent and retention apply under the privacy rules that govern your business before any channel is connected.
How Be Human approaches this in managed operations
In a first engagement, Be Human defines one useful role for the studio, the memory and tools that role needs, the approval boundaries for refunds, rank changes and exceptions, and an observable success criterion that staff can check. Managed operations can then cover monitoring of the answers the agent gives, recurring evaluations against real questions, permission reviews when staff roles change, and controlled updates when the handbook or the registration system changes. The agent's identity, memory and channels stay under the studio's control, and the studio decides what it may do next. If you want to find the first task in your studio worth handing to an agent, take the free Be Human AI diagnostic.
Frequently asked questions
Can an AI agent change a student's belt rank? No, not on its own. The agent can show the rank history on file and propose a correction with the supporting note, but an instructor confirms any award or change before it is written to the record. This keeps the belt record reliable for families and for the next evaluation.
Does a studio need a new membership system before using an agent? Not necessarily. Many studios start by organizing the records they already have into one agreed memory, with a clear owner for each field. A new system can come later if current tools cannot hold pause dates, attendance history or policy versions.
How should a studio measure whether the agent is working? Choose one criterion that staff can check against the record, such as whether answers about enrollment, attendance and makeups match what the front desk would have said. Review a sample each week at first, and rerun the same set of real questions after every change.
Is it safe to let an agent talk to parents about their children? It can be, when the agent has read-only access to the records it needs, a written list of what it may answer, and a clear handoff to staff for refunds, exceptions, safety or medical concerns. Guardian contact details and medical notes should be limited to the roles that need them, and the studio should confirm its privacy obligations before connecting any channel.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


