Loading
Loading
Assessments
Clerks define mark-entry layouts. Course coordinators create named instances. Professors enter marks for their groups. Rubrics pull aggregates when the keys match.
Live today: Assessment Formats, CC instances, professor marks entry, and Rubrics Management bound by output keys.
The path on the live product, not a brochure funnel.
Format
The clerk sets kind, fields, aggregate rule, and output_key for a course or subject.
Instance
The course coordinator creates MST 1, Assignment 2, or a custom named assessment.
Marks
Professors open the instance from Classes and fill columns for their teaching group.
Aggregate
The engine applies best-of-N, mean, sum, or the rule on the format. No hand roll-up.
Rubric
Final report fields whose name matches the output_key autofill on the internal report.
Course default or subject override. Kind is MST, assignment, or custom. Each field needs a name, label, and max marks.
Set the aggregate rule and a stable output_key. Professors and coordinators do not design columns. They only create instances and enter marks.
Coordinators open Course Coordinator → Assessments, confirm a format exists, then create the instance name and kind.
Optional date, due date, file, or max marks appear only when the format enabled them. Teachers of that subject then enter marks from Classes.
From Classes → subject → Assessments, open Enter marks on the instance. Columns and max marks come from the format snapshot.
Save and re-open to correct marks while still allowed. Aggregates for the final report are computed from saved marks. You do not compute best-of-N by hand.
Assessment Formats define mark-entry columns. Rubrics Management defines internal report columns. They meet on output_key.
Bind rubric field names to the format key, and to instance keys when expose instances is on. Attendance-derived marks use their own key. Changing a key after marks exist breaks autofill until both sides match again.