Manage class prerequisites and student completion

Current release boundary: The reviewed DSM Next build can evaluate existing prerequisite groups and show prerequisite results during enrollment, but it does not currently provide a self-service class editor for creating those groups. Its current student Prerequisites picker is also not connected to the same visit records used by the reviewed eligibility check in the standard studio data layout. Treat class setup and visit correction as support-assisted until your studio's exact workflow passes the controlled test in this guide.

Important: Do not use the prerequisite feature as the only control for a safety-critical, legal, licensing, medical, or safeguarding requirement. The current checks can allow registration when prerequisite storage is missing or unreadable, an administrator can acknowledge an enrollment warning, and the reviewed Quick Registration path does not run the prerequisite eligibility service.

#Understand the rule before configuring it

A prerequisite rule has three parts:

• the target class a student wants to join;
• one or more prerequisite groups attached to that target class; and
• a required visit count for each group.

Every group must be complete. Within one group, visits from its listed classes are pooled.

In this example, two Foundation A visits plus two Foundation B visits satisfy the first group. The student must also have one Orientation visit. Four foundation visits alone do not satisfy the second group.

Use separate groups for requirements that must all be completed. Put true alternatives in the same group. A class level, member category, enrollment, purchase, or staff note is not a prerequisite visit and does not increase this total.

#Before you begin

• Name the target class and each acceptable prerequisite class by unique class code and class ID, not name alone.
• Decide whether classes in one group are alternatives whose visits can be combined.
• Set a positive required visit count for every group.
• Confirm which attendance status means Attended in the current studio configuration.
• Review existing class rules, attendance history, registration settings, and affected future enrollments.
• Identify one fictional student below the requirement, one exactly at it, and one above it.
• Close or restrict registration for the target class while an unverified rule is being changed.
• Use a direct fictional Online Client login for testing. Do not infer client behavior from an administrator's impersonated session alone.

Warning: Changing a class rule or a student's completion total can immediately change who appears eligible in the Online Client. There is no reviewed prerequisite change journal or one-step undo. Preserve an approved before-state record and a rollback instruction before any correction.

#Enable prerequisites

An owner or authorized administrator can review the studio setting:

1. Open Settings > Global Settings.
2. Open the Global tab and Common category if they are not already selected.
3. Search for prerequisite.
4. Set Prerequisite classes enabled to Yes.
5. Save the settings.
6. Reload an individual student record and confirm Main Account > Prerequisites appears.

Enabling the setting activates supported prerequisite checks and conditionally reveals the student picker. It does not create a class rule, calculate missing visit totals, or repair existing records.

#If you cannot find the setting

Confirm that you are in Global Settings, have permission to update settings, and searched the Global > Common category. Ask support to verify the studio's current setting record rather than creating a duplicate setting.

The application also contains an environment-level prerequisite feature entry, but the reviewed current interface and eligibility services use the studio's Prerequisite classes enabled setting. Changing server environment configuration is not part of the customer workflow.

#Define the prerequisite groups for a class

The reviewed current Create Class and Edit Class forms do not include a prerequisite-group editor. Do not use the student record picker as a substitute: that picker concerns one student's class/count rows, not the target class's rule.

Prepare this worksheet for an authorized support or engineering change:

Ask the authorized person to:

1. Verify that the target and prerequisite classes exist in the correct studio.
2. Read and record the target class's current groups before changing anything.
3. Create one group for each independent requirement.
4. Keep alternative classes together only when their visits should be pooled.
5. Read the saved groups back from the same source used by eligibility.
6. Return the exact class IDs, groups, required counts, date, build, and rollback record.

Do not configure an empty group, a zero-count group, the target class as its own prerequisite, or a class whose identity is ambiguous. Do not copy an old screenshot's values into the current system. Historical screens showed a Required selector and class-group controls, but those controls were not found in the reviewed DSM Next class form.

#Record completion through accurate attendance

A prerequisite visit represents an attended class occurrence. Maintain the underlying attendance honestly:

1. Open the exact dated class occurrence.
2. Confirm the student and class identity.
3. Record Attended only when the studio's approved attendance policy is satisfied.
4. Correct a mistaken attendance status on the original occurrence rather than adding a fictional visit.
5. Re-run the prerequisite report for the same student, class, and date range.

Enrollment in a class is not completion. Scheduled, waiting, cancelled, late-cancelled, or no-show records should not be presented as attended visits merely to make a student eligible.

Current synchronization warning: The current prerequisite reports calculate Times Taken from attended schedule rows. The reviewed current attendance mutation paths do not update the separate stored visit totals read by eligibility. A correct report count therefore does not prove that registration will pass. If the two results disagree, stop and request reconciliation; do not edit attendance again to chase the eligibility result.

#Review or correct a student's stored class/count rows

When prerequisites are enabled, an individual record can show Main Account > Prerequisites. The current picker lets an authorized user search classes, add a class, enter a number, remove a row, and select Save.

Do not use this picker to change enforced prerequisite completion unless support has first confirmed that it is connected to the eligibility records for your studio and build. In the reviewed current build, the picker and eligibility service use separate data paths.

If support has confirmed the picker for a specific studio variant:

1. Preserve the student's before-state and the evidence supporting the correction.
2. Open the exact student's Main Account > Prerequisites tab.
3. Search using a unique class code or name. Stop if two results are ambiguous.
4. Select Add for the approved class.
5. Enter only the verified count.
6. To remove one row, select Remove. This changes only the on-screen list until you save.
7. Review every remaining class/count row.
8. Select Save once.
9. Wait for Saved, reload the entire page, reopen Prerequisites, and confirm the persisted result.
10. Test the student's registration result and compare it with attendance evidence.

The current success message is based on the request response and the picker does not automatically reload the saved records. A full reload is part of verification.

Removing a student's row is not the same as removing a prerequisite group from the target class. To change the rule for everyone, use the class-level support-assisted process.

#Use the prerequisite reports

The current reports are attendance-history tools. They do not display the target class's prerequisite groups, and they do not read the stored visit summary used by the current eligibility service.

#Prerequisite by Student

Open Reports > Prerequisite by Student to review students who match selected class and membership-category filters.

Available filters include:

• Classes;
• Membership Categories;
• Number of Times Taken;
• all students or active students only; and
• start and end dates.

The report shows student ID, linked student name, phone, email, first class date, and Times Taken. Number of Times Taken is an exact-match filter, not a minimum. If you enter 4, a student with five visits is not included in that filtered result.

When classes are selected, the current query also requires a matching active class-enrollment relationship. A person with valid historical attendance but an inactive or archived class relationship can therefore be absent. Use the result as an investigation aid, not the sole completion certificate.

#Prerequisite by Numbers

Open Reports > Prerequisite by Numbers when you need to focus on one student ID, hide zero counts, or compare days since the first selected class.

Available filters include:

• Classes;
• Membership Categories;
• Student ID;
• all students or active students only;
• show or hide zero class counts; and
• start and end dates.

The report shows student ID, linked student name, first class date, Times Taken, and Days Since First Class.

The selected date range limits Times Taken, but the current First Class Date in this report is calculated across the selected classes without that date range. A first date earlier than the filter is therefore possible.

#Read both reports carefully

• Membership Categories filters the student's active membership-category relationships; it does not define the prerequisite class group.
• Only attended schedule rows are counted when the attendance-status field is available.
• Leaving the class filter empty counts across every class in scope, which is rarely the right prerequisite audit.
• The report pages sort and paginate the returned rows in the browser. No dedicated prerequisite export was configured in the reviewed pages.
• Prerequisite by Student exposes phone and email. Limit access and do not use a public screen share.

#Understand the Online Client result

For the normal signed-in class registration flow, the current service checks prerequisites when:

• Prerequisite classes enabled is on;
• the target class has readable prerequisite groups; and
• readable student visit totals are available.

All groups must be complete. If the student is below a group total, the student-selection or purchase-option flow can show Prerequisite required and explain that required classes are incomplete.

The class list has an intentional nuance: when incomplete prerequisites are the only blocker, it can still show Book Now so the next step can display the student-specific reason. A list card or button is not proof that every family member is eligible.

If age, membership category, prerequisite, and enrollment-date checks all fail, the current student result reports the first matching reason in that order. Resolve and retest one truthful data issue at a time.

#Missing data can allow registration

The current eligibility and administrator warning checks treat missing prerequisite tables, missing required fields, and several read failures as no prerequisite block. If an expected below-count student appears eligible, do not assume the rule is satisfied. Close registration for the target class and ask support to verify the setting, groups, visit records, and exact studio connection.

#Understand administrator enrollment

When authorized staff add a student to a class, the current administrator enrollment check can show:

Student must complete prerequisite classes first.

This is a warning in the reviewed add workflow. Staff can submit an ignore warnings choice and continue. Decide who is permitted to approve an exception, what evidence is required, and where the approval is recorded outside the prerequisite counter.

After any approved exception, verify the class enrollment, schedules, pricing or purchase, charges, messages, and the reason for the exception. Do not change the student's visit count to disguise an administrative override.

#Do not use Quick Registration as a prerequisite gate

The reviewed Quick Registration route validates its schedule key, profile fields, security challenge, and agreements, then enrolls the person in the selected schedule. It does not call the current class prerequisite eligibility service.

Do not publish or distribute a Quick Registration link for a prerequisite-controlled class until a controlled end-to-end test proves the intended rule is enforced on that exact route and build. Use the normal signed-in Online Client flow for the prerequisite test.

#Keep related controls separate

Do not use a level or category to imitate visit history. If the real policy is membership, invitation, age, or staff approval rather than attendance count, use the control designed for that purpose and test it separately.

#Permissions and privacy

Prerequisite history can reveal a student's participation pattern, progression, and past class activity. It may concern minors.

• Give settings and correction access only to staff authorized by the studio's policy.
• Test a view-only and instructor role; do not assume that seeing a student record and changing prerequisite rows are separated correctly in every current route.
• Restrict prerequisite reports to staff who need the student identities and contact details they display.
• Do not include real names, birth dates, emails, phone numbers, addresses, account balances, or attendance history in screenshots or videos.
• Do not write medical, disability, disciplinary, or safeguarding details into a prerequisite count.
• Keep approval evidence and before/after records in the studio's protected system.
• Define how long exception and correction evidence is retained.

The Online Client's reviewed prerequisite message is generic; it does not publish the student's detailed attendance history. Keep support replies equally limited and verify identity before discussing a student's records.

#Verify the complete rule

Use a disposable class and fictional students. Do not open public registration until every expected result is observed.

For each fictional student:

1. Record the expected attendance rows and expected total for every group.
2. Run both prerequisite reports with narrow class and date filters.
3. Record the support-confirmed eligibility totals separately.
4. Sign in directly as the fictional client.
5. Check the class list, select Book Now when offered, and inspect the exact student result.
6. Stop before payment or final enrollment unless the fixture and no-notification path are explicitly approved.
7. Use the administrator add dialog to confirm the warning state without submitting a real enrollment.
8. Recheck with a restricted staff role.
9. Record the build, setting, class and student IDs, group definitions, report filters, result, and cleanup status.

#Recover from a mismatch

If the report, student picker, and registration result disagree:

1. Close or restrict Online Client registration for the target class.
2. Do not repeat Save, change attendance again, or raise the visit count as a guess.
3. Record the studio, target class ID, prerequisite class IDs, student ID, expected groups, report filters, current result, time, and signed-in role.
4. Preserve the relevant attendance rows and the before-state of the support-managed rule and visit summary.
5. Ask support to compare the class groups, eligibility visit totals, attendance history, setting, studio data layout, and request result.
6. Correct the authoritative source once under an approved rollback plan.
7. Repeat the below, exact, and above tests before reopening registration.

If an unsupported picker Save says Save failed, do not keep selecting Save. The reviewed endpoint can return that result when its optional storage is absent. Repeated attempts do not create the missing structure and can make the investigation harder.

#Troubleshooting

#The student Prerequisites tab is missing

Confirm Prerequisite classes enabled is on, save the setting, and reload the individual student record. Also verify the signed-in role and that the studio is using a student/account mode that exposes the current Main Account view.

#There is no prerequisite control on the class form

That is the reviewed current DSM Next boundary, not a reason to use a different field. Prepare the group worksheet and request the controlled support-assisted change.

#A student has enough report visits but is still blocked

The reports and eligibility currently read different sources. Preserve the evidence and request reconciliation of the student's enforced visit summary. Do not create duplicate attended rows.

#A student without enough visits can continue

Check the studio setting, target class groups, every group's required count, stored eligibility visits, and exact route. Missing prerequisite storage can allow registration, an administrator warning can be overridden, and Quick Registration does not run the inspected check.

#The report is empty or misses a former student

Narrow the date range carefully, select the correct prerequisite class, review Active students only, membership-category filters, and active class enrollment. The current class filter can exclude a person whose matching enrollment relationship is not active even when historical attendance exists.

#Book Now appears for a blocked student

Continue only to the student-selection or purchase-option step. The current class list deliberately defers a prerequisite-only explanation. Stop when Prerequisite required appears.

#An instructor can change a prerequisite row

Stop role testing without saving real data. The reviewed save endpoint uses student-view authorization rather than a separate student-update check. Restrict the workflow operationally and request a permission review.

#Related articles

• Control who can register for a class
• Launch a class for online registration
• Create a group class
• Manage student enrollment
• Attendance and rosters
• Families and students
• Categories
• Roles and permissions
• Create and manage a private registration link
• Find and register for classes