IA1 design challenge - the format, conditions and weighting of the first internal assessment, what each phase of the design process must demonstrate within the challenge, how it is judged, and the strategy for showing the full explore-develop-resolve loop under controlled conditions

What this dot point is asking

QCAA's IA1 is the design challenge - the first internal assessment, worth 20 percent. This page explains what the challenge asks, the conditions it runs under, and how to demonstrate the full design process when time is tight. The challenge tests whether you can apply explore, develop and resolve responsively rather than at leisure, so the strategy differs from the long projects. Marks come from a visible, evidenced process and a justified response, even under pressure.

The answer

What IA1 is

The design challenge is the first of three internal assessments. It presents a design challenge and asks you to apply the design process to respond to it. Compared with the projects, the challenge is more contained - the scope is narrower and the conditions are tighter - so it tests your ability to run the process responsively and efficiently rather than over an extended period. It is worth 20 percent of the subject result.

The conditions

The design challenge runs under defined conditions set by QCAA and the school. That typically means a constrained timeframe and controlled circumstances, so you cannot endlessly iterate. The constraint is the point: it tests process fluency. Always confirm the exact duration, format and response requirements against the current QCAA instrument your school is using, because conditions can vary between syllabus versions.

What each phase must demonstrate

Even compressed, the response must show all three phases:

• Explore - understand the challenge, identify the need, and write design criteria. Skipping this is the most common failure, because without criteria there is nothing to develop toward or resolve against.
• Develop - generate a genuine range of distinct ideas, visualise them with quick annotated sketches, and test or evaluate them against the criteria to converge.
• Resolve - refine the chosen idea into a proposal, evaluate it criterion by criterion, and justify how it meets the need.

The challenge is built on the same explore-develop-resolve backbone as everything else in the subject; what changes is the time you have to show it.

How it is judged

The challenge is judged on how well you apply the design process and how defensible your response is. Markers look for evidence at each phase and a clear thread connecting them - a need that leads to criteria, criteria that guide ideas, ideas that converge to a proposal, and a proposal justified against the criteria. A polished outcome with no documented process scores poorly; a clear process with a modest outcome can score well.

Strategy under time pressure

The discipline that wins the challenge is resisting the urge to leap to a single solution. Under pressure that urge is strongest, and giving in to it is the classic low-band move. Instead:

1. Spend real time in explore - a wrong problem dooms everything after it.
2. Write criteria fast but genuinely, from the need.
3. Generate a quick spread of distinct ideas, not three variations of one.
4. Show at least one iteration - a test, an evaluation, a refinement - so the process reads as iterative.
5. Justify the final proposal against the criteria explicitly.

A compressed but complete loop beats a single polished idea with no process every time.

Worked example