You designed the perfect graded project. Now you have to mark it.

You've done the hard creative work. The graded project is designed, the brief reads well, it maps cleanly to your outcomes, and you can already picture students getting into it. For a moment, the job feels done.

Then you picture the other half: thirty or sixty submissions landing on your desk, each one needing a grade you can defend — to the student, to a colleague, to an external examiner. That half wasn't designed at all. It was going to happen "when you got to it."

Designing and grading are two different jobs

Building a graded project is a creative act: pick the scenario, set the constraints, decide what students actually have to do. Grading it is a different job entirely — deciding, in advance, what separates strong work from weak work, and holding that line the same way on submission one and submission sixty.

Most of us do the first job properly and improvise the second. We write the brief, run the project, and only think hard about criteria the night before marking starts. By then, the standard gets invented on the fly — generous on the first few, stricter by the end, different for every marker if more than one of you is grading.

The project doesn't grade itself — however good it is

A well-designed graded project doesn't come with fair grading built in. However sharp the brief, "good work" still has to be written down before anyone submits: which criteria count, what each achievement level actually looks like, and where the passing line sits. Skip that step and even the best project gets graded by feel — which means two students who did comparably good work can walk away with different marks, and neither of you can point at why.

That's not a flaw in the project. It's a second design job that got skipped, because the first one already took every spare hour you had.

What planning the grading actually looks like

Three things, decided before a single submission comes in:

• The criteria. Not generic labels like "Content" or "Quality" — the specific things this

project asks students to demonstrate. If the brief asks them to justify a decision under constraints, "quality of the reasoning" is a criterion; "presentation" probably isn't the one that should carry the most weight.

• What each level looks like. A short, concrete description of what "Excellent" versus

"Satisfactory" work actually contains — for this project, not as a general idea of good work.

• Where the line sits. Anchor the levels to your institution's own passing grade, so "pass"

means the same thing on submission one as on submission sixty.

Write those three things down and the grading stops living in your head — which is the only place it can drift.

Same design work, one more step

None of this is a criticism of how you design a graded project. It's a reminder that the project and the way it gets graded are two separate pieces of work, and only one of them usually gets planned in advance. That's the gap a rubric closes — not as an afterthought scribbled the night before marking, but as the other half of the design, decided at the same time as the brief.

That's also the gap Quindaria was built to close on both sides. You describe your course and choose the kind of project you want — Quindaria builds it, grounded in your outcomes. Then, for that same project, it builds the rubric: criteria drawn from what the project actually asks, the achievement levels you choose, anchored to your passing grade. The design and the grading, done together, in minutes.

Your course. Your style. Always aligned.

Next time you finish designing a graded project, don't leave the grading for later — build the rubric while the brief is still fresh, and grade submission sixty exactly like submission one.