An HSC maths faculty program should do three jobs at once: guide the next lesson, show coherent coverage across the course, and leave a trustworthy record of what was taught and assessed. If it serves only the third job, teachers experience programming as retrospective paperwork. If it serves only the first, the faculty can lose visibility of syllabus alignment and assessment coverage.
The head teacher's role is to establish a common minimum standard and a review rhythm, not to force every teacher into identical lesson notes. This guide sets out a practical structure for NSW Mathematics Standard, Advanced and Extension courses.
As at 3 August 2026, Year 11 and Year 12 mathematics cohorts are on different syllabus versions. The official NSW mathematics syllabus list identifies the 2024 syllabuses as current for Year 11 and the 2017 syllabuses as current for Year 12. Every faculty document should name its course, year, cohort and syllabus version.
Download the HSC maths faculty programming calendar (PDF). It provides a term-by-term review rhythm, named decision points and a neutral tool-evaluation checklist for a faculty meeting.
Define the Faculty's Minimum Program
Start with a one-page agreement. A maintainable HSC program normally identifies:
- course, cohort and syllabus version
- scope and sequence with indicative time
- applicable syllabus outcomes and content
- teaching and learning activities at a useful level of detail
- planned formative and formal assessment evidence
- resources and equipment
- differentiation, adjustments or access considerations
- evaluation or annotation showing what changed in delivery
The document does not need to record every question asked in class. It does need enough detail for a qualified colleague to understand the intended learning, sequence and evidence.
Agree on where each element lives. If the scope and sequence is in one system, lesson resources in another and evaluation in a third, include stable links and ownership. Avoid duplicate versions that drift apart.
Build a Course Map Before Weekly Programs
The course map is the faculty's control document. Put weeks, content, outcomes, formal tasks and revision in one view.
For each outcome, identify:
- where it is first explicitly taught
- where students practise it in a new context
- where evidence is collected
- where feedback or reteaching occurs
- where it is retrieved before trials and the HSC
This prevents the common mistake of treating “appears in the textbook chapter” as proof of coverage. It also exposes overloaded weeks. If a formal task, a new complex topic and a major school event all sit together, change the sequence before teachers reach that week.
Use exact outcome wording from the applicable official course page. Do not copy 2024 codes into a 2026 Year 12 program or preserve 2017 codes in a Year 11 program because the topic title looks familiar.
Set Non-Negotiables and Leave Professional Space
Common expectations might include:
- agreed syllabus and outcome mapping
- common formal task schedule and approved task conditions
- a shared approach to secure assessment materials
- agreed evidence for practical, investigative or modelling work
- a common process for marking, checking and recording formal marks
- scheduled retrieval and cumulative practice
- program annotations completed close to delivery
Teachers can still choose examples, explanations, grouping and formative activities for their class. Standardisation should protect course integrity and comparability, not erase responsive teaching.
NESA's current guidance says schools develop course-specific formal assessment programs using the applicable school-based assessment requirements, ACE rules and school policy. It also tells schools to consider the timing of tasks in the teaching and learning cycle and their demands on students and teachers. See Developing school-based assessment programs, checked 3 August 2026.
Faculty Action: Run a 30-Minute Alignment Check
Open one course map, one current teaching program and the assessment schedule side by side. Use the HSC maths teaching program template to record one gap, one duplication and one decision with an owner and date. Repeat course by course rather than attempting a whole-faculty rewrite in one meeting.
Review the Chain, Not the Folder
Quality assurance should follow a small sample through the whole chain:
syllabus outcome and content
→ scope and sequence
→ teaching program and learning activity
→ assessment evidence
→ student work and feedback
→ program evaluation and next action
Choose one taught concept and ask whether each link is visible and coherent. A large folder can still fail this test if outcome codes were pasted without a genuine relationship to the task.
For an accredited individual non-government school, this chain also reflects the current registration manual. The February 2026 NSW Registered and Accredited Individual Non-government Schools Manual describes alignment among syllabus outcomes and content, scope and sequence, teaching programs and activities, assessment plans and records, and student work when demonstrating the standard of teaching. This article does not extend that manual to government schools or registration systems and member schools.
Use a Sampling Calendar
Do not wait until the end of the year to inspect every program. Sample small amounts regularly:
| Time | Review focus | Useful output | |---|---|---| | Before course | Syllabus version, course map, assessment schedule | Approved baseline and owners | | Weeks 4–5 | Pace, prerequisite evidence, first annotations | Sequence adjustment | | Before each task | Taught content, conditions, marking plan | Task approval record | | After each task | Marking consistency, outcome evidence, feedback | Reteaching decision | | End of term | Coverage and program evaluation | Revised next-term map | | After trials | Error patterns and remaining content | HSC revision priorities |
Keep a short decision log: date, evidence reviewed, decision, owner and follow-up. Minutes that merely say “programs discussed” are much less useful.
Moderate Before and After Marking
Programming and assessment cannot be separated. Before a formal task, check:
- the assessed content has been taught under the notified conditions
- the task samples the intended outcomes and components
- the mark allocation matches the evidence required
- valid alternative methods are anticipated
- the marking guidelines can distinguish levels of achievement
- accessibility and approved adjustments have been addressed through school processes
After marking, select scripts near key boundaries and compare marker decisions. Record changes to the guidelines and how any affected scripts were treated. NESA's marking formal assessment guidance also requires secure recording of marks and notes that assessment evidence can take several forms.
Make Annotations Useful
“Completed” is an attendance record for content, not an evaluation. A useful annotation says what evidence was observed and what will change.
Examples:
- “Two lessons added before annuities: exit ticket showed 11 of 24 students confused nominal annual rates with rate per period.”
- “Network flow investigation moved after maximum-flow examples; students could calculate but could not justify the cut.”
- “Question 7 produced two valid methods not anticipated in the guideline; both added before double marking.”
Use a simple convention across the faculty: evidence → judgement → action. That is enough to support next year's revision without producing pages of narrative.
Manage the Two-Syllabus Transition
In 2026, file naming is a compliance control. Include the course and syllabus year in folder names and assessment headers. Archive superseded resources as read-only where possible. A good question may remain useful across versions, but its outcome mapping and place in the course must be rechecked.
Run a transition register with columns for resource, current cohort, applicable syllabus, reviewer, action and date. “Same topic” is not a completed review.
Induct New and Out-of-Field Teachers Into the Program
Induction should help a teacher make good decisions in the first week, not ask them to absorb the whole drive in one sitting. A new or out-of-field teacher needs a clear route through the course and a named person to ask when the documents do not answer the classroom problem.
Start with a ninety-minute course orientation:
- identify the cohort and applicable syllabus version
- walk through the course map and the next six weeks
- show the common assessment schedule and approval process
- locate the current teaching program, solutions and core resources
- explain how the faculty records formative evidence and annotations
- rehearse where marks, adjustments and sensitive records belong
- name the mentor and schedule the first check-in
Do not equate subject knowledge with familiarity with the program. An experienced teacher joining from another state may need the NSW terminology and school processes. An out-of-field teacher may also need planned mathematics support: worked solutions checked before the lesson, observation of a colleague explaining a difficult concept, time to rehearse technology and a route for escalating content uncertainty without embarrassment.
Use a staged release. In week one, provide the current unit, shared routines and assessment horizon. In weeks two and three, add the course map, moderation process and resource-contribution expectations. By the end of the first unit, ask the teacher to annotate what worked and where the program assumed knowledge they did not have. That feedback is a quality test of the program, not a deficit in the new colleague.
A useful mentor check-in asks:
- Which lesson is hardest to prepare this week?
- Which solution or explanation needs a second check?
- What student evidence changed the planned pace?
- Is any common requirement unclear or unworkable?
- What should be added to the handover notes for the next teacher?
Avoid giving the new teacher an abandoned course and calling it autonomy. Shared minimum resources and scheduled review protect students while the teacher builds confidence and adapts the sequence responsively.
Report to the Executive With Evidence, Not Folder Counts
An executive update should explain whether the faculty is delivering the course coherently, what risk needs attention and what decision or resource is requested. “All programs are on the drive” does not answer those questions.
Use a compact report with five headings:
| Heading | Evidence | Executive-level question | |---|---|---| | Course status | Pace against course map; syllabus version | Is planned delivery on track? | | Assessment assurance | Tasks approved, moderation completed, records secure | Is the formal program operating as approved? | | Student evidence | Common misconceptions, attendance-to-learning impacts, intervention | What is changing because of evidence? | | Faculty capacity | Staffing, induction, resource or timetable constraint | What support or decision is needed? | | Next checkpoint | Named owner and review date | How will we know the action occurred? |
Aggregate appropriately. The executive usually needs trends, risks and decisions, not a duplicate list of every student's marks. Keep student-level records in the authorised system and follow school privacy rules.
Separate a genuine compliance or assessment risk from a development preference. A wrong syllabus version or unapproved task condition needs prompt escalation. A desire to reformat every worksheet does not. When requesting budget, connect it to a defined faculty problem, evidence of current effort, a trial design and a decision point. That gives the executive something concrete to approve or challenge.
Build a Resource Bank That Survives Staff Turnover
A durable resource bank has provenance and ownership. A folder of files called “good worksheet final NEW” does not.
For each core resource, capture:
- course, cohort and syllabus version
- outcome or content mapping checked by a named reviewer
- author or source and permission to store or adapt it
- date last reviewed
- student-facing file, worked solution and any marking guidance
- known issues or alternative valid methods
- where it sits in the program
- status: draft, approved core, optional extension or archived
Use stable naming and a shallow folder structure. Teachers should be able to reach the current version from the course map. Superseded formal tasks must be archived securely; do not leave them alongside student practice where access controls or reuse become unclear.
Make contribution part of the review cycle rather than an end-of-year rescue. After a unit, the teacher can spend ten minutes recording one correction, one useful scaffold and one note about timing. After an assessment, the faculty updates the marking guidance with valid methods discovered during moderation. Small contemporaneous changes are more trustworthy than a December folder clean-up based on memory.
Assign stewardship by course or topic, with a second reviewer for high-stakes material. Ownership means maintaining the shared version, not controlling it privately. If a steward leaves, the course map, review date and decision log allow another teacher to continue.
Audit rights and licence conditions before uploading commercial past papers, textbook material or resources created outside the school. A resource bank is not improved by storing material the faculty is not entitled to reproduce. Link to the approved source where that is the safer arrangement.
A Buying Checklist for HSC Maths Faculty Tools
Begin with the job, not the demo. A faculty seeking a deep archive of past-paper questions may reasonably prefer an established past-paper product. A team needing broad multi-subject content may favour a cross-curriculum platform. A faculty whose priority is new, outcome-targeted HSC maths practice, written-working review or coverage visibility may reach a different conclusion. The checklist should allow those outcomes.
Curriculum fit
- Does the product name the exact NSW course and syllabus version?
- Can the supplier explain how outcome and content mappings are verified?
- Does it support Standard, Advanced and Extension at the depth the faculty actually teaches?
- Can teachers inspect and edit material before students receive it?
Assessment and mathematical quality
- Are questions, solutions and marking guidance mathematically reviewed?
- Does the system handle diagrams, notation, units and alternative methods reliably?
- Can the faculty control difficulty, content and conditions rather than accept opaque generation?
- Does it preserve teacher judgement for formal assessment and marking?
Workflow and evidence
- Does it reduce a measured pain point or merely move the work?
- Can resources be shared, versioned and handed over across the faculty?
- Is outcome coverage visible at the level leaders need?
- Can the faculty export usable records and resources if it leaves the service?
Privacy, security and procurement
- What student, teacher and response data is collected, where is it hosted and how long is it retained?
- Which subprocessors and AI providers are involved?
- Are access, deletion, incident and support processes documented?
- Has the school followed its own approval, privacy, cyber-security and contracting requirements?
Trial and total cost
- Can the faculty test representative workflows rather than a curated demo?
- What setup, training, checking and exception-handling time is required?
- Are pricing, renewal, limits and exit terms clear?
- What evidence and decision date will determine whether the trial continues?
Score must-have criteria before comparing convenience features. Invite classroom teachers to test the workflow and a leader to review evidence and governance. Record counter-evidence: if the archive is too shallow, mappings need frequent correction or the workflow takes longer, that belongs in the decision.
The honest recommendation may be a competitor, the existing system, a narrow pilot or no purchase. A credible process makes a positive recommendation stronger because the criteria were capable of rejecting it.
What a Head Teacher Should Be Able to Answer
At any point in the course, the faculty should be able to answer:
- Which syllabus applies to this cohort?
- Where is each current outcome taught and evidenced?
- What was changed because of student evidence?
- How was this formal task checked and approved?
- Where are marks and feedback securely recorded?
- How do selected samples of student work connect to the program?
- Which gaps remain before trials or the HSC?
If an answer requires opening six unlabelled folders and asking the only teacher who understands them, the immediate need is information architecture, not a longer template.
Keep Improvement Proportionate
Start with the highest-risk gaps: wrong syllabus version, missing course coverage, formal assessment misalignment, insecure records or programs that do not resemble delivered teaching. Then improve consistency and ease of use.
For outcome mapping, use the NESA outcome-code guide. For task design, use how to write an HSC maths assessment task. A strong program is not the thickest one; it is the one teachers use, leaders can verify and evidence can support.