Years 7–8TechnologyContext Triage

Context Triage for Technology

Putting the information evaluation step back into design tasks at Years 7–8

The condition

The design brief arrives. Students open a tool. Text appears. The brief is "answered." Except the brief was not answered. It was processed. The student skipped the step that Technology actually assesses: deciding what information matters for this specific design context. Context Triage puts that step back in before any generating begins.

The move — Context Triage

Students sort the available information into three groups before any design work begins. The triage is the thinking — and it takes about seven minutes.

  1. After presenting the design brief, give students the brief, their class notes, and any provided materials. Ask them to sort the available information into three groups before any design work begins.
  2. Keep: directly relevant to the design purpose and user need. Cut: interesting but not useful for this task. Question: needs checking or clarifying before it can be used.
  3. Students record their triage in a simple three-column format. A page divided into three columns works well. This is not a formal document — it is a thinking record.
  4. Students write one sentence for each group explaining the sorting decision: why these pieces serve the brief, why those do not, and what the uncertain pieces need before they are usable.
  5. Collect the triage record before any design development begins. At submission, students add a brief note: which "Keep" pieces actually appeared in the final design.
What the student produces
A sorted three-column triage record naming what was kept, cut, and questioned, plus a one-sentence explanation for each group. At submission, a brief note confirming which "Keep" pieces appeared in the final design. The triage shows whether the student read the brief as a set of constraints, not just a starting prompt.
Why it holds up

Technology learning assesses students' understanding of the relationship between design, context, and outcome. Context Triage makes that relationship a visible thinking act before any generating or making begins. When the triage is done, a tool can help with options and structure. But the decisions about what matters and why are already on paper, in the student's hand, ready to be assessed.

Teacher judgement note

Review triage records in a short checkpoint conversation before design development begins. Students who have sorted everything into "Keep" have not yet applied the brief as a lens — they need a prompt to identify what does not serve this specific user and purpose.

Governance reminder

Introduce Context Triage at the briefing stage, not as a separate activity. When the three categories — Keep, Cut, Question — are part of every brief analysis from Year 7 onwards, students begin reading design briefs more carefully before reaching for a tool. Brief your Technology faculty: triage time is design time, not extra time.

NZ Curriculum connection: Technology — Technological practice; Design thinking; Understanding technological systems

Print or save this resource as a PDF using your browser.

← Back to Evaluating AI Output