SACE Stage 2 Business Innovation common mistakes
SACE Stage 2 Business Innovation · Understand the traps and how to avoid them.
Writing a business report that describes what a chosen enterprise does instead of analysing the problem, evaluating options and recommending a justified course of action.
Students treat the report task as a research assignment and summarise background material they have collected, because description feels safe and analysis risks being wrong.
What to do instead
Before writing, draft a one-line problem statement and a decision statement ('The business should... because...'). Allocate roughly one third of the word count to the problem and its evidence, one third to evaluating at least two options against stated criteria, and one third to the recommendation, implementation steps and risks. Delete any sentence that only reports a fact without linking it to the decision.
Citing evidence without naming the source, date or business function it relates to, so data appears invented or generic.
Students gather figures from a case study or simulated business but compress them into vague claims such as 'sales have fallen recently' to save words.
What to do instead
Build an evidence table before drafting: for each claim record the figure, its source (case study, survey, financial statement), the date and the business area. Insert the strongest three or four figures directly into the problem statement with attribution, and keep the rest in an appendix referenced by the report.
Producing a financial analysis that calculates ratios or break-even correctly but never interprets what the numbers mean for the business decision.
Students rehearse calculation procedures from class and stop once a number is produced, believing the maths is the assessed skill.
What to do instead
After every calculation write a two-part sentence: what the figure shows and what it implies. For example, state the break-even quantity, then state how far current sales sit above or below it and what that means for the proposal's viability. Mark each calculation in the draft and check that an interpretation sentence follows it.
Ignoring the legal, ethical or sustainability dimensions of a proposal, or mentioning them in a single closing sentence.
Students focus on financial feasibility because it is easiest to quantify, and treat stakeholder and regulatory issues as optional extras.
What to do instead
Use a fixed evaluation framework for every option: financial, operational, legal and regulatory, ethical and social, environmental, and stakeholder impact. Award each option a short paragraph under each heading with at least one specific consequence. This structure also generates the content needed for the recommendation's risk section.
Presenting a recommendation with no implementation plan, timeline, responsible person or success measure.
Students see the recommendation as the end point of the report rather than the start of action, so they stop writing once they have chosen an option.
What to do instead
Attach a short action table to the recommendation: action, owner, timeframe, resource required, and the indicator that will show it is working. Add a review point with a specific date and a contingency if the indicator is not met.
Using a generic structure (introduction, body, conclusion) rather than the conventions of the required business document such as a report, proposal or pitch.
Students default to essay habits from other subjects and are unsure which headings, sections and register the specified format requires.
What to do instead
Memorise a template for each format the course requires. A report needs a title, executive summary, situation analysis, options evaluation, recommendation, implementation and references; a proposal needs a clear purpose, scope, cost and benefit case; a pitch needs a hook, problem, solution, evidence and ask. Practise converting one set of content into two different formats.
Submitting a written response that exceeds the word limit or falls well short, with the excess or shortfall concentrated in analysis rather than description.
Students draft without counting and either pad with background or cut the evaluation section when time runs out.
What to do instead
Plan word budgets per section before drafting and check the count after each section, not at the end. If over, cut description and repetition first. If under, add evaluation criteria, stakeholder impacts or implementation detail rather than restating facts.
Misreading the external assessment question's directive word, for example describing when asked to evaluate, or listing when asked to justify.
Under time pressure students answer the topic they revised rather than the question asked, and directive words look similar at a glance.
What to do instead
Underline the directive word and the key nouns in every question before writing. Keep a personal glossary of directive words with a one-line action for each: describe means state features; explain means give reasons; analyse means break into parts and show relationships; evaluate means weigh against criteria and judge; justify means give evidence for a position. Start each answer by restating the directive in your own words.
Writing answers to short external assessment questions that are too brief to earn the available marks, giving one point where three are required.
Students do not connect mark allocation to the number of distinct points, examples or reasoning steps expected.
What to do instead
Use marks as a planning signal: allow roughly one distinct, developed point per mark. For a four-mark question, plan four numbered points or two points each with a reason and an example. Jot the plan in the margin before writing so no mark-bearing element is omitted.
Running out of time in the external assessment because early answers are overlong, leaving extended-response questions unfinished.
Students write everything they know on the first questions and underestimate how long a structured extended response takes to plan and write.
What to do instead
Set checkpoint times before the exam based on the paper's structure and stick to them, moving on when a checkpoint passes. Cap short answers at the planned number of points and reserve the final block for the extended response, starting it with a brief plan so the structure survives even if time is tight.