Common NCCD Evidence Mistakes (and How to Avoid Them)

Why the same mistakes keep recurring

The NCCD asks every school to answer four questions for each student it includes: Is an adjustment provided? What level is it? What category of disability is it addressing? And is there evidence to support all of the above? The model is anchored in the Disability Discrimination Act 1992 and the Disability Standards for Education 2005, and the data is collected against the census reference date — the first Friday in August.

The errors below are not signs of a careless team. They happen because the framework asks staff to translate everyday teaching judgements into a consistent national record, and the gaps usually appear at the seams: between a student's *diagnosis* and the *adjustments actually provided*, between a *plan* and *practice*, and between *doing* the work and *documenting* it. Let's walk through the five that come up most often.

Mistake 1: Imputing disability from academic underperformance

The single most common error is reasoning backwards from results: "This student is failing maths, so there must be a disability we can impute." Imputed disability is a legitimate and important part of the NCCD — your team can impute a disability based on available evidence without a formal diagnosis, *provided adjustments are being made*. But the trigger is the functional impact of disability, not the academic gap itself.

The 2026 guidance sharpened this point. Adjustments must address the functional impact of disability — not academic gaps, behaviour, attendance, or home circumstances on their own. A student who is behind in reading because of disrupted attendance, English as an additional language, or a tough home year does not, on those facts alone, belong in the NCCD.

The fix. Before you impute, name the functional impact in plain language and locate it in one of the eight domains of functioning — for example, *Attention, Executive Function & Self-Regulation*, *Communication*, or *Social, Emotional & Behavioural Wellbeing*. Then ask: what is the school doing differently because of that impact? If you can describe the impact and point to a real adjustment, you have a defensible imputation. If all you can point to is a low mark, you don't. Our NCCD evidence collection guide works through the assessed-individual-need evidence area in more detail.

Mistake 2: Mis-levelling — especially over-recording Extensive

Adjustment levels — Quality Differentiated Teaching Practice (QDTP), Supplementary, Substantial, and Extensive — describe *how much* the school is doing beyond usual practice, recorded at the level provided most of the time. Two patterns recur:

• Diagnosis-driven levelling. A student with a significant diagnosis is recorded at Substantial or Extensive because the label "feels" serious, even though classroom practice sits at Supplementary. The level must reflect the adjustments observable in the school week, not the diagnostic label.
• Inflating to Extensive. Extensive is the most scrutinised level for a reason: it means intensive, sustained, highly individualised support required at all (or nearly all) times. Crucially, Extensive adjustments must be in place at all times — the more forgiving 10-week threshold that applies to the other levels does not rescue an Extensive record that was only partially implemented.

The fix. Run a quick "most of the time" test for every student near a level boundary: across a typical fortnight, what level of adjustment was actually in place for the majority of the student's school time? Moderate borderline cases as a team rather than individually — consistent professional judgement across staff is exactly what the moderation step in the annual cycle exists to build. For a level-by-level breakdown of the evidence each tier needs, see our NCCD adjustment levels guide.

Mistake 3: Thin or retrospective evidence

This one surfaces in Term 3, during validation, when someone realises a student's file is a single plan written in February and nothing since. Two related problems:

• Thin evidence — a plan exists, but there's little or no proof the adjustments were actually *provided* and *reviewed*.
• Retrospective evidence — files assembled hurriedly just before the census, which read as reconstruction rather than a record of practice.

Remember the 10-week rule: for most levels you need evidence that reasonable adjustments were provided for at least 10 weeks within the 12 months before the census. A plan dated in Term 1 with no implementation trail doesn't demonstrate that.

The fix. Spread evidence across all four evidence areas — assessed individual need, adjustments provided, consultation and collaboration, and monitoring and review — and capture it *as it happens*, not in August. The good news is that schools reuse existing records: the NCCD does not require new bespoke paperwork. Lesson-plan annotations, class observation notes, meeting minutes, communication logs, and progress data all count. The annual cycle is designed to keep this current — Planning in Term 1, Implementation in Term 2, Validation in Term 3, and Reflection in Term 4 — so the file grows naturally rather than in a panic.

Mistake 4: Missing or undocumented consultation

Consultation is a distinct evidence area, and it is the one most often left implicit. A vital distinction: parental consent is *not* required to count a student in the NCCD, but consultation is. You must consult with parents and carers — and with the student where appropriate — about the adjustments being made.

The 2026 guidance tightened the documentation expectation here. If consultation did not precede an adjustment, record the reason. A genuine conversation that leaves no trace is, for audit purposes, a conversation that didn't happen.

The fix. Treat every parent meeting, phone call, email, or care-team discussion as consultation evidence and log it: date, who was present, what was discussed, what was agreed. Where an urgent adjustment had to go in before you could consult, note why. This is one of the easiest evidence areas to strengthen because the conversations are already happening — they just need capturing.

Mistake 5: Confusing the plan name with the evidence

Plan names vary by state and sector — IEP, ILP, PLSP, ICP, NEP, PLP. These are just *containers* for the same NCCD-aligned content. Teams sometimes assume that having a plan, of whatever local name, *is* the evidence. It isn't. The plan is one record; the NCCD wants evidence across all four areas, including proof the plan was implemented and reviewed.

The fix. Audit your plan template against the four evidence areas and the five areas of personalised learning and support — Curriculum/teaching and learning; Communication; Participation; Health and Personal Care; and Movement/Mobility. If your container captures need, adjustments, consultation, and review, it's doing its job. If it only captures goals, you'll need to point to other records for the rest.

What to document: a quick worked check

For one student near a level boundary, confirm you can answer all four NCCD model steps with a record attached:

1. Is an adjustment provided? Name it, and the functional impact it addresses (tie it to one of the eight domains).
2. What level? Apply the "most of the time" test; for Extensive, confirm it's in place at all times.
3. What category? Physical, cognitive, sensory, or social/emotional — imputed by the team.
4. Where's the evidence? One record from *each* area: assessed need, adjustments provided, consultation, monitoring/review — spanning at least 10 weeks.

If any cell is empty, you've found your gap before the principal has to attest to it. The principal's attestation covers every student's inclusion, category and level, so the goal across the team is that nothing in that attestation rests on memory alone.

Bringing it together

None of these fixes asks for more meetings or new paperwork — they ask for the records you already create to be captured consistently, contemporaneously, and against the four evidence areas. That's where a single, Australian-hosted student-support record helps: capturing consultation logs, observations, plan reviews and progress notes as they happen makes evidence collection and tracking part of the daily workflow rather than an August scramble, and keeps your file NCCD-ready and aligned with the national data standards.

If you coordinate this work, it's worth seeing how purpose-built documentation can lighten the load — explore Grounded Scribe for Disability Inclusion Coordinators, built by a school-psychologist-founded team with Australian privacy at its core.

Related reading

• NCCD Evidence Collection: A Documentation Guide for Australian Schools
• NCCD Adjustment Levels: A Documentation Guide for Australian Schools
• Grounded Scribe for Disability Inclusion Coordinators