SACE Stage 2 Information Processing and Publishing common mistakes
SACE Stage 2 Information Processing and Publishing · Understand the traps and how to avoid them.
Writing task responses as general prose about the topic instead of answering the specific instruction verb (explain, evaluate, justify, analyse) and linking to the stated audience and purpose.
Students revise content knowledge but not command terms, so they default to describing everything they know and never make the judgement or reasoning the marker is looking for.
What to do instead
Before writing, underline the command term and the audience/purpose in the prompt, then write a one-sentence plan that states the judgement or explanation you will deliver. Check at the end that the first and last sentences of the response actually perform the required verb.
Producing a design or document without a documented planning stage: no client brief restated, no audience profile, no annotated sketches, no justification of layout and colour choices.
Students see planning as paperwork and rush to the final product, forgetting that the design process and its documentation are assessed separately from the artefact itself.
What to do instead
Build a fixed planning checklist (brief, audience, purpose, constraints, two annotated layout options, justification of chosen option) and complete it before opening any software. Keep the planning pages in the submitted folio so the evidence exists.
Using generic statements about the audience such as 'it is for teenagers so it should be fun' rather than specifying measurable characteristics that drive concrete design decisions.
Audience analysis is taught as a heading to fill in, so students write a label instead of deriving implications for reading level, colour contrast, device, image choice and amount of text.
What to do instead
For each audience trait, write a paired sentence: trait, then the design decision it forces (for example, 'accessed mainly on phones, so body text will be at least 16px and single-column'). Every design choice in the folio should trace back to one of these pairs.
Treating evaluation as a description of what was made ('I used blue and added three images') instead of judging the product against the original brief, audience and purpose with evidence and suggested improvements.
Students conflate the design justification written earlier with evaluation, and they lack practice in collecting feedback or testing the product against criteria.
What to do instead
Restate the brief as three to five success criteria, then evaluate each one separately with evidence (feedback quotes, test results, comparison to the brief) and state a specific improvement for any criterion not fully met.
Submitting a polished final artefact with no evidence trail: drafts, versions, feedback received, and changes made are missing or undated.
Students work in one file and overwrite it, or complete the product at home without recording the iterative cycle that the school assessment is designed to reward.
What to do instead
Adopt a version-naming convention from day one (v01, v02 with date) and keep a short change log noting what feedback prompted each revision. Save screenshots of earlier states before major edits.
Answering extended-response questions on the external paper with unreferenced opinions about technology ('social media is bad for people') rather than explaining the underlying information-processing concept with a relevant example.
Topical issues invite moralising, and students do not practise converting a real-world example into the terminology and process steps the syllabus uses.
What to do instead
Structure each extended answer as concept, process or mechanism, then a specific example, then a consequence. Rehearse this with three current examples per topic area so the example is ready before the exam.
Confusing the stages and purposes of the data-information-knowledge distinction and of system development or project stages, giving definitions that overlap or are in the wrong order.
These terms are learned as vocabulary lists rather than as a sequence, so students can define each word in isolation but cannot place them correctly under exam pressure.
What to do instead
Draw the sequence from memory weekly and attach one concrete example to each stage. Practise questions that ask 'at which stage would X occur' rather than only 'define X'.
Ignoring the mark allocation and writing a single sentence for a five-mark question, or writing a page for a two-mark question and running out of time.
Students do not translate marks into expected depth, and they have not practised under timed conditions, so pacing collapses in the external paper.
What to do instead
Adopt a rule of one distinct, developed point per mark and a time budget of roughly one minute per mark. Do at least two full timed papers and mark your own script against the allocation before the exam.
Describing legal, ethical or security responsibilities in vague terms ('be careful with data', 'follow the law') without naming the obligation, who it protects, and what a organisation must actually do.
Students remember that the topic exists but not the specific principles, so they avoid detail for fear of being wrong and lose the marks for precision.
What to do instead
Build a one-page table of the relevant principles with three columns: obligation, whose rights are protected, and a concrete workplace action. Test yourself by writing a short scenario response for each row.
Producing technically working documents that fail basic publishing conventions: inconsistent heading hierarchy, no alignment grid, mismatched fonts, poor contrast, uncaptioned images, and no consideration of accessibility.
Students focus on software features and content and treat visual consistency as cosmetic, and they rarely view the product at final output size or on a second device.
What to do instead
Before submission, run a fixed quality check: view at 100 percent and in print preview, verify heading styles are applied consistently, check colour contrast, add alternative text and captions, and confirm every image and font choice is justified in the folio.