For coachesBookings & payments
Single lessons, weekly bookings and packages: a coach's practical guide
Keep lesson plans, confirmed times, payments and changes connected, using a worked example of single, weekly and package lesson records.

In this guide
← For coachesGive each lesson its own record, even when it belongs to a weekly arrangement or package. Keep the learner, current confirmed time, venue, payment status and any pending change together. A future plan, an authorised payment and a confirmed lesson describe different things.
This guide explains what your records need to make clear. Product-specific payment and cancellation rules still come from the system and terms you are using.
Separate the arrangement from each individual lesson
| Lesson arrangement | Keep clear at arrangement level | Keep clear for each lesson |
|---|---|---|
| Single lesson | What has been agreed for that booking | Current time, venue, payment and confirmation |
| Weekly arrangement | The intended sequence and relevant conditions | Which lessons are requested, confirmed, paid or pending |
| Package | What was purchased and the package conditions | The identity, time and status of every included lesson |
A learner saying “Tuesdays work for me” is useful planning information. It does not, by itself, establish that every future Tuesday has been confirmed or paid.
Likewise, changing the time of one package lesson should remain attached to that lesson. It should not create a second apparent entitlement or erase what happened to the original record.
Use a consistent record format
Illustrative coach scenario: Alex and the learners below are fictional. The lesson identifiers, dates, payment labels and sequence are examples of record-keeping, not actual bookings or screenshots of VOLOCOACH.
Alex uses a simple review view to distinguish three arrangements. The identifiers are example labels; he would use the actual references generated by his booking system.
| Example lesson | Arrangement | Current record | Next action |
|---|---|---|---|
| S-01, Mia, 13 Oct at 18:00 | One single lesson | Time confirmed; required payment recorded | Check final venue details |
| W-01, Sam, 14 Oct at 17:00 | First lesson in a weekly arrangement | This lesson confirmed; required payment recorded | Keep later lesson statuses separate |
| W-02, Sam, 21 Oct at 17:00 | Later lesson in the same arrangement | Intended time; not recorded as confirmed in this example | Follow the system's confirmation and payment process |
| P-01, Jo, 15 Oct at 19:00 | One lesson within a package | Confirmed; allocation linked to this lesson | Retain the lesson reference if its time changes |
The value of the view is that Alex can identify what requires attention without searching separate conversations. The table is a general example, not a description of an available App report.
Track a change against the same lesson
Suppose the fictional Mia asks to move S-01 from 13 October at 18:00 to 16 October at 18:00. Alex needs to distinguish the request from the final outcome.
| Stage of the illustrative change | What the record needs to show |
|---|---|
| Request received | Existing confirmed time and proposed new time |
| Response pending | Who needs to respond and the applicable deadline |
| Additional payment required, if applicable | The quoted components and payment deadline |
| Change confirmed | New confirmed time, linked to the original lesson |
| Request unsuccessful | The resulting booking status under the actual system's rules |
Do not overwrite the original time simply because someone has proposed a replacement. Follow the booking system's process and keep the final status visible to the learner.
In VOLOCOACH, a learner's request does not instantly move a lesson. The coach must respond, and any required payment must succeed before the change is confirmed. Use the current policy for deadlines and charges rather than copying a general example into a booking decision.
Treat a package as individual lessons with shared conditions
In another fictional example, Jo has a package containing four lessons. Alex records two as completed, one as confirmed for an upcoming time, and one as needing an agreed time. These counts illustrate a review method; they are not a claim about a customer's purchase or an App credit balance.
For the upcoming lesson, a time change remains a change to that same lesson. Alex also checks the package conditions before discussing a cancellation, expiry or refund.
VOLOCOACH's confirmed Package Lessons have separate conditions from Single Lessons. Moving a lesson does not create a reusable credit. See the FAQ and policy for the actual options.
Review exceptions before the week starts
Check unresolved requests, unclear venue arrangements and payments that have not reached the required state. Then check the final details the learner can see.
Ask yourself:
- Is this a confirmed lesson or only part of a future plan?
- Does the payment status mean authorised, collected or something else?
- Is there an outstanding change request?
- Are the current time and venue consistent across the record and messages?
- If a lesson belongs to a package, does it retain its original reference?
This review is about finding outstanding actions. It does not replace the platform's actual confirmation, payment or change process.
Common lesson-management questions
Is a weekly arrangement the same as a confirmed lesson?
No. Check individual lesson status and the relevant payment process. A recurring intention does not establish the status of every future lesson.
Can I use one cancellation rule for every lesson type?
Do not assume so. Single, recurring and package lessons may have different conditions. Use the rules for the actual booking rather than a rule copied from another lesson.
Can I keep discussing changes in chat?
Use chat to discuss the options, then complete the required booking action and check the final status. Our WhatsApp admin guide explains how to measure the work created when conversations become separate booking records.
If your current tool cannot keep these distinctions clear, use the booking-software checklist to test alternatives. Explore the coach overview for VOLOCOACH's product introduction.
Keep the useful ideas. Lose the admin.
Explore volocoach

