Start with the decision the report supports
A dashboard should help a school decide what to improve. Website traffic, enquiry counts and enrolments describe different parts of the journey. A report becomes less useful when it combines them without explaining the relationship.
GOV.UK’s service guidance treats measurement as part of understanding and improving a service. For a school, begin by agreeing the process questions your team needs answered, then define the events and data that can answer them.
Define five measures consistently
| Measure | Working definition to agree | Why it helps |
|---|---|---|
| Genuine enquiries | New relevant parent enquiries, with duplicates and test records handled consistently. | Understand demand. |
| Substantive response time | Elapsed time to a useful staff reply, with working-hour rules stated. | Review enquiry handling. |
| Confirmed visits | Visits with agreed arrangements, rather than submitted requests. | See booking progress. |
| Attended visits | Confirmed visits recorded as attended. | Review attendance and coordination. |
| Application progression | Movement through agreed stages, not just a clicked application link. | Understand what follows interest. |
These are proposed operational definitions, not a universal reporting standard. Agree whether a record represents a family, an enquiry, a child or a visit, and keep that unit visible.
Make denominators and timing explicit
A conversion rate needs a numerator, a denominator and a period or cohort. “Attended visits divided by confirmed visits” is interpretable only when both refer to a compatible set of visits.
A family may enquire in one month and visit in another. Comparing all of this month’s enquiries with all of this month’s applications does not necessarily describe the conversion of those enquiries. Use cohort views where the question requires them, and explain any reporting lag.
Keep reschedules, siblings and duplicate submissions visible in the rules. Otherwise activity may grow on paper while the number of families progressing stays the same.
Add context before drawing conclusions
Year-group capacity, seasonality, campaigns, entry requirements and intended start dates can affect results. A fully subscribed year group and one actively seeking pupils should not be judged by the same immediate objective.
Record changes to the website or follow-up process alongside the data. A change after a pilot does not by itself prove that the pilot caused it. Use an appropriate comparison and describe the limits of the evidence.
Turn the review into one action
Choose a reporting rhythm that the team can maintain. Discuss one meaningful issue, assign the next action and check whether it helped at the following review.
For a group, agree shared definitions while preserving local context. Start with one school before aggregating results. Do not create a performance league table from incomparable systems or inconsistent records.
Claims about financial return need a separately agreed model using school-supplied capacity, contribution and attribution assumptions. An enquiry count is not a revenue figure, and a booked visit is not an enrolled pupil.
Sources & scope
External guidance informs the relevant design principles. The school workflows, examples and review suggestions above are Abneos4Schools editorial recommendations, not validated conversion benchmarks or evidence of school results.
Start with your parent journey.
Take the self-reported assessment and get three practical priorities to explore with your team.
