How research works, what makes a source good, Harvard referencing, lean writing, plagiarism and ethical AI use
Instructor: Teboho Mpholo (Mr.), Founder and Lead Instructor
The single most useful idea in this document is this: research is a conversation that has been going on for decades, and your job is to join it, not to restart it. Every field already contains people who have asked your question, disagreed with each other, built on each other's work and left gaps. A research report is your contribution to that conversation: here is what is known, here is where the accounts disagree, here is the gap, here is what I did about it, here is what it means.
This reframes everything. A literature review is not a list of summaries. It is a map of who says what, where they disagree, what the evidence supports, and where you stand. A citation is not decoration; it is a pointer to the person you are responding to. When you understand this, referencing stops feeling like a chore and starts feeling like the mechanism of the whole enterprise.
| Stage | What happens | What you produce |
|---|---|---|
| 1. Question | A problem is identified, narrowed and made answerable | A research question or hypothesis |
| 2. Literature | Read what is known, find the disagreement and the gap | A literature review |
| 3. Method | Decide how the question can be answered and what would count as evidence | A method section, or a design |
| 4. Data | Collect measurements, observations, cases, artefacts, survey responses | A dataset |
| 5. Analysis | Apply the analysis method and interpret what the numbers or evidence mean | Results and discussion |
| 6. Claim | State what you conclude and how confident you are | A conclusion with hedged, defensible claims |
| 7. Peer review | Independent experts check method and claims before publication | Reviewer comments, revisions |
| 8. Publication | Work enters the record and can be cited | A paper, standard, report or thesis |
| 9. Critique and replication | Others test, extend or dispute it | New papers citing, confirming or refuting yours |
Two things follow from this cycle. First, published work is not automatically true; it is the best current candidate that survived scrutiny. Second, a single paper is never the whole story. This is why a good report cites several sources agreeing or disagreeing, and not one paper that happens to support the conclusion you wanted.
| Type | What it is | STEM examples | When to use it |
|---|---|---|---|
| Primary | Original work, first-hand data, the thing itself | A randomised trial, a measurement dataset, the IEEE standard text, the source code, the lab notebook, a patent, a census file | Whenever you can. Strongest evidence for a specific claim. |
| Secondary | Analysis, summary or interpretation of primary work | A review article, a textbook, a systematic review, a technical white paper summarising research | To orient yourself quickly, and to cite a synthesis of many studies. |
| Tertiary | Compiled reference material | Encyclopaedias, dictionaries, Wikipedia, handbooks of constants | To learn vocabulary and find primary sources. Rarely cited directly in STEM. |
Peer review means that independent experts in the field assessed the work before publication. It filters obvious errors, methodological weaknesses and unsupported claims. It does not guarantee that the findings are correct, that the statistics are sound, that the code works, or that the authors have no conflicts of interest. Retractions of peer-reviewed papers happen every year. Peer review raises the base rate of quality; it does not certify truth.
This is why you evaluate sources yourself (Part 2) rather than assuming that the word "journal" settles it. It also explains why preprints exist and why you must flag them: a preprint has not been peer reviewed, so it is a claim, not a finding.
Most STEM papers follow IMRaD: Introduction, Methods, Results, and Discussion. Knowing the structure changes how you read. The abstract tells you what the paper claims. The introduction tells you what gap it addresses. The methods tell you whether you should believe the results. The results are the data, not the interpretation. The discussion is where the authors interpret, admit limitations and say what should come next.
A literature review answers four questions. What is agreed? What is disputed? What is missing? Where does my work sit? Organise by theme or debate, never by source. A review that says "Smith found X. Jones found Y. Patel found Z." is a list. A review that says "The field agrees that X holds under condition A, but Smith and Jones disagree on condition B, and neither addresses small deployments, which is the gap this report fills" is a review.
| Weak organisation | Strong organisation |
|---|---|
| Author by author, in order of publication | Theme by theme, with authors grouped by position |
| Describes each source | Compares and contrasts sources |
| No gap identified | A clear gap that the study addresses |
| No judgement | Evidence weighed, quality assessed, contradictions surfaced |
Every time you read something useful, capture five things in your notes immediately: the full citation, the page number, the exact claim or quote, your own one-line comment on why it matters, and the tag that links it to a theme in your outline. If you capture the citation at the moment of reading, the reference list writes itself. If you do not, you will spend the last night hunting for a page number and will be tempted to guess, which is how fabricated references happen.
Not all sources are equal. In STEM the rough hierarchy, strongest to weakest, is:
| Rank | Source type | Notes |
|---|---|---|
| 1 | Systematic reviews and meta-analyses | Synthesise many studies; strongest for "what does the evidence say overall" |
| 2 | Peer-reviewed journal articles and top-tier conference papers | The backbone of a STEM literature review |
| 3 | Standards (IEEE, ISO, IEC, TIA, NIST) | Authoritative for specifications, protocols, measurement and compliance |
| 4 | Government and institutional reports, official statistics | Authoritative for policy, national data, regulations |
| 5 | Industry white papers from reputable vendors | Useful for engineering detail and market context; commercially motivated, say so |
| 6 | Textbooks and edited handbooks | Good for established theory; slower to reflect new work |
| 7 | Vendor documentation and release notes | Correct for what a product does; not evidence about the field |
| 8 | Reputable technical websites and magazines | Useful for orientation; cite sparingly |
| 9 | News articles | Use only for the fact that something happened, never for the science |
| 10 | Blogs, forums, Wikipedia, AI chatbots | Not citable as evidence in academic work. Use to orient, then cite the primary source they point to. |
Before you cite anything, ask six questions. If a source fails two or more, find another.
| Question | What to check | Red flag |
|---|---|---|
| 1. Who wrote it? | Named authors, institutional affiliation, relevant expertise | No author, no affiliation, or an author with no traceable record |
| 2. Where was it published? | Recognised journal, conference, standards body, government department | Unknown publisher, journal with an implausibly broad scope |
| 3. Is it current? | Publication date appropriate to the type (Part 3) | Latest data from a decade ago presented as current |
| 4. Is it peer reviewed? | Stated on the journal site, or the paper is clearly a preprint | Preprint presented as if peer reviewed |
| 5. Is it supported? | Claims backed by data, method described, references given | Bold claims, no method, no data, no references |
| 6. Why does it exist? | Academic, regulatory, or commercial purpose stated | Vendor material presented as neutral evidence |
Predatory journals charge a publication fee and provide no real peer review. They exist because publication is a currency in academia. Citing one is not automatically misconduct, but it weakens your evidence and a marker who knows the field will notice.
| Warning sign | What you see |
|---|---|
| Implausible speed | Acceptance within days, including for a full experimental paper |
| Flattery by email | Unsolicited invitations to submit, addressed to "Dear esteemed researcher" |
| No real editorial board | Board page missing, or names listed without consent |
| Fake or meaningless metrics | "Impact factor" from an organisation you cannot verify |
| Scope too broad | A journal covering "all engineering and science" |
| No retraction policy | No visible ethics, corrections or retraction page |
| Fees before review | Payment demanded before peer review |
| Tool | Best for | Note |
|---|---|---|
| Google Scholar | Broad first pass, citation chaining | Use "Cited by" to move forwards and the reference list to move backwards |
| IEEE Xplore | Electrical, electronic and computing engineering | Standards and conference proceedings are here |
| ACM Digital Library | Computing and information systems | Strong for systems and HCI |
| ScienceDirect, SpringerLink, Wiley | Broad science and engineering | Many articles behind a paywall; check your library access |
| Scopus, Web of Science | Systematic searching, citation metrics | Best for a defensible literature search |
| arXiv, SSRN | Preprints, very recent work | Not peer reviewed. Always say "preprint" when you cite one. |
| ISO, IEEE, IEC, NIST, TIA | Standards and guidelines | The authoritative source for specifications |
| National statistics offices, World Bank, ITU | Official data | The only acceptable source for national statistics |
An old source is not automatically a bad source. Age is a signal, not a verdict. What matters is whether the claim you are using it for is still valid. A 1948 paper by Shannon is still the correct source for information theory. A 2015 paper on the throughput of 802.11ac is now superseded for current design decisions but still valid as a historical benchmark. The question is always: has this claim been superseded, and does my reader need the current version?
| Source type | Typical acceptable age | Why |
|---|---|---|
| Seminal or foundational work | Any age | It is the origin of the idea; you cite it because it is the origin, not because it is current |
| Standards (IEEE, ISO, IEC) | Cite the edition in force; check for amendments | The year is part of the identity. A superseded standard is a wrong citation. |
| Method or algorithm | Usually within 5 years for fast-moving fields; older if still the accepted method | If a newer method dominates, using the old one needs justification |
| Textbooks | Latest edition preferred; older edition acceptable if you cite that edition and say so | New editions correct errors and add developments |
| Technology performance figures | 2 to 5 years, often less | Capabilities change quickly; a 2016 figure for Wi-Fi 6 is impossible because the standard did not exist |
| Statistics and market data | The latest release only | Superseded statistics are a factual error |
| Government policy and regulation | Cite the version currently in force | Policy changes; an old version misstates the law |
| Review articles | 5 to 10 years, depending on the field's pace | Reviews age faster than the primary work they summarise |
| Conference papers | Field dependent; computing moves fast, civil engineering slowly | Judge by whether the finding is still the state of the art |
Many journals and examiners use a rule of thumb: in a literature review, a substantial proportion of your sources should be recent, often at least half within the last five years. This is not a law; it is a signal that you have engaged with the current frontier and not just with whatever came up first in a search. A report whose newest source is from 2016, submitted in 2026, reads as though you stopped reading halfway. A report whose sources are all from last year reads as though you do not know where the ideas came from.
| Situation | Why it is a mistake | What to do |
|---|---|---|
| Citing a superseded standard | The specification has changed; your design may be wrong | Check the standards body for the current edition and any amendments |
| Presenting old statistics as current | Factually wrong at submission | Use the latest release, and state the reference year |
| Describing a technology using a pre-standard source | The final standard may differ from the draft | Cite the final standard |
| Using an old method when a better one is standard | Your results are not comparable with current work | Use the current method, or justify the older one explicitly |
| Citing an old paper for a claim that has since been retracted or overturned | The claim is no longer supported | Check for retraction and for later refutations before citing |
The opposite failure is equally common and less often noticed. If every source is from the last two years, you have read the surface of the field and not its foundations. You will not know why the current method exists, what it replaced, or what problem it was invented to solve. You will also be more likely to repeat a mistake the field already corrected ten years ago. Foundational sources earn their place in a reference list.
Referencing does four jobs. It credits the person whose work you used. It allows verification, so a reader can check whether you have represented the source fairly. It shows the evidence base for your claims. And it separates your contribution from everyone else's, which is the foundation of academic integrity. A reference list is not a formality; it is the audit trail of your argument.
| Half | Where it goes | What it does |
|---|---|---|
| In-text citation | At the point in your sentence where the claim is made | Points the reader to the full entry in the reference list |
| Reference list | At the end, alphabetical by author surname | Gives the full details needed to find the source |
| Situation | In-text form | Example |
|---|---|---|
| Paraphrase, one author | (Surname, year) | Length is a stronger defence than complexity (NIST, 2017). |
| Author as subject | Surname (year) argues | NIST (2017) recommends against forced periodic password changes. |
| Direct quotation | (Surname, year, p. x) | Wi-Fi 6 "splits each channel into resource units" (IEEE, 2021, p. 43). |
| Two authors | (Surname and Surname, year) | (Smith and Jones, 2020) |
| Three or more authors | (First author et al., year) | (Smith et al., 2020) |
| Corporate author | (Organisation, year) | (World Health Organization, 2024) |
| No date | (Surname, no date) | (Smith, no date) |
| Several sources, one claim | Separated by semicolons, alphabetical | (Jones, 2021; NIST, 2017; Smith, 2020) |
| Source quoted in another source | (Original, year, cited in Secondary, year) | (Shannon, 1948, cited in Stallings, 2020) |
| Same author, same year, two works | Add a, b, c | (Smith, 2020a) and (Smith, 2020b) |
Harvard has no single international authority; institutions publish their own variants. The examples below follow the Cite Them Right pattern, which most universities use. Check your module handbook and follow it exactly, because consistency with the required style is part of the mark.
Tanenbaum, A.S. and Bos, H. (2015) Modern operating systems. 4th ed.
Boston: Pearson.
Smith, J. (2020) 'Routing in dense networks', in Jones, A. (ed.)
Wireless networking handbook. London: Springer, pp. 45-67.
Smith, J. and Patel, R. (2021) 'Throughput analysis of 802.11ax in
dense deployments', IEEE Transactions on Wireless Communications,
20(4), pp. 1234-1248. doi: 10.1109/TWC.2021.1234567.
Smith, J. (2022) 'A comparison of Wi-Fi 6 and Wi-Fi 5 in campus
networks', Proceedings of the IEEE International Conference on
Communications, Rome, May. pp. 88-95.
IEEE (2021) IEEE standard for information technology: wireless LAN
medium access control and physical layer specifications, amendment 1.
IEEE Std 802.11ax-2021. New York: IEEE.
NIST (2017) Digital identity guidelines: authentication and lifecycle
management. NIST Special Publication 800-63B. Gaithersburg:
National Institute of Standards and Technology.
Cisco (2023) Wi-Fi 6 and Wi-Fi 6E: technical white paper. Available at:
https://www.cisco.com/example (Accessed: 12 October 2026).
Smith, J. (2020) Performance of dense wireless networks in urban
campuses. PhD thesis. Botho University.
Statistics Botswana (2024) Population and housing census 2022.
Available at: https://www.statsbots.org.bw (Accessed: 12 October 2026).
Canonical (2024) Ubuntu 24.04 LTS [computer program]. Available at:
https://ubuntu.com (Accessed: 12 October 2026).
| Rule | Why it matters |
|---|---|
| Alphabetical by author surname, then by year | Readers scan by author; a random order is unusable |
| Hanging indent on every entry | Visual clarity; also what most style guides require |
| Italics for book and journal titles, plain for article titles | Distinguishes the container from the item inside it |
| Page ranges use pp. | Consistent formatting is part of the mark |
| DOI where one exists | The DOI is permanent; a URL may rot |
| Accessed date for anything online | Web content changes; the date proves what you saw |
| Same style throughout | Mixed styles read as carelessness |
Use a reference manager: Zotero, Mendeley or EndNote. Install the browser connector, and capture the citation the moment you read the source. The manager stores the metadata, formats the reference in Harvard and inserts in-text citations into your word processor. This removes the two failure modes that cost students most marks: a reference list that does not match the citations, and a page number guessed at midnight. A reference manager does not do the intellectual work, but it removes the clerical errors that hide good work.
Academic writing is not complicated writing. It is precise writing. The goal is that a competent reader in your field understands your claim on the first read, and can check it. Complexity that does not add precision is a defect, not a virtue. The best technical writing is plain, short and specific.
It is important to note that in the context of the deployment of wireless networking infrastructure within an institutional environment, a considerable number of factors must be taken into consideration with regard to the optimisation of performance outcomes.
Campus wireless performance depends on three factors: access point density, channel planning and client behaviour.
The second version is shorter, names the three factors, and makes a checkable claim. The first version says nothing a reader can use.
| Rule | Why | Example |
|---|---|---|
| Average 15 to 25 words per sentence | Longer sentences lose the reader before the verb arrives | Split at "and", "which" and "because" if the sentence exceeds 30 words |
| One idea per sentence | Two ideas in one sentence produce ambiguity about which is the claim | "The AP failed, so the building lost coverage" beats "The AP, which had been installed three years earlier and was due for replacement, failed and caused coverage loss in the building." |
| Active voice by default | Names the actor and shortens the sentence | "The sweep marks expired permits" not "Expired permits are marked by the sweep" |
| Passive only when the actor is unknown or irrelevant | Passive hides responsibility and adds words | "The cable was cut during construction" is correct passive; "It has been decided" is evasion |
| Cut nominalisations | Verbs turned into nouns add words and lose force | "We analysed" not "We conducted an analysis of" |
| Define acronyms at first use | Not every reader shares your shorthand | "Wireless local area network (WLAN)" then "WLAN" thereafter |
| Hedge claims to match evidence | Overclaiming is the most common credibility failure in STEM | "The results suggest" and "is consistent with", not "proves" unless it does |
| Use units and significant figures consistently | Precision is part of the claim | 940 Mbps, 0.4 ms, 99.9 percent, not "very fast" |
A paragraph is one unit of argument. It has four parts, usually in this order:
| Part | Function | Example opening |
|---|---|---|
| Topic sentence | States the claim the paragraph will support | "Sixteen gigabytes is the correct RAM choice for the workstation build." |
| Evidence | Gives the reason, data or source | "The working set of Windows 11, a browser and Office exceeds 8 GB in normal use (Microsoft, 2024)." |
| Analysis | Explains what the evidence means for your claim | "Once physical memory is exhausted the OS pages to disk, which is felt as slowness." |
| Link | Connects to the next paragraph or back to the question | "The cost is small against a year-two rebuild, which is why the BOM carries 16 GB." |
Four to eight sentences is a typical lean paragraph. One sentence is not a paragraph in academic writing (except occasionally for emphasis). Twelve sentences is usually two paragraphs that have not been separated.
Cohesion is what stops a report reading as a list of disconnected observations. Three techniques do most of the work. Signposting: tell the reader where you are going ("This section evaluates the hardware; the next section evaluates the software"). Repetition of key terms: in technical writing, repeating the exact term is better than elegant variation, because variation introduces ambiguity. Transitions used sparingly: "however", "therefore" and "in contrast" earn their place when they mark a real logical turn, and become noise when used in every paragraph.
| Section | What it does | Common failure |
|---|---|---|
| Abstract | States problem, method, result, conclusion in 150 to 250 words | Written first, before the results are known |
| Introduction | Context, problem, gap, aim, structure | Too much general background, no gap |
| Literature review | Maps the conversation and locates the gap | Author-by-author summary, no synthesis |
| Method | What you did, in enough detail to repeat it | Missing parameters, no justification for choices |
| Results | The data, presented, not interpreted | Interpretation mixed into results |
| Discussion | What the results mean, limitations, implications | Repeating the results without interpreting |
| Conclusion | What you conclude and what should happen next | Introducing new material |
| References | The audit trail | Mismatch with in-text citations |
| Appendices | Supporting material too long for the body | Hiding the main evidence in an appendix |
Every table and figure must have a number, a caption, a source line if it is not yours, and a sentence in the body that refers to it ("Table 3 shows that..."). A table that is never mentioned in the text is decoration. A table that duplicates the text word for word wastes space. The rule is: present the numbers in the table, interpret them in the text, and never do both jobs twice.
| Pass | What you look for |
|---|---|
| 1. Structure | Does each section do its job? Is the gap clear? Does the conclusion answer the introduction? |
| 2. Paragraph | Does each paragraph have one claim? Is the topic sentence first? Is there a link? |
| 3. Sentence | Any sentence over 30 words? Any two ideas in one sentence? Any passive that hides the actor? |
| 4. Word | Any nominalisation? Any filler ("it is important to note")? Any unhedged overclaim? |
| 5. Citation | Does every claim of fact have a source? Does every citation appear in the list? |
| 6. Consistency | Units, spelling variant, terminology, tense, figure numbering |
Plagiarism is presenting someone else's work, words or ideas as your own. It does not require intent. Copying a paragraph and forgetting the citation is plagiarism whether or not you meant it. The offence is that the reader is misled about the origin of the work.
| Type | What it looks like | Why students do it |
|---|---|---|
| Verbatim | Copying text word for word without quotation marks and citation | Time pressure; believing that changing a few words is enough |
| Mosaic or patchwork | Stitching together phrases from several sources, with citation but no real paraphrase | Confusing "referenced" with "rewritten" |
| Inadequate paraphrase | Synonym swapping while keeping the sentence structure | Not knowing what paraphrasing actually is |
| Uncited idea | Using someone's argument or finding without a citation | Believing that ideas are free if you did not copy the words |
| Self-plagiarism | Reusing your own earlier submitted work without disclosure | Not knowing that prior submission counts |
| Collusion | Working with others when the task is individual, or sharing your work | Believing collaboration is always allowed |
| Contract cheating | Paying someone, or a service, to produce the work | Time pressure; desperation |
| Fabrication | Inventing data, results or references | The most serious category; often AI-assisted |
| Technique | What it is | When to use it |
|---|---|---|
| Paraphrase | Restate the idea in your own words and sentence structure, with a citation | Most of the time. This is the default. |
| Quote | Use the exact words in quotation marks, with page number | When the exact wording matters: a definition, a legal clause, a standard's precise requirement |
| Summarise | Condense a longer passage into its main claim, with a citation | When you need the conclusion of a long argument or a whole paper |
Common knowledge is a fact that a reader in your field would accept without checking a source. It does not need a citation. In STEM, "water boils at 100 degrees Celsius at sea level" is common knowledge; "Wi-Fi 6 was standardised as 802.11ax in 2021" is arguably common knowledge in a computing report but should be cited in a general report; "this campus has 800 staff" is a fact about a specific case and needs a source. When in doubt, cite. Over-citing is a mild weakness; under-citing is misconduct.
Turnitin compares your text against a large database: published journal and book content, web pages, and previously submitted student papers. It reports a similarity score and highlights the matching strings. It does not decide whether you plagiarised. It flags matches for a human to review. This distinction is essential.
| Turnitin does | Turnitin does not |
|---|---|
| Find strings of words that match its database | Understand the meaning of your text |
| Report a percentage of matched text | Decide whether a match is plagiarism |
| Show which sources match and where | Detect a well-paraphrased copy of an idea with no matching words |
| Exclude quotes and references if configured to do so | Guarantee that your work is original |
| Score | What it might mean | What to do |
|---|---|---|
| High (say 40 percent) | Could be a correctly quoted and referenced block from a standard, or a copied essay | Read the report. If the matches are in quotes with citations, it may be fine. If they are in your own prose, rewrite. |
| Moderate (say 15 percent) | Could be a few common phrases, standard terminology, or a copied paragraph | Check each match. Standard phrases and references are usually excluded. |
| Low (say 3 percent) | Could be clean work, or a copied paragraph from a source not in the database | Do not treat a low score as proof of originality. Turnitin only knows what it has seen. |
Reusing your own earlier assignment in a new module without disclosure is self-plagiarism. It is not always wrong to build on earlier work, but it must be disclosed: "This section draws on my earlier report for module X" with a citation. The offence is the concealment, not the reuse.
Collaboration is working together to understand material. Collusion is producing submitted work together when the task is individual. If the brief says individual, discussing ideas is usually fine, but sharing text, code or files is not. When in doubt, ask the lecturer before you share, not after.
The useful question is not "did you use AI?" but "what did you use it for, and can you defend what you submitted?" There is a real difference between using an AI tool to understand a concept and using it to produce the work you submit. The first is closer to using a textbook or a tutor. The second is closer to submitting someone else's work, and is what most academic integrity policies prohibit when they ban AI tools.
| Task | Typical position | What to do |
|---|---|---|
| Asking an AI to explain a concept you do not understand | Usually acceptable | Then verify against a textbook or paper, and cite the source you verified, not the chatbot |
| Using AI to suggest search terms or a reading list | Usually acceptable | Find and read the actual sources |
| Using AI to check grammar or clarity in your own text | Often acceptable, check the handbook | Keep your own wording; do not accept rewrites that change your meaning |
| Using AI to debug code you wrote | Often acceptable, check the handbook | You must be able to explain the fix |
| Asking AI to write your submitted prose | Usually prohibited | Write it yourself |
| Asking AI to generate code you submit | Usually prohibited unless the brief allows it | If allowed, disclose and be able to explain every line |
| Asking AI for references | Dangerous | AI tools fabricate plausible references. Never cite a source you have not opened. |
| Using AI when the brief explicitly bans it | Prohibited | Do not use it, even for planning |
Large language models generate text that looks like a reference. Author names, journal titles, years, volumes and DOIs can all be invented and all look real. A fabricated reference is academic misconduct even when it was produced by accident, because the reader is misled about evidence that does not exist. This is the single most damaging AI failure in academic work, and it happens constantly.
If your institution allows any AI use, it will usually require disclosure: what tool, for what task, and how you verified the output. A short statement in an appendix is enough. Disclosure is not a confession; it is part of the integrity record, and it protects you if a marker notices AI-like phrasing in your work. Undisclosed use is what turns a permitted use into misconduct.
AI detectors are unreliable in both directions. They produce false positives (flagging human writing, especially from non-native speakers, as AI) and false negatives (missing AI-generated text). Passing a detector is not evidence of integrity, and failing one is not proof of misconduct. Do not build a strategy around beating a detector. Build a strategy around being able to defend every sentence in a viva.
Imagine a marker asking you to explain any sentence in your submission, justify any design choice, and modify any part of your code. If you can, the work is yours in the sense that matters. If you cannot, no detector result will save you, because the marker does not need a detector to notice that you cannot explain your own report.
The reason institutions restrict AI is not suspicion for its own sake. The skills you are being assessed on, reading, synthesising, arguing, designing, debugging, are built by doing them. If AI does the doing, you do not build the skill. The students who get the most out of AI use it as a tutor and a sparring partner, not as a ghostwriter. Ask it to explain a concept, to quiz you, to point out weaknesses in an argument you wrote, to suggest what you might have missed. Then do the work yourself.
| Use it for | Do not use it for |
|---|---|
| Explaining concepts you then verify in a textbook or paper | Producing any submitted sentence |
| Generating practice questions and flashcards | Generating references |
| Critiquing your own draft ("what is weak in this argument?") | Rewriting your draft so that it is no longer your voice |
| Suggesting search terms you then use in a real database | Summarising a paper you have not read |
| Debugging code you wrote, with an explanation you understand | Writing code you cannot explain line by line |
| Checking grammar on your own text | Using it at all when the brief bans it |
| Term | Meaning |
|---|---|
| Abstract | A short summary of a paper's problem, method, result and conclusion |
| Citation | A pointer in the text to a source, usually author and year |
| Common knowledge | A fact a reader in the field would accept without checking; no citation needed |
| DOI | Digital Object Identifier, a permanent identifier for a publication |
| Grey literature | Material not published through commercial academic channels: reports, white papers, theses, standards |
| Harvard style | An author-date referencing system; variants exist, check your handbook |
| IMRaD | Introduction, Methods, Results, Discussion, the standard structure of a STEM paper |
| In-text citation | The short reference inside the body of the text |
| Literature review | A synthesis of existing work that maps the field and identifies a gap |
| Paraphrase | Restating an idea in your own words and structure, with a citation |
| Peer review | Independent expert assessment before publication |
| Plagiarism | Presenting someone else's work, words or ideas as your own |
| Preprint | A paper shared before peer review; must be flagged as such |
| Primary source | Original work or first-hand data |
| Reference list | The full details of every cited source, at the end of the document |
| Secondary source | Work that interprets or summarises primary sources |
| Self-plagiarism | Reusing your own earlier submitted work without disclosure |
| Similarity score | The percentage of text Turnitin matches against its database; not a verdict |
| Tertiary source | Compiled reference material such as encyclopaedias |
Answer these without looking back. If you cannot, reread the relevant part.