How to Manage Drop-In Students Alongside Enrolled Students
Cover image ·
The problem with mixing drop-ins and regulars
You have a Tuesday evening class. Eight students are enrolled for the term. Then someone texts asking if they can "just come this once." You say yes, they show up, and now you have a ninth person on the mat, in the studio, or at the desk — one who may or may not have paid, whose name might not be on the register, and who you'll probably forget to invoice.
Multiply that by a few classes a week and a few months of operation, and you have a real problem: attendance records that don't match payments, capacity limits that get quietly ignored, and a roster that no longer tells you who is actually supposed to be in the room.
This article gives you a practical framework for running drop-ins and enrolled students side by side — cleanly, without chaos.
Decide upfront: is this class open to drop-ins at all?
Not every class should allow drop-ins. Before you open the door, answer three questions:
Does the content depend on continuity? A class that builds week on week (exam prep, graded music syllabus, progressive dance technique) is a poor fit for drop-ins. A newcomer disrupts pacing and gets poor value. Save drop-ins for classes where each session stands alone.
Do you have genuine spare capacity? A class capped at eight students that regularly fills to seven has one spare seat. That's a reasonable drop-in slot. A class that routinely hits capacity should not accept drop-ins — over-enrollment is a real operational headache, and it happens more easily than you'd expect. Real operators have reported finding five or six students in a class capped at four after drop-ins were added without a clear process.
Can you price the drop-in fairly? A drop-in student costs you the same instructor time as an enrolled student but pays for one session. Set a per-session drop-in rate that reflects that. It should be higher per session than the equivalent enrolled rate — otherwise you're incentivising people not to commit.
Write the answers down. Make it a policy, not a case-by-case judgment call.
Keep two separate lists — always
The single biggest source of confusion is treating drop-ins and enrolled students as one group. They are not. They have different payment terms, different attendance expectations, and different administrative needs.
Your enrolled student list should show:
Name
Billing plan (monthly, per-term, credit pack)
Start date and, if applicable, end date
Which track or cohort they're in (if you run multiple days or levels)
Your drop-in log should show:
Name and contact
Which session(s) they attended
Amount charged and whether it was collected
Whether they've expressed interest in enrolling
These can be two tabs in a spreadsheet, two sections of a paper register, or two views in whatever tool you use. The format doesn't matter. The separation does.
Set a hard capacity rule and enforce it before the session
Capacity problems almost always happen at the point of booking, not in the room. By the time a sixth person walks into a four-person class, it's too late to have the conversation.
The fix is a simple pre-session check:
Count confirmed enrolled students for that session.
Subtract from your capacity limit.
The remainder is the maximum number of drop-ins you can accept.
Do this check when the drop-in request comes in, not when they arrive. If you're at capacity, say so. "We're full this week, but I can put you on a list for next week" is a complete answer.
If you run multiple sessions of the same class (say, Tuesday and Thursday), keep capacity counts separate. A drop-in who can't get into Tuesday doesn't automatically get Thursday — that's a separate booking.
Charge drop-ins before the session, not after
Chasing payment after a drop-in has left is one of the most common revenue leaks in small schools and studios. The student had a good time, they meant to pay, and then life happened.
The rule is simple: payment before attendance. This applies whether you're taking cash, a bank transfer, or a card payment. If someone can't pay in advance, they can't drop in.
For students who want to drop in regularly but not commit to a full enrolment, a credit pack is a reasonable middle ground — they buy a block of sessions upfront, and each drop-in draws down from that balance. This gives you the cash in advance and gives them flexibility. Just be clear about expiry: credits that never expire create a long-tail liability on your books.
Handle the "interested in enrolling" conversation deliberately
Drop-ins are often prospective enrolled students. Treat them that way. After their session, have a short, scripted follow-up — in person or by message — that covers:
What the enrolled programme looks like
The cost difference between dropping in repeatedly versus enrolling
The next available start date
Don't leave this to chance or memory. If you have a CRM or even a simple spreadsheet, log every drop-in with a "follow-up done?" column. A drop-in who attends three times and never gets a proper enrolment conversation is a missed opportunity.
Watch for roster gaps when students join mid-cycle
One issue that catches many operators off guard: when a student joins a recurring class partway through a term — whether as a new enrolment or converting from drop-in — they may not automatically appear on sessions that were generated before they joined. This means your attendance record for earlier sessions looks clean, but the student's history is incomplete.
The practical fix is to manually verify the roster for any session that falls within a student's enrolment period but was scheduled before they were added. Check the session, confirm they're listed, and add them if not. It takes two minutes and prevents billing disputes later.
A simple weekly rhythm
If you run drop-in classes regularly, build a short weekly check into your routine:
Before the week: Confirm enrolled headcount per session. Calculate available drop-in slots.
As drop-in requests come in: Check against available slots. Collect payment. Add to drop-in log.
After each session: Mark attendance for both groups. Note any no-shows.
End of week: Review drop-in log for anyone who's attended two or more times. Flag for enrolment conversation.
This takes under 30 minutes a week for most small schools and prevents the majority of the problems described above.
A note on what we built
At Noto, we built group class management specifically for schools and studios running exactly this mix — recurring enrolled students alongside per-session drop-ins, with separate pricing, capacity controls, and attendance tracking for each. The problems described in this article — over-enrollment, roster gaps, payment gaps — are the ones we heard about most from operators before they had a system that handled both groups in one place. If you're at the point where a spreadsheet is no longer cutting it, that's what Noto is for.
