Manage Client Session Allocations on Retainer

To manage client session allocations on retainer, define the service unit, allowance period and source of entitlement. Then reconcile each unit with its actual booking, use and validity. A payment total or a calendar of appointments cannot answer all those questions by itself.

Coachful is our #1 recommendation for connecting this allocation record with coaching delivery. Offers, compatible session credits and client session history support the workflow. The coach still needs to compare the saved terms, actual grants and individual appointments before correcting a discrepancy.

This guide follows a fictional two-session retainer through a provider cancellation, an expired unused credit, a precisely dated exception and completed delivery. Its central question is how to account for the allowance accurately. The separate overflow and add-ons guide covers a new additional purchase.

Define the unit before counting it

A session allocation needs an owner, compatible session type, quantity, source and applicable dates. One fifty-minute individual session is not an hour of consulting, a transferable employee seat or a credit for any other session type.

Define what the service includes around the conversation. Preparation, notes and a brief agreed follow-up may be part of delivering one unit. A client should not have to guess whether a listed session also promises unlimited written advice.

A credit is an entitlement record, not necessarily a separate payment. Two included credits from a recurring purchase may carry no individual cash price while remaining part of a paid service. Equally, a booking showing a list price or paid-at marker does not establish another captured payment.

Use a consistent unit in the client explanation and internal ledger. If an organization has a financial budget rather than individual session grants, keep that budget distinct until the actual named entitlements have been assigned through a suitable process.

Separate the three clocks

The billing clock determines when a payment is due. The allowance clock determines when a quantity of sessions becomes available. The validity clock determines the relevant deadline for an issued entitlement. They can align, but they are not interchangeable.

Two sessions per calendar month describes twenty-four sessions over twelve full calendar months. One session every two weeks describes twenty-six over a fifty-two-week planning year. Those service promises cannot be substituted casually.

A monthly allowance can also be anchored to the membership's start date rather than the first day of each calendar month. Explain the actual saved arrangement, including a start near the end of a month. Do not promise a calendar-month reset because the price says “monthly.”

Validity may be measured in elapsed days. Thirty-one days is not always one calendar month, and a deadline at 09:00 is not the end of that date. A precise client record prevents an argument based on two different interpretations of the same word.

Program scheduling adds another distinction. A Program's included sessions can be the authoritative allowance rather than an additional standalone credit deposit. Check the actual source before describing the balance.

Explain the lifecycle without counting a unit twice

An available unit can be reserved against a booking. A booked unit has not necessarily been attended or consumed under the relevant policy. A completed or late-cancelled appointment can have a different final credit result depending on the agreed settings.

Refunded, revoked, archived and paused records may require further distinctions. Build the reconciliation around the actual states in that account; a simplified four-column example is not a universal schema for every situation.

For a particular cohort of grants, the units should reconcile across mutually exclusive current states. When a unit moves from expired to available, it is the same unit in a new state. It does not become a second historical grant.

Keep the unit identifier and linked appointment visible. A correction should preserve what happened and why, rather than rewriting a completed appointment to make the totals look tidy.

Make carry and exceptions specific

“Sessions roll over” is incomplete. Define which unused units qualify, how many, the next deadline, whether further carry is possible and what happens to already booked appointments. Do not label every unconsumed credit eligible.

A policy allowing at most one eligible unit to carry uses the smaller of one and the eligible unused count. That formula still depends on the eligibility rules. A previously carried unit, a refunded purchase and a future reservation may need different treatment.

Separate a routine service policy from a corrective exception. A coach who cancelled a promised appointment should review the appropriate remedy rather than applying a generic forfeiture message. A client's ordinary nonuse and a provider's failure to supply a suitable opportunity are different facts.

For UK consumer contracts, the CMA's fair-contract guidance stresses clear, prominent terms and explains concerns about disproportionate cancellation charges and keeping prepayments. Its scope is trader-consumer relationships. Have the actual terms and remedies reviewed for your buyer and jurisdiction; the label “retainer” does not settle them.

Configure a service promise that the delivery process can support. A custom carry cap is not automatically a Coachful setting, and changing a credit's validity does not rewrite the subscription, refund money or create a new appointment.

The demonstration calendar illustrates appointments. It does not establish the fictional client's balance, attendance or source of entitlement.

Worked example: a cancelled appointment leaves one unused unit

All people, prices, dates, identifiers and outcomes in this example are fictional. Coach Ellis works with client Priya through a £600 monthly retainer containing two fifty-minute sessions and the defined preparation and brief follow-up for each.

The saved recurring Offer includes the actual fifty-minute standalone session type, quantity two and a monthly allowance. Billing also renews monthly. There is no Program included as a second session source.

The type's credit validity is thirty-one elapsed days from grant. The reviewed service terms explain that exact rule, the ordinary cancellation policy and a process for agreeing a remedy when the coach cannot deliver a scheduled session. No automatic carry cap or whole-subscription freeze is promised.

The first purchase and two actual credit grants are verified on 1 December 2029. Both credits' recorded grant time is 09:00 Europe/London, and their expiry is 1 January 2030 at 09:00 Europe/London. The dates align across this particular December; Ellis does not claim thirty-one days always matches the next monthly renewal.

Priya attends on 8 December using D-1. D-2 is reserved for 22 December. On 21 December, Ellis becomes unavailable and cancels the appointment. He checks that the actual cancellation released D-2 to available; he does not grant another credit on top.

No mutually suitable replacement fits before the existing deadline. Priya asks to discuss an early January replacement. Ellis confirms he will resolve the provider-caused disruption rather than treating the unused appointment as an additional sale.

Reconcile the record before correcting it

The 1 January renewal succeeds and its actual two new credits, J-1 and J-2, are verified. Their recorded grant time is 09:00 Europe/London and their thirty-one-day deadline is 1 February at 09:00 Europe/London. A successful billing record and the actual two grants are checked separately.

J-1 is booked for 19 January. J-2 remains available. D-2 has passed its old deadline and is expired; D-1 remains used. At the start of the 3 January review, the four historical grants reconcile as follows.

Four grants equal one used, one expired, one booked and one available. The system is not missing an entire January allowance. The specific unresolved issue is D-2 and the agreed remedy for its cancelled appointment.

Priya's message says she expected three January opportunities: the replacement and her two ordinary sessions. Ellis can now answer that expectation from identifiable units rather than guessing from a summary balance.

Complete the exception with an exact deadline

Ellis confirms that D-2 qualifies for the supported unused standalone-credit exception: it is expired, not booked or consumed, not Program-controlled and not refunded, revoked, archived or paused. The session type is still active and standalone.

In Clients > Priya > Sessions > Session credits, he opens D-2's menu and chooses Restore expired credit. At 10:00 Europe/London on 3 January, he confirms a new validity period of seven days.

The actual new endpoint is 10 January at 10:00 Europe/London, exclusive. The proposed replacement on 7 January is within that period. Ellis checks the restored record and its dated exception history before communicating completion.

Completed fictional client confirmation: “The unused December unit D-2 is available again, with a new deadline of 10 January at 10:00 Europe/London. This corrects the appointment I cancelled. It is the same unit, with no additional payment. Your January units J-1 and J-2 remain separate. If you agree, we can confirm 7 January, 11:00–11:50 Europe/London for the replacement.”

The restoration itself does not send that message, book the session, change the monthly charge or extend every resource. Ellis sends the confirmation separately and waits for Priya's choice.

Priya accepts. Before Ellis books, four grants now reconcile to one used, one booked and two available. After he confirms 7 January using D-2, they reconcile to one used, two booked and one available. The totals never become five.

He checks the actual appointment date, time, timezone, joining route and funding source. J-2 has not been used for the replacement, and J-1 remains linked to 19 January.

Count the work created by the exception

Ellis has a 270-minute January service allocation for Priya. This is a fictional capacity decision for the example, not a recommended caseload or margin target.

Each of the three January conversations requires ten minutes preparation, fifty minutes live and fifteen minutes notes and agreed follow-up: seventy-five minutes. Three units require 225 minutes. Fifteen minutes of separate scheduling and allowance administration brings the plan to 240, leaving thirty minutes unallocated.

The ordinary two-session month would require 150 minutes for those sessions plus fifteen administration, or 165. The replacement therefore creates a real extra delivery commitment this month even though it does not create a new sale.

Ellis checks that the early January time and whole-month workload fit before confirming it. If they did not, he would need to discuss an appropriate alternative remedy, not restore a credit that Priya had no practical opportunity to use.

This check also explains why broad unlimited carry promises can create problems. Several old units can become simultaneous commitments alongside the current allowance. Counting only the new month hides that work.

Verify the completed outcome and final ledger

The replacement session takes place on 7 January for fifty minutes. Priya uses it to prepare a bounded request to a colleague. Her chosen action is to send the request that afternoon, not to guarantee the colleague will accept it.

Ellis's preparation takes ten minutes and notes and follow-up take twenty rather than fifteen. That session therefore uses eighty working minutes. The two ordinary January sessions on 19 and 28 January each use the planned seventy-five.

Actual session work is eighty plus seventy-five plus seventy-five, or 230 minutes. With fifteen administration, January service work totals 245 against the 270-minute allocation, leaving twenty-five minutes unallocated. The extra five minutes is counted; it is not added as an unagreed charge.

Four granted units now equal four used, with none booked, available or expired in this four-unit cohort. The exception history still explains why D-2 was used after its original deadline. It has not been erased or counted as a third January grant.

The December and January payments remain £600 each, £1,200 in total. There is no add-on payment for the replacement and no implied refund. February's future allowance has not been borrowed.

Priya confirms that the corrected record matches the sessions delivered. That closes this operational discrepancy. It does not prove that every retainer client will use their allocation or that a scheduling exception resolves every service complaint.

Compare a different source before applying the same fix

Another fictional client receives calls through an included Program. The Offer uses Use the program's sessions, so that Program remains authoritative. Adding a separate recurring call allowance would create a different entitlement, not merely restate the same promise.

If the client needs a Program schedule adjustment, inspect that Program's actual workflow and terms. The unused standalone-credit restoration described above does not apply to Program-controlled credits.

Likewise, a company agreeing twelve sessions across three employees does not necessarily create a pooled wallet. Four units per named employee would reconcile separately. Six used, two booked and four available across the company totals twelve, but the four available units still belong to their actual owners.

A sponsor can receive the agreed allocation logistics without automatically receiving private coaching content. A budget holder's request is not permission to rewrite an employee's used session history or transfer an entitlement without checking the arrangement.

Measure use with a denominator that matches the question

Choose the question before reporting a utilization percentage. Sessions delivered during January and January-issued credits eventually used are different measures. A replacement from December can increase January delivery without becoming another January grant.

In the completed example, January contains three attended conversations but only two newly issued January units. Reporting “three of two credits used” as a January credit-consumption rate would mix delivery dates with source periods.

A useful operational note says: “January delivery: three sessions, including one replacement funded by the December unit. January grant cohort: two issued and two used by 29 January. December grant cohort: two issued and two ultimately used, including the recorded January exception.”

A December-end snapshot would still show only one of that month's two units used at that time. Keep its date instead of rewriting the old report after the replacement. A later cohort review can show the completed second use alongside the original snapshot.

These distinctions help inspect service access. Repeated unused units may reflect scheduling barriers, unclear instructions, changed needs or ordinary client choice. Ask about the actual obstacle before treating nonuse as a reason to sell more support or assume low commitment.

Even complete use is an operational measure. Four used credits do not establish that the client achieved four goals, received an appropriate remedy in every respect or benefited clinically. Keep service accounting separate from the client's own review of the coaching.

Keep pause decisions separate

When someone asks to pause, identify what they mean before changing anything. Billing, future allowance issuance, existing credits, appointments, Program scheduling and portal resources are six separate questions.

Record the confirmed effective dates and the supported actions needed for each. A future payment pause does not by itself establish that an already booked appointment moved or an unused credit's deadline froze.

Ask only for information necessary to decide the scheduling or service issue. An ordinary exception request does not automatically require a medical document or detailed personal narrative.

If the actual route cannot provide the promised combination, explain that before confirming the arrangement. A reviewable written decision is more useful than a general “everything is paused” message with contradictory records.

The demonstration Offers screen illustrates different services. It is not evidence of this fictional retainer's saved cadence, terms or payments.

Run the allocation workflow in Coachful

1. Read the saved purchase. Identify the owner, actual session type, quantity, allowance source, billing rhythm and validity. Separate descriptive benefits from configured fulfillment.
2. Confirm grants at the source. A monthly renewal and the actual corresponding units are different evidence. Longer billing rhythms with shorter allowances use a distinct supported top-up route; do not assume any invoice always grants another set.
3. Reconcile units and appointments. Compare identifiers, source periods, dates and current states. A booked unit is reserved; an actual paid event needs its own financial evidence.
4. Investigate the specific discrepancy. Inspect attendance, cancellation, expiry and access. Avoid a duplicate grant while the original unit is simply booked or eligible for correction.
5. Use an eligible correction only. Restore expired credit changes one eligible unused standalone unit from confirmation for the selected period. Check the new deadline and audit record; it does not change the whole purchase or notify the client.
6. Confirm the service outcome. Send the actual decision, agree and verify any replacement booking, then reconcile the completed attendance and remaining balance.

For the financial setup, read retainer billing setup. Explore Coachful's features for connected client and session records.

Troubleshoot the unresolved state

The client expected a calendar reset. Compare the actual membership anchor, allowance rhythm and issued deadlines. Correct misleading service wording rather than merely explaining the internal calculation.

The balance looks too high. Check whether the Program and a separate Offer allowance were both configured. Preserve legitimate existing commitments while investigating; do not delete records to force the desired total.

A cancelled appointment still holds a credit. Inspect the actual linked booking and cancellation result before issuing another unit. Cancellation, restoration and a cash refund are different outcomes.

Restore expired credit is unavailable. Check the actual eligibility: booked, used, Program-controlled and other excluded states cannot use that action. Investigate the relevant supported route instead of making a duplicate purchase history.

The client has valid credit but cannot reserve. Check session type, booking mode, availability and any type-wide booking limit. The type's reservation count is a separate control from this person's purchased balance.

Frequently asked questions

Does monthly billing always mean calendar-month sessions?

No. Read the actual allowance source and membership timing. The price label alone does not establish when credits are issued or when their validity ends.

Can I offer automatic rollover?

Define the intended rule and verify the supported delivery process first. A custom cap, eligibility formula and exception policy are not automatically native settings.

Does a booked credit count as used?

It can be reserved without being consumed. Check attendance and the actual cancellation-window policy, including the linked appointment, rather than relying on the calendar date.

Does restoring an expired unit charge or notify the client?

The supported exception restores the same eligible unused standalone credit with a new validity period. Payment, communication and a replacement booking remain separate actions.

Can I transfer unused corporate sessions freely?

Check the legal buyer, named owner, actual source and agreed permissions. An organization's unused budget does not itself establish a transferable native credit pool.