For a maths faculty preparing for NESA registration or accreditation review, the goal is not to manufacture an “inspection folder”. It is to make the school's normal evidence easy to trace: the applicable syllabus leads to a scope and sequence, the program leads to learning and assessment, and student work shows delivery.
This guide is deliberately narrow. It applies only to the NSW Registered and Accredited Individual Non-government Schools Manual (February 2026), checked on 3 August 2026. It does not state requirements for NSW government schools or for schools operating through a registration system. Those settings have different manuals and governance arrangements.
The controlling source is NESA's current Registered and Accredited Individual Non-government Schools Manual. Use the current manual, ACE rules, official notices and your school's advice when making compliance decisions. This article is an organisational aid, not legal advice or a substitute for the school's approved process.
NESA's current school inspections overview explains that inspection is tied to ongoing compliance with the Education Act registration requirements and that its risk-based approach includes random short-notice selection. The school—not this article—must determine which current manual, inspection scope and evidence request applies.
Download the NESA inspection maths faculty checklist (PDF). It separates faculty-owned evidence from whole-school evidence and provides a six-week readiness sequence without pretending to be an official NESA form.
Understand the Evidence Chain
For an accredited school offering HSC courses, the manual's Part C describes records and alignment across:
- relevant NESA syllabus outcomes and content
- scope and sequence of learning or units of work
- teaching programs and learning activities
- assessment plans, schedules and records
- student work
It also identifies HSC-related evidence including allocated hours, student patterns of study, written assessment advice and procedures for marking, malpractice, illness or misadventure, appeals and N determinations.
The practical faculty question is: can a reviewer follow one taught concept through this chain without relying on an oral explanation from one person?
Build an Evidence Map, Not a Duplicate Archive
Create a short index for each course:
| Evidence area | What the maths faculty links | What to check | |---|---|---| | Course identity | Course, cohort, syllabus version, teacher | Correct version for the calendar year and year group | | Time and sequence | Timetable, allocated hours, scope and sequence | Coherent sequence and recorded changes | | Syllabus alignment | Outcomes and content mapped to units | Exact official references, not legacy codes | | Teaching delivery | Current programs, activities and resources | Corresponds with the scope and sequence | | Assessment | Schedule, notifications, tasks, guidelines | Matches applicable course and school requirements | | Achievement records | Marks, feedback, selected work | Secure, legible and connected to the task | | Evaluation | Program annotations and faculty decisions | Shows evidence, judgement and response |
The map can contain stable links to approved systems. Avoid copying student records into a new drive merely for an inspection. Duplication creates privacy, access-control and version risks.
Check the Syllabus Version First
In 2026, NSW mathematics has a transition between syllabuses. The official mathematics syllabus list shows the 2024 Standard, Advanced and Extension 1 syllabuses being taught in Year 11, while Year 12 remains on the 2017 Stage 6 syllabuses. The 2024 Extension 2 syllabus begins from Term 4, 2026.
Every program and formal task should identify the course, cohort and syllabus version. Where an older resource is reused, recheck its content and outcome mapping. A topic with the same broad name is not evidence that the mapping is unchanged.
Sample Vertically Through One Unit
Choose a recently completed unit in each course and assemble a traceable sample:
- syllabus outcome and content reference
- place in the scope and sequence
- relevant section of the teaching program
- learning activity or class task
- assessment or formative evidence
- anonymised or appropriately accessed student work across a reasonable range
- feedback and program evaluation
Do not curate only the most polished student response. The manual says schools may need to provide samples of student work demonstrating curriculum delivery and should be able to draw on day-to-day work available at inspection. A normal, well-organised evidence trail is stronger than a showcase disconnected from routine teaching.
Follow school privacy and records procedures. Whether work is anonymised, shown in its normal secure system or provided another way is a school decision, not determined by this guide.
Faculty Action: Trace One Unit Today
Select one HSC maths unit taught this term. Open the HSC maths teaching program guide and record links for the seven sample points above. If a link is missing, assign the smallest corrective action with an owner and date; do not begin by rebuilding the entire faculty drive.
Review HSC Assessment Records
For each HSC maths course, check that the school's approved records make visible:
- the applicable assessment schedule
- written advice provided to students
- task conditions, components and weightings where required
- the approved task and marking guidelines
- final marks and evidence of feedback
- processes used for absence, illness or misadventure, malpractice and appeals
- any changes to an invalid or unreliable task, with the school's decision record
The manual places these within school policies and ACE requirements. A maths faculty should not invent a local process that conflicts with the school's policy. The faculty contribution is accurate course documentation and reliable implementation.
Use NESA's current Stage 6 assessment-program guidance when reviewing the formal program, then verify course-specific requirements on the applicable course page.
Show Program Evaluation
Annotations should demonstrate that the program is a live record. Strong examples link evidence to an action:
- “Common error in interpreting the residual plot; added comparison example before the investigation.”
- “Two lessons lost to disruption; networks review moved and assessment preparation adjusted within notified requirements.”
- “Alternative valid solution identified during marking; guideline clarified and affected scripts reviewed.”
Avoid rewriting annotations months later to make the document appear complete. A regular faculty review rhythm produces more credible and useful evidence.
Choose Student Work Samples That Show Delivery
Student work samples should help a reviewer follow the enacted curriculum, not advertise only the faculty's strongest result. Start from the program or learning sequence, then identify ordinary work that demonstrates what students were asked to learn and how the teacher responded.
A useful sample set for one unit may include:
- an early diagnostic or prerequisite check
- a routine class task showing the taught method
- a more demanding application or investigation
- work from different points in the achievement range
- teacher feedback or a student correction where available
- the associated task, solution or criteria
- a short reference back to the relevant program section
The number and form of samples should follow the current manual, the actual NESA request and school direction. This article does not prescribe a universal sample count. “Across a range” is also not permission to create a public display of identifiable student records.
Keep context with the sample. A response without the question, conditions or criteria can be misread. A mark without feedback may show recording but not the teaching response. A beautiful project from three years ago does not demonstrate delivery for the current cohort or syllabus version.
Use the school's authorised storage and access controls. Do not email sensitive scripts to a personal account, create a public link, or copy an entire student record when a bounded sample is requested. Record where the authoritative file lives and who can grant access. If the school decides to anonymise a copy, preserve enough context to connect it correctly without exposing unnecessary personal information.
Where a sample shows an error in teaching material or marking, do not hide it. Record the correction, who reviewed affected work and what changed in the program under the school's process. A visible evidence-to-action chain is more useful than a spotless archive that does not resemble normal delivery.
Check Resources and Equipment
The individual-school manual states that resources and equipment must be available for each course provided. For mathematics, evidence may include access to appropriate teaching resources, approved calculators where relevant, graphing or statistical tools used by the course, and arrangements supporting students' learning needs.
Do not turn this into an invented NESA inventory template. Record what the school actually uses, where it is available, how faults or shortages are addressed and how the resources relate to course delivery.
Keep Faculty and Whole-School Ownership Clear
Some evidence belongs primarily to school leadership or administration, including registration certificates, governance, whole-school policies, staffing records and premises. Some is shared, such as assessment procedures and records. Some is faculty-owned, such as course maps, programs and task materials.
Use an ownership table:
| Item | Accountable owner | Faculty contribution | |---|---|---| | Registration/accreditation application | Principal or delegate | Accurate course information | | Assessment policy | School leadership | Course schedule and implementation evidence | | Staff accreditation records | Approved school process | Confirm teaching allocation only | | Curriculum documentation | Head teacher/faculty | Current, aligned programs and evaluations | | Student achievement records | School and faculty systems | Accurate marks, feedback and work samples |
This avoids faculties copying sensitive whole-school material into local folders.
For a maintainable course-review rhythm, use the head teacher guide to HSC maths faculty programming. When the evidence gap concerns task construction rather than document storage, work through how to write an HSC maths assessment task against the applicable course page and school policy.
Run a Proportionate Readiness Review
Use three statuses:
- Traceable: current evidence exists and the chain can be followed.
- Needs clarification: evidence exists but naming, links or ownership are unclear.
- Gap: a required school process or record appears absent and must be escalated.
Prioritise wrong syllabus versions, missing HSC assessment records, absent program-to-student-work links and unclear ownership. Cosmetic formatting comes later.
A Six-Week Readiness Checklist
This sequence assumes the school has scheduled an internal readiness review six weeks before an expected inspection or registration milestone. A short-notice inspection may provide less time, which is why the normal system needs to stay current. The principal or delegated school lead controls the actual response.
Week 6: confirm scope and ownership
- obtain the current NESA correspondence and identify the applicable manual
- confirm whether the school is an individual non-government school or part of a registration system
- identify the inspection or application scope; do not assume every manual section is a faculty request
- name the school lead, faculty lead, evidence owners and secure working location
- record questions requiring advice rather than guessing at answers
Output: a one-page scope, responsibility and escalation map approved by the school lead.
Week 5: verify course identity and curriculum maps
- list every mathematics course, cohort, syllabus version, teacher and allocated time
- compare scope and sequence, program headings and formal assessment documents
- flag legacy outcome codes, missing units and inconsistent file names
- choose one vertical sample unit per course for deeper tracing
Output: a course register and prioritised gap log. Correct wrong-version risks first.
Week 4: trace teaching and student work
- follow each selected unit from official syllabus reference to sequence, program, activity and student evidence
- locate contextualised student work samples under the authorised access process
- check that feedback and program evaluation are visible where expected
- record absent links as actions with owners and dates
Output: a traceability index that points to authoritative records rather than duplicating them.
Week 3: review assessment and HSC records
- reconcile the approved schedule with notifications, tasks, marking guidelines and results
- sample evidence of task checking, moderation and secure mark recording
- confirm where illness or misadventure, malpractice, appeals and N-determination records are managed
- escalate any material gap through the school's approved process
Output: an assessment assurance note and an escalation record for unresolved issues.
Week 2: test access and explainability
- ask a colleague who does not own the course to follow the evidence map
- repair broken permissions, ambiguous names and stale links
- rehearse concise explanations of normal faculty processes without coaching staff to speculate
- verify that sensitive data is not unnecessarily copied into the working folder
Output: a tested index and a short list of legitimate unresolved matters with owners.
Week 1: freeze the review copy and continue normal records
- confirm requested documents with the school lead
- record the date and version of the evidence index
- ensure nominated staff know the practical access arrangements
- continue contemporaneous teaching, assessment and program annotations
- avoid last-minute retrospective rewriting that obscures what actually occurred
Output: a controlled review set linked to live authoritative systems, plus a current change log.
After the milestone, hold a short debrief. Record which evidence was hard to locate, which duplicate archive caused confusion and which routine should change. Assign owners and review the improvements in the normal faculty calendar rather than waiting for the next inspection.
Questions to Ask Before Sign-Off
- Are we using the February 2026 individual non-government-school manual, not a different sector manual?
- Can each course be identified by cohort and syllabus version?
- Can we trace outcomes and content into sequence, teaching, assessment and student work?
- Do programs reflect delivered teaching and current evaluation?
- Are assessment records held securely under the school's policy?
- Can ordinary day-to-day student work be located without creating a special portfolio?
- Have whole-school gaps been escalated to the accountable owner?
Inspection readiness is best treated as a quality-of-system check. When the evidence chain is maintained through normal teaching, the faculty gains something more valuable than a compliant folder: it gains a program that can be reviewed, handed over and improved.