One assessment workflow carries an assignment from brief to rubric to grade. Lectimax's Forge, Rubrica and Gauge share the same data, so a term stops having loose ends.
A course runs on a chain of small documents. The brief tells students what to build, and the rubric sets out how it will be judged. The grading pass turns both into a mark. When these three stay separate, the term is full of loose ends, so an assessment workflow connects them into one flow.
Most lecturers feel the friction where those documents meet. The brief mentions a focus that the rubric never names, and the marker reads both again before judging. One assessment workflow keeps the brief, the rubric and the grade reading from the same source, so the term stops pulling in three directions.
How do the brief, the rubric and grading connect?
The connection runs in a single direction, and the chain starts with the brief. This is the assignment the student reads, so it has to say what good looks like. The rubric translates that promise into criteria and bands. The grading pass then applies the rubric to the work. Each step reads the one before it, so none of them drift.
Lectimax runs the chain in three modules. Lectimax's Forge drafts the assessment brief. Rubrica turns the brief into a rubric, and Lectimax's Gauge walks the rubric through each submission. Because the three share one set of data, the document that students read is the document that markers use.
Why does the workflow matter for a whole term?
That shared source pays off most across a semester, more than in any single assignment. When the rubric has a home, every marker grades on the same standard. When the brief and the rubric line up, students stop asking what you meant. The flow removes the small questions that eat a teaching week.
The research on constructive alignment makes the same case. A course works when the assessment tests what the teaching set out to do. The brief, the rubric and the grade are the practical proof of that link, and they only prove it when they speak to each other.
The same link pays off in the quiet parts of the day. You notice fewer retyped marks, fewer 'which rubric did we use' messages and fewer late rereads of a brief to divine the intent. A lecturer who settles the workflow once stops deciding the same questions again every week.
Where does the rubric come from?
The rubric is where the link to the brief is easiest to see. A good rubric starts from the brief instead of a template. Read the assignment and list what you will reward. Turn that list into criteria, and give each criterion clear bands. The result is a rubric that a student can read before they start and a marker can apply without guessing.
Building the rubric this way keeps the two documents honest. A brief that promises originality gets a rubric band for original thinking, and a brief that asks for analysis gets a criteria row for it. When they match, the grade defends itself.
One practical tip keeps the rubric sharp. Write the bands from the student's side, so each level describes work a reader can recognise on sight. Vague bands produce vague marks, and clear bands produce defensible ones.
How does grading stay consistent across a cohort?
Once the bands are clear, the sticky moment is marking many submissions on one rubric. Two scripts can earn the same band and feel nothing alike. The fix is to apply the criteria one band at a time and let the stated standard settle the decision, with the first impression playing no part.
Gauge supports this by arranging the cohort in one grading view, with the rubric beside each script. You judge against the stated bands, and the mark comes from the bands you choose. The consistent part is the standard, and the judgement stays human. This is grading based on a rubric, where the machine organises the work and the lecturer owns the mark.
How does the workflow protect the mark?
Consistent marking also makes each mark easier to defend. When a student asks why a grade sits where it does, you can point at the brief and the rubric together. The brief set the task, the rubric named the standard, and the grading applied it. The chain answers the question without a scramble.
That chain also shortens the conversations that follow. A mark that the rubric explains does not need a long justification, and a brief that the rubric follows does not need a fresh guess. The record of the term is the record of the standard.
The same discipline carries forward into the next term. The brief sets the task and the standard stays firm, so a new cohort gets the same fair start. The workflow leaves the full work of teaching in place, and it makes that work add up to something you can defend.
FAQ
What is an assessment workflow? It is the chain that carries an assignment from brief to rubric to grade, with each step reading from the same source.
Why does the brief matter so much? The brief sets the task students follow. When it names what good looks like, the rubric and the grade can defend the mark.
Where does the rubric come from? From the brief. List what you will reward, turn that list into criteria, and give each criterion clear bands.
Does the machine grade the essays? The machine organises the work and sets out the rubric. You choose the bands, so the judgement stays yours.
How do I keep marking consistent? Apply the rubric band by band across the whole cohort, and let the stated criteria settle the mark.
Where to go next
Meet Forge where the brief takes shape, see Rubrica for the rubric, and watch Gauge carry it through grading. The three modules are the workflow in action.