Calculate reward earners
- Without HP Source
- Copy exports into a formula-heavy tracker and manually investigate duplicates or missing fields.
- With HP Source
- Validate one import and apply the school’s saved, visible reward rules consistently.
Critical Developments · Product 05
HP Source
Make recognition timely, fair and visible.
House points, rewards and recognition.
The operational problem
Recognition should be more than a number with confetti.
House points can reward effort, animate collective life and ensure that good work is noticed. They can also become a formula-heavy spectacle whose rules are invisible and whose rewards arrive late, if at all. HP Source treats recognition as a chain of accountable acts: evidence, calculation, decision, follow-through and, only then, celebration.
-
01
House-point exports are rebuilt through private spreadsheet formulas.
Duplicates, missing rows, rule changes and corrections are difficult to trace.
Checked imports preserve source evidence while a visible, versioned policy derives scoring and reward results.
-
02
Pupil points and House Cup event bonuses are combined in one mutable total.
The published score cannot explain whether it came from pupil activity, an event or a correction.
Separate pupil-point and Cup ledgers reconcile into the official score without changing pupil totals.
-
03
A threshold is calculated but no person owns the reward.
Pupils appear on a list while recognition remains unissued.
Rewards Due records entitlement, owner, due date, issue state, notes and correction review.
-
04
A leaderboard becomes public by default.
Pupil names or sensitive cohort information travel beyond their legitimate audience.
Staff analysis, aggregate display and individually approved recognition are separate permission and publication decisions.
-
05
A presentation rebuilds the House race by hand.
Event order, corrected points or tied results can drift from the verified ledger.
Report, Showcase and Grand Finale read one frozen snapshot; reveal order may change the drama, never the result.
Capability map
The fuller programme.
HP Source covers the complete route from imported evidence to accountable recognition.
Verify and calculate
Roster and point intake
Checked CSV staging for dated points or a limited cumulative fallback, with preview, exception handling, commit and reversal.
Dated House membership
Pupil points remain associated with the House membership that applied when they were earned.
Versioned policy
Visible category, scoring and reward rules derive totals from immutable evidence; later policies do not rewrite frozen history.
Rankings and contribution views
Week, term and academic-year views across school, Year, House and form scopes with proper tied ranks and controlled access.
Turn scores into owned work
Rewards Due
Entitlements, owners, due and issued dates, overdue state, notes and correction review.
House Cup ledger
Reviewed event templates, complete placings, tied-award calculation, discretionary bonuses, reversals and season finalisation kept separate from pupil totals.
Recognition approval
A permitted publisher prepares a current rank-one item, uses a generic achievement label, obtains separate approval and can revoke publication.
Present and govern
Three presentation modes
Report for summary, Showcase for unattended display and presenter-controlled Grand Finale for a verified event-by-event reveal.
Grand Finale reconciliation
Frozen inputs, every eligible event exactly once, corrected transactions and sole or joint champion endplates that reproduce published standings.
Reports and archive
Score composition, movement, milestones, contributions, season history and historic champions with readable table alternatives.
Communications, integration and lifecycle
Scoped staff alerts behind delivery gates, read-only Wonde through the shared data contract, governed exports, retention and tenant exit.
This does not claim a live Wonde feed, enabled email delivery, deployed public display, school approval or certified outcome.
Working sequence
The result is frozen before the theatre begins.
Presentation can change the reveal order. It cannot change the evidence, the points or the champion.
-
01
Evidence
Checked imports and separately recorded House Cup events.
-
02
Policy
A visible version derives scores and reward thresholds.
-
03
Follow-through
Rewards Due gives each earned item an owner and state.
-
04
Snapshot
Corrections and ties are reconciled into one frozen result.
-
05
Celebration
Report, Showcase and Grand Finale all read that result.
Product roadmap
From the first task to accountable review.
-
01
Verify
Imports and policy
Check roster and point evidence, reconcile the source and apply visible, versioned scoring rules.
-
02
Act
Rankings and Rewards Due
Move from explainable rankings to owned reward queues, due dates, issue records and correction review.
-
03
Compete
House Cup
Keep pupil points separate from Cup events, templates, discretionary bonuses, reversals and tied places.
-
04
Recognise
Recognition and display
Publish approved aggregate snapshots and only deliberately approved individual recognition.
-
05
Understand
Reports and archive
Follow composition, movement, milestone progress and historic champions without rewriting past policy.
-
06
Connect
Communications and integrations
Add approved staff digests, reward alerts and read-only Wonde behind separate school and release gates.
How it differs
Compare the product boundary, not the gloss.
Official published descriptions checked 27 August 2026. Feature sets change; procurement requires direct verification with each vendor.
-
01
ePraise
ePraise foregrounds a broad engagement platform: praise points, badges, certificates, biographies, House leaderboards, shops, draws and more. HP Source is narrower, concentrating on verified point evidence, versioned scoring, owned Rewards Due work, a separately reconciled House Cup ledger and controlled recognition.
-
02
Class Charts
Class Charts foregrounds data-rich seating plans joined to rapid achievement and behaviour points and analytics. HP Source approaches the same point data from the other end: source verification, policy application, reward follow-through, House competition and frozen publication.
-
03
Arbor Behaviour Points
Arbor foregrounds recording points from the homepage, lesson dashboard, pupil profile or behaviour dashboard. HP Source does not replace MIS point recording. It accepts the minimum evidence needed to reconcile rankings, rewards and House scores.
- Best fit
- A school that already records points but needs one inspectable source for reward thresholds, House standings, corrections, follow-through and carefully governed celebration.
- Not intended to replace
- The MIS or classroom behaviour-entry system, safeguarding or pastoral casework, the school's decision about what deserves recognition, or the human act of actually giving the reward.
The practical difference
Where the work gets lighter.
The point is a shorter reward cycle, consistent thresholds and less staff time rebuilding rankings and notification lists.
- Faster reward cycles
- Consistent thresholds
- Timelier tutor recognition
Prepare group summaries
- Without HP Source
- Rebuild tutor-group and year-group rankings and charts for each reward cycle.
- With HP Source
- Generate the agreed staff views and small graphs from the same checked dataset.
Notify tutors
- Without HP Source
- Compile and send separate lists, then rely on informal follow-up to deliver rewards.
- With HP Source
- Notify the responsible tutor when a threshold is reached and retain a clear follow-up state.
Measure it properly. Any published time-saving figure will come from the same task measured before and during a school pilot.
Editorial perspective
The argument behind HP Source.
House points can reward effort, animate collective life and ensure that good work is noticed. They can also become a formula-heavy spectacle whose rules are invisible and whose rewards arrive late, if at all. HP Source treats recognition as a chain of accountable acts: evidence, calculation, decision, follow-through and, only then, celebration.
The spreadsheet is not the neutral option
Many reward systems begin reasonably enough. Points are exported, formulas are added, rankings appear and somebody promises to tidy the workbook before the next cycle. Over time, the spreadsheet becomes both calculator and constitution.
The problem is not that spreadsheets are wicked. It is that consequential rules become difficult to inspect. HP Source keeps imported values as evidence and makes the policy that interprets them visible and versioned.
Celebration is not made less joyful by being accurate. It is made less embarrassing later.
One number can hide several kinds of point
Pupil-earned points and House Cup bonuses may both contribute to a House race, but they are not the same record. HP Source keeps those ledgers separate, appends reversals rather than editing history and treats tied placings as ties.
These rules allow a score to remain explainable when the excitement has passed and somebody reasonably asks how it was produced.
Rank is not a theory of human worth
A leaderboard is a view of recorded points under a defined policy, not a moral inventory of pupils. Staff analysis and public display are separate. A ranking does not automatically authorise publication of a child's name.
Reaching a threshold can create an entitlement and an owned item in Rewards Due; it does not guarantee that the reward has actually been issued. Celebration that never reaches the pupil is just an impressive chart of unfinished work.
Drama without creative accounting
Grand Finale can reveal verified events in an order designed to preserve suspense. The boundary is simple: presentation order changes only the reveal. It does not change dates, results, points or the champion.
A tied final result remains a joint result; software does not invent a tie-break because a singular crest would look better on the last screen. The ceremony may build tension. The ledger must not.
Timely recognition needs an owner
Rewards Due identifies what has been earned, who owns the next step, when it is due, whether it has been issued and what requires correction. This prevents the product from claiming success at calculation while the human act of recognition remains stranded between an export and an inbox.
HP Source cannot decide what a school ought to praise. It can make the chosen rules inspectable, the evidence traceable, the follow-through owned and the celebration faithful to the result.
Security · UK GDPR
School data deserves more than a padlock icon.
Security and data protection are part of the product boundary. Certification, school approval and live use remain separate decisions.
Collect less
Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.
Control access
Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.
Protect and delete
Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.
Make procurement evidence available
Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.
School-facing boundary: the school will still need an appropriate lawful basis, privacy information, access policy, retention decisions and—where the risk requires it—a DPIA. The supplier’s job is to make those decisions informed, documented and technically enforceable.