Revising Your Brief

Overview

Today you will revise your AS91608 brief so it clearly reflects what you now intend to develop and why. You will use your research, modelling, stakeholder feedback, and evaluations to write a brief that allows judgement of the outcome’s fitness for purpose in the broadest sense.

Learning intentions

Students will be able to:

• revise an initial brief using evidence from research, functional modelling, testing, and stakeholder feedback
• write a clear “set the scene” statement explaining the situation and need
• identify and rewrite constraints (non-negotiables) and requirements for the outcome
• convert broad ideas into specific, testable specifications across physical, functional, and social factors

Success criteria

• I can re-write my brief so the situation and need are clearly stated and match my investigation evidence.
• I can list my constraints and non-negotiables and explain how they shape design choices.
• I can write precise specifications that cover physical and functional performance, plus social acceptability and broader environmental/health and safety factors.
• I can justify (in my brief) what I intend to achieve/create and how my specifications support fitness for purpose.

Curriculum links

• AS91608 — Undertake brief development to address an issue within a determined context: establishing an issue, identifying context considerations, determining a need or opportunity, ongoing stakeholder reflection, reflecting context considerations, and developing a final brief for fitness for purpose.
• AS91610 — Develop a conceptual design considering fitness for purpose in the broadest sense (supporting link): using research and functional modelling evidence to evaluate and explain potential to meet the brief.
• NZC Technology: students create and refine technological outcomes through iterative, evidence-informed development and decision-making (including considering people, systems, and environments).

Lesson structure (50 minutes)

1. 0–5 min · Set the scene (warm-up). Teacher displays an anonymised “good brief” paragraph and highlights where it states the situation and need. Students identify the sentence that makes the need obvious and underline it.

2. 5–12 min · Quick teach: what “revision” means for your brief. Teacher explains that revision should be evidence-based: research → modelling → stakeholder feedback → evaluation → updated brief. Students skim their own notes and write one margin note: “My biggest evidence is…”

3. 12–22 min · Evidence-to-brief mapping. Teacher gives a one-page template with four boxes: Research, Modelling/Testing, Stakeholder feedback, and Evaluations/changes made. Students complete the template for their project and select 3–5 evidence points that must appear in their revised brief.

4. 22–33 min · Rewrite the brief section-by-section. Teacher models how to start with: situation/need → what you intend to create → constraints → specifications. Students draft their revised “final brief” using sentence starters:

• “The situation is…”
• “The need/opportunity is…”
• “I intend to create/develop…”
• “Constraints/non-negotiables are…”
• “My specifications are…”

5. 33–42 min · Specifications check: physical, functional, social + broader factors. Teacher introduces a simple checklist students must meet before they can “lock” the brief. Students run a self-check and revise any vague statements into specific requirements (e.g., size range, material requirements, performance targets, accessibility needs, maintenance expectations, health and safety constraints, disposal/lifecycle considerations).

6. 42–48 min · Stakeholder reflection spot-check. Teacher prompts students to reread their stakeholder feedback: what changed in your intent and constraints? Students write two brief lines under their brief: “Based on stakeholder feedback, I will…” and “This affects my specifications by…”

7. 48–50 min · Exit ticket: readiness to submit brief. Students complete a 2-question exit ticket:

• “My top 2 specifications (most measurable) are…”
• “The evidence that justifies my revisions is…”

Resources

• Student project brief(s) from earlier steps (initial brief and any drafts)
• Research summary notes and functional modelling/evaluation notes
• Stakeholder feedback notes (comments, survey results, interview notes, testing observations)
• Brief revision template handout (set the scene → intent → constraints → specifications)
• Highlighters or colour coding pens (physical/functional vs social vs broader factors)
• A4 paper or digital document for drafting and finalising
• Assessment checklist card (fitness-for-purpose in the broadest sense prompts)

Assessment

• Teacher circulates during drafting to check students are using evidence (not opinions) to revise constraints and specifications.
• Formative check: students must complete the evidence-to-brief mapping box before writing the final brief.
• Exit ticket verifies that at least two specifications are measurable and that evidence justifies the revisions.

Differentiation

• Support: provide sentence starters, a specifications bank (examples of measurable statements), and a checklist focusing on physical/functional first, then social and broader factors.
• Support for students needing structure: allow them to copy their best two evidence points into the “situation/need” and “constraints” sections before drafting specifications.
• Extension: ask students to include a brief “fitness-for-purpose scope” line (e.g., how their specifications will be tested or checked during prototyping/implementation).
• EAL/SEN: allow brief bullet responses in the first draft stage; provide a glossary of words like “constraint”, “non-negotiable”, “specification”, “context considerations”.