Use this guide as a working review for Harvard Referencing for Computer Science. Begin with “Know what needs a citation”, then move through “Record source details early” 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.
Know what needs a citation
A practical way to handle “Know what needs a citation” 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.
Keep the evidence proportionate to the marks. Screenshots, code excerpts, tables or references should prove something specific; they should not be added simply to make the report longer. If this stage changes the implementation, record what changed and why so the final reflection is based on evidence.
Record source details early
For “Record source details early”, 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 “Reference documentation carefully”.
Keep the evidence proportionate to the marks. Screenshots, code excerpts, tables or references should prove something specific; they should not be added simply to make the report longer. If this stage changes the implementation, record what changed and why so the final reflection is based on evidence.
Reference documentation carefully
For “Reference documentation carefully”, 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 “Separate evidence from your own analysis”.
Keep the evidence proportionate to the marks. Screenshots, code excerpts, tables or references should prove something specific; they should not be added simply to make the report longer. If this stage changes the implementation, record what changed and why so the final reflection is based on evidence.
Separate evidence from your own analysis
A practical way to handle “Separate evidence from your own analysis” 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.
Keep the evidence proportionate to the marks. Screenshots, code excerpts, tables or references should prove something specific; they should not be added simply to make the report longer. If this stage changes the implementation, record what changed and why so the final reflection is based on evidence.
Check consistency before submission
A practical way to handle “Check consistency before submission” 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.
Keep the evidence proportionate to the marks. Screenshots, code excerpts, tables or references should prove something specific; they should not be added simply to make the report longer. If this stage changes the implementation, record what changed and why so the final reflection is based on evidence.
Final check for Harvard Referencing for Computer Science
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.