VCE Extended Investigation common mistakes
VCE Extended Investigation · Understand the traps and how to avoid them.
Framing the research question as a broad topic ('social media and teenagers') rather than a sharply bounded, answerable question with named variables, population and context, then discovering mid-report that the evidence cannot settle it.
Students treat the question as a label for their interest area and draft it before reading enough literature to know what is measurable and what has already been settled; the school's early approval deadline also rewards submitting something quickly.
What to do instead
Draft the question after a scoping literature pass, then apply a self-check: can I name the independent and dependent variables (or the phenomenon and its boundaries), the population, the setting and the time frame? Write two or three alternative phrasings, test each against the evidence you already know exists, and get the final wording signed off before data collection begins.
Producing a literature review that is a sequence of source summaries ('Smith found X. Jones found Y. Lee found Z.') with no synthesis, no explicit gap, and no argument linking the gap to the chosen methodology.
Students equate reviewing with reporting, and paraphrase each source as they read it rather than grouping sources by theme or by disagreement; many have never been taught the difference between summary and synthesis.
What to do instead
Build a matrix of sources (author, method, sample, key finding, limitation) and write the review in themes, not sources: for each theme state what is agreed, what is contested, and what remains unexamined. End with one paragraph that names the specific gap and states exactly why your method addresses it.
Choosing a method because it is convenient (an online survey of whoever responds) rather than because it can answer the question, and then failing to justify the choice against alternatives.
Students default to surveys because they are familiar and low-effort, and they underestimate what a defensible methodological justification looks like; the report template's 'methodology' heading invites description rather than reasoning.
What to do instead
Write a short methods comparison before committing: list two or three candidate designs, state what each could and could not establish, and record why the chosen design wins for this question. Include a sentence in the report explicitly naming rejected alternatives and the reason for rejection.
Ignoring ethics beyond a signed form: collecting data from minors or vulnerable groups, storing identifiable responses on personal devices or shared drives, or failing to explain consent and withdrawal in language participants understand.
Students see ethics as a permission slip to be obtained rather than a design constraint, and school processes often reduce it to a single form; the risks of re-identification in small samples are rarely appreciated.
What to do instead
Write a data management plan alongside the ethics application: what is collected, where it is stored, who can access it, when it is destroyed, and how anonymity is protected in a small sample (for example, reporting only aggregate categories). Pilot the participant information statement on someone outside the study and check it is comprehensible.
Treating the methodology as something to be decided once and then reported as if it went to plan, hiding pilot changes, abandoned questions, equipment failures or recruitment shortfalls.
Students believe a report should present a clean, linear process and fear that admitting changes looks incompetent; the genre of the school report rewards confidence over candour.
What to do instead
Keep a dated research journal from the first week and log every decision with its reason. In the report, include a short 'changes to the design' subsection explaining what was altered, when, and what it means for interpretation; examiners reward justified adaptation, not a fiction of smooth execution.
Presenting data in tables or graphs that do not answer the question: percentages of tiny samples with no counts shown, graphs with unlabelled axes or truncated scales, or qualitative data reduced to a few unsupported generalisations.
Students choose the chart type by habit or by what the spreadsheet offers first, and they do not check whether the display supports the specific claim being made; small-sample percentages look more impressive than raw counts.
What to do instead
For each figure, write the one-sentence claim it is meant to support, then check the figure does exactly that. Always report raw counts alongside percentages, label axes and units, avoid truncated scales without flagging them, and for qualitative data use coded themes with representative quotations rather than impressionistic summary.
Discussing results as if they were conclusions: restating what the data show without interpreting what they mean, weighing them against the literature, or acknowledging alternative explanations and limitations.
Students conflate the results and discussion sections because the distinction was never modelled for them, and evaluating their own work feels like undermining it.
What to do instead
Use a strict separation: results state what was found; discussion states what it means. In the discussion, answer the research question directly, compare each key finding with at least one literature source, name two or three plausible alternative explanations, and state what the study cannot establish.
Overclaiming from a small, self-selected or convenience sample, using causal language ('this proves that X causes Y') for correlational or qualitative evidence, and generalising beyond the participants studied.
Students are invested in their findings and want them to matter; the language of proof is everywhere in popular science writing and is easy to absorb uncritically.
What to do instead
Adopt a hedging vocabulary and apply it deliberately: 'suggests', 'is consistent with', 'in this sample'. For every claim, ask what design would be needed to support the strong version, and state that limitation explicitly. Have a peer read the conclusion and flag any sentence that goes beyond the evidence.
Referencing that is decorative rather than functional: citations to sources not actually used to support a specific claim, missing or inconsistent in-text citations, a reference list that does not match the citations, and over-reliance on a handful of websites.
Students add references at the end to satisfy a requirement, often from memory or from a quick search, and are not taught that a citation is a claim about intellectual debt that must be verifiable.
What to do instead
Cite only where a specific sentence depends on a specific source, and build the reference list from the citations rather than the reverse. Use a reference manager or a single consistent style from the first draft, verify every entry against the source, and prioritise peer-reviewed or authoritative sources over general websites.
Treating the oral presentation as a spoken summary of the whole report, reading from a script or slides, running over time, and failing to explain the intellectual journey or respond substantively to questions.
Students prepare the presentation last, after the report is submitted, and reuse report prose; nerves push them toward a script, and they have not rehearsed timing or anticipated likely questions.
What to do instead
Design the presentation around a different question from the report: why this question, what was hard, what was found, what it means. Rehearse aloud to a strict time limit at least three times, reduce slides to prompts rather than text, and prepare by writing the five hardest questions an informed listener would ask and drafting answers to each.