Checked CSV intake
Load a defined house-point export, validate the expected columns and flag incomplete or duplicate rows before calculation.
Planned feature set
HP Source is planned as a configurable house-point and rewards workflow. Staff load a school export, administrators define the thresholds and rules, and the product turns the result into useful rankings, small visual summaries and timely tutor notifications.
Load a defined house-point export, validate the expected columns and flag incomplete or duplicate rows before calculation.
Let authorised administrators set thresholds, eligibility rules and reward cycles without burying the logic in a private spreadsheet formula.
Generate staff views of leading pupils, tutor groups and year groups alongside small, readable graphs of the current cycle.
Tell the relevant tutor when a pupil has reached a reward threshold, closing the gap between earning recognition and receiving it.
Why it earns a place
A product should do more than put a polished skin over the same institutional friction.
Thresholds and calculations remain visible to authorised administrators rather than hiding behind unexplained product logic.
The product does not stop at a chart; it identifies who needs to act so earned rewards are followed through.
Staff can examine individual achievement and collective patterns without maintaining separate tutor and year-group trackers.
Expected impact
The intended impact is a shorter reward cycle, more consistent application of agreed thresholds and less staff time spent rebuilding rankings and notification lists.
No invented stopwatch claims. Numeric time savings will be published only after pilot schools have established a baseline and measured the same task using the product.
Security · UK GDPR
These are requirements for the planned service, not a claim that an unfinished product is certified or that software makes a school automatically compliant.
Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.
Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.
Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.
Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.