Use this guide as a working review for Computer Science Technical Report Guide. Begin with “Build the report around the marking criteria”, then move through “Explain decisions rather than narrating clicks” and the remaining stages against your own brief. The aim is to leave a clear trail from the requirement to the technical evidence and final explanation, rather than relying on a generic submission checklist.
Build the report around the marking criteria
A practical way to handle “Build the report around the marking criteria” is to create a small, inspectable output first. Compare it with the rubric, record any dependency or source you relied on, and only then expand the work. This prevents the final report from becoming disconnected from the actual technical process.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Explain decisions rather than narrating clicks
For “Explain decisions rather than narrating clicks”, work directly from the wording of your own assessment. Note the exact action verbs, required files and marking signals that relate to this stage. Then decide what concrete evidence will demonstrate completion before moving on to “Use figures as evidence”.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Use figures as evidence
Treat “Use figures as evidence” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “Connect tests to requirements” much easier to justify.
Use a reader-first check: could someone who did not build the project understand the requirement, the action you took and the evidence that supports the outcome? If not, add the missing context now rather than trying to reconstruct it at the end of the assignment.
Connect tests to requirements
For “Connect tests to requirements”, work directly from the wording of your own assessment. Note the exact action verbs, required files and marking signals that relate to this stage. Then decide what concrete evidence will demonstrate completion before moving on to “Write an evaluative conclusion”.
Use a reader-first check: could someone who did not build the project understand the requirement, the action you took and the evidence that supports the outcome? If not, add the missing context now rather than trying to reconstruct it at the end of the assignment.
Write an evaluative conclusion
Treat “Write an evaluative conclusion” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “Build the report around the marking criteria” much easier to justify.
Use a reader-first check: could someone who did not build the project understand the requirement, the action you took and the evidence that supports the outcome? If not, add the missing context now rather than trying to reconstruct it at the end of the assignment.
Final check for Computer Science Technical Report Guide
Return to the first section, compare the finished work with each rubric row and verify that every important claim is supported by code, a test, a result, a source or a clearly reasoned explanation. Remove evidence that does not help the reader understand or assess the work.