Common NCCD compliance mistakes in a school's process
Ten school-level NCCD mistakes, from inclusion and level choice to moderation and the sign-off pack, and the process fixes that stop them coming back each year.
On this page
Most NCCD compliance mistakes are not caused by a lack of care. They come from the school's process: how students are included, how levels are chosen and checked, where evidence lives, and when anyone looks at it. A process mistake repeats across many files and comes back every year until the process changes.
This guide covers those school-level mistakes and the fix for each. For the gaps inside one student's record, such as a vague note or a missing consultation record, see how to spot and fix NCCD evidence gaps.
New to the NCCD? Start with What is the NCCD?
Ten school-level mistakes to check for
Each of these is a process problem: fix it once, and it stops appearing in file after file.
| Mistake | What it looks like | Why it is risky | The process fix |
|---|---|---|---|
| The label decides inclusion | A diagnosis is treated as automatic proof of inclusion or level. | The NCCD is about functional impact and educational adjustment, not diagnosis alone. | Agree that inclusion rests on a disability under the DDA, diagnosed or imputed, its functional impact, and at least 10 weeks of the school's adjustments. A diagnosis is context, and it is not required. |
| Differentiation counted as an adjustment | Everyday differentiation is counted without a disability-related need behind it. | Not every teaching support belongs in the NCCD. | Agree what a disability-related need looks like. A student with disability supported within QDTP is counted at QDTP; differentiation with no disability behind it is not counted. |
| Levels carried over | Last year's level is copied forward without review. | The school reports the highest level provided for 10 weeks in the 12 months before this Census Day. | Review every level every year, against this year's evidence. |
| Levels chosen by effort or concern | A level reflects how hard a student is to support, or the funding it attracts. | A level the evidence cannot support is hard to defend in quality assurance, and the data is used to calculate funding. | Test levels against frequency, intensity and range in moderation, never against effort or funding. |
| No moderation, or too late | Level decisions rest on one person's judgement, or are checked in the final days. | Decisions are inconsistent between classes and hard to defend. | Moderate a sample in Term 2, and the edge cases again before Census Day. |
| Decisions not recorded | Moderation happens, but nobody writes down the decision or the reason. | The same argument happens again next year, and a reviewer cannot see why. | Record each decision, the evidence behind it and any follow-up. |
| Evidence scattered | Records sit across inboxes, drives, paper folders and teacher notebooks. | The school may have evidence, but not in a form anyone can check quickly. | Agree one place for evidence and one naming rule before the year starts. |
| Late coordinator review | Files are first checked in the last days before Census Day. | Late review creates rushed decisions, missed gaps and staff stress. | Set checkpoints across the year, so gaps are found while they are easy to fix. |
| Sign-off without a ready pack | The principal receives a list, but not a summary of evidence strength and open risks. | Sign-off becomes a trust exercise instead of a verification step. | Bring a one-page summary, the exceptions list and sample files to sign-off. |
| System record does not match | The data entered in the collection does not match the moderated school decisions. | The school reports something it did not decide. | Check totals, levels and categories against the validated list before submission. |
An audit readiness view shows which students are thin in which pillar across the school, which catches several of these early.
How to run a clean review of your process
Start with the student list, but do not stop at it. Sort students into three groups: clearly ready, likely ready but incomplete, and not ready yet. That stops the review becoming one large task, and it lets the coordinator start with genuine risk.
Then look for patterns rather than individual files. If six students are missing consultation records, the fix is not six reminders; it is a better way for consultation to reach the record. If levels are uneven between two classes, the fix is moderation, not a rewrite.
Finally, decide what the principal will need to see: a short summary of readiness, a list of unresolved cases, and confidence that sample files open quickly.
Levels and consistency are the job of an NCCD moderation process. Following up with individual teachers is covered in following up on evidence without chasing.
A review rhythm that prevents last-minute panic
Set one review point in late Term 2 and another early in Term 3. The first catches missing consultation, weak descriptions and level drift. The second confirms that the evidence period and the final moderation decisions are visible before submission.
Where a teacher is already supporting the student well, the coordinator's job is not to create extra work. It is to help that work become visible, findable and ready for validation.
When teachers log adjustments as part of their day, evidence logging for teachers means each review point finds records that are already half-built.
What to bring into principal sign-off
The principal needs a clear school-level picture, not a pile of files. Principal sign-off covers the one-page summary, the samples and the agenda. It helps to flag where the school tightened its process during the year: it shows the review was active, not passive.
Why this matters
NCCD data is used to calculate the student with disability loading, and principals are responsible for its accuracy before it is submitted. Process mistakes are the ones that turn up in many files at once, so fixing them does more for a school's confidence than any amount of last-minute file checking.
What to do next
Run the ten checks against how your school worked this year, pick the two that cost the most time, and fix those first. Then pair this guide with the NCCD Census Day checklist, so the week before Census Day becomes confirmation rather than rescue.
Questions
Read next
- Evidence and documentationNCCD evidence gaps in a student's record, and how to fix themThe gaps that weaken one student's NCCD record, from missing consultation to vague notes and patchy 10-week coverage, and how to fix each without inventing anything.
- For coordinatorsNCCD moderation: how to run it, with a checklist and record templateNCCD moderation is how a school team checks each student's level and category are consistent and defensible. Who runs it, the steps, a checklist and a template.
- For coordinatorsPrincipal sign-off on NCCD data: what to ask, what to bringHow a coordinator prepares principal sign-off on NCCD data, and the four questions a principal should ask from Term 1 to sign-off: summary, samples, agenda, checklist.
Log NCCD evidence in seconds
Free for up to 3 students, no card. A whole school can try the School Plan free for 30 days.