The week before Census Day is not the time to start building NCCD evidence. It is the time to check what already exists, close small gaps, and help staff feel clear about what still needs attention.
This NCCD Census Day Checklist for Coordinators is written for the person holding the whole-school view. You may be an inclusion lead, learning support coordinator, deputy principal, or NCCD coordinator. Your job is not to rewrite every teacher’s notes. Your job is to confirm that each included student has enough evidence to support the reported category of disability, level of adjustment, consultation, and ongoing review.
Use this as a calm final-week check. It will not replace your education authority’s requirements, but it will help you walk through the key areas with less scrambling.
Start with the students, not the paperwork
The fastest way to review NCCD readiness is to work student by student. A spreadsheet, folder, or platform view is only useful if it helps you answer one question: does the evidence show that this student received reasonable adjustments because of disability-related functional need?
For every included student, you should be able to explain the need, the adjustment, the level, the consultation record, and the evidence period without hunting through five separate places.
A strong final-week process should make gaps visible quickly. If one student has many evidence notes but no consultation record, that is a gap. If another has consultation but no clear adjustment trail, that is also a gap. Volume alone is not readiness.

The coordinator's seven-point Census Day checklist
Use this NCCD Census Day checklist for coordinators as a practical final pass. It works best when you review students by year level, class, or case manager, then flag only the records that need action.
The annual NCCD, described on the NCCD Portal, is a collection about Australian students with disability and the adjustments they receive. The key word for the final week is adjustments — you are checking the link between need, support, consultation, and review.
The 2026 NCCD Guidelines explain that evidence should cover assessed individual need, consultation and collaboration, at least 10 weeks of adjustments where required, and ongoing monitoring and review. That gives you a simple structure for the final-week pass.
There are seven areas worth a final pass for every included student. Student inclusion: confirm the student meets NCCD inclusion requirements — a common final-week issue is a student listed because they receive support, but with disability-related need that is unclear. Disability category: confirm the category matches the main driver of adjustment, not the diagnosis on its own. Adjustment level: confirm the level matches the frequency and intensity of support — Supplementary, Substantial, or Extensive should not be chosen without enough evidence. The 10-week evidence period: adjustments need to be documented across the required period, with dates that hold together rather than scattered or unclear. Consultation: parent, carer, student, or relevant associate consultation should be recorded — verbal consultation is fine, but it has to have been logged. Monitoring and review: evidence should show whether the adjustment helped, not just that it was provided. Evidence storage: the records have to be findable quickly rather than living across emails, drives, folders, and teacher notes.
The 20-minute readiness sweep
For each student, run this quick check. Open the student record. Check the disability category and adjustment level. Confirm the evidence shows the reason for the adjustment. Check dates across the evidence period. Look for consultation. Look for monitoring or review. Then mark the student as ready, needs small fix, or needs coordinator review.
This is where a whole-school view helps. Schools that want a faster way to keep records organised use Superadjust to let teachers log NCCD evidence in seconds while coordinators see evidence gaps before Census Day.
For wider context on evidence quality, the Superadjust NCCD Evidence Centre supports staff who need clearer examples of what strong evidence looks like for each quality pillar.
Check the quality pillars before you check the quantity
A student can have twenty records and still have weak NCCD evidence if those records all say the same vague thing. Your final-week check should focus on coverage across the quality pillars, not just count the number of files.
Think of each record as part of a story. One note may show an adjustment. Another may show consultation. A third may show monitoring. Together, they should make it clear why the student is included and how the school has supported access and participation.
A useful NCCD record should show the student need, the adjustment provided, when it happened, and whether it helped. A few side-by-side examples make the difference clear.
A weak reading-support note might say "supported student during reading". A stronger version says "provided text-to-speech during independent reading because decoding fluency affected access to the task; student completed the comprehension questions with reduced prompting" — it shows the adjustment, the disability-related reason, and the impact.
A weak parent-contact note might say "called parent". A stronger version says "spoke with parent about current reading adjustment and agreed to continue audio-supported texts for the next unit, with a review planned in Week 5" — it captures the consultation and the decision.
A weak adjustment note might say "modified task". A stronger version says "reduced written response load and provided a visual planning scaffold for persuasive writing due to working memory and written expression needs" — it shows why the adjustment was reasonable.
When teachers or leaders are unsure whether their final-week pass is hitting every quality pillar, the Census Day week-before checklist inside the Evidence Centre is a useful internal reference to walk staff through before sign-off.

Review adjustment levels, consultation, and Census Day readiness
The final week is where level decisions need careful attention. The NCCD level should reflect the frequency and intensity of reasonable adjustments, not the loudness of the student's need, the amount of teacher concern, or the presence of a diagnosis alone.
The Disability Standards for Education resources are useful for grounding staff in the idea that adjustments are about access and participation on the same basis as other students. For NCCD, your evidence should show what the school did in response to disability-related functional need.
Adjustment level review
Ask these questions before sign-off. Does the evidence match the reported level of adjustment? Is the student receiving QDTP, Supplementary, Substantial, or Extensive support? Is the level based on what was provided, not what might be needed later? If the student moved levels during the year, is the final decision explained? For higher levels, does the evidence show frequency, intensity, and review?
Consultation review
Consultation does not need to be written like a formal legal document. It does need to be findable. A short file note can be enough if it shows who was consulted, what was discussed, and how the information shaped support.
Good consultation evidence may include parent meeting notes, email summaries, student voice, phone call notes, support group records, or specialist input. What matters is that the record connects consultation to the adjustment decision.
What to fix in the final week
The final week is for targeted fixes, not wholesale rewriting. Focus on records that are almost ready but missing one clear piece. A coordinator can usually make the biggest difference by giving teachers a precise request instead of a general reminder.
Instead of saying, "please update your NCCD evidence", say, "please add one dated note showing how the writing scaffold helped Mia complete the persuasive paragraph task". Specific requests save time and improve the record.
Final-week fix list
Match each pattern to a precise ask. If you find an adjustment listed with no reason, ask for the disability-related functional need to be added. If a parent meeting happened but is not recorded, ask for a short consultation note with the date and outcome. If the 10-week period is unclear, ask for dated records to be added or located across the evidence period. If a level feels too high or too low, walk back through the evidence against the level descriptors. If monitoring is missing, ask for a brief note on student response or progress. If evidence is scattered, save the key records in the agreed student file or system.
For schools that want to fold this final-week check into a wider rhythm — teacher logging, coordinator review, gap follow-up, then Census Day sign-off — Superadjust coordinator software gives coordinators a practical view of evidence gaps, staff follow-up, and Census Day readiness across the whole student list.
A useful coordinator script for the week: I am not asking you to create new evidence from scratch. I am asking you to record what already happened clearly enough that the student's support can be understood later.

Build a calmer Census Day rhythm next year
A good Census Day check should feel like confirmation, not rescue. If the final week feels heavy, use that information. It tells you where the system needs a better habit next year.
The best NCCD systems make evidence logging part of ordinary teaching. Teachers record adjustments when they happen. Consultation is noted close to the conversation. Coordinators check gaps during the term, not only in August.
That rhythm protects everyone's time. More importantly, it gives a clearer picture of how students are being supported across the year.