Engineering reports: what markers look for beyond the calculations

There is a belief that runs deep in engineering students: if the numbers are right, the report is right. Get the calculations correct and the mark follows. Then the marked report comes back with full marks on the working and a middling grade overall, and the belief takes a knock. The truth is that in most engineering rubrics, the calculations are only one criterion among several — and rarely the one where reports are won or lost.

Correct numbers are the entry ticket, not the prize

Getting the maths right is necessary. It is not sufficient. An engineering report is a professional communication, and the rubric marks it as one. Marks are awarded per criterion, which means a report with perfect calculations and a shapeless structure loses the structure marks no matter how clean the working is. The examiner is not only checking whether you can solve the problem; they are checking whether you can be trusted to report an engineering result to someone who will act on it.

What the rubric weighs beyond the working

Look past the calculation criterion and you will usually find three others carrying serious weight:

• Justification of assumptions:every real problem forces simplifications. The rubric rewards stating them explicitly and defending them — why this load case, why this safety factor, why this model — not silently baking them into the numbers.
• Structure and method: can the reader follow your reasoning from problem to solution? A logical progression, clear sections, and a method someone else could reproduce all carry marks.
• Communication: clear figures, correctly presented results, units and uncertainty handled properly, prose that a busy engineer could read once and trust.

These are the same conventions that govern technical writing generally — the parallels with science report marking are exact: method, results and interpretation each judged on their own terms.

Why assumptions are where good students lose marks

The highest-scoring reports are not the ones with the most impressive arithmetic. They are the ones that show judgement. Two students can reach the same answer; the one who justifies why the assumptions behind it are reasonable, and acknowledges where they might break down, demonstrates the engineering thinking the rubric is actually trying to measure.

An engineer is not paid to produce a number. They are paid to produce a number someone can act on — and the report is where that trust is earned or lost.

Unstated assumptions read as either luck or carelessness. Stated and defended, they read as competence. That single habit — making your reasoning visible — separates a middle-band report from a top one.

Mark the whole report, not just the maths

When you check your own draft, resist the pull toward the calculations. You already know if those are right. The marks you are leaving on the table are in the criteria you skim past: is every assumption justified, does the structure carry the reader, would the communication survive a sceptical reader?

That is where Mark's engineering report feedback earns its keep. Upload your rubric and your draft, and he returns a mark per criterion with the quoted line as evidence — so you see not just that the structure criterion is weak, but exactly where. If you're heading further into a degree, the same rubric-first habit carries into wider university assessment.

The loop is always the same: mark, fix the lowest criterion, re-mark. In engineering, that lowest criterion is almost never the arithmetic. It is the reasoning around it — and that is the part worth practising.