Skip to content

Superadjust launches June 13

SuperadjustSuperadjust
Evidence & Adjustments

NCCD Evidence Quality: What Auditors Actually Look For

SA
Superadjust TeamNCCD Resource
26 February 2025
·
9 min read
Back to Blog

A thick folder does not automatically mean strong evidence. For NCCD Evidence Quality, the real test is whether another person can understand the student need, the reasonable adjustments provided, the consultation that informed those adjustments, and the monitoring that shows whether support helped.

That matters because NCCD is not asking teachers to prove they care. Teachers already adjust lessons, scaffold tasks, speak with families, and track progress every week. The challenge is making that everyday work visible in a way that holds up when a coordinator, principal, system reviewer, or auditor needs to check the record.

This article explains what strong NCCD evidence usually contains, why weak records fall short, and how schools can build better evidence without turning teachers into paperwork clerks.

What auditors usually check in NCCD evidence

Auditors are not looking for perfect prose. They are looking for a clear, reasonable trail. Can the school show that the student has an identified disability-related need? Can it show that reasonable adjustments were provided? Can it show consultation and review? Can the chosen level of adjustment be understood from the evidence?

The official NCCD Portal describes the NCCD as an annual collection of information about Australian school students with disability and the adjustments they receive. The Disability Standards for Education 2005 explain the legal context for supporting students with disability to access and participate in education on the same basis as other students.

In plain English, the evidence should answer this question: "What did the school know, what did it do, and how did it check whether the support was working?"

Strong NCCD evidence is not just a note that support happened. It shows the student need, the adjustment, the reason for the adjustment, the date or period, and the review point. A short record that connects those five things is usually more useful than a long file with none of them clearly linked.

The four parts of strong NCCD Evidence Quality

NCCD Evidence Quality improves when each record connects four things: identified need, adjustment, consultation, and monitoring or review. These are often described as evidence areas or quality pillars. They do not need to sit in four separate documents, but they do need to be clear somewhere in the school's records.

For a deeper explanation of what evidence can look like across different student scenarios, the Superadjust NCCD Evidence Centre is the natural next step. If the issue is whether the level is QDTP, Supplementary, Substantial, or Extensive, the NCCD adjustment levels guide is a useful companion reference.

Each evidence area gets stronger when teachers move from generic notes to specific ones. A weak identified-need note might say "student struggles with writing"; a stronger version says "student's dysgraphia affects handwriting speed and written output during timed tasks". A weak adjustment note might say "helped in class"; a stronger version says "provided speech-to-text for written reflection and allowed oral planning before drafting". A weak consultation note might say "spoke to parent"; a stronger version says "parent confirmed writing fatigue at home; agreed to trial speech-to-text and review in Week 6". A weak monitoring note might say "seems better"; a stronger version says "after four weeks, student completed longer written responses with less fatigue; continue trial next term".

NCCD guidance explains that evidence should be generated through the ordinary course of determining student needs and responding to them. Schools do not need to create a separate paperwork system just for the sake of it. They need retrievable, credible records that show the work already happening.

What this looks like in practice

A Year 6 teacher notices that a student with a diagnosed specific learning disorder avoids independent reading tasks. The teacher records that the student has difficulty decoding longer text, provides text-to-speech during reading rotations, checks comprehension verbally, and speaks with the parent about how the same support works at home.

That one sequence can support several evidence areas. It shows need, adjustment, consultation, and review. It also gives the NCCD coordinator enough context to understand why the adjustment is reasonable.

Instead of writing "reading support provided", a teacher could write "provided text-to-speech during independent reading because decoding fatigue affects comprehension; student answered verbal comprehension questions with improved accuracy". The richer record turns a vague action into a clear story another reviewer can follow.

Four connected NCCD evidence areas shown as need, adjustment, consultation, and review.

Strong vs weak evidence examples

Weak NCCD evidence usually has one of three problems. It is too vague, too isolated, or too disconnected from the student's disability-related need. A note can be truthful and still not be useful enough for review.

Strong evidence does not need to be long. It needs to be specific. A two-sentence note written close to the lesson is often more useful than a polished summary written months later.

A few side-by-side examples make the difference clear. For task support, "supported student with maths" becomes "used number line and worked example during fractions task because working memory difficulty affects multi-step calculation". For behaviour support, "student had a bad lesson" becomes "used planned regulation break after signs of escalation; student returned after five minutes and completed modified task". For consultation, "Mum contacted" becomes "discussed trial of reduced written load with parent; parent reported homework fatigue and agreed to review after three weeks". For progress review, "improving" becomes "student completed 4 of 5 scaffolded tasks independently this week, compared with 1 of 5 before visual checklist was added".

For schools building a shared standard, it can help to create a few accepted examples. Keep them short. Show teachers what "good enough and useful" looks like. The goal is not a perfect paragraph. The goal is a record that another staff member can understand without needing the teacher to explain it verbally.

Strong and weak NCCD evidence comparison shown with complete and incomplete record cards.

A practical quality check for teachers and coordinators

The easiest way to improve NCCD Evidence Quality is to check each record against a simple test: need, action, reason, review. If one of those pieces is missing, the record may still be useful, but it may not be enough on its own.

Teachers can use this as a 15-second review before saving a note. Coordinators can use it during moderation, internal file checks, or week-before-Census review.

The NARR quality check

For each record, ask four short questions. Need: what student need is being addressed — reading fluency, sensory overload, processing speed, anxiety during assessment? Action: what adjustment was provided — visual checklist, reduced written load, extra processing time, alternate response mode? Reason: why was that adjustment reasonable — does it connect to a disability-related impact rather than a generic preference? Review: what happened next — progress, changed strategy, parent feedback, student response, continued support?

The NCCD coordinator role guide inside the Evidence Centre can help schools think about this at a whole-school level, especially when evidence sits across classrooms, learning support notes, emails, plans, and meeting records.

A useful coordinator prompt sets the standard: if a teacher left tomorrow, could another staff member understand why this student was included, what adjustment was provided, and why the chosen level makes sense? If the answer is yes, the evidence set is doing its job.

A school does not need every record to answer every question. The evidence set should answer them collectively. One entry may show the adjustment. A meeting note may show consultation. A progress note may show review. The problem starts when no part of the file clearly explains the connection.

For schools that want a faster way to keep evidence organised, Superadjust evidence logging for teachers helps teachers log NCCD evidence in seconds while keeping the record connected to the student, adjustment, and review point.

How to make evidence easier to review before Census Day

The week before Census Day is not the time to start building NCCD evidence from memory. It is the time to check the trail. Coordinators should look for missing links, not rewrite every record.

Start with students whose evidence looks uneven. That may include students with strong adjustment notes but no consultation record, students with a plan but little monitoring, or students whose level of adjustment does not match the intensity of support shown in the file.

The Australian Government Department of Education provides national schooling context, while state and sector guidance may give additional process details for how schools manage NCCD locally. Keep your school's internal process aligned with your system requirements, but keep the evidence readable for real humans.

Week-before-Census evidence review

Before sign-off, check that each included student has evidence of disability-related need. Confirm reasonable adjustments are recorded over the relevant period. Check consultation with the student, parent, carer, guardian, specialist, or relevant staff where applicable. Look for monitoring or review notes that show whether support helped. Make sure the level of adjustment matches the frequency, intensity, and type of support. Flag gaps early enough for teachers to clarify recent evidence while it is still fresh.

Common evidence gaps to fix first

Some gaps matter more than others because they make the evidence hard to interpret. A missing date can often be clarified. A missing link between the student need and the adjustment is more serious, because it makes the support look generic.

Prioritise these fixes in order. First, vague adjustment language — replace "support given" with the actual adjustment. Second, no reason for the adjustment — connect it to the student's disability-related functional need. Third, missing consultation — add the parent, student, specialist, or staff discussion where it exists. Fourth, no review point — add what changed, what helped, or what needs to be tried next. Fifth, level mismatch — check whether the evidence supports the selected level of adjustment.

Coordinator reviewing NCCD evidence quality and readiness before Census Day.

Build a standard teachers can actually follow

NCCD Evidence Quality improves when teachers know exactly what a useful record looks like. A school-wide standard should be short enough to remember and practical enough to use mid-lesson.

A simple sentence pattern carries most of the work: "Because [student need], I provided [adjustment] during [learning activity]. The student [response or review point]."

A working example might read: "Because the student's processing speed affects written assessment, I provided extra planning time and a visual prompt sheet during the science task. The student completed the explanation with fewer teacher prompts than last week."

That is not long. It is not formal. It gives the reviewer what they need.

Strong NCCD evidence does not depend on teachers writing more. It depends on teachers recording the right details at the right time. When the evidence shows need, adjustment, consultation, and review, the school has a clearer record of the support it is already providing.

See how Superadjust makes NCCD evidence a 3-second habit.

See how Superadjust makes NCCD evidence a 3-second habit.

No account needed. No demo required.