How to Write Assignments That Don't Lose Marks

Here is an uncomfortable estimate worth testing against your own returned work: a meaningful share of the marks you have lost on assignments was not lost to ignorance. You knew the material. You lost the marks to a missed rubric row, an unexplained step, a figure nobody could read, or a file submitted in the wrong shape five minutes before midnight. This post is about collecting the marks that are already yours — the ones the presentation layer keeps confiscating.

Start from the rubric, not the topic

If the assignment ships with a rubric or marking scheme, that document is not decoration — it is the actual game. Graders work through it row by row, allocating marks per criterion. Your report should be structurally unable to lose a rubric row.

The conversion is mechanical: turn each row into a checklist item. A rubric row like “explains trade-offs between approaches (5 marks)” should map to a section or paragraph explicitly labelled in your structure. “Correct results (8 marks)” maps to a results section that makes the correct values impossible to miss — not buried mid-paragraph. When you finish writing, walk the rubric and point at the sentence or table that satisfies each row. If you have to squint, the grader will too.

No rubric provided? Then reverse-engineer expectations from the brief, past feedback, and how your instructor talks about strong submissions — or ask, which brings us to an earlier point than most people think: clarifying questions asked early are a normal part of the work, not an imposition.

Structure that reads in a hurry

Graders read many submissions in one sitting, often tired, often with a checklist. Write for that reader:

• Lead with the answer. State the result, conclusion or recommendation in the first lines of the relevant section, then show the working that backs it. Evidence after conclusion is far easier to verify than a suspense novel with numbers.
• Show your working at the decision points. You will not get credit for arithmetic the grader cannot follow; unexplained leaps read as guesses even when they are not.
• Label figures, tables and listings with numbers and captions that carry the message (“Figure 2: latency before and after the index change”), because a table without a caption is a riddle.
• State assumptions explicitly. One sentence — “assuming round-trip times exclude DNS lookup” — prevents entire follow-up deductions.

The presentation tax, and how to stop paying it

Keep a personal list of the logistics you have previously been dinged for. The usual suspects:

• Formatting inconsistency: mixing fonts, citation styles or date formats between sections.
• Code assignments: inconsistent naming, no comments at decision points, dead code left in, output screenshots that don't match the code version submitted.
• File naming and submission format: the instructions almost always specify a name and a format; the instruction is part of the assignment.
• The submit-early rule: for anything with a hard electronic deadline, submit a working version at least a few hours early, then update if time remains. This single habit converts “submission failed at 23:58” from a catastrophe into an inconvenience.

The overnight rule

A report finished at 2 a.m. feels identical to the author as a report finished at 8 p.m. It does not read identically to anyone else. Finish with a gap before the deadline — even one night — and use the gap for two passes:

1. Read it aloud. You are checking for two things only: does every sentence connect, and does every claim match the evidence above it. Reading aloud catches both; silent skimming catches neither.
2. Run the pre-submission checklist: rubric rows covered, all figures referenced in text, all referenced figures exist, name and identifier on the document, correct file format and name, submitted to the right place.

Integrity basics, briefly

Follow your course's rules on collaboration, sources, and any external help — including tools that generate text or code. Where sources are used, cite them properly; where you received explanations from classmates, the understanding should still be yours at assessment time. These rules exist in every course, they vary in detail, and the version that matters is always the one in your outline. Nothing else in this article compensates for getting this part wrong.

FAQ

How much do presentation marks actually matter?

Check the rubric: most schemes reserve some weight for structure, clarity, formatting or code quality. Even at five percent, it is among the cheapest marks on the table — it is the difference between demonstrating your work and making it guessable.

Should I write the report before or after doing the work?

Interleave. Outline the structure and the “what we will show” claims at the start; fill in results as they arrive; write conclusions last. Writes-ahead reports drift from what was actually done, and graders can smell the drift.

What is the fastest decompression trick for a done report?

The overnight gap plus a friend swap: you read their rubric and they read yours, each checking only the checklist items. Fifteen minutes of fresh eyes consistently finds what fifteen hours of the same eyes missed.

The takeaway

Assignments grade two separate things: your understanding, and your ability to hand it over legibly. The first takes studying; the second takes a rubric checklist, a structure that leads with answers, a tight submission ritual, and an overnight gap. All four are cheap, and together they recover marks you are already earning. If the next bottleneck is the term's collision weeks, the time management system is the companion piece; for organised practice material, see the study resources page.