How sessions are counted

A session is one ten-minute practice conversation. Any run of a minute or longer costs one session. A run under a minute is a misfire and costs nothing.

Everything in Evolve Sim is priced and counted in sessions. A session is one ten-minute practice conversation with scored feedback.

What one run costs

• A run that lasts under one minute is treated as a misfire. The learner never got going, a tab was closed, or a microphone failed. It costs nothing.
• Any run of one minute or longer costs exactly one session. It does not matter whether the conversation ran for three minutes or the full ten.

There is no per-minute charging and no half session. Ending a run early with End sim still costs one session if you had passed the one-minute mark, and the run is scored as it stands.

Rehearsing your own sim inside the builder with Save and try is free. It never debits a session.

Whose sessions a run uses

For a signed-in learner, the run is paid from the first of these that applies.

1. The assignment's own session quota, if the sim was assigned to you with one.
2. Your team's allocation.
3. Your organisation's pool.
4. Your own balance, for an individual with a Learner Pass or Creator Seat.

A run from a workshop link or an embed is paid by the person who created the link, from their team, organisation or personal balance in that order. The participant never pays.

Where to see your balance

Your remaining sessions show in three places.

• Sessions left on Sessions & Billing.
• The Sessions balance card in the sidebar (labelled Organisation sessions or Team sessions for admins).
• The top bar of the portal.

If you are a team member on an organisation allocation, the billing page is called My Sessions and shows your usage without a way to buy more. Your admin tops you up.

The ledger

Session ledger on the billing page lists every credit and debit on your account in sessions. A purchase, an allocation from your admin, a charged run and a refund each appear as a line.

You will sometimes see a balance with a decimal, such as 4.5 sessions. That happens when an admin allocates a quota that is not a whole number of sessions. Only whole sessions can be spent, so 4.5 sessions funds four runs.