Use AI to draft the paperwork and let your studio software do the sending: a registration form of about a dozen fields, a seven-email enrolment sequence, and three waitlist messages (offer, reminder, release) with a fixed hold time. Keep children's names and medical details out of the chat, and read every message yourself before it goes.
The AI knows nothing about your term dates, class caps or fees, and it will invent plausible ones if you leave gaps. So every draft starts from a one-page facts sheet that you write once. The rules in that sheet (who gets priority, how long a held place lasts, what happens when nobody replies) do more for your enrolment than any clever wording.
What the AI drafts and what stays with you
Registration involves three kinds of work: wording, sending and deciding. AI is good at the first. Your studio software or mailing tool handles the second. A named person has to own the third.
| Job | The AI drafts | You or your software do |
|---|---|---|
| Registration form | Question labels, help text, consent sentences | Build the form, mark required fields, store the answers |
| Enrolment emails | Subject lines, body copy, reminders | Schedule, merge names in, stop sending to families who have registered |
| Waitlist | Offer, reminder and release wording; a one-page rules sheet | Add and remove names, run the hold timer, decide who is next |
| Class placement | Nothing | The teacher judges level and age-group fit |
| Medical and access notes | A neutral question to ask | One named staff member reads the answers; the AI never sees them |
| Replies to individual parents | A first draft | You read, edit and send, especially fee queries and complaints |
The dividing line is names. The AI writes [first name] and your software swaps in the real one after you have approved the draft, so the assistant never sees your register. If your software has no mail merge, a spreadsheet plus your email client's merge feature does the same job.
Eleven form fields and the ones to leave off
Every extra field costs a parent half a minute and gives you something more to protect. If you enrol families in the EU, data-protection law such as the GDPR asks for personal data that is 'adequate, relevant and limited to what is necessary' (Article 5), and it is a sound rule wherever you teach. For a dance studio, that points to a short form.
| # | Field | Why you need it | Who sees it |
|---|---|---|---|
| 1 | Parent or guardian name | Account holder; the person who agrees to the policies | Office |
| 2 | Parent mobile | Waitlist offers lapse in hours, so you need a second route besides email | Office |
| 3 | Parent email | Confirmations, timetable changes, offers | Office |
| 4 | Dancer's name | Register, costume and recital lists | Office, teacher |
| 5 | Age on the first day of term (or date of birth) | Age-group placement; ask for the full date only if your insurer or class rules need it | Office, teacher |
| 6 | First and second choice of class | Registration, plus an alternative to offer if the first choice is full | Office |
| 7 | Previous dance experience (one line, optional) | Lets the teacher place a dancer with two years of ballet in the right group | Teacher |
| 8 | Emergency contact who is not the parent | For the day the parent can't be reached | Office, teacher on the day |
| 9 | Medical or access needs (optional free text) | Only what the teacher needs to run the class safely | That teacher and the manager |
| 10 | Photo and video permission | A separate optional tick, unticked by default | Office, whoever posts on social media |
| 11 | Agreement to the studio policies | One tick, with a link to your handbook | Office |
Classes where parents don't stay add one more field: the names of people allowed to collect the dancer. Everything else stays off until you can say what you would do with it.
Leave off the home address (unless your payment provider insists on a billing address), school, the parent's employer, the dancer's gender, full medical history, family doctor details, identity documents and social media handles. 'How did you hear about us?' can move into the confirmation email as a one-click question, where it doesn't slow down registration.
Set the deletion rule while you build the form, not after a complaint. Article 5 also asks for data to be kept no longer than necessary, so decide now: waitlist entries removed two weeks after term starts, and forms for leavers deleted after whatever period your adviser suggests.
To use the AI for the form itself, give it the table and ask only for the wording:
Write the labels and one line of help text for a dance studio registration
form with exactly these fields: [paste the eleven fields].
Rules: plain English a parent can read in one pass; say which fields are
required; for the medical field, tell parents to share only what the
teacher needs to run the class safely; do not add fields I haven't listed;
never ask for a home address, school or any identification number.Then build the form in your studio software or form tool. The AI's job ends at the wording, and the most common correction is an extra field or two it added 'to be helpful' (a school name, a home address). Delete them.
Parental consent: one tick for classes, separate ticks for the rest
Registration forms often bundle four different permissions into a single 'I agree'. Pull them apart: taking part and accepting the studio's policies (required), photos and video for your website and social media (optional), sharing medical or access notes with the teacher and first-aider (required only if that field is filled in), and news and offers by email or text (optional, and separate from service messages such as a timetable change).
Two rules in the GDPR show why the split matters. Consent is less likely to count as freely given when a service is made conditional on consent to data use that isn't necessary for it (Article 7(4)), and withdrawing must be as easy as giving it (Article 7(3)). In practice: never make the photo tick a condition of joining, and put an 'update my permissions' link in every email you send.
Here is a bundled sentence a studio might inherit from an old form, followed by the version an assistant produced when asked to 'split any sentence that asks for more than one permission and say which parts are optional' (illustrative):
Before: I agree to the studio using my child's name, image and information for promotion and to sharing any information with staff.
After, required: I am the parent or legal guardian of the dancer named above and I agree to the studio policies in the handbook.
After, optional and unticked: You may use photos or video of my dancer in class on the studio's website and social media. I can withdraw this at any time by telling the studio, and it will stop for new posts.
After, required only if the medical box is filled in: The studio may share what I have written about my dancer's medical or access needs with their teacher and first-aider, and nobody else.
After, optional and unticked: Send me studio news and offers by email.
A first draft like this often adds a promise that withdrawn photos will be 'removed from all platforms within 24 hours'. A studio with years of posts can't keep that promise, so cut it back to 'stop being used in new posts'. AI tends to over-promise in consent wording because reassurance reads well. Check each sentence against what a front-desk person could actually do on a Monday morning.
Your dance studio handbook is where the policies behind the first tick live, and the after-school club registration form tutorial covers the same consent split for a different kind of children's activity. Ask a data-protection adviser or solicitor to read the final wording. The AI can't know which rules apply to you, including the age at which a young person can consent for themselves.
A one-page facts sheet that stops invented terms
Write this once, fill in every bracket, and paste it at the top of every prompt. Here it is filled in for an imaginary studio (illustrative fees and rules):
STUDIO FACTS (paste above every prompt)
Studio: [studio name]. Weekly classes, 36 weeks a season. First class [date].
Registration: opens [date] 9am for current families. Priority closes
[date] 9pm. Opens to everyone [date] 9am.
Classes (cap 12 each): Ballet 5-7 Sat 9:30 | Jazz 8-10 Tue 5:00 |
Tap 6-8 Thu 4:30 | Contemporary 11-14 Wed 6:00 | (and so on)
Fees: $45 a month per class. Registration fee $20 per dancer, once a year.
No sibling discount.
Registered means: form complete AND first month's fee paid.
Leaving: one month's written notice. No refunds for missed classes.
Waitlist: free. First come, first served. An offer is held 48 hours before
term, 24 hours once term has started. No reply = place offered to the
next family and the first family comes off that class's list.
Contact: [studio email], [studio phone]. Replies within 2 working days.
Tone: warm, brief, plain English, no emoji, no exclamation marks.
Never say: guaranteed, limited time, anything about a dancer's ability,
or any date, fee or rule that is not listed above.ChatGPT and Claude both have Projects, where a file and standing instructions sit behind every new chat, and both are available on free plans with tighter file limits (check the current caps). Put the sheet in one and every draft starts from the same facts. When a fee or date changes, you edit the sheet once instead of fixing fifty prompts.
The line 'Registered means: form complete AND first month's fee paid' looks fussy and prevents the most common muddle of the season: a parent who filled in the form, never paid and believes their place is secure.
Seven emails from heads-up to first week
| # | Goes out | Audience | Its one job |
|---|---|---|---|
| 1 | Three weeks before registration opens | All current families | Dates, fees and any class changes, so nothing surprises them on the day |
| 2 | Registration opens (morning) | All current families | The link, the priority deadline, and what 'registered' means |
| 3 | Five days in | Current families who have not registered | Reminder with the deadline and how to ask a question |
| 4 | Day before priority closes | Those still not registered | A plain notice that places open to new families after the deadline |
| 5 | Morning after priority closes | Enquiries, former dancers, waitlist sign-ups | Registration is open; classes with three places or fewer are named |
| 6 | Immediately on registration | Each family, sent by the studio software | Confirmation: what they booked, what is due, what happens next |
| 7 | One week before the first class | Registered families | What to wear, where to arrive, where parents wait, who to contact |
Emails 3 and 4 only work if they skip anyone who has already registered. That filtering is a job for your software or mailing tool, and the AI can't do it. A reminder sent to everyone produces a wave of 'did my payment go through?' replies from families who finished days ago, and it teaches parents to ignore your reminders. If your system can't filter by status, send one registration-open email and one 'last day' email to all, and word both so they make sense to someone who has already registered.
Sending limits matter if you use a free mailing tool. At the time of writing, Mailchimp's pricing page lists the Free plan at up to 500 sends a month with 250 a day, and the Essentials plan at ten times your contact count a month. In an illustrative studio with 112 families and 60 enquiry contacts, emails 2 to 5 come to 112 + 34 + 19 + 60 = 225 sends in the month registration opens (email 1 went out the month before, and the studio software sends email 6). Add email 7 to roughly 125 registered families and waitlist messages to 23 families (about 70 sends) and the month reaches about 420 of the 500. It fits, narrowly. Without the filtering, emails 3 and 4 would go to all 112 families, 224 sends instead of 53. That adds 171 and takes the month to about 590, over the free limit. The Free plan also has no scheduled sends or automated flows, so each email goes out by hand on its day. Essentials adds scheduling and automated flows of up to four steps.
Keep the sequence for families who are already yours. For lapsed or inactive members, the fitness studio welcome, waitlist and lapsed-member emails tutorial uses the same ideas with a different cadence.
Drafting the five-day reminder without promising a place
This is the prompt for email 3, the five-day reminder. The structure works for any of the seven; change the goal and the audience.
You are writing emails for a children's dance studio. Use ONLY the facts
sheet below. If a fact you need is missing, write [MISSING: what] instead
of guessing.
[paste the facts sheet]
Write email 3 of 7: the five-day reminder to current families who have not
yet registered. Goal: they register before the priority window closes.
Constraints: under 150 words. Give three subject lines under 45
characters. One link, written as [registration link]. Address the parent
as [first name]. Never mention a dancer by name. Do not promise a place
beyond the deadline. No emoji.A typical first draft (illustrative, as the assistant returned it):
Subject options: Priority registration closes [date] / Keep your usual class: register by [date] / Five days left to keep your place
Hi [first name],
Just a quick reminder that priority registration for current families closes at 9pm on [date]. Your dancer's place is guaranteed until then, so there's no need to rush! After that, any unclaimed places open to new families.
To keep your usual class, complete the form here: [registration link]. Registration is complete once the form and the first month's fee are in.
Warmly,
[your name]
It reads fine and still has four problems.
- 'Guaranteed' and 'no need to rush'. The facts sheet says a place is held until the deadline, not guaranteed. The sentence also undercuts the whole point of a reminder. Replace it with 'Your usual class is held until 9pm on [date]'.
- The exclamation mark. The tone line said none. Assistants slip back to type after a few drafts.
- No way to ask a question. The sheet gives a contact and a reply time. The draft ignores both.
- 'Unclaimed places' is vague. Say when they open: 'from 9am on [date]'.
Run the same prompt for the other emails and you will meet the same four faults in different forms. After the second round, add each recurring fault to the 'never say' line so the next draft starts cleaner. Keep a dancer's name out of subject lines too, because lock-screen previews show them to whoever is holding the phone.
Waitlist rules that fit on one page
Most waitlist disputes are really arguments about a rule nobody wrote down. Settle these six before you draft a single message, then publish them on your registration page.
| Decision | Choices | What it costs you |
|---|---|---|
| Who goes first | First come, first served; or current dancers moving up first | The second is kinder to loyal families but needs a written rule and a field showing who is current |
| Hold time | 24 hours or 48 hours | 24 hours fills places faster but misses parents who check email in the evening; 48 hours is fairer and can add a day per lapse |
| How the offer travels | Email only, or email plus text | Text is seen sooner; email carries the details. Use both if your software allows |
| If nobody replies | Remove them, or move them to the back | Removal keeps the list honest. Moving to the back makes every later count wrong |
| What confirms the place | A reply of YES, or the form plus payment | Payment as confirmation settles things faster but excludes families waiting for payday |
| Clean-up | A fixed date, such as two weeks into term | Without it the list fills with families who found another class weeks ago |
If your studio software has a waitlist feature, check four things before relying on it. Does the offer go out by text, email or app? Does the first person to reply get the place, or the first person on the list? Is there a response deadline you can set? What happens when it passes? Vendors describe these differently on their pages, and I haven't compared any here, so test your own system with a dummy family (see the last section). The AI-run class waitlist tutorial goes further into automating the offers themselves.
A quick sum shows why the rules are worth fixing, using an illustrative nine places opening across your classes in the first month. Chased by hand, each takes about four messages (offer, chase, release, next offer) at roughly five minutes each: 9 × 20 minutes = 3 hours. With approved wording and a fixed hold time, each message is copy, fill the brackets, send. At about a minute and a half per message you spend around 54 minutes, and the hold timer, not your memory, decides when to move on. These are illustrative estimates, so time your own first week and replace them.
Offer, reminder and release: three waitlist messages
All three put the class name, never the dancer's name, in the subject line, and all three give a full day and time rather than 'within 48 hours'. A deadline written as a duration depends on when the parent opened the message. A deadline written as 'by 4pm on Wednesday' doesn't.
The prompt behind the three messages below, pasted under the facts sheet:
Write three waitlist messages for the class [class name]:
(1) the offer, (2) a reminder sent the morning the hold ends, (3) the
release when the hold lapses with no reply.
Each: under 90 words; class name in the subject line; no dancer names; the
deadline as a full day and time; say what happens if there is no reply;
mention the second-choice class in messages 2 and 3. Do not write
"next in line", "guaranteed" or anything about a dancer's ability.The offer
Subject: A place has opened in Saturday Ballet 5-7
Hi [first name],
A place has opened in Saturday Ballet 5-7 (9:30). It is yours if you want it: reply YES or use [accept link] by 4pm on [day].
If we haven't heard by then, we will offer the place to the next family so the class stays full, and you will come off this class's list. To confirm, we need the registration form [link] and the first month's fee of $45.
[your name], [studio name]
The reminder, sent the morning the hold ends
Subject: Your place in Saturday Ballet 5-7 is held until 4pm today
Hi [first name],
The place in Saturday Ballet 5-7 is still held for you until 4pm today. Reply YES to take it. If it no longer suits, reply NO and tell us if you'd like us to try [second-choice class] instead.
The release
Subject: The Saturday Ballet 5-7 place has gone to the next family
Hi [first name],
We didn't hear back by 4pm on [day], so we have offered the place to the next family and taken you off this class's list. If you'd still like a place, you can join the list again at [link]. We can also tell you straight away if a place opens in [second-choice class].
Three details do most of the work. The offer says what happens if nobody replies, so the release never feels like a surprise. The reminder mentions the second choice you collected on the form, which turns a 'no' into a different class instead of a lost family. And the release is a message in its own right, because silence leaves parents unsure whether they still have a claim. Have the AI write all three in one chat so the wording stays consistent, and give it the facts sheet each time.
One class, three days: a waitlist run to the hour
An illustrative case, using the rules above. The Saturday Ballet 5-7 class has a cap of 12, all 12 places taken, and seven families waiting (W1 to W7). In the first week of term two places open: one family moves away and another dancer decides ballet isn't for them. Term has started, so the hold is 24 hours.
| When | What happens | Message |
|---|---|---|
| Mon 4pm | Both places open. W1 and W2 each get an offer, one offer per open place | Offers to W1 and W2 |
| Mon 6pm | W1 replies YES and pays that evening. Place 1 is filled after two hours | Confirmation to W1 |
| Tue 8am | W2 has been silent for 16 hours; the hold ends at 4pm | Reminder to W2 |
| Tue 4pm | Hold expires with no reply | Release to W2; offer to W3 |
| Tue 7pm | W3 replies NO: they have found a class on another day | Offer to W4 |
| Wed 9am | W4 replies YES and pays by lunchtime. Place 2 is filled | Confirmation to W4 |
Place 1 was filled in two hours. Place 2 took from Monday 4pm to Wednesday 9am, 41 hours, because W2 went quiet and W3 declined. Eight messages went out, counting the two confirmations: about twelve minutes of your time when the wording is ready, against around forty minutes if you write each one fresh.
A 48-hour hold would have run W2's offer to Wednesday 4pm, so W3 would have been asked then and answered that evening, and W4's YES would have landed on Thursday 9am. That is 65 hours, a full day longer. Each family that goes quiet costs you a whole hold, which is the argument for a short hold once term has started and a longer one before it, when parents are away or planning.
Two more lessons sit in the table. 'One offer per open place' stopped two families being told they were first in line for the same spot. And W3's 'no' arrived at 7pm, after most offices close, so the sequence only stays quick if someone or something sends the next offer that evening. If your software can't, fix two daily times (say 8am and 4pm) for checking replies and sending the next offer, and tell families in the offer which times those are.
Once enrolment settles, the same facts sheet and placeholders carry into recital emails. The dance recital planning tutorial covers the schedule, costumes and parent messages.
Keeping children's details out of the chat
The facts sheet, the templates and your own draft emails are safe to paste, because none of them contain a real child. Never paste dancer names, birth dates, medical notes, photos, the registration export or parents' contact details. Anything you would pull off a register stays out.
The temptation arrives when you are busy. A realistic mistake: an owner exports the waitlist, pastes all 23 rows into a chat and asks the assistant to 'sort them by priority and write each family an offer'. The names and phone numbers go to a third party for no reason, and the assistant, being a language model, quietly drops a row and reorders two. The fix costs nothing. Sort the list in a spreadsheet by sign-up time, write the offer once with [first name], and let mail merge do the rest.
On business plans (ChatGPT Business, Claude Team and similar), the vendors say they don't train on your content by default. On personal plans there is a model-training switch in privacy settings. Neither makes it sensible to upload a children's register, and the safest data is data that never entered the chat. The children's data in a nursery tutorial works through the same question for a setting with stricter rules.
If you do want help with numbers, use counts: 'Saturday Ballet 5-7 has 12 enrolled and 7 waiting; Tuesday Jazz has 8 enrolled and none waiting. Suggest where a second group would help.' That is a useful question and needs no names.
Dummy families before launch, four numbers after
Before the first real email, create three dummy families using addresses you control, ideally one at a free webmail provider and one on your own domain.
- Family A registers on time. Check that they receive the confirmation and the first-week email, and none of the reminders (emails 3 and 4).
- Family B joins a waitlist, receives an offer and replies YES. Check the deadline shows the right day and time, and that the place appears on the class register.
- Family C joins the same waitlist and ignores the offer. Check the reminder arrives at the right moment, the release follows, and C comes off the list.
Open each email on a phone. Check the permissions link works, replies go to a mailbox someone reads, and nothing landed in spam.
After the first fortnight, compare four numbers with last season. First, the share of current dancers registered when priority closed. Second, the hours between a place opening and an accepted offer. Third, waitlist offers accepted against offers sent. Fourth, the emails and calls asking things the sequence should have answered ('when does it start?', 'did my payment arrive?'). If the fourth number hasn't fallen, the fault is in the emails rather than the families, so go back to the facts sheet and see what it leaves out.
Questions studio owners ask before automating enrolment
How long should a waitlist offer stay open?
Match it to how quickly your families reply. Forty-eight hours is fair to working parents before term starts. Once classes are running, 24 hours is usually enough and stops a place sitting empty for days. Whatever you choose, put the exact day and time in the offer and say what happens when it passes.
Do I need separate consent for photos and video?
Treat it as a separate, optional tick that is unticked by default and never a condition of joining. Under the GDPR, consent is less likely to be freely given when a service depends on consent that isn't necessary for it, and withdrawing must be as easy as agreeing. Ask a data-protection adviser to review your final wording.
Should the first family on the waitlist always get the place?
First come, first served is the simplest rule to explain and defend. Some studios let current dancers moving up a level go first. Either works if it is written on your waitlist page and applied the same way every time, because the complaints come from families who think the rule changed.
Further reads
- Can AI Draft a Martial Arts School Waiver for Children? — Waiver wording for children's classes, drafted and checked.
- Pilates Studio Software: Reformer Capacity, Waitlists and AI Features — How capped classes and waitlists work in studio software.
- Swim School Management Software: Do You Need AI Features? — Most swim schools need level tracking, waitlists, make-up lessons and billing to work first. AI features come last, and here is how to test them.
- Martial Arts Summer Camp Ideas: Sign-Ups and Parent Emails With AI — A four-week camp plan for a martial arts school: 20-place pricing, daily timetable, safeguarding and pick-up rules, a sign-up page and six parent emails.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: GDPR Articles 5 and 7 (data minimisation, storage limitation, conditions for consent); Mailchimp's pricing page (Free and Essentials send limits, scheduling and automated flows). Studio-software waitlist features were not compared, so check your own system.