Turn an assignment prompt into a rubric before you grade, pull the criteria from the brief, and then mark the whole pile to one consistent standard.
The assignment prompt you write already carries most of the rubric you need. If you pull its requirements into a rubric before you mark, you grade the whole pile to one standard and avoid rediscovering your expectations on script forty. This guide turns a prompt into a usable rubric in about thirty minutes.
Once that rubric exists, Lectimax's Gauge can apply it. Gauge is Lectimax's rubric grading module, and it scores each submission against a rubric you supply, so the standard stays the one you wrote. Gauge grades the work against your criteria. It does not scan for who wrote the work and does not police authorship, so the judgement about what a submission shows stays entirely with you.
Start with the learning outcome
Before listing any criteria, open with the outcome the prompt tests, not the activities. A brief that says write a fifteen hundred word essay on the nervous system is testing something, but it does not say what. The rubric needs the tested skill, such as tracing a pathway, evaluating a claim, or arguing a position. Write that skill down before you touch the submissions, because every criterion then hangs off it.
What does the prompt require?
With the outcome written down, go through the brief line by line and write out every requirement as its own row. A prompt that asks for an abstract, an argument, two sources and a reference list yields four rows. Name each row in a few words and add one line on what earns the level. Keep the list between five and seven rows, because every extra row adds a decision to every script.
The rows should mirror the brief closely enough that a student reading the rubric sees the same task they were set. If the prompt promises a weighting or a minimum number of sources, that belongs in a row too, because a rubric that quietly changes the deal invites appeals.
How do you turn vague verbs into observable ones?
Once the rows are in place, their verbs decide whether they work, and soft verbs make a row useless. A criterion that says demonstrates understanding cannot be applied the same way twice, so rewrite it around what appears on the page. Observable wording names the proof, for example states the mechanism in their own words and links it to the case study. That wording lets a second marker apply the same standard and lets a moderator see the basis for the mark. Where the prompt says critically discuss, decide what critical discussion looks like on the page and say it.
A simple test shows whether a descriptor is observable. Ask whether a stranger could apply it to the same script and reach the same level. If two people could land on different scores from the same paragraph, the descriptor is still vague.
Weight the rows by the outcome, not the length
When the descriptors are clear, the next job is to set a weighting that totals one hundred and follows the outcome. If the argument matters more than the formatting, the argument row carries the heavier weight, and that has to survive a neatly formatted report that says very little. Give the writing quality rows two or three levels instead of the full spread, because they decide less of the mark and exist mostly to keep the award defensible.
Try to give the row that carries the learning outcome about half the available marks, so a student who nails the skill cannot be beaten by a prettier submission that misses it. When the weighting fights the outcome, change the weighting and leave the outcome alone.
Test the rubric on two old scripts
With weights set, the draft is ready for a trial before you grade the batch. Run it over two submissions from an earlier term, or the first two that land. Where a descriptor does not fit, edit the descriptor instead of forcing the score. If you can, ask a colleague to grade the same two scripts and compare. Every place your scores differ is a vague cell, and you should fix it before it multiplies across the pile.
Grade the batch to one standard
After the test and any edits, the rubric is final and you can grade the pile against it. Because the standard is written and fixed, script twenty seven meets the same bar as script three. A student who appeals gets a mark that traces to a descriptor and not to a moment of judgement. When the rubric needs to change next term, you adjust the wording instead of rebuilding the system. See the full Lectimax feature set.
Share the rubric before they submit
The same rubric also helps students, but only if they see it early. Post the finished rubric the same day you brief the task, so the standard shapes the work and does not just judge it at the end. A student who can see that argument carries the marks writes a different essay from one who guesses.
FAQ
How long should this take? It takes around thirty minutes for a typical module brief, and less the second time because the outcome and most of the criteria carry over.
Do I need a separate rubric for every assignment? One per assignment, but they usually share the same outcomes. Reuse the outcome rows and change the task specific ones, which is where keeping the rubric stored pays for itself.
Does Gauge scan for AI written work? No. It scores each submission against the rubric you supply and leaves the question of authorship entirely to you. Gauge grades the work, not the writer.
You set the standard, and Gauge runs the repetitive pass. Coming off an older rubric tool, compare Lectimax as an iRubric alternative, then read how to grade a batch with an AI rubric grader. New accounts get 200 free credits (limited-time promo) to build their first rubric at Lectimax pricing.
- [[wiki/drafts/blog/burst/_index|burst drafts hub]]
- [[rubric-vs-points-grading]]
- [[moodle-questions-to-question-bank]]