VCE VET ICT common mistakes
VCE VET ICT · Understand the traps and how to avoid them.
When a scored-assessment task asks for an explanation of how a unit-of-competency outcome was achieved, the candidate writes a narrative of what they did day by day ("first I logged in, then I opened the spreadsheet") without naming the performance criteria or the evidence that proved competence.
Candidates trained on project logs confuse a diary of activity with an argument for competence; they think describing effort demonstrates achievement, so they never connect their actions to the standard.
What to do instead
Before writing, list the two or three performance criteria the task targets, then for each write one sentence of the form: criterion, what I produced, and how it shows I met it. Delete any sentence that does not name a criterion or an artefact.
Candidates answer a scored-assessment question about a workplace or simulated scenario in general textbook terms ("organisations should back up data") instead of applying it to the particular client, constraints and job role given in the prompt.
Under time pressure, rehearsed generic content feels safer than interpreting an unfamiliar scenario, and candidates have often memorised definitions without practising transfer to a case.
What to do instead
Underline the scenario's specifics (client type, budget, existing system, user skill level) before answering, then force each paragraph to quote at least one of those specifics. If a sentence could apply to any organisation, rewrite it to name the scenario detail.
On questions requiring a work health and safety or legislative consideration in an ICT task, candidates list a hazard or law by name only, without stating the control, the responsible person, or the consequence of non-compliance.
Candidates treat compliance as a vocabulary test and recall the term (for example ergonomics or privacy principles) without learning the operational action that follows from it.
What to do instead
Practise a fixed three-part sentence for every compliance point: the requirement, the concrete control or procedure, and who is accountable. Mark any answer that stops after naming the requirement as incomplete.
Candidates describe the final product in a scored-assessment response but omit the testing, iteration or client feedback that changed it, presenting a clean linear process that never happened.
Students believe assessment rewards a polished success story and fear that admitting problems weakens their answer, so they sanitise the process and lose marks for missing evidence of evaluation.
What to do instead
Keep a running evidence log during the project recording each problem, the test performed, and the change made. In the response, include one worked example of a fault found and corrected, with the before-and-after evidence.
When a question asks candidates to select or justify an appropriate software tool or technology for a stated need, they recommend the tool they personally know best and justify it with preference ("it is easy to use") rather than criteria drawn from the need.
Personal familiarity is the only basis many candidates have for comparison, and they have not practised deriving selection criteria from a requirements statement.
What to do instead
Convert the stated need into three or four weighted criteria (cost, compatibility, scalability, support, user skill) before naming any product, then score the options against those criteria in a short table and let the table drive the recommendation.
In the scored assessment, candidates spend disproportionate time on one high-mark extended response and leave short-answer items blank or rushed, or they write far beyond the mark allocation for low-value questions.
Candidates judge importance by how interesting a question is rather than by marks per minute, and they have not rehearsed timing under exam conditions.
What to do instead
Before the assessment, compute a target time per mark (total minutes divided by total marks) and write it on the paper. In practice runs, use a timer and enforce a rule of moving on when a question exceeds its target time, returning only after all items are attempted.
Candidates answer a question that asks them to evaluate or recommend by describing what they did instead, so a response to "assess whether this approach met the client's needs" becomes a recount of steps with no judgement or criteria.
Command words are skimmed; students see a familiar topic and start writing the story they have rehearsed, missing that the verb changed from describe to evaluate.
What to do instead
Circle the command word in every question and write its demand in the margin (for example evaluate becomes strengths, weaknesses, criteria, verdict). Structure the answer to visibly contain each of those elements before any description.
Candidates use unexplained jargon and abbreviations from the ICT workplace (for example referring to a LAN, SLA or UAT) as if the assessor shares their context, and never define terms or link them to the scenario.
Immersed in workplace and classroom shorthand, students assume shared meaning and do not realise that unexplained terminology reads as vague rather than expert.
What to do instead
Adopt a rule of expanding every abbreviation on first use and adding a plain-language clause: term, expansion, and what it means here. Have a peer read the response and flag any term they cannot define from the text alone.
When interpreting a results report or feedback on their performance, candidates read only the overall score and ignore the criterion-level descriptors, so they repeat the same weakness in the next assessment task.
The single number is salient and emotionally decisive, while criterion descriptors are dense and require mapping feedback to specific skills, which students have not been taught to do.
What to do instead
After each result, build a three-column table: criterion, descriptor awarded, descriptor above. Choose the two criteria with the largest gap, write one concrete action for each, and check those two actions at the start of the next task.
Candidates treat the scored assessment as a memory test and reproduce definitions of concepts rather than demonstrating the applied problem-solving the assessment design rewards, so answers are accurate but shallow.
Past schooling rewards recall, and students have limited exposure to tasks that require transferring knowledge to an unfamiliar ICT problem under exam conditions.
What to do instead
Practise with unseen scenarios only: take a concept, invent a short client situation, and write an answer that applies the concept to that situation in under five minutes. Self-check that the answer contains a decision and a justification, not just a definition.