A training program can serve many people over a year while needing fewer people active at once. Model when each group needs access before comparing proposals, then ask each provider to explain how its billing and reassignment rules apply to that pattern.
Map access over time
Build a calendar showing cohort start dates, expected practice windows and the overlap between groups. Include learners who need additional practice after the planned end date. Add established employees returning for refresher training, seasonal staff and people moving into a new role. Count trainers and administrators separately until you know how the provider treats them.
Keep distinct totals for people served during the year, people needing access in each period and people expected to use the tool during each billing period. These numbers answer different questions. A concurrent-access estimate does not establish your bill if the contract charges for named users or everyone active during a month.
Ask the provider to price the same model
Share the calendar and ask the provider to define its billing unit in writing. Clarify what activates a charge, whether an invitation counts, what happens when a learner returns and how reassignment works. Ask about minimum commitments, usage allowances, overages and the treatment of short seasonal peaks.
Check how access changes affect learning history and reporting. Do not assume that removing a license deletes a record, preserves it indefinitely or allows another person to inherit it. Ask which administrator and reviewer roles require payment, and request a proposal that separates recurring charges from setup or other services.
Use a cohort access worksheet
Create one row per group and period, then add a summary using the provider's actual charging definition. Avoid adding groups twice when a learner moves from onboarding into ongoing practice.
| Field | What to enter |
|---|---|
| Group and period | Onboarding cohort, refresher group or seasonal intake; access start and end dates. |
| Expected access | People requiring access, including overlaps and likely extensions. |
| Return pattern | When learners may need access again and whether their records must remain available. |
| Contract treatment | Written billing unit, reassignment conditions and any minimum or extra charge. |
| Planning cases | Expected demand, delayed completion and peak demand, priced using the same terms. |
A fictional example: overlapping onboarding groups
An imaginary support team starts a group of 20 learners every two weeks, with each group practicing for four weeks. At steady state, two groups overlap, giving 40 onboarding learners who need access. Ten established representatives also practice throughout the month. These are illustrative planning numbers, not customer usage or a recommended purchase quantity.
The administrator then models a delayed graduation: one group needs two additional weeks, creating an overlap with another intake. Separately, procurement calculates how many distinct people would be active within the provider's billing month. Depending on the contract, neither the peak access count nor the annual headcount alone may determine the charge.
Agree ownership before signing
Assign someone to reconcile the access calendar with the proposal and someone to maintain learner access during rollout. Keep written answers about reassignment, returning users and historical records with the commercial agreement. If a provider offers flexibility, confirm its exact conditions rather than relying on the word ‘flexible.’ Revisit the model when hiring or refresher plans change so that expansion decisions use the current program rather than last year's headcount.
