Science school · 700 students · PK
Result cards built from the marks staff already entered
Examination setup, marks entry and result cards moved onto one workflow instead of a spreadsheet per teacher.
- One source
- Marks entry
- Generated
- Result cards
Set the examination, let staff enter marks against it, and generate result cards under your own grading scheme. No merge, and a correction does not mean starting again.
Book a demoEvery teacher keeps their own marks file. At term end somebody merges thirty of them, discovers two use different column orders, and rebuilds the sheet by hand.
Then a correction arrives. One mark changes, and the merge has to be redone, because the result cards were generated from a copy rather than from the marks.
When marks are entered against the examination itself, the result card reads from the same place. A correction flows through instead of restarting the week.
Grouped by the job it does rather than listed as one long set of features.
Terms, papers, maximum marks and weightings defined once for the whole institution rather than per teacher.
Paper scheduling that respects room and invigilator availability, published to students and families.
Staff enter marks for their own subjects in their own portal, against the examination the school configured.
Your own boundaries, GPA or percentage, with different schemes for different programmes if you need them.
Generated from the entered marks under your template, ready to print or publish, without a merge step.
Subject and overall remarks captured with the marks rather than written on the card afterwards.
Class and overall positions calculated rather than worked out on a separate sheet.
A student compared against their own previous terms, not just against the class.
Results visible in the family portal when the school chooses to release them.
The correction that arrives after printing. One mark was mis-keyed. If the cards were generated from a copied sheet, every downstream number - position, average, merit list - is now wrong too.
The student who missed a paper. Absent, medical, or sat a resit. A blank and a zero are very different things, and averaging them the same way is how a result card becomes indefensible.
The subject with a different weighting. A practical worth thirty per cent, a project worth twenty. Systems that assume every paper is equal force the calculation back into a spreadsheet.
The grade boundary that changed mid-year. The scheme was revised in January. Which boundary applies to the autumn term result, and can the system still produce the old card?
These are the cases worth testing in a demo. Bring the messiest one you have.
The same records, presented differently depending on the job.
Enter marks for their own subjects and see their own class performance. Not the whole cohort.
Configures the examination, publishes the datesheet, checks completeness and releases results.
See their own child's result when released, with the remarks that explain it.
Subject and class performance across the institution, without waiting for a compiled report.
The examination roll comes from the student record, so a student admitted in January is on it and one who left is not. Nobody maintains a separate candidate list.
Results attach to the student's history rather than to a term-specific file, so a transcript years later is a query rather than an archaeology project. Where a school ties examination eligibility to attendance or fee status, that check reads the same records.
The result card is a view of data the institution already holds, which is why a correction is a correction rather than a rebuild.
What changed when marks stopped living in thirty separate files.
Science school · 700 students · PK
Examination setup, marks entry and result cards moved onto one workflow instead of a spreadsheet per teacher.
The parts of the institution this touches most.
The weighted practical, the resit policy, the boundary that changed. Those are the parts worth testing before you commit.
Book a demo