Check recurring delivery capacity before adding a client.
Define the commitment before automating the balance
A client asks a reasonable question: after the session you moved, how many do I have left? You should be able to answer without reconstructing an email chain or confusing an appointment with a payment.
For an established Melbourne executive-coaching practice, a package is a commitment to provide specific work. Your administrator needs to know what was bought, what is reserved, what has been delivered and which exception you agreed—not just see a number beside a client’s name.
Gbeya has service and booking records and a public coaching-package planning tool. A service can record an included-session count. That is not yet evidence of an automatically reconciled session-credit ledger. This guide defines the workflow and acceptance checks needed before offering that automation as available.
Can your administrator explain the balance?
Use one anonymised scenario before deciding what to automate.
- Identify the original service units and agreement version.
- Separate available, reserved, completed and expired amounts.
- Trace each adjustment to its reason and authorisation.
- Check whether cancellation changed a credit, money, both or neither.
- Explain the next step to the client without exposing confidential notes.
Any unexplained difference becomes a reconciliation task before the balance is shown as authoritative.
Operational checklist; not a contract template, accounting judgement or guarantee of coaching outcomes.
One agreement, different session states
Use this proposed model to explain the balance. It is a planning diagram, not a demonstration of an automated Gbeya ledger.
Purchased units
The original promise: keep individual sessions and group places distinct.
Available
Units that can still be reserved under the agreement.
Reserved
Units held for future appointments, not yet delivered.
Completed
Delivered sessions, recorded separately from progress towards goals.
Booking can move an available unit to reserved; attendance can move it to completed. Restoration, expiry and bonus adjustments need explicit rules and history. Payment and refund outcomes remain separate.
1. Define what one package actually includes
Write the promise in units your client recognises: individual sessions of a stated duration, a group place, an initial assessment or a review conversation. Do not silently treat these as interchangeable credits.
Agree who is participating, who pays and what information a sponsor receives. Professional coaching guidance puts the agreement and confidentiality ahead of administration; software should reflect that agreement rather than invent it.
- Why this matters
- An entitlement is a recorded right to a specified service. Keeping the service type and unit explicit prevents a shared total from hiding different commitments.
- Work through the example
- An assumed package includes four individual sessions and one group workshop. Record those separately unless you have explicitly agreed how substitution works.
- When the usual approach changes
- A flexible retainer may promise access or time rather than a fixed number of appointments. It needs a different definition, not a forced session count.
- Your decision
- Describe each unit, substitution rule and excluded work before assigning a balance.
2. Separate available, reserved and completed sessions
A future appointment has not yet been delivered. If booking reserves a credit, show it as reserved; if attendance consumes it, record the completion separately. Otherwise a client can see a balance fall without knowing why.
The inspected Gbeya service has an included-session field, while bookings carry their own status and order link. A client-level entitlement ledger, reservation rules and atomic credit redemption were not established by this scoped review. Verify the complete workflow and build any missing parts before relying on automatic balances; the field alone does not establish them.
- Why this matters
- A ledger records each change with its reason and related booking. An atomic reservation means two simultaneous booking requests cannot both spend the same final credit.
- Work through the example
- With one available credit, two browser tabs attempt different appointments. The acceptance test requires one reservation to succeed and the other to explain that no credit remains.
- When the usual approach changes
- For a small practice, a carefully reconciled manual register may be safer than an unfinished automated balance. It still needs an owner and a clear update process.
- Your decision
- Do not call the balance automatic until concurrent requests, retries and reconciliation have been tested.
3. Treat cancellation, credit restoration and refund as different decisions
Moving an appointment changes a diary entry. Restoring a session changes an entitlement. Refunding money changes a financial record. A single cancelled label cannot tell you that all three happened.
Agree how your practice handles timely cancellation, late cancellation, coach cancellation and an exceptional adjustment. Use context-specific professional advice for contractual terms; this operational model does not decide anyone’s refund rights.
- Why this matters
- Separate records preserve the reason for each action. An approved restoration can return a credit without pretending a payment was refunded, and a refund must be checked against the provider’s confirmed state.
- Work through the example
- A coach cancels an appointment and restores its reserved credit. The payment may remain unchanged if the agreed next step is another appointment; record that decision rather than implying a refund.
- When the usual approach changes
- A genuine dispute or termination needs individual review. A rigid balance rule should not silently determine the entire relationship.
- Your decision
- Show the appointment outcome, entitlement adjustment and money outcome independently, with an authorised reason and dated history.
4. Make expiry, transfers and bonus sessions visible
If a package has a time boundary, state whether the client must book before that date or attend before it. Those rules can produce different results. Include the applicable timezone and an understandable date in the agreement and interface.
A transferred or bonus session should have its own reason and authorisation. Do not overwrite the original purchase count and leave the administrator guessing why the arithmetic changed. These controls and reminders are acceptance requirements, not verified current Gbeya features.
- Why this matters
- Explicit boundaries let the system evaluate the right event. Dated adjustments preserve what was originally promised and what changed afterwards.
- Work through the example
- A planning scenario allows booking before the final day but attendance later. A test should cover a booking just before and just after the boundary, including the Melbourne timezone.
- When the usual approach changes
- Some packages have no expiry or allow an agreed pause. Do not impose a default deadline simply because another product offers one.
- Your decision
- Write and test the actual rule. Never infer a universal expiry policy from a supplier’s implementation.
5. Close the package with a conversation, not just a zero balance
Using every appointment does not prove that coaching achieved its purpose. Review the client’s goals, what changed and whether continuing, changing direction or concluding is appropriate.
A sponsor may need administrative confirmation while session content remains confidential. Decide the reporting boundary with the people involved. Do not treat an entitlement report as permission to disclose coaching notes.
- Why this matters
- Administrative completion and progress review answer different questions. Keeping them separate lets you reconcile delivery without turning attendance into an outcome claim.
- Work through the example
- The ledger shows every agreed session delivered. In the review, the client identifies a useful change and an unresolved concern. Record the agreed next step without inventing a numerical success score.
- When the usual approach changes
- Ending before every session is used may be appropriate under the agreement. A remaining balance is a matter to resolve, not automatic proof that coaching failed.
- Your decision
- Review delivery, goals and the relationship separately before proposing another package.
The agreement matters more than a convenient total
Professional guidance prioritises a clear agreement and confidentiality. Scheduling documentation shows why seemingly simple choices—such as appointment units and expiry—have precise meanings. Coaching research and practitioner guidance add a different point: reviewing progress and the relationship cannot be replaced by counting sessions.
For this practice, the sensible starting point is a small, explainable ledger tied to the agreed service units. The opposing case is a well-owned manual register: if your volume is low, it may serve you better than an unverified automated balance. Automation earns its place when it handles simultaneous bookings and awkward changes reliably.
This is a medium-confidence operational recommendation, not evidence of improved revenue or client outcomes. The current Gbeya primitives provide a starting point; the entitlement, adjustment and boundary acceptance checks remain necessary before claiming complete package automation.
Medium for the scoped operating model; no quantified product or coaching outcome claim.
No direct interviews with this practice, production redemption test or validated outcome model.
Session reconciliation with stated assumptions
Six sessions, one clear reconciliation
Assume six individual sessions were purchased. Two were completed, one is reserved and three remain available. The reserved appointment is then cancelled under an agreed restoration rule: the reservation returns to available, leaving two completed and four available. No refund is implied.
Before cancellation
2 completed + 1 reserved + 3 available = 6 sessions
After agreed restoration
2 completed + 0 reserved + 4 available = 6 sessions
Before: 6 = 2 completed + 1 reserved + 3 available. After restoration: 6 = 2 completed + 0 reserved + 4 available.
These are stated planning inputs. Restoring the reservation does not establish that money was refunded.
A late-cancellation rule might produce a different entitlement outcome. A bonus credit would increase the total through a separate adjustment, not rewrite the original purchase.
Reconcile the same units and keep monetary outcomes separate.
Three assumptions worth checking
Sessions included means credits are tracked automatically.
An offer field is not a tested client-level ledger.
Cancelling an appointment automatically refunds it.
Appointment, entitlement and payment states are separate.
A fully used package proves a successful coaching outcome.
Delivery completion and progress towards agreed goals require different evidence.
Your next 30 days
Days 1–7
Define the agreement
Specify units, changes, reporting and boundaries with the relevant parties.
Ready for the next step: The client-facing promise can be explained without assumptions.
Days 8–14
Map the ledger
Work through normal, cancelled, bonus, transferred and expired cases using anonymous examples.
Ready for the next step: Each change has an owner, reason and expected balance.
Days 15–21
Verify the implementation
In a test environment check concurrent redemption, retries, boundaries and authorised adjustments without real payments.
Ready for the next step: Observed results match expected balances and failures are visible.
Days 22–30
Review the handover
Have the administrator explain a reconciliation and prepare the client’s progress review.
Ready for the next step: Delivery and progress remain distinct; unresolved automation stays inactive.
Questions before you automate a package
Does Gbeya already track a remaining package balance?
The inspected code establishes included-session service data and individual bookings, not a fully verified entitlement ledger. Scope and test remaining-credit automation before relying on it.
Can individual and group sessions share one balance?
Only if the agreement defines the conversion clearly and the implementation supports it. Otherwise keep service units separate.
Does cancellation restore a session?
That depends on the agreed rule and its implementation. Verify restoration separately from appointment cancellation and payment refund.
Can I add bonus or transferred sessions?
Treat these as authorised, traceable adjustments. Current automatic controls were not established by the scoped inspection.
Does package expiry mean attendance must finish by that date?
Not necessarily. Specify whether the boundary applies to booking or attendance and test that precise rule.
Can I start planning now?
Use the public package-planning tool and booking overview, then request a scope for the entitlement and exception controls you need.
Prepared by Gbeya · Sources reviewed 30 October 2026. Planning guidance; automatic package balances and exception handling require separate implementation and verification.