A trainee has been accepted, paid a deposit and missed one module. Before issuing a completion certificate, the director needs the agreed payment record and evidence that the training requirements were met.
Separate admissions, payments, attendance and completion when choosing software. A sold place is only the start of the participant's record.
Start with the training model, not the feature list
Map the programme before you book demos. A 200-hour in-person training, a hybrid 300-hour programme, and a continuing-education weekend have different records, staff roles, and failure points.
| Operating question | What the system should make visible | Why it matters |
|---|---|---|
| Who may join? | Application answers, prerequisites, reviewer decision, acceptance date, and consent | An enquiry is not an enrolled trainee. Staff need a clear handoff from interest to admission. |
| What is owed? | Deposit, instalments, due dates, failed payments, refunds, credits, and any manual exceptions | A cohort can look full while its cash collection is incomplete. |
| What has been completed? | Session attendance, required hours, make-up status, assignments, practicum, and sign-off | Completion should be a decision based on records, not memory. |
| What can the trainee access? | Calendar, joining instructions, forms, documents, and changes | One source of truth reduces last-minute messages and outdated attachments. |
| What does the school need to retain? | Certificate details, completion date, payment history, consent, and any record required by the programme | Retention should follow a written policy and the school’s actual obligations. |
If a vendor cannot show this journey for one realistic trainee, from application to certificate, do not let a polished booking page decide the purchase.
The records a training programme normally needs
Build a simple participant record before choosing software. It prevents the common mistake of buying one tool for sales, another for attendance, and a third for completion without deciding how the records connect.
Application and admissions
Keep the information needed to make the admission decision, not every detail a form can collect. Typical fields include the programme selected, relevant prerequisites, acceptance status, notes from the reviewer, agreement to terms, and the date the offer expires.
Decide in advance who can view sensitive answers and who can change an acceptance decision. A front-desk team may need to see whether someone is enrolled; it may not need access to every application response.
Payments and enrolment
The commercial record should distinguish an accepted place from a paid place. At a minimum, track the agreed price, deposit, instalment schedule, payment status, refund or transfer policy, and any exception approved by the school.
For a programme with a deposit and balance, test the hard cases in the demo: a late instalment, a voluntary withdrawal, a transferred place, a payment-plan change, and a participant who has completed the course but still has an outstanding balance. The purpose is not to force one policy; it is to make the chosen policy executable.
Cohort and attendance
A cohort needs its own calendar, capacity, faculty assignments, locations or video links, and a clear definition of what counts as attendance. If make-up sessions are allowed, track the original missed session, the replacement session, the approver, and the final result. Otherwise a completion total becomes impossible to audit later.
If the training is registered with Yoga Alliance, check the current requirements for the relevant credential rather than assuming an old 200-hour template still applies. Yoga Alliance publishes standards for Registered Yoga Schools, including curriculum and delivery requirements, and separate guidance on how credit hours are calculated. Review the current standards before configuring the programme.
Completion and certificates
Do not treat “attended the final weekend” as the same thing as “eligible to graduate.” The completion workflow should show the requirements the school has set, the evidence for each one, the final approver, and the certificate issue date.
For Yoga Alliance registration, its certificate guidance identifies specific information that may be required on a completion certificate, including the RYS name, authorised signature, track designation, completion date, and trainee’s legal name. It also says schools should ensure trainees have met applicable completion obligations before issuing a certificate. Read the current certificate guidance and use it to review your own process; do not rely on a generic certificate template.
A practical workflow from inquiry to graduation
The strongest software is usually the one that makes handoffs explicit. This is a useful default workflow to test.
- Inquiry: a prospective trainee reads the programme page and asks a question or starts an application.
- Application: the school collects only the information it needs, records consent, and assigns a reviewer.
- Decision: the applicant is accepted, waitlisted, declined, or asked for more information. The decision and its owner are visible.
- Enrollment: the accepted trainee receives the agreement, payment choices, start-date information, and next deadline.
- Delivery: staff manage the calendar, attendance, faculty changes, documents, make-up work, and participant communication from the cohort record.
- Completion review: the director checks the programme’s defined requirements before approving graduation.
- Certificate and follow-up: the certificate is issued, the participant receives any next-step instructions, and the school retains only the records it needs under its policy.
This model is deliberately operational. It works whether the programme is sold through a studio, a specialist learning platform, or a mixture of systems.
When a booking platform is enough and when it is not
A booking and payment platform can be a good fit when the training sits alongside public classes, workshops, memberships, retreats, and private events. In that case, one customer and payment history can reduce duplicate records and make the commercial side of the programme easier to run.
It is not automatically the right system for every training provider. Choose a learning-management system or specialist education platform when the programme depends on graded coursework, complex assessment, accreditation-specific reporting, proctoring, detailed learning analytics, or a large on-demand curriculum. The right answer can be a connected stack, provided staff can identify which system owns each record.
Gomry’s public website describes a platform for ticketing, bookings, payments, memberships, distribution, and mobile operations. That makes it worth evaluating where a teacher training is one part of a wider experience business. It is not evidence that Gomry provides every admissions, assessment, certificate, or accreditation workflow described above. Ask for a demonstration of the exact workflow you need before promising it to trainees.
A vendor-demo script that exposes gaps
Give every vendor the same scenario. For example: a 200-hour cohort has 24 places, a deposit plus three instalments, one participant who changes payment dates, two absences requiring make-up work, a faculty substitution, a withdrawal, and a graduate whose certificate cannot be issued until the director signs off.
Ask the vendor to show, not describe:
- the participant’s full record and permission model;
- every payment state and how the finance team reconciles it;
- how a missed module becomes a documented make-up;
- which staff member can approve completion;
- what the participant sees when the schedule or requirement changes;
- how data is exported if you move systems later.
Score the workflow with the people who will actually use it: training director, administrator, front desk, finance, and faculty. A system that looks elegant in a sales demo but sends those people back to spreadsheets is not saving work.
Questions to settle before configuration
Write these policies before turning features on:
- What makes an applicant eligible, and who may override that decision?
- What happens after a missed payment or a withdrawal?
- Which absences can be made up, by when, and with whose approval?
- What evidence is required before a certificate is issued?
- Which records must be retained, for how long, and who can access them?
- Which requirements come from the school, an accreditor, a professional body, an insurer, or local law?
Software can enforce a clear policy. It cannot choose one for you.
Use Gomry for the supported booking records
An Event can provide a fixed capacity and ticket classes for a cohort. Participant forms can collect information, but demonstrate how the application, decision and payment are connected before using approval-required tickets for admissions. Do not infer a card-hold-to-deposit conversion from the approval setting.
If the programme uses separate deposit and balance payments, keep the agreed total, due dates and remaining amount under a clear booking reference. The payment-plan guide explains what must be reconciled.
For module attendance, demonstrate how each session relates to the cohort and trainee. A booking at a module does not establish completion of required hours, make-up work or an assessment.
Gomry does not host the curriculum or issue certificates. Keep assessment and completion decisions in the school's learning records, with an explicit handoff from booking and payment. The studio software guide covers the surrounding classes and workshops.
Frequently asked questions
Can one system handle applications, payments, and attendance?
Sometimes. The important test is whether the records stay connected as the trainee moves from application to enrollment, attendance, and completion. If the system cannot handle an essential part of the process, define the handoff and source of truth before launch.
What should a yoga teacher training certificate include?
Use the requirements of your school and any relevant credentialing body. Yoga Alliance publishes certificate guidance for RYT registration; check its current requirements rather than copying a template from another school.
Should a training programme use instalments?
It can, if the school can clearly administer due dates, payment failure, refunds, withdrawals, and exceptions. Choose the policy first, then test whether the software can execute it without manual reconciliation.
Is an LMS necessary for a yoga teacher training?
Not always. It becomes more useful when online coursework, assessments, progress tracking, or accreditation-specific evidence are central to the programme. For a mainly in-person cohort, a booking and operations platform may cover more of the day-to-day work.
What is the biggest implementation risk?
Treating sales, attendance, and graduation as separate projects. Start with one participant record and a written workflow, then test exceptions before opening enrollment.
Use one trainee's application, payment and missed-module case in the demonstration. Ask the director to find the evidence needed for the next decision without rebuilding the record from email.