The common complaint in student feedback is that the brief seemed clear until the work was due. The reason is usually that the brief described the task for the lecturer who wrote it rather than for the student who has to do it. This guide walks through the parts of a brief that prevent the midweek emails, the disputable marks and the resits.
Forge is Lectimax's project and practical module. It holds the brief, the rubric and the submission rules together. Students and markers read the same document. Forge keeps it consistent and reusable across terms, while the brief itself is yours to write and approve.
What learning outcome should the brief serve?
Open with one line on what the student must prove they can do. Make it the testable version: build, analyse, design or argue. The brief exists to test that skill, and every instruction that follows either supports it or gets cut.
The outcome line is the guardrail. A brief tied to a single outcome is easy to write and easy to defend. When the task is clear about the skill it tests, a student who meets that skill passes even if the format is imperfect. An appeal also has a standard to point at. Keep it to one outcome; a brief that claims to test three skills at once is a brief that tests none.
How do you give the deliverable and format up front?
Name exactly what the student hands in: the report, the prototype, the artefact or the code. Give the format requirements in the first section. Word counts, file types, referencing style and the submission method go here. There is no question at the deadline.
The format block is cheap to write and expensive to miss. When the deliverable and its format are the first thing a student reads, they plan around them. When the format lives in a later section, half the class builds the wrong artefact and the rest email to ask. State the deliverable in one line and the format as a short list, and both student and marker grade against the same contract.
Spell out the criteria and the weightings
The brief must mirror the rubric. List the criteria and the share of the mark each earns, so a student can see where the marks sit. If analysis is forty percent and presentation is ten, the brief says so and students allocate their effort accordingly.
The criteria block is where briefs usually go vague, and a vague criteria block is where appeals come from. A brief that says good work will be rewarded gives a student nothing to aim at and a marker nothing to defend. A brief that lists analysis forty, structure twenty five and method twenty five tells both parties where the effort belongs. Presentation ten sets where the remaining marks sit. Keep the criteria identical to the rubric you grade with, because a mismatch between brief and rubric is a resit waiting to happen.
Write the instructions the way a student reads them
Write each instruction as a concrete, observable action. "Explain why your method suits the problem" beats "show understanding of the method". Use short numbered steps and put the compulsory parts first.
The test is whether two students read the same instruction and produce work aimed at the same standard. An abstract instruction like "demonstrate critical thinking" produces as many interpretations as students. An observable one, such as "compare your result with the baseline and say where the difference comes from", produces work a marker can grade. Rewrite every instruction that does not name an action a student can check off.
Name the failure modes and the support
Tell students what does not get marks and where to find help. List the common mistakes: work that does not answer the question, formatting that ignores the file type, submissions past the deadline. Then point them to the real support, the consultation hours or the worked example.
A brief that names the traps is a brief students trust, because it shows the marker thought about where the work goes wrong. Add the support line as a real resource rather than a general offer, so help is a place a student can find. When the failure modes and the support sit side by side, fewer students discover a mistake after the deadline.
Keep the brief and the rubric together
A brief that lives apart from its rubric drifts, because the two get edited on different dates and stop matching. Keep the brief, the rubric and the submission rules in one place, so the document a student reads and the standard a marker applies are the same version.
This is the practical case for a brief tool. Forge holds the brief, the rubric and the submission settings as one reusable document. A revision updates the matching rubric. The same brief carries to next term with your changes. The module keeps the parts aligned; the brief is yours to draft and approve. Review the full Lectimax feature set.
FAQ
How long should an assessment brief be? Long enough to state the outcome, the deliverable, the criteria and the rules. No longer. Most briefs run to one or two pages once the format block and the criteria are listed.
Why do students email to ask what to do? Usually because the brief leaves the deliverable, the format or the criteria to a later section. When those are up front, the questions mostly disappear.
Can a brief be too standardised? A template is fine as long as the specific task and the specific criteria change for each assignment. The outcome and the rubric must match the actual brief.
Does a tool write my assessment brief for me? No. The task and the criteria are yours to write. A brief module holds the parts together so students and markers read the same document and it carries to next term.
Where to go next
The brief sets the standard the rubric then applies, so write the two together. See how to write a rubric for an assignment, or review Lectimax pricing and the full feature set.