HSC Maths Outcome Coverage Audit: A Faculty Workflow

An HSC maths outcome coverage audit should answer a more useful question than “Did we mention every code?” It should show what was taught, what students had an opportunity to demonstrate, what formal assessment evidence exists and what the faculty should do about any genuine gap.

For the 2026 HSC cohort, audit against the applicable 2017 Mathematics Standard, Advanced, Extension 1 or Extension 2 syllabus. The 2024 syllabuses began with Year 11 in 2026, begin with Year 12 in Term 4, 2026, and are first examined in the 2027 HSC. NESA confirms that transition on its Mathematics curriculum reform timeline. Do not merge the outcome codes for those two cohorts into one tracker.

This article was checked against current NESA and NSW Curriculum material on 3 August 2026. Official course pages remain the source of truth if requirements change.

Download the HSC maths outcome coverage matrix (PDF). It gives a faculty a clean audit record without pretending that one local template is a NESA-mandated form.

What a coverage audit should contain

A practical audit has four separate evidence columns:

| Layer | The question to answer | Useful evidence | Common false positive | | --- | --- | --- | --- | | Intended curriculum | What did the program plan to teach? | Scope and sequence, program, lesson sequence | A code copied into a program but never addressed | | Enacted curriculum | What learning experiences actually occurred? | Annotated program, lesson records, resources | A postponed unit still shown as complete | | Demonstrated learning | What could students show? | Classwork, exit checks, investigations, worked responses | Worksheet completion without evidence of the outcome | | Formal assessment | What evidence contributed to the school program? | Notifications, tasks, marking guidelines, results | Treating every outcome as needing its own formal task |

These layers should not be collapsed. An outcome can be taught and checked formatively without appearing as a separate row in every formal task. Conversely, listing an outcome on an assessment notification does not prove that the questions elicited evidence of it.

NESA describes assessment activities as opportunities for students to demonstrate knowledge and understanding so teachers can gather evidence relative to syllabus outcomes. Its current formal assessment programs and tasks rules also require schools to retain assessment records that may be used in an appeal. That makes traceability important, but it does not create a universal NESA spreadsheet format.

Step 1: lock the cohort and syllabus version

Start the audit header with four identifiers:

1. course name
2. cohort and completion year
3. syllabus version
4. date and owner of the audit

“Year 12 Mathematics Advanced” is not precise enough during transition. Write “2026 HSC Mathematics Advanced — 2017 syllabus” or “2027 HSC Mathematics Advanced — 2024 syllabus”. This prevents an apparently familiar topic name from carrying the wrong formal code into a task.

Use the official syllabus and outcomes pages, not a legacy faculty list, for wording. The NSW mathematics syllabus directory links both current and new Stage 6 materials. Curriq’s NESA outcome-code lookup can help navigate the transition, but the official course page remains authoritative.

Step 2: build a content-to-evidence matrix

Create one row per outcome or auditable content grouping. Outcomes are broad, so add a content reference or focus area rather than allowing a green outcome cell to hide an untouched part of the course.

Recommended columns are:

• formal outcome code and short descriptor
• syllabus content reference or focus area
• planned teaching window
• actual teaching status
• formative evidence location
• formal task and question references, where applicable
• evidence strength
• issue owner and next action
• review date

Use evidence-strength labels with defined meanings. For example, “mapped” can mean that a question appears to target the outcome; “verified” can mean a reviewer has checked the stimulus, prompt and marking criteria; “student evidence” can mean responses have been sampled. A colour by itself is too ambiguous for moderation or handover.

Test the question, not just the notification

For each formal task mapping, ask:

• What must the student know or do to answer this item?
• Which wording in the prompt elicits that evidence?
• Which marks recognise it?
• Could a student earn the marks without demonstrating the claimed outcome?
• Is a different outcome doing most of the work?

If an Advanced question asks students to differentiate accurately and then interpret a maximum in context, it may provide different evidence from a routine derivative item. The mapping should reflect the actual mathematical demand, not every topic that appears in the story around it.

A gap has surfaced and the next task is already due? Use the HSC maths assessment-task workflow to map questions and marking evidence deliberately before filling the space with a token item.

Step 3: audit the assessment program as a whole

Course outcomes are only one dimension. Check the applicable course-specific school-based assessment requirements, including any mandated components and their program weightings. Schools make some choices about task type, count and individual weighting within current NESA requirements; the faculty schedule must record the choices actually approved at your school.

Run these totals independently:

| Check | What to total | What not to assume | | --- | --- | --- | | Task weighting | Approved contribution of each task | That equal marks mean equal weighting | | Course components | Component allocation across all tasks | That a topic label proves the component | | Outcome evidence | Quality and spread of opportunities | That each outcome needs identical frequency | | Cognitive demand | Routine, multi-step, modelling and reasoning evidence | That mark value alone measures demand | | Conditions | In-class, take-home, investigation or examination conditions | That one format is universally required |

NESA does not prescribe a universal rule that each outcome must appear once, twice or in every formal task. Repeated evidence may be valuable where a later task elicits deeper or different performance. The audit should identify accidental over-concentration, not penalise intentional revisiting.

Build the Advanced and Standard 2 lookup correctly

Do not start by copying a list from a previous faculty spreadsheet. For the 2026 HSC cohort, open the official Mathematics Advanced Stage 6 (2017) syllabus page or Mathematics Standard Stage 6 (2017) syllabus page, then use the syllabus download linked there as the complete outcome lookup. Copy the formal code and wording exactly, record the syllabus version in the audit header, and add one row for every applicable Year 12 outcome before the faculty enters evidence.

For Mathematics Advanced, preserve the distinction between outcomes concerned with working mathematically and the course-specific knowledge and skills across functions, trigonometric functions, calculus, financial mathematics and statistical analysis. For Mathematics Standard 2, preserve the course's own Year 12 outcome set and content organisation rather than translating an Advanced list into easier language. Standard 2 evidence can involve algebra, measurement, financial mathematics, statistical analysis and networks; the precise code and wording must still come from the applicable official syllabus.

The useful audit work begins after the list is complete. Beside each formal outcome, break broad claims into auditable content references, then distinguish whether the faculty planned it, taught it, gave students practice, collected formative evidence and assessed it formally. This prevents a single green cell beside a broad outcome from concealing an untouched focus area. During the 2026–2027 transition, maintain separate sheets rather than placing 2017 and 2024 codes in adjacent columns and assuming they are direct replacements.

Step 4: sample student evidence

A document audit tells you what was offered; a response sample tells you whether the item worked. Select a small, purposeful sample from across the performance range and inspect:

• whether students interpreted the question as intended
• whether the marking guideline captured valid methods
• whether the claimed outcome was visible in responses
• whether access or wording issues obscured the intended mathematics
• whether marker annotations show consistent application

This is not a request to remark the cohort or alter recorded results outside the school’s approved processes. It is a program-quality review. If the review uncovers a possible marking or rank issue, follow the school assessment policy and current NESA review rules rather than quietly changing a spreadsheet.

Step 5: classify gaps before acting

Not every blank cell is the same problem. Use categories that lead to a proportionate response:

• record gap: teaching or evidence occurred but the reference is missing
• mapping gap: evidence exists, but the formal mapping is weak or incorrect
• teaching gap: required content was not completed as planned
• evidence gap: content was taught but students had no suitable opportunity to demonstrate it
• cohort gap: some students missed the opportunity and need an accessible alternative
• assessment-design gap: a formal task did not elicit what its map claimed

Then assign an action. A record gap may need an annotation. A teaching gap may need rescheduled instruction. An evidence gap may need a formative check or, where the approved assessment program and school policy allow, a carefully designed later task. Do not retrospectively relabel unrelated questions simply to produce a complete-looking heatmap.

For recovery planning, the six-week HSC maths recovery plan shows how to prioritise remaining instruction without pretending that every gap can be solved by more testing. For resource sequencing, use the HSC maths teaching program template.

A defensible faculty review cycle

A useful cadence is local policy, not a NESA mandate. One workable faculty cycle is:

1. the course teacher updates actual coverage and links evidence
2. a second teacher samples the claimed mappings
3. the head teacher checks program requirements and unresolved red flags
4. the faculty records decisions, owners and dates
5. the map is archived with the version of the program it audits

Keep personal information out of shared curriculum maps unless access is authorised and necessary. Student-level intervention records belong in the school’s approved system, with access and retention managed under school procedures. The coverage map can usually show counts or de-identified patterns.

The output should be a short decision list, not merely a coloured grid: what is secure, what is uncertain, what will change, who owns it, and when it will be checked again.

This illustrative view should never automatically declare an outcome “mastered” because one question was assigned or one mark was recorded. Teacher judgement, the quality of the evidence and the applicable school processes remain essential.

FAQ

Does NESA require every HSC maths outcome to appear in a formal task?

Do not apply that as a universal rule. Check the applicable syllabus and course-specific assessment requirements, then judge whether the complete program provides valid evidence against its required outcomes and components.

Can one question map to several outcomes?

It can, but only where the response genuinely provides evidence for each claim. Map the assessable demand and marking criteria, not every mathematical idea mentioned in the stem.

Is the same audit valid for the 2026 and 2027 HSC cohorts?

No. The 2026 HSC mathematics cohort uses the 2017 syllabuses. The 2024 syllabuses are first examined in 2027 and use different structures and outcome codes.

Is a faculty coverage tracker an official NESA record?

Not automatically. It is a local quality-assurance tool unless your system or school policy gives it a formal recordkeeping role. Keep required assessment records in the approved systems and formats.