Subject playbook
AI for TAS Teachers
Use AI to draft design briefs, projects, procedures and folio scaffolds for NSW TAS — while you verify every measurement and complete every WHS risk assessment, and the designing stays the student's own.
Why this course
TAS is the practical, hands-on KLA — and that is exactly where confident AI is most hazardous. Ask a general model for a procedure and it will write a plausible, professional-looking method that may be UNSAFE or non-compliant: a missing machine guard, no PPE, an incompatible chemical, a food-hygiene gap, an electrical step that shouldn't be a classroom step. It also gets the things TAS lives or dies by quietly wrong — measurements, specifications, quantities, costings, material properties. And because TAS assessment is built on the student's *own* design folios and major projects, AI that does the designing isn't help — it's an integrity breach. Yet TAS is also where AI saves a teacher real hours: drafting design briefs and project scenarios, scaffolding the design process, ideation starters, worked techniques, differentiated task sheets, folio and documentation scaffolds, recipe/specification/material-list drafts, and turning a rubric into student-friendly criteria. This playbook teaches TAS faculties to harvest that time while keeping the discipline that matters — verify the technical detail, complete the WHS check, and keep the designing the student's — and shows how Lessio drafts NSW-grounded TAS programs, resources and assessments (a Technology Mandatory design project, a Food Technology unit, a design-folio assessment with marking guidelines) that you then verify and safety-check and own.
Modules
Each module: clear learning outcomes → short, accurate TAS input → a hands-on activity using the Lessio generator → interactive knowledge checks. Grounded in the real NSW Technology outcomes and the design process, and mapped to the Australian Professional Standards for Teachers. The 'verify technical accuracy, complete the WHS safety check, and keep the designing the student's own' discipline runs through every module.
Click a module to read it.
1
Where AI actually helps in TAS — and where it fails
The high-value TAS use cases (design briefs, project scenarios, design-process scaffolds, procedures, differentiated task sheets, folio scaffolds, rubric-to-criteria) — and the three failure modes that are uniquely dangerous in TAS: unsafe/non-compliant practical instructions (WHS), AI doing the student's designing, and wrong technical detail.~50 minBy the end of this module you'll be able to:
- Identify the high-value AI use cases in TAS and tie each to the design process and the relevant Technology focus area.
- Name the three TAS-specific failure modes — unsafe/non-compliant practical instructions, AI doing the student-led designing, and wrong measurements/specifications/quantities/material properties — and recognise each in an output.
- Apply the rule that AI is never trusted for a procedure, a risk assessment or a technical specification without a qualified WHS check and an independent accuracy check.
Standards2.1 Content and teaching strategies of the teaching area2.6 Information and Communication Technology (ICT)4.4 Maintain student safetyStart here: TAS is the practical KLA — so confident AI is most dangerous here
You've done the flagship course — you know AI is a fluent next-word predictor, that plausible isn't true, and that the teacher stays in the loop. TAS raises the stakes on every one of those points, because in TAS the output isn't only read — it is made, on machines, with tools, with heat, with chemicals, with food. A wrong word in an English draft is a style note. A wrong adjective here might be a missing guard on a bench saw, an omitted PPE line, an incompatible cleaning chemical, or a food left in the temperature danger zone. So this playbook keeps one discipline in front of everything: verify the technical detail, complete the WHS risk assessment, and keep the designing the student's own.
Where AI genuinely helps a TAS teacher
Used as a drafting assistant, AI is a real time-saver across the TAS workflow. The high-value cases:
Use case What AI drafts Your job Design briefs & project scenarios A first-draft brief with a real-world need, client/context, constraints and success criteria Pitch it to your cohort and outcomes; make the designing the student's Design-process scaffolds Frames for each stage — identify & define → research → generate & develop ideas → produce/realise → test & evaluate Keep the creative decisions the student's; check it scaffolds, not solves Ideation / brainstorming starters Divergent idea-prompts to kick-start students' own thinking Never the student's final design — a springboard only Step-by-step procedures & worked techniques A DRAFT method or technique outline (a joint, a seam, a soldering sequence, a food prep step) Verify it is correct and safe; you complete the WHS risk assessment Recipes / specifications / material lists Draft ingredient lists, cutting lists, material/component lists, quantities and costings Re-check every quantity, measurement, spec and cost; confirm availability Differentiated task sheets Enable / extend versions of a task targeting the same outcome Confirm the adjusted version still meets the outcome and is safe Folio & documentation scaffolds Headings and prompts for a design folio / portfolio of evidence Keep the folio the student's own designing, making and evaluating Rubric → student-friendly criteria Marking guidelines rewritten as 'I can…' success criteria Verify they stay faithful to the standard Notice what runs through the right-hand column: the design process and WHS. In the NSW Technology syllabuses, students use the design process — broadly identifying and defining → researching and planning → generating and developing ideas → producing and implementing → testing and evaluating — and they work safely with tools, materials and processes. AI can scaffold every stage of that process — if the designing stays the student's. AI cannot do the designing, and it cannot sign off the safety.
The three failure modes that are uniquely dangerous in TAS
General models fail in TAS in ways that don't show up in most other subjects. Know all three by name — you'll hunt for them for the rest of the course.
1. UNSAFE or non-compliant practical instructions (WHS). This is the one that makes TAS different from almost every other subject. An AI asked for "a procedure to cut and join this timber", "a soldering activity for Year 9 electronics", "a quick cleaning routine for the food room", or "an impressive practical" can produce instructions that are genuinely hazardous or simply not compliant — a missing machine guard or lock-out step, no PPE, no ventilation, an incompatible chemical mix, mains-electrical work that shouldn't be a student task, or a food step that breaches hygiene and temperature control. It writes it confidently and it looks like a normal method.
The hard line for TAS: never use an AI-generated practical procedure, demonstration, risk assessment or safety instruction without checking it against your school's WHS policy and the relevant safety guidance (machinery, electrical, food hygiene, chemicals), and completing your own formal risk assessment. AI drafts the procedure; a qualified human signs off the safety.
This is APST 4.4 — Maintain student safety in the most literal sense, and it sits squarely on the syllabus: every TAS elective carries an explicit safety outcome (the
-SAF-01outcome — e.g. selects and safely uses tools, materials, technologies and processes), and Technology Mandatory's TE4-SAF-01 is exactly that. Throughout this course, the AI only ever produces a DRAFT procedure or a risk-assessment starter — a prompt for your thinking — never an authority you act on.2. AI doing the student's designing — the design process is student-led. TAS assessment is built on the student's own designing, making and evaluating — recorded in design folios and, in the senior years, major projects. The design process is theirs to drive: their need, their research, their ideas, their realisation, their evaluation. AI must not do the creative or design work for them. AI-assisted folio content presented as a student's own is an academic-integrity issue — and in a senior major project (Design & Technology, Industrial Technology, Textiles & Design, Engineering Studies, and the like) it can jeopardise the award. AI may help you build a scaffold or a rubric; it must never be the student's design.
3. Wrong measurements, specifications, quantities, costings and material properties. TAS runs on precise technical detail, and models slip on exactly that: a cutting-list dimension that doesn't add up, a recipe quantity scaled wrong, a costing that's out, a fabric or timber or polymer ascribed a property it doesn't have, a component rated incorrectly, a tolerance invented. A plausible-looking spec can be quietly, completely wrong — and a wrong measurement wastes material, breaks a build, or fails a dish. Re-check every number, dimension, quantity, cost and material claim yourself.
Why a grounded engine changes the odds (but not the duty)
A general chatbot writes TAS from general text about Technology. Lessio drafts to the verbatim NSW Technology outcomes and the DoE program template, which sharply reduces the syllabus-accuracy errors (wrong outcome codes, wrong focus area, off-stage content, missing the design-process spine). It does not remove your duty to verify technical detail, complete the WHS risk assessment, or keep the designing the student's — no tool does. Grounding improves the draft; the discipline is still yours.
Activity — map your week onto the grid (12 min)
Open the Lessio generator and pick a TAS focus area you teach this term (say a Technology Mandatory Materials and production processes project, or a Food Technology unit). Generate a short resource for it — a design brief, a task sheet, or a procedure outline. Now mark it against the eight-row use-case grid above: which cell is this? Then deliberately stress-test it for the three failure modes — find (or rule out) any safety/WHS gap you'd never run without a risk assessment, any place it has done the student's designing for them, and any measurement, quantity, spec or material claim you'd have to verify. Write down the one thing you'd check first before this touched a class.
Knowledge check
1Name the three TAS-specific failure modes of general AI.
2Why can you never use an AI-generated procedure or risk assessment as-is in TAS?
3A Year 11 student pastes an AI-generated design and folio commentary into their major project. What's the problem?
2
Subject-specific prompt craft for TAS
Grounding prompts in real NSW Technology outcomes and the design process, the TAS pitfalls that need built-in self-checks (WHS hand-back, technical-accuracy flagging, keep-it-the-student's-design), and a TAS prompt library you can use Monday.~50 minBy the end of this module you'll be able to:
- Anchor a TAS prompt to a real NSW Technology outcome and to the design process, using the RICE structure.
- Build the TAS-specific self-checks (the WHS risk-assessment hand-back, technical-accuracy flagging, and 'scaffold but don't design for the student') into the prompt itself.
- Select and adapt a prompt from the TAS prompt library for a real task.
Standards2.1 Content and teaching strategies of the teaching area2.6 Information and Communication Technology (ICT)3.4 Select and use resourcesRICE, with a TAS accent
You learned RICE in the flagship course — Role, Intent, Constraints, Examples. The structure doesn't change for TAS; what changes is what you put in each slot, because TAS has its own anchors (the design process; the focus areas) and its own traps (safety; the student's authorship; technical precision).
- R — Role & context. Name the TAS role and the de-identified cohort. "You are an experienced NSW TAS teacher delivering Technology Mandatory to a mixed-ability Year 8 class with several EAL/D learners and three students with reading-support needs."
- I — Intent (task + the syllabus anchor). This is where TAS prompting gets its power: anchor to a real focus area / outcome and the relevant design-process stage. "Draft a design brief and a 'generating and developing ideas' scaffold for a project in the Materials and production processes focus area (TE4-DES-01, TE4-PPM-01) — and keep the actual designing for the students to do."
- C — Constraints & format. Reading level, Australian spelling, the structure you actually use — and the TAS guard-rails: "state all measurements and quantities explicitly so I can verify them"; "do not present any procedure as ready to run — mark it DRAFT and hand the safety back to me"; "scaffold the design process; do not generate the students' design ideas or solutions for them".
- E — Examples & evaluation. Show your style, and demand the TAS self-check: "At the end, list (a) every measurement, quantity, specification, cost or material property I must independently verify, (b) — for any practical element — a plain statement that I, the teacher, must complete the WHS risk assessment against my school's safety guidance before use, and (c) confirm you have scaffolded the process without doing the students' designing."
The TAS self-check is not optional
In other subjects the closing self-check is good hygiene. In TAS it is a safety control and an integrity control. Build these into every TAS prompt:
"Flag every measurement, quantity, specification, costing and material-property claim I must independently verify. For anything practical, provide only a DRAFT procedure and a risk-assessment STARTER, and state explicitly that the teacher must complete the formal WHS risk assessment before use — do not present safety as settled. Scaffold the design process only; do not design the solution for the students."
This turns the model's three worst TAS habits — unsafe instructions, wrong technical detail, and doing the student's designing — into a checklist it hands you.
Ground it, don't just ask it
A weak TAS prompt produces a generic, sometimes-unsafe, sometimes wrongly-measured task. A grounded one produces something you can verify quickly because it's tied to the syllabus and the design process.
Weak prompt Strong, TAS-grounded prompt "Make a woodwork project for Year 8." "You are a NSW TAS teacher delivering Technology Mandatory. Draft a design brief for a small timber product project in the Materials and production processes focus area (TE4-DES-01, TE4-PPM-01, TE4-SAF-01), for a mixed-ability Year 8 class. Include a real-world need, client/context, constraints and success criteria, and a 'generating and developing ideas' scaffold — but leave the actual design for students to create. State any indicative dimensions or material quantities explicitly so I can verify them, and provide only a DRAFT make-sequence with a risk-assessment STARTER; state that I must complete the formal WHS risk assessment before use." "Give me a recipe lesson for Food Tech." "You are a NSW Food Technology teacher. Draft a practical lesson around a dish for the Food selection for nutrition and health focus area (FT5-NSA-01, FT5-SAF-01), for a de-identified Stage 5 class. Provide a DRAFT recipe and method — state every ingredient quantity and time/temperature explicitly so I can check them — and a food-safety/hygiene risk-assessment STARTER only. Do NOT present it as ready to run: state that I must complete the formal WHS and food-safety risk assessment, and confirm temperature-control steps, before any student cooks." The strong prompts are longer because they carry the real focus area and outcome, the design-process stage, the measurement/spec guard-rails, the safety hand-back, and the keep-it-the-student's-design instruction. In Lessio, the syllabus anchor is built in — you select the real Technology outcomes and it grounds the draft for you, so your verifying and safety-checking are faster.
Keep the designing the student's — even in the prompt
The most TAS-specific habit to build: prompt for scaffolds, prompts and exemplar structures, never for the student's finished design. Ask for "a 'researching and planning' template with guiding questions", not "three product designs the student can submit". Ask for "ideation prompts to start students' own brainstorming", not "the best design solution for this brief". The folio and the major project must be the student's own designing, making and evaluating — your prompts should produce the frame, and leave the creation to them.
Activity — rebuild a TAS prompt, then ground it in Lessio (15 min)
Take a TAS task you'd hand to AI this week. Write your instinctive one-liner. Rebuild it with RICE: add the TAS role, a real focus area / outcome code, the design-process stage, the measurement/spec guard-rails, the WHS hand-back, and the keep-it-the-student's-design line. Run it. Then build the same task in Lessio and notice how much of the outcome-anchoring is already done — leaving you to verify the technical detail and complete the safety check rather than chase the syllabus.
Knowledge check
1What three TAS-specific guard-rails belong in the Constraints slot of a TAS prompt?
2Why anchor a TAS prompt to both a focus-area outcome and a design-process stage?
3What two instructions must any TAS prompt that touches a practical always include?
3
Planning & resources for TAS with Lessio
Generate a connected TAS set — scope & sequence → program → resources (design briefs, projects, procedures) — grounded in the real NSW Technology syllabus, then verify the technical detail, safety-check it, and own it. Worked example: a Technology Mandatory design project and a Food Technology unit.~50 minBy the end of this module you'll be able to:
- Produce a syllabus-aligned TAS scope & sequence, program and resources (design briefs, projects, procedures) as one connected set in Lessio.
- Verify a generated TAS program against the real NSW Technology outcomes, the range-of-technologies / design-project requirements, and practical/WHS safety requirements.
- Apply review-before-use to TAS drafts so the edits — technical, safety and design-authorship — are visibly your professional judgement.
Standards2.2 Content selection and organisation2.3 Curriculum, assessment and reporting3.4 Select and use resourcesPlan TAS as a connected chain
Faculty TAS planning is a chain, not a pile of lessons: scope & sequence (the year) → program / unit (the weeks) → resources — design briefs, project scenarios, procedures, task sheets, folio scaffolds — → assessment (the measure) — all pointing at the same NSW Technology outcomes and built around the design process. Lessio is built to generate exactly these artefacts, grounded in the verbatim NESA Technology syllabus and the DoE program template. (Assessment is module 4; here we focus on the first three.)
Worked example 1 — a Technology Mandatory design project
Say you're writing a Materials and production processes project for Year 8. In Lessio you select the real outcomes — TE4-SDP-01 (explains relationships between sustainability, design and production), TE4-MSC-01 (explains how materials, systems and components contribute to solutions), TE4-DES-01 (communicates and evaluates design ideas and solutions), TE4-PPM-01 (applies processes in the planning, management and production of projects) and TE4-SAF-01 (selects and safely uses tools, materials, technologies and processes) — and it drafts a program against the DoE's five-column teaching-and-learning sequence:
Outcomes & content · Teaching and learning activities · Evidence of learning · Differentiation & adjustments · Registration & evaluation
A grounded draft will sketch the design-process flow — identify & define the need → research materials and existing solutions → generate and develop ideas → produce the project → test and evaluate — with activities, a place for the practical/make sequence, and differentiation under the UDL headings. That's a strong starting point. Now your judgement takes over — and in TAS that includes the safety and the technical detail.
Worked example 2 — a Food Technology unit
For Food selection for nutrition and health (Stage 5, FT5-NSA-01) plus the safety outcome FT5-SAF-01, Lessio drafts the unit, the practical lessons and the recipes. The grounding fixes the syllabus — but you verify every quantity and time/temperature, and you complete the food-safety and WHS risk assessment for every practical before it runs. The engine never signs off the kitchen.
Mind the mandatory shape of Technology Mandatory
A TAS-specific coverage check the generic reviewer won't catch: in Technology Mandatory (Years 7–8), students use the design process and must work with at least six different technologies across four to eight design projects, drawing on the four focus areas — Digital and communication technologies, Engineering technologies and systems, Food and agricultural practices, Materials and production processes. When you generate a Technology Mandatory scope & sequence, check the draft actually delivers that range and that number of projects — an AI draft can look complete while quietly under-covering the technologies or focus areas.
Review-before-use — the TAS edition
Run every TAS draft through this before it becomes a real document:
- Codes & focus areas — every outcome code is real and current (e.g. TE4-DES-01, FT5-SAF-01, INT5-DES-01), matched to the right focus area and stage. AI can fabricate codes that look perfectly real (an invented "TE4-DES-02"); verify each one.
- Technical accuracy — every measurement, quantity, dimension, cutting/ingredient list, costing, tolerance and material-property claim is correct. Re-check the numbers, not just the structure — a wrong dimension wastes material; a wrong quantity ruins a dish.
- The design process is built — and stays the student's — the program genuinely scaffolds identify → research → generate/develop → produce → test/evaluate, and the designing is left to the students, not pre-solved for them.
- Practical & WHS safety — every procedure, demonstration, machine, tool, chemical or food step named is one you will risk-assess against your school's WHS policy and the relevant safety guidance; no method is treated as ready. Equipment, machinery, tools and ingredients are ones your school actually has and permits.
- Coverage — mandatory requirements respected (Technology Mandatory's range of technologies and number of design projects; the elective's required focus areas / modules; project-time expectations).
- Inclusion — language, contexts and examples are inclusive and culturally safe, including Aboriginal and Torres Strait Islander Peoples' technologies and practices where authentic (the syllabuses name examples such as Budj Bim eel traps and Brewarrina fish traps) — and respect ICIP: don't have AI fabricate cultural content.
If you couldn't defend the program in a faculty meeting or a registration audit — and couldn't run every practical in it safely — it isn't ready. The edits you make are the proof of your professional judgement — that's what the teacher-in-the-loop principle looks like for a TAS program.
Across the TAS span
The same loop holds wherever you teach:
- Technology Mandatory (7–8) — generate design projects across the four focus areas, then verify the technical detail, ensure the technology range and project count, and risk-assess every make activity.
- TAS electives (7–10) — Design & Technology, Food Technology (e.g. Food industry processing and operations FT5-IET-01), Industrial Technology (e.g. a Timber or Metal or Electronics industry project — INT5-DES-01, INT5-PRO-01, INT5-SAF-01), Textiles Technology (e.g. Textile design and product development TT5-CDT-01, TT5-SAF-01), Agriculture (AGT5-PRA-01, AGT5-SAF-01), Engineering (EGT5-MEA-01, EGT5-SAF-01), and the computing electives. Each carries its own safety outcome — keep it in front.
- Senior (11–12) — Design & Technology, Engineering Studies, Food Technology, Industrial Technology, Textiles & Design, Software Engineering, Enterprise Computing and Agriculture — many with major projects. Generate resources and the scaffolds for the major project (more in module 4) — but never let the engine, or the student, outsource the designing.
Activity — generate a TAS unit, then verify it (15 min)
In Lessio, generate a program / unit of work for a TAS focus area you teach next term (try a Technology Mandatory Materials and production processes project, or a Food Technology unit). Then do the three edits that make it yours: (1) verify two outcome codes against the official NSW Technology syllabus; (2) check the technical detail — pick one measurement, quantity, cutting/ingredient list or material claim and confirm or fix it; and (3) flag every practical/make activity in the unit as 'WHS risk assessment required — mine to complete'. Those three edits are the visible record of your professional judgement.
Knowledge check
1What are the connected TAS artefacts Lessio generates, in order?
2Beyond checking outcome codes, what two TAS-specific checks does review-before-use add?
3What mandatory coverage must you check when Lessio generates a Technology Mandatory scope & sequence?
4
Assessment, feedback & integrity in TAS
Build valid TAS assessments — design folios, projects and major-project scaffolds with marking guidelines; give design-process-shaped feedback; and assure authorship the way NESA expects — by design, not detectors — keeping the designing, making and evaluating the student's own.~50 minBy the end of this module you'll be able to:
- Draft a valid TAS assessment — a design folio / project task with marking guidelines — then verify every criterion, mark and technical requirement.
- Scaffold a design folio / major project with AI while keeping the designing, making and evaluating the student's own.
- Assure authorship and integrity in TAS the way NESA expects — by task design and process checkpoints, not 'AI detectors'.
Standards2.3 Curriculum, assessment and reporting5.1 Assess student learning5.2 Provide feedback to students on their learningAssessment AI can draft — and what you must verify
AI is genuinely useful for drafting TAS assessment: design-folio task descriptions, project briefs with constraints, marking guidelines and rubrics, and student-friendly success criteria from those rubrics. But TAS assessment is where the failure modes bite hardest, so the verification is non-negotiable:
- Every criterion checked against the outcomes. A rubric that measures the wrong thing, or omits the design process, mis-assesses the whole task.
- Every technical requirement verified. If the task sets a dimension, a tolerance, a quantity or a material spec, confirm it is correct and achievable with your school's resources.
- Marks that match the demand. Check the mark allocation reflects the cognitive and practical demand of each criterion (a whole design folio worth a token mark, or 'evaluate' worth one mark, is a red flag).
- Validity — the task measures the intended outcomes across the design process (designing, producing and evaluating), not just a finished product or just recall.
Use AI to draft the assessment, the rubric and the student-friendly criteria; use your subject expertise to make it correct, valid, fair — and safe (APST 5.1).
Design folios & major projects — scaffold, don't author
TAS assessment is built on design folios and, in the senior years, major projects (Design & Technology, Industrial Technology, Textiles & Design, Engineering Studies and the like). These are the student's own designing, making and evaluating, evidenced across the design process. AI is a strong scaffolding partner here — and a serious integrity hazard if misused. The line:
AI may help build the frame — a folio structure with headings, guiding questions for each design-process stage, a documentation checklist, a project-management/Gantt template, a marking rubric, or student-friendly success criteria. AI must not do the designing — not the student's design idea, not their research synthesis, not their development decisions, not their realisation, not their evaluation. The whole point of a folio or major project is the student's own design journey; an AI-generated design presented as the student's is malpractice — and in a senior major project it can jeopardise the RoSA/HSC award.
A safe use: generate a folio scaffold and rubric for the class, then teach students to document their own designing inside it — and design the checkpoints (below) that keep it theirs.
Feedback — design-process frames from AI, judgement from you
TAS work has a structure you can feed back against: the design process and the project's success criteria. AI drafts process-shaped feedback fast — is the need clearly defined? is the research used to justify decisions? are ideas generated and developed (not just one)? is the realisation skilful and safe? is the evaluation honest against the criteria? Then you make it specific, technically accurate and kind for the actual student's project. Never paste an identifiable student's folio or work into a general tool (flagship Module 2) — de-identify, or use your school's approved secured environment. And check the AI hasn't 'corrected' a student toward a wrong technique, an unsafe practice, or someone else's design — verify the feedback before it goes back.
Integrity in TAS — by design, not detectors
Schools decide whether AI is permitted for a given task, and you uphold HSC and RoSA integrity. In TAS, design for authorship rather than chasing it with unreliable "AI detectors":
- Make the design process visible — staged folio submissions, in-class design decisions, photos of their prototyping and making, draft-and-redraft of development and evaluation.
- Anchor to the student's own making — a folio tied to the artefact they physically produced, with progress evidence, is hard to fake and easy to discuss.
- Talk to students about their designing — a short viva ("why this material? why this joint? what failed in testing and what did you change?") confirms authorship far better than any detector.
- Teach disclosed, ethical AI use — students may use AI as a research aid or a sounding board they critique and acknowledge, not a ghost-designer for their folio or major project.
Activity — build and verify a TAS assessment (15 min)
In Lessio, generate a short design-folio or project assessment with marking guidelines for a focus area you teach (e.g. a Technology Mandatory Materials and production processes project, or a Stage 5 Food Technology task). Then do the TAS verification: check every criterion maps to the outcomes and the design process, verify any technical requirement (dimension, quantity, material, tolerance), confirm each mark allocation matches its demand, and add one authorship checkpoint (a staged folio submission, in-class making evidence, or a viva question) that makes the task hard to outsource to AI.
Knowledge check
1What must you verify on an AI-drafted TAS marking guideline / rubric before you use it?
2Where exactly is the line for AI use in a design folio or major project?
3How does NESA expect you to assure authorship in TAS — and what should you not rely on?
5
Capstone — build a real TAS resource and critique it
Build a connected, defensible TAS set with Lessio — program + resource (design brief / project / procedure) + a design-folio or project assessment — then verify the technical detail, complete the WHS safety check, confirm the designing stays the student's, critique it, and log it as PD.~50 minBy the end of this module you'll be able to:
- Build a connected TAS program, resource and assessment with Lessio, end to end.
- Critique and improve it against the real NSW Technology syllabus — verifying every measurement and specification, completing the WHS check, and confirming the designing stays the student's.
- Self-assess against the TAS Ethical-Use Checklist, reflect, and record the hours as Standards-relevant PD.
Standards2.1 Content and teaching strategies of the teaching area6.2 Engage in professional learning7.1 Meet professional ethics and responsibilitiesThe task — a real, connected, defensible TAS set
Choose a TAS topic you'll teach next term. Using Lessio, build and then critique:
- A program / unit of work for one focus area (e.g. a Technology Mandatory Materials and production processes project, a Food Technology unit, or a senior module).
- A resource within it — a design brief / project scenario, a differentiated task sheet, a folio scaffold, or a DRAFT procedure / recipe (with a WHS risk-assessment starter you will complete).
- An assessment — a design-folio or project task with marking guidelines (and, if senior, a major-project scaffold that leaves the designing to the student).
Then make it yours — the TAS verification pass
Improve each artefact with your professional judgement. For TAS, that specifically means:
- Codes & coverage — every outcome code real and current; the right focus area and stage; the design process genuinely built; Technology Mandatory's range of technologies / design-project count, or the elective's required focus areas, respected.
- Technical accuracy — every measurement, dimension, cutting/ingredient list, quantity, costing, tolerance and material-property claim checked and corrected.
- WHS safety — every procedure, demonstration, machine, tool, chemical or food step is one you have risk-assessed against your school's WHS policy and the relevant safety guidance; no AI-generated practical, procedure or risk assessment is used without that qualified check.
- Student authorship — the resource and assessment scaffold the design process; they do not do the students' designing, making or evaluating, and the folio / major-project work remains the student's own.
- Inclusion & fairness — inclusive, culturally safe contexts (respecting ICIP); the assessment valid and fair, with reasonable adjustments.
A connected, syllabus-accurate TAS set you'd actually use — drafted by AI, unmistakably shaped, verified, safety-checked and owned by you. Your edits — and especially your WHS checks and your protection of the students' own designing — are the evidence of your professional judgement.
Self-assessment — the TAS Ethical-Use Checklist
Run your capstone against all five checklist items on this page (below the modules). Every box should be honestly tickable — including "every measurement, specification, quantity and material claim verified", "no AI-generated practical procedure or risk assessment used without a qualified WHS check", and "the design/making remains the student's own work". If one isn't tickable, fix the artefact. That is the learning.
Reflection — write a short response
- What did AI genuinely save you time on in TAS, and what did you have to fix (a measurement, a quantity, a technique, a safety gap, a place it had done the designing)?
- Where did your subject expertise — and your WHS judgement — change the output?
- What's the one TAS-specific rule you'll keep for using AI responsibly — and does it put safety and student authorship first?
Log it as professional learning
This module is your assessment: a complete, critiqued TAS set plus your ethical-use reflection — keep it as evidence of practice. Because NESA removed the Accredited/Elective PD distinction in 2024, Standards-relevant learning like this counts toward your 100 maintenance hours — record it in your eTAMS PD log against the Standards it addresses (especially Standard 2 — including 2.1 content and teaching strategies of the teaching area — plus 4.4 student safety, 4.5, 5, 6 and 7). Your faculty can also run this playbook as part of its professional-learning plan or a staff development day.
Knowledge check
1What turns an AI-generated TAS unit into defensible professional work?
2Which three checklist items are the TAS non-negotiables in your capstone self-assessment?
3How does this playbook count toward your NESA professional-development hours?
Take-away prompt library
Ready, RICE-shaped prompts for common NSW teaching jobs (Module 3). De-identified — copy one, swap in your details, and use it today.
Design brief for a project
You're starting a new design project and want a strong, real-world brief — without the AI designing it for the students.
You are a NSW TAS teacher. Draft a design brief for a [Technology Mandatory / elective] project in the [focus area, e.g. Materials and production processes] for a de-identified [stage/year] class, anchored to [outcome code(s), e.g. TE4-DES-01, TE4-PPM-01, TE4-SAF-01]. Include a genuine real-world need, a client/context, design constraints, and success criteria — but leave the actual design solution for students to create (do NOT propose designs). Suggest indicative materials and state any indicative dimensions or quantities explicitly so I can verify them. Self-check: list every measurement/quantity I must verify, confirm you have NOT designed the solution for the students, and (if there is any making) provide only a DRAFT make-sequence and state that I must complete the WHS risk assessment before use.
Design-process scaffold (student-led)
Students need a frame to work through the design process themselves.
You are a NSW TAS teacher. Build a design-process scaffold for a [de-identified class] working on [project], anchored to [outcome code(s)]. Provide guiding questions and templates for each stage — identifying & defining, researching & planning, generating & developing ideas, producing/realising, testing & evaluating — that prompt the STUDENTS' own thinking. Do NOT generate design ideas, research findings or solutions for them; the designing must be theirs. Plain English, Australian context. Confirm at the end that this scaffolds the process without doing the students' designing.
DRAFT step-by-step procedure (teacher completes the WHS risk assessment)
You want a first-draft technique or make-sequence to adapt — safely.
You are a NSW [Industrial Technology / Food Technology / Textiles / Engineering] teacher. Draft a step-by-step DRAFT procedure for [technique/task, e.g. a corner joint / a soldered connection / a seam / a food preparation step] for a de-identified [stage/year] class, anchored to [outcome code(s), incl. the safety outcome -SAF-01]. State every measurement, quantity, time and temperature explicitly so I can verify them. Provide only a risk-assessment STARTER (hazards to consider, PPE, guarding/ventilation/temperature-control prompts). Do NOT present this as ready to run: state explicitly that I, the teacher, must complete the formal WHS risk assessment against my school's safety guidance, and have it checked, before any student uses it. Verify technical accuracy AND complete the safety check before use.
Differentiated task sheet (enable + extend)
You have a core TAS task and a mixed-ability class.
You are a NSW TAS teacher planning for a mixed-ability [de-identified class, key needs incl. EAL/D]. From the task below, produce two versions targeting the SAME outcome [code]: an 'enable' version with more scaffolding, worked steps and sentence/visual starters; and an 'extend' version with greater design complexity and an open-ended challenge. Keep the outcome and the safety requirements constant, and tell me what you changed in each. Flag anything I should verify and confirm both versions remain safe. [paste task]
Design-folio / documentation scaffold
Students need a structure to document their own designing — not have it written for them.
You are a NSW [Design & Technology / elective] teacher. Create a design-folio / portfolio-of-evidence scaffold for a [de-identified class] project, anchored to [outcome code(s)]. Provide section headings and guiding questions for each design-process stage and a documentation checklist — as prompts for the STUDENT to complete with their own designing, research, development and evaluation. Do NOT write folio content or design decisions for them. Confirm the scaffold prompts the student's own work and does not author it.
Project / folio marking rubric
You need a rubric for a design folio or project, mapped to the outcomes and the design process.
You are a NSW TAS teacher. Draft a marking rubric for a [project / design folio] for a de-identified [stage/year] class, anchored to [outcome code(s)]. Build criteria across the design process — defining the need, research, generating & developing ideas, producing/realising (skill and safe practice), and testing & evaluating — with performance descriptors at three or four bands and a mark allocation. Then add student-friendly 'I can…' versions of the criteria. Self-check: confirm every criterion maps to the outcomes and the design process, flag any technical requirement (dimension/quantity/material/tolerance) I must verify, and confirm marks match the demand. Verify technical accuracy AND complete the safety check before use.
Standards alignment
Mapped to the Australian Professional Standards for Teachers — especially Standard 2 (know the content and how to teach it), including 2.1 (content and teaching strategies of the teaching area), 2.2, 2.3 and 2.6; plus 3.3 and 3.4 (teaching strategies and resources); 4.4 (maintain student safety) and 4.5 (use ICT safely, responsibly and ethically); 5.1 and 5.2 (assess and give feedback); 6.2 (engage in professional learning); and 7.1 (meet professional ethics and responsibilities). Each module lists its descriptors.
Assessment of learning
Interactive knowledge checks in every module + a capstone TAS artefact (program, resource and a design-folio/project assessment) + an ethical-use reflection. Completion certificate; log the hours in eTAMS as Standards-relevant PD toward NESA's 100-hour maintenance requirement.
The Lessio Ethical-Use Checklist
- Every measurement, specification, quantity, costing and material-property claim verified against a reliable source — never assumed from the AI.
- No AI-generated practical procedure or risk assessment used without a qualified WHS check against the school's safety guidance (machinery, electrical, food hygiene, chemicals).
- The design/making remains the student's own work — AI scaffolds the task and the rubric; it never does the student's designing, making or evaluating.
- No student personal data entered into general AI tools; cohorts described, never children — and every outcome code checked against the official NSW Technology syllabus.
- Every AI output reviewed and owned by the teacher; AI use disclosed where policy requires, and students taught to use AI with integrity in their folios and projects.
Frameworks & sources
Grounded in the current national and NSW frameworks (verified June 2026):
- Australian Framework for Generative AI in SchoolsThe national framework: 6 principles and 25 guiding statements for safe, ethical AI use, in force since Term 1 2024 — the backdrop this TAS playbook works inside.
- NSW DoE — Guidelines on generative AI & NSWEduChatNSW's recommended secured tool plus minimum safety practices and the six ethical checks staff apply to any AI use, including in TAS.
- NESA — AI & academic integrity in assessmentSchools decide whether AI is permitted task-by-task and uphold HSC/RoSA authorship — critical for TAS design folios and senior major projects, which must be the student's own designing.
- NESA — Professional development (100 hours)From Aug 2024 the Accredited/Elective categories were removed; Standards-relevant PD like this playbook counts toward your maintenance hours, self-logged in eTAMS.
- Disability Standards for Education 2005Reasonable adjustments for students with disability are a legal requirement — AI can speed up differentiated TAS task sheets and resources, but you confirm each adjustment still targets the same outcome and is safe.
Hands-on throughout
Activities use the Lessio generator on real NSW-syllabus planning. Part of the 'Subject AI Playbooks' line, included in the whole-school Lessio programme; also available standalone per teacher or per faculty. Because NESA removed the Accredited/Elective PD categories in 2024, this playbook counts as Standards-relevant PD without an endorsement gate — a TAS faculty can run it as a twilight or staff development day, with Lessio doing the NSW-grounded TAS generation (design briefs, projects, procedures, folio assessments) underneath, teacher-verified and safety-checked.
Standards-relevant professional learning, mapped to the APST · content verified against national and NSW frameworks, June 2026 · self-log the hours in eTAMS.