VCE VET Creative and Digital Media common mistakes
VCE VET Creative and Digital Media · Understand the traps and how to avoid them.
Submitting a design or media product without ever testing it on the intended audience or in the intended context (e.g., a poster never checked at print size, a video never played on a phone), then claiming it meets the brief.
Candidates treat the brief as a checklist of features to build rather than a problem to solve, and run out of time before any evaluation, so they never discover legibility, sync, or usability problems.
What to do instead
Build a short test step into the production schedule: show the draft to at least two people outside the class or view it in the real delivery format, record what they noticed or missed, and list one change made as a result in the evaluation section.
Describing the process as a straight line ('I researched, then designed, then made it') and omitting the rejected drafts, client feedback, and revisions that actually occurred.
Candidates think a clean narrative reads as more competent, and they discard evidence of earlier versions rather than keeping dated screenshots or files.
What to do instead
Keep every version with dates and a one-line note on why it changed; in the folio, present at least two rejected options with the reason each was dropped, framed as decisions rather than failures.
Treating copyright and intellectual property casually: using a found image, song, or font without checking its licence, or crediting a source only in the reference list rather than clearing permission.
School projects often tolerate borrowed assets, so candidates carry the habit into assessed work and confuse 'publicly available online' with 'free to use'.
What to do instead
For every asset, record source, licence type, and permission status in an asset register before it enters the project; where a licence is unclear, replace the asset with one under a known licence and note the substitution.
Answering a client or audience brief with a personal-preference design, then justifying it with 'it looks better' or 'I like these colours' instead of evidence tied to the stated purpose and audience.
Candidates default to their own taste because it is fast and confident, and they have not converted the brief's audience description into testable criteria.
What to do instead
Rewrite the brief as three to five measurable criteria (e.g., readable at two metres, understandable without sound, recognisable as the brand) and justify each design choice against one of them.
Producing a file that fails at delivery: wrong resolution or colour mode for print, wrong aspect ratio or codec for screen, missing fonts, unlinked assets, or audio levels that clip.
Candidates work only inside the editing application preview and never export to the final specification, so embedded-versus-linked files, bleed, and loudness problems stay invisible.
What to do instead
Before submission, export the real deliverable and open it on a different machine or device; check the technical specification sheet (dimensions, resolution, colour space, codec, loudness) item by item and tick each one.
Leaving safety and legal compliance to the end: no risk assessment for a shoot, no talent release or consent form for people filmed, no consideration of work health and safety around equipment and cables.
Candidates see paperwork as administrative busywork unrelated to creative quality, and they underestimate how often assessment criteria reward documented planning.
What to do instead
Complete a one-page risk assessment and consent forms at the planning stage, before any camera or equipment is booked, and file them with the production schedule so they are dated before the shoot.
Writing a reflective evaluation that recounts what was done ('first I made a storyboard, then I filmed') without judging quality, identifying weaknesses, or stating what would change next time.
Description is easier and safer than judgement, and candidates fear that admitting flaws will cost marks.
What to do instead
Structure the evaluation as strengths, weaknesses, evidence, and next steps; every weakness must name a specific moment in the product and a concrete alternative approach, not a general aspiration.
Misreading the question's command word - describing where analysis is required, listing where comparison is required, or ignoring a stated constraint such as word count, audience, or format.
Under time pressure candidates skim the stem for familiar keywords and answer the topic they revised rather than the task actually set.
What to do instead
Underline the command word and every constraint before writing, then check the finished answer against each underlined element; if the task says 'compare', ensure both items and an explicit judgement appear.
Using industry terminology loosely or interchangeably - calling any visual 'composition', any planning document a 'storyboard', or confusing resolution with file size - in both written answers and folio annotations.
Candidates absorb vocabulary from tutorials and peers without checking precise meanings, and examiners reward accurate use of terms in context.
What to do instead
Maintain a personal glossary of 20 to 30 core terms with a one-sentence definition and a real example from the candidate's own project, and review it before the exam and before folio submission.
Managing time and files poorly: no production schedule, work left to the final sessions, and files saved with names like 'final2new', so versions cannot be identified or recovered when something breaks.
Candidates underestimate production time and rely on memory to track versions, which collapses when a file corrupts or a deadline moves.
What to do instead
Create a dated schedule with milestones and buffer, and adopt a naming convention (project, version number, date) with a backup copy in a second location updated at the end of every session.