An HSC maths teaching program template is useful only if it helps teachers make decisions: what to teach, when to assess it, how to map NESA outcomes, and where to leave time for revision. A polished table with no outcome logic will not help in Term 3 when trials, illness, excursions, and unfinished topics collide.
This guide gives a copyable structure for Year 12 Standard 2 and Advanced planning. Treat it as a faculty planning scaffold, not a substitute for your school's official assessment schedule or NESA documentation.
What a teaching program needs
A Year 12 HSC maths program needs more than a list of topics. At minimum, it should include:
- week and term
- topic or unit title
- NESA outcome codes
- core skills and applications
- planned assessment links
- revision and retrieval tasks
- resource notes
- evidence of differentiation
The key is that outcome codes and assessment timing should be visible in the same document. If the scope and sequence says "calculus" but the assessment notification says "C1.2 and C1.3", teachers need to know exactly when those outcomes were taught and practised.
The program should also show assumptions. If a unit depends on Year 11 algebra, trigonometry, or functions, name the prerequisite and schedule a short diagnostic. Otherwise, the first formal task becomes the diagnostic, which is too late.
For a deeper explanation of outcome mapping, use the NESA outcome codes guide. If you are designing the formal task itself, pair this with how to write an HSC maths assessment task.
Backward planning from the HSC
Start from the end of the course, then work backwards.
The external HSC exam date changes each year, so do not hard-code last year's timing into the next program. Instead, divide the year into planning zones:
- Final HSC revision: past-paper practice, mixed-topic feedback, exam technique.
- Trial-to-HSC repair: targeted reteaching based on trial data.
- Trial preparation: full-paper timing, mixed sections, formula and calculator fluency.
- New content completion: final syllabus outcomes taught and assessed.
- Core content build: the main sequence of Year 12 topics.
The mistake is leaving all revision until every topic is complete. Students need retrieval practice while content is still being taught. A teaching program should therefore include small revision tasks every fortnight, not just a large block at the end.
Term-by-term sequence (Standard 2 example)
This is an example only. It assumes a school year with four terms of Year 12 teaching, with trials in Term 3. Adjust to your local calendar, assessment schedule, and faculty sequence.
| Term | Weeks | Focus | Outcome notes | |---|---:|---|---| | Term 4 | 1-3 | Algebra and modelling refresh | Use prerequisite checks before new Standard 2 content | | Term 4 | 4-6 | Measurement | Map to relevant Standard 2 measurement outcomes | | Term 4 | 7-9 | Financial Mathematics: money, investments, loans | MS-F1 and MS-F4 | | Term 1 | 1-3 | Financial Mathematics: annuities | MS-F5 | | Term 1 | 4-6 | Networks | Map to network outcomes | | Term 1 | 7-10 | Statistical Analysis | Map to univariate and bivariate outcomes | | Term 2 | 1-4 | Mixed applications and exam-style modelling | Link questions across topics | | Term 2 | 5-7 | Assessment task preparation and feedback | Use assessment notification outcomes | | Term 2 | 8-10 | Trial revision foundations | Topic tests, calculator drills, reference-sheet fluency | | Term 3 | 1-3 | Trial paper practice | Mixed papers under timed conditions | | Term 3 | 4-5 | Trial exam and marking | Analyse by outcome, not just total mark | | Term 3 | 6-10 | Trial repair and HSC revision | Reteach weak outcomes, then mixed-paper practice |
The exact order can change. The important rule is that financial maths should not be crammed into one late block if students need time to distinguish simple interest, compound interest, loans, depreciation, and annuities.
Mapping outcomes to weeks
A good program makes outcome coverage auditable. Every outcome should have:
- first teaching week
- first practice week
- first formal or informal assessment point
- revision week
- evidence source
For example:
| Outcome | First taught | First practised | Assessed | Revised | Evidence | |---|---|---|---|---|---| | MS-F1 | Term 4 Week 7 | Term 4 Week 8 | Task 1 | Term 2 Week 8 | Worksheet, quiz, task | | MS-F4 | Term 4 Week 8 | Term 4 Week 9 | Task 1 | Term 3 Week 2 | Loan table quiz | | MS-F5 | Term 1 Week 1 | Term 1 Week 2 | Task 2 | Term 3 Week 6 | Annuity worksheet | | C1.2 | Term 4 Week 4 | Term 4 Week 5 | Task 1 | Term 2 Week 9 | Differentiation quiz |
This makes gaps visible. If an outcome has been taught but never assessed, that is a risk. If it has been assessed but not revised after poor results, that is also a risk.
For the data side of this workflow, see using NESA data to plan HSC maths teaching.
Where assessment tasks fit
Assessment tasks should follow teaching, not drive it backwards into rushed coverage. The teaching program should show when students have had enough exposure for a valid task.
Before placing a task, check:
- Have all listed outcomes been explicitly taught?
- Have students seen both routine and unfamiliar applications?
- Is there time to return marked feedback before the next related unit?
- Does the task fit the school's assessment schedule?
- Does the task create a useful diagnostic for future teaching?
A task immediately before a long break can be hard to use diagnostically because feedback arrives too late. A task with no mapped follow-up week becomes a reporting event rather than a teaching tool.
The best programs include a feedback week after major assessment. That week is not "lost time"; it is where the assessment becomes useful.
Template
Copy this structure into your faculty planning document.
| Week | Topic | Outcome codes | Core skills | Practice evidence | Assessment link | Revision thread | |---|---|---|---|---|---|---| | T__ W__ | | | | | | | | T__ W__ | | | | | | | | T__ W__ | | | | | | |
Use this version for Advanced if your faculty wants a more detailed sequence:
| Term/week | Unit | Outcomes | Lesson focus | HSC-style practice | Common mistakes to target | Follow-up | |---|---|---|---|---|---|---| | T4 W1 | Functions review | F outcomes | Domain, range, transformations | Graph interpretation | Ignoring domain restrictions | Exit quiz | | T4 W2 | Functions and relations | F outcomes | Inverse and composite functions | Mixed short answer | Confusing inverse notation | Homework check | | T4 W3 | Differential calculus | C1.1/C1.2 | First principles and rules | Worked derivative set | Missing chain rule | Mini quiz | | T4 W4 | Applications of differentiation | C1.3 | Tangents, normals, optimisation | Extended response | Weak interpretation | Feedback lesson |
The template should be revised after each assessment cycle. If Task 1 shows weak algebraic manipulation, the program needs extra algebra retrieval even if the next topic is not "algebra".
curriq supports this by generating worksheets and exams from selected outcomes, then tracking which outcomes have been practised and assessed. That makes the teaching program a live planning document rather than a file written once and ignored.
FAQ
What should be in an HSC maths teaching program?
It should include weeks, topics, NESA outcomes, core skills, assessment links, revision points, resources, and evidence that the outcomes have been taught and practised.
Is a scope and sequence the same as a teaching program?
No. A scope and sequence gives the order and timing of content. A teaching program adds lesson-level intent, outcomes, assessment links, resources, and evidence of learning.
How often should a Year 12 maths program be updated?
Update it after each assessment cycle and after any major timetable disruption. The program should respond to evidence, not just preserve the original plan.