Academic Performance Intelligence Hub
A school holding several years of results in mark sheets, spreadsheets, or an existing management system, and no way to see patterns across them.
The reality
A school holds several years of results in mark sheets, spreadsheets, or an existing management system, with no way to see patterns across them. Every question about performance, is this subject weaker than last year, is this cohort slipping, did the new scheme of work change anything, requires someone to compile an answer by hand.
Where it breaks
- Every performance question requires someone to compile an answer by hand, so the questions stop getting asked.
- Historical marks live across mark sheets, spreadsheets and whatever system came before, in formats that don't agree with each other.
- An average conceals a bimodal class: two groups of students moving in opposite directions look, on paper, like no movement at all.
- Board reporting gets assembled by hand each term instead of generated from a source everyone can see.
The Afivox approach
Afivox doesn't propose replacing how the school records marks. It starts from what already exists, mark sheets, spreadsheets, whatever system is already in use, and builds the layer that turns years of scattered records into one set of agreed definitions everyone can trust.
The system
Users
Head, proprietor, board, subject teachers (development-framed access)
Application
Ingestion, metric layer, subject/cohort/student views
Services
Comparison, reporting
Data
SourceImport, MetricDefinition → MetricVersion, MarkRecord, Report
Integrations
Existing mark records, spreadsheet, database or prior system
Security
Versioned metric definitions, full source traceability
How it flows
- Marks recorded
- Ingested
- Normalised
- Aggregated
- Compared
- Reported
Secure by design
- Metric definitions are versioned: changing one creates a new version rather than rewriting history, so a figure quoted last term still reconciles.
- Every aggregate traces back to its source records.
- Imported marks retain their source file reference.
- Teacher-attributed views, where they exist, are restricted to the head and framed for development, not ranking. A decision the school makes explicitly, never a default.
Designed to improve
- Visibility: the head can see how a subject is moving across terms without asking anyone to compile it.
- Early signal: a cohort's trajectory is visible while there's still time to act on it.
- Reporting speed: board reporting is generated, not assembled by hand each term.
Before
- A question about subject performance means someone compiling an answer by hand, so it stops getting asked.
- An average hides a class that's actually splitting into two groups moving in opposite directions.
- Board reporting gets assembled fresh each term from whatever data can be found.
After
- The head sees how a subject is moving across terms without asking anyone to compile it.
- A cohort's trajectory is visible while there's still time to act.
- Board reporting is generated from the same source everyone sees.
This is what we'd build. Yours will look a little different.
Every concept on this page changes once we sit with how your operation actually runs. Tell us what's different about yours.
Start the operations review