How the dashboard's indicators are calculated
This reference explains the rules behind the sensitive indicators on the Dashboard, so nothing is misread during financial and administrative reviews. To understand the dashboard's structure and tabs first, see Reading your school dashboard, and for the daily task lists and alerts see the Operations page.
Where do these indicators appear?
The path: Dashboard from the sidebar, then:
- Conversion funnel and Conversion & timing on the Registrations tab.
- Outstanding exposure on the Finance & delivery tab.
- Over-capacity and Operational alerts on the Operations page.
The Trainer follow-up percentages appear on their own screen in the Reports group, and their rules are in section 5.
1. The conversion funnel
The chart shows the funnel's stages in order: Submitted → Approved → Paid → Continuing → Completed, to identify the point at which a parent falls away from completing a registration or paying. The Conversion & timing card sums up the two main conversion stages in two figures:
- Approval rate: the proportion of requests the school approved out of all requests submitted.
approval rate = (approved requests ÷ submitted requests) × 100 - Payment rate: the proportion of requests fully paid out of all requests submitted, and the closest indicator to overall conversion.
payment rate = (paid requests ÷ submitted requests) × 100 - Cancelled and rejected registrations: Rejected and Cancelled — no payment requests stay in the denominator (all requests submitted), so they lower the rate and reflect the lost operational opportunity accurately.
The section also shows a Decisions (approve / reject) counter and the average time to approval and to payment.
2. The over-capacity state
- The definition: it occurs when the number of seats actually filled reaches or exceeds the activity's defined capacity.
excess = (approved/paid registrations) − the activity's capacity - The operational effect:
- Once capacity is reached or exceeded, a red warning flag appears, and the case is listed under Over-capacity and in the Operational alerts feed on the Operations page.
- Waiting list requests are not counted among over-capacity seats, because those people have not been accepted yet. To set the capacity, see Fees and capacity, and to manage those waiting see The waiting list.
3. Outstanding exposure
- The definition: the value of registrations the school has approved and not yet collected — that is, registrations still in the Awaiting payment status.
outstanding exposure = the sum of the fees of registrations in Awaiting payment - The ageing breakdown: the amounts are split into time bands by how long they have been outstanding — 0-2 days, 3-7 days, 8-14 days, 15+ days — to separate recent debts from stalled ones.
- What it means for a finance supervisor: it is the volume of suspended cash requiring collection follow-up before the payment window expires and the request is cancelled automatically.
4. Operational alerts
The Operational alerts feed on the Operations page classifies early-warning cases into categories, showing the most serious first. Below are the categories most closely tied to the indicators above:
| Category (as it appears on the board) | What triggers the alert | Suggested action |
|---|---|---|
| Capacity — over capacity | The seats filled have reached or exceeded the activity's capacity. | Raise the capacity, or move some students to an alternative activity. |
| Payment at risk | An approved request has passed the allotted payment window unpaid (and may be cancelled automatically). | Contact the customer, confirm the payment, or cancel to free the seat. |
| Data quality — an activity with no scheduled sessions | An activity with no weekly sessions defined. | Add the session times from Scheduling weekly sessions. |
| Data quality — an activity with no trainer assigned | An active activity with no trainer assigned to mark it. | Assign a trainer from Managing trainers. |
"An activity with no scheduled sessions" and "an activity with no trainer assigned" are not separate categories, but two examples of the Data quality flags that appear within the alerts feed. The feed also includes other categories such as Pending review, Unmarked attendance, Waitlist, and Refund backlog.
5. Trainer follow-up
The Trainer follow-up screen, in the Reports group, works out three percentages for every trainer in every week (Sunday to Saturday, Riyadh time), then derives their status from them. They are evidence only, and no amount of any kind is calculated from them.
| Aspect | Percentage | Upper threshold | Middle band | Below the lower threshold |
|---|---|---|---|---|
| Attendance | (children marked on time + half of those marked after the deadline) ÷ children registered in the judged sessions | 90% or more | 70% to under 90% | under 70% |
| Notes | children whose parents got a note in the week ÷ children expected | 80% or more | 50% to under 80% | under 50% |
| Plans | (plans sent on time + half of the late ones) ÷ plans expected, excluding Send time unknown | 75% or more | 40% to under 75% | under 40% |
- Judged sessions: the week's sessions that have registered children and whose marking deadline has passed, other than cancelled or excused sessions and the sessions of programs that use door check-in. The marking deadline is 12:00 noon on the working day after the session; Thursday, Friday and Saturday sessions are due by Sunday 12:00. Each child's first mark time is what counts, and a session counts as marked whoever marked it: the trainer, a substitute trainer or staff.
- Children expected a note: every child with a standing registration in the group (not on the waiting list) who was placed in it on at least one session day of the week. A note counts for them if it was shared with the parent within the same week, is still shared, and was written by one of the group's responsible trainers. An internal note does not count.
- Plans expected: one plan for every group that had children expected that week. Its deadline is 12:00 noon on the Sunday of its week, and its first send is what counts. Sent after the end of the week, a draft, and a withdrawn or blank plan are all Not sent.
- Who is responsible for a group: its trainers and the trainers of its main program, together, so the session, child or plan counts for each of them. If the trainers assigned to the group changed during the week, that week counts against no one in that group.
- Small sample: each aspect looks at the last 4 weeks up to the week shown. With fewer than 6 judged sessions for attendance, 20 expected notes for notes, or 3 expected plans for plans, that aspect shows Small sample, with no colour and no verdict.
- From the aspects to the status: the status is the worst of the known aspects: an aspect below the lower threshold makes it Not done; failing that, an aspect in the middle band makes it Partial; failing that, it is Committed. An aspect showing Small sample, or one that cannot be known, plays no part in this. If no known aspect is left and one of them shows Small sample, the status is Small sample. The meaning of every status is in Trainer follow-up.
- "—" is not zero: when a percentage has no denominator because nothing was expected, or the data are not enough to know the answer, "—" appears, not 0%.
- The note quality numbers (average words, repeated text, rating, tags and photos) are for information only, and are never part of any percentage or the status.
Frequently asked questions
Why is the payment rate always lower than the approval rate? Because the payment rate measures a later stage in the conversion funnel: every paid request was approved first, but not every approved request is paid. The gap between the two rates reveals how many requests are stuck after approval. See the Registrations tab in the dashboard.
What is the difference between outstanding exposure and revenue collected? Outstanding exposure is the fees of approved requests not yet paid (in the Awaiting payment status), while revenue collected is what has actually come in. You will find both on the Finance & delivery tab of the dashboard.
Where do I find the over-capacity alert, and what do I do about it? It appears in the Operational alerts feed and in the Over-capacity list on the Operations page. Deal with it either by raising the activity's capacity from Fees and capacity, or by moving some students to an alternative activity.
Do people on the waiting list raise the over-capacity figure? No. Waiting list requests are not counted among the filled seats, because those people have not been accepted yet, so they do not enter the excess calculation. For more, see Managing the waiting list.
Why did an approved request become "payment at risk"? Because it passed the allotted payment window unpaid, and may be cancelled automatically to free the seat for someone else. Follow it up from the Operational alerts feed on the Operations page, and confirm the payment or contact the guardian before the window closes.