A Year 12 HSC maths assessment schedule template should make the approved assessment program understandable to students and auditable by the faculty. It should not invent a universal number of tasks, weighting range or notice process and label those local choices as “NESA rules”.
The applicable requirements depend on the course and syllabus version. The 2026 HSC mathematics cohort remains on the 2017 syllabuses. The 2024 Mathematics Standard, Advanced, Extension 1 and Extension 2 syllabuses are first examined in the 2027 HSC. Confirm the cohort before reusing a schedule.
This template guide was checked against NESA’s formal assessment programs and tasks ACE rules and the official NSW mathematics syllabus directory on 3 August 2026. Your final schedule must also follow the applicable course page, system requirements and school assessment policy.
Download the Year 12 HSC maths assessment schedule template (PDF). It is a faculty planning scaffold; replace every placeholder with the requirements and approved decisions for the exact course, syllabus and school.
Start with a program summary
Place the identifiers above the task table so a detached page is still meaningful:
| Field | Example only | Why it matters | | --- | --- | --- | | School and faculty | Example Secondary — Mathematics | Identifies the document owner | | Course | Mathematics Advanced | Prevents transfer across courses | | Cohort | 2026 HSC | Anchors the implementation year | | Syllabus | Mathematics Advanced Stage 6 (2017) | Distinguishes the transition cohorts | | Schedule version | Approved 12 November 2025; revised 3 February 2026 | Makes changes traceable | | Policy reference | School assessment policy, current version | Connects local procedures | | Contact | Head Teacher Mathematics | Gives students a route for questions |
The example dates are illustrative. Approval authorities, document control and publication dates are school decisions.
Copyable task schedule structure
Use one row for each formal task, then adapt the columns to the applicable official requirements and school format.
| Task | Timing | Task type and conditions | Outcomes/content | Components | Task weighting | Notification issued | Due/sitting details | | --- | --- | --- | --- | --- | ---: | --- | --- | | 1 | Term __, Week __ | __________ | __________ | __________ | __% | __________ | __________ | | 2 | Term __, Week __ | __________ | __________ | __________ | __% | __________ | __________ | | 3 | Term __, Week __ | __________ | __________ | __________ | __% | __________ | __________ | | 4 | Term __, Week __ | __________ | __________ | __________ | __% | __________ | __________ | | Total | | | | Check required totals | 100% | | |
This four-row layout is a drafting convenience, not a claim that every HSC maths course or syllabus version must have four formal tasks. Add or remove rows only after checking the applicable NESA course-specific school-based assessment page.
For each task, specify enough detail to distinguish it from a topic heading. “Calculus task” does not tell a reviewer whether the format is an in-class test, investigation or formal examination, what students will do, or how it contributes to the approved program.
Worked Mathematics Advanced schedule with rationale
The following is a worked planning example, not a current NESA prescription. It deliberately omits official component percentages because a faculty must insert the labels and weightings verified on the course-specific page applying to its cohort. Its four-task shape, timing, types and individual weightings are illustrative school choices.
| Task | Example timing | Example format | Example scope | Example weighting | Planning rationale | | --- | --- | --- | --- | ---: | --- | | 1 | Term 4, Week 8 | In-class skills and reasoning task | Functions and introductory calculus taught by that date | 20% | Creates early evidence without allowing one first task to dominate the annual result | | 2 | Term 1, Week 8 | Investigation with an in-class component | Statistical analysis or financial modelling, according to the taught program | 25% | Elicits interpretation, modelling and communication that a short test may under-sample | | 3 | Term 2, Week 7 | Mixed in-class task | Trigonometric functions, calculus and selected earlier content | 25% | Checks delayed retrieval and method selection rather than assessing only the newest unit | | 4 | Term 3 trial period | Trial examination under approved school conditions | Representative sample of taught examinable course content | 30% | Provides sustained course-wide evidence without making the trial the majority of the school program | | Total | | | | 100% | Reconcile component contributions separately before approval |
The rationale matters because a numerically balanced table can still be educationally weak. Check that each task occurs after a fair opportunity to learn the relevant content, that students meet different mathematical demands across the year, and that the whole program—not a single row—satisfies the applicable Mathematics Advanced requirements. If your school's approved program uses a different number or mix of tasks, change the structure rather than forcing local decisions into this example.
Add a component check beneath the table
Where the course has mandated assessment components and weightings, include a reconciliation table using the exact labels and values from the applicable official course materials:
| Required component | Task 1 | Task 2 | Task 3 | Task 4 | Program total | Official requirement | | --- | ---: | ---: | ---: | ---: | ---: | ---: | | [Exact component label] | __ | __ | __ | __ | __ | Verify | | [Exact component label] | __ | __ | __ | __ | __ | Verify | | Total | __ | __ | __ | __ | 100 | 100 |
Do not copy component names or values from another maths course, a previous syllabus, or this generic table. A schedule can total 100% and still be non-compliant if its component allocation is wrong.
Use one consistent convention. If the component cells show percentage points in the overall program, label them that way. If they show proportions within a task, include the calculation. Avoid a table where the same number sometimes means marks and sometimes means weighting.
Map outcomes without overclaiming
List only formal outcomes that the task is designed to elicit, using codes from the syllabus applied to that cohort. Maintain a working question-to-outcome map behind the public schedule. It should show:
- the question or criterion producing the evidence
- the content or focus area involved
- the marks or performance evidence available
- the assessment component contribution
- the reviewer who verified the mapping
The public schedule may need a shorter outcome list, but the faculty’s internal document should be testable. If a code appears only because a concept is mentioned in a stimulus, remove it or redesign the question.
The HSC maths outcome coverage audit explains how to distinguish planned, taught and assessed coverage. There is no need to force every outcome into one formal schedule row merely to colour a tracker green.
The schedule balances on paper, but the next task still needs real evidence. Use the HSC maths assessment-task guide to draft questions and marking criteria together.
Build notification fields into the workflow
NESA’s current ACE rules require sufficient written notice for formal tasks and say that NESA recognises exceptional circumstances where a two-week notice period may not be possible. This should not be misreported as “every school must always issue exactly two weeks’ notice with no exception”. Follow the current official rule and your school’s process.
The working schedule can include a notification-control table:
| Notification check | Faculty record | | --- | --- | | Date, time or due date | __________ | | Time allowed for an in-class task | __________ | | Weighting | __________ | | Outcomes and/or content assessed | __________ | | Task description and submission instructions | __________ | | Marking information required for this task | __________ | | Illness, misadventure, extension and adjustment pathway | Link to school policy/process | | Date written notice issued | __________ | | Approved variation, if any | Authority, reason, communication date |
Some detail belongs in the task notification rather than the one-page annual schedule. Link the documents or give matching task identifiers so students are not left choosing between conflicting dates.
NESA notes that marking criteria may be appropriate for some task types but not, for example, a trial examination. Do not promise identical advance marking detail for every format. State what applies to the actual task and the school’s approved procedure.
Stress-test the calendar
An assessment schedule is also a workload and access plan. Before approval, overlay:
- school examination blocks and reporting dates
- excursions, camps, work placement and major school events
- public holidays and known timetable disruptions
- tasks in other subjects where whole-year information is available
- time needed to teach the assessed content
- time for marking, moderation and useful feedback
- approved disability adjustments and room or staffing needs
- NESA submission dates managed by the HSC coordinator
This overlay is planning practice, not a universal NESA spacing formula. A faculty may set local limits on clustered tasks; describe those as school policy.
Check course combinations rather than imagining an “average” student. Extension students may have several mathematics papers and different assessment loads. A schedule that is convenient for one class can create a bottleneck for students taking another course on the same line.
Control changes after publication
Sometimes a task date or condition must change. The schedule should identify the approved version and the school process for changes. A basic change log includes:
| Version | Date | Change | Reason | Approved by | Students notified | | --- | --- | --- | --- | --- | --- | | 1.0 | ______ | Initial schedule | Annual program | ______ | ______ | | 1.1 | ______ | ______ | ______ | ______ | ______ |
Do not overwrite the old schedule and leave no record of what students received. Communicate changes consistently to the cohort, preserve required notice, and consider whether absence from the announcement creates an access issue. If students in the same course cannot complete an in-class task on the same day because of scheduling, NESA’s ACE guidance says arrangements must be communicated ahead of time.
Faculty approval checklist
Before publishing, verify:
- The course, cohort and syllabus version are explicit.
- The task count, types and individual weightings satisfy the applicable course requirements.
- Task weightings total 100%.
- Required components use the official labels and total correctly.
- Formal outcomes come from the correct syllabus.
- Tasks occur after students have a fair opportunity to learn the assessed material.
- Conditions and notification fields agree across documents.
- Dates have been checked against the school calendar.
- Adjustments and alternative arrangements can be delivered.
- Change control, illness/misadventure and review routes point to approved school procedures.
A colleague should independently recalculate totals. Spreadsheet formulas reduce arithmetic errors but do not validate whether a question genuinely contributes to a component or outcome.
Pair the final schedule with an annotated HSC maths teaching program. The two documents should agree about sequence without becoming duplicates: the program explains learning, while the schedule explains formal assessment.
2026 and 2027 should be separate templates
The 2026 Year 12 cohort is examined under the 2017 mathematics syllabuses. Year 11 began the 2024 Standard, Advanced and Extension 1 syllabuses in Term 1, 2026; Year 12 implementation begins in Term 4, 2026, including Extension 2, for first HSC examination in 2027.
Keep separate source files labelled by syllabus and cohort. Even if the faculty chooses similar task timing, formal outcomes and course-specific requirements must be checked anew. “Roll forward last year’s schedule” should mean using its layout as a starting point, not treating its compliance decisions as inherited facts.
FAQ
How many formal assessment tasks must Year 12 HSC maths have?
Check the school-based assessment requirements for the exact course and syllabus version. This generic template does not assert one universal task count across all HSC mathematics courses and cohorts.
Does every formal task require exactly two weeks’ notice?
Current NESA guidance requires sufficient written notice and recognises exceptional circumstances where a two-week period may not be possible. Apply the current ACE rule together with your school policy.
Can we reuse the 2026 schedule for the 2027 HSC?
Not without a fresh review. The 2026 HSC mathematics cohort uses the 2017 syllabuses; the 2027 cohort is first examined on the 2024 syllabuses.
Should raw marks appear in the annual schedule?
They can where useful, but distinguish raw task marks from task and component weightings. The published schedule must make the approved contribution to the school assessment program clear.