Ready grading schemes
CBSE grading, state divisions, pass/fail, or your own scheme, configured once, applied everywhere.
05 · Marks go in once, correctly.
Marks and report cards stay tied to each academic year without exception.
Hear it from Syfty

Why it matters
Marks have a strange property: they get entered once, quickly, usually by a teacher juggling several sections, and then they're trusted for the rest of the year. Edsyft's marks grid is built for that reality. Every assessment is tagged as either counting toward the report card or staying internal practice, so a quick class test doesn't accidentally influence a term result. And a mark isn't just a number, absent counts as a zero the way it should, but excused and exempt are recorded as distinct states and left out of the calculation entirely, so a genuinely excused absence doesn't drag down an average the way a missed exam would.
When a subject teacher and a coordinator both work on the same section marks, every mark entry carries a version number, and a save states the version it expected to find. If someone else has already changed that row, the save is rejected outright and the affected rows are flagged for review, rather than one edit silently overwriting the other. Nothing gets lost to a race between two open tabs.
Publishing a report card is treated as a real event, not a formatting step. Once published, a card is frozen: marks, grades, and the template it used, exactly as they were at that moment, and its status only moves forward from provisional to published to, if genuinely necessary, retracted. If a mark that feeds a report card needs a genuine fix after publishing, that correction is captured against the specific mark it changes, with a reason attached. The record shows the old value, the new value, who made the change, and why, before the card is republished.
Grading itself doesn't assume every school runs the same way. Whether you use CBSE grading, state-board divisions, pass/fail, or a custom scheme, the grading logic is configured once and then simply applies, the same way, to every report card generated under it. Org leadership can see, across every campus at once, how many report cards are published and how many have been retracted, so a pattern of retractions at one school shows up long before it becomes a parent complaint.
What it handles
Every capability below maps to a real operating decision, handoff, or record inside the module.
CBSE grading, state divisions, pass/fail, or your own scheme, configured once, applied everywhere.
Absent counts as zero; excused and exempt are recorded but left out of the calculation entirely.
If two people edit the same marks sheet, the second save is rejected and flagged, not silently overwritten.
A published card locks its marks, grades, and template at that exact moment.
A genuine fix after publish records the old value, the new value, who changed it, and why.
See published and retracted report cards by school, and what still needs attention.
How it is controlled
Permissions, approvals, and state changes are part of the workflow itself, not instructions left for a staff meeting.
A marks save carries the version it expected. If someone else already changed that row, the save is rejected and flagged, not merged quietly.
Absent counts against the average the way it should. Excused and exempt are recorded but deliberately left out of the calculation.
Fixing a mark that already fed a published report card is a tracked action: old value, new value, who, and why, before the card is republished.
Value propositions
What changes for the team once this module is running in daily work.
What a parent sees the night of publishing is exactly what the school approved, and it says the same thing months later.
Subject and class-teacher mappings can be replaced mid-year without losing the record of who taught what, and when.
Set a grading scheme once, CBSE, state board, pass/fail, or custom, and every card generated under it applies it the same way.