Find NCCD gaps
- Scan the Audit Report for thin records.
- Check the Evidence Log for files and owners.
- Review Plan Coverage for missing levels or categories.
- Open Adjustments with Attachments for missing files.
- Review student activity for active students not included.
- Assign the next action in plain teacher language.
Make the next conversation obvious: which student, which record, which proof, which staff member.
What each word means in plain English
- EvidenceA note, plan detail, file, photo, meeting record or work sample that shows what support was provided.
- AdjustmentA change a teacher makes so a student can access learning. It might be extra time, visual prompts, a modified task, seating support, assistive technology or a different way to show learning.
- AttachmentA supporting file connected to the record, such as a learning plan, timetable, meeting note, assessment sample, email, image or observation record.
- Student activityA sign that staff have been working with the student in Junipa. Activity is not proof by itself, but it tells you where to look next.
- Not includedA student or record is not counted in NCCD reporting yet. That may be correct, but someone should check why before census week.
Start with the Reports hub
The school Reports hub is the starting point. Use it to move quickly between Audit, Evidence Log, Plan Coverage, Student activity and Adjustments with Attachments instead of checking student records one by one.
Start broad. Then narrow down.
For a teacher, the useful question is simple: "Which students do I already support, and what is missing from the record?" The Reports hub helps you answer that before you open every student profile.
Find report gaps in the Audit Report
The Audit Report gives you the broadest evidence view first. Use it to check which students have evidence recorded, which adjustment levels are represented, and where records need attention before a formal review.
Look for:
- Students with sparse evidence.
- Students whose adjustment level has changed.
- Students with adjustments or activity but no clear NCCD reporting position.
- Evidence that does not clearly explain the adjustment being made.
- Records that have been excluded or marked not included and need a deliberate decision.
The uncomfortable rows are the useful rows. They show where the school still has time to clean up the story.
Use the Evidence Log when you need proof
The Evidence Log is the chronological view. It is useful when you need to answer a more specific question:
- What evidence was recorded for this student?
- Who added it?
- Was a file attached?
- Is there a linked case note?
- Has anything been excluded from reporting?
That detail matters because census readiness is not only about having evidence. It is about being able to explain why the evidence supports the adjustment level.
Use the teacher test: would a colleague who does not teach this student understand what happened, when it happened, and why it matters for learning access?
Check adjustments with attachments
Open Adjustments with Attachments when you need to see whether planned adjustments are backed by evidence attachments. This is the report that makes the gap plain: the adjustment exists, but the supporting attachment count may not.
Use the summary cards first. If the number of adjustments is higher than the number with attachments, you have a practical follow-up list.
Then check the row detail:
- Evidence tells you whether an adjustment has evidence connected.
- Attachment tells you whether that evidence has supporting files.
- Last evidence tells you how recent the supporting record is.
- Recorded by gives you the staff member to follow up with.
This is the report to use when the conversation is concrete. If the record says a student receives a modified task, attach the modified task. If the record says the student has a seating plan, attach the plan or the relevant note. If the record says regular check-ins are happening, add the case note that shows what changed and why.
Look at Student activity before you decide a student is fine
Student activity is where you catch the students who are active in the system but still need a reporting decision.
Look for students who have case notes, adjustments, plan edits, evidence records or attachment activity, but are not included in NCCD reporting yet. They may be correctly not included. They may also be the students most likely to be missed if the review only starts from the final census list.
That is the courage part. Do not only check the tidy list. Check the students sitting just outside it.
Do not use activity as the final answer. Use it as the signal to follow up. A student with regular activity may need stronger evidence, a clearer adjustment, or a deliberate decision that they should stay out of the census list.
Check Plan Coverage before you chase individual records
The Plan Coverage view helps you see whether plans and evidence are distributed across the school in the way you expect. It breaks coverage down by year group, so you can spot patterns before opening individual student records.
Use it to find:
- Year groups with students missing NCCD levels.
- Cohorts with disability categories still unclassified.
- Students with plans but no evidence.
- Evidence coverage that looks too light for the adjustment level being claimed.
Treat the gaps as a to-do list, not a blame list. Plan Coverage helps leaders decide where to help teachers first: one year group, one cohort, one category, or one set of missing records.
Keep student records connected
If your school uses Compass or Wonde, student details can stay in sync from your student information system. That reduces manual record drift, especially around enrolments, year levels and departures.
Before census, check that your integration is still running and that departed or re-enrolled students are showing the way you expect. A reporting gap is sometimes an evidence problem, but it can also be a student record problem.
For the broader product picture, the main Junipa site explains how schools use Junipa across NCCD, evidence, adjustments and school workflows. The Junipa updates page is the place to check recent product changes that may affect reporting work.
A simple weekly review pattern
Run this pattern weekly as census approaches:
- Open the Audit Report and scan for students with weak or missing evidence.
- Open Adjustments with Attachments and find planned adjustments without supporting files.
- Open Plan Coverage and check whether a year group or cohort needs attention.
- Use the Evidence Log to investigate the records that look thin or unclear.
- Check student activity for students with real support activity who are not included in reporting.
- Confirm student details are current if your school syncs through Compass or Wonde.
- Assign follow-up work in your normal school process, then review the same reports again.
Words teachers can use
When asking for evidence: "Can you add the note, file or example that shows this adjustment happened for the student?"
When checking an adjustment: "Is this still what we do for the student, and does the record say it clearly?"
When a student is active but not included: "This student has support activity in Junipa. Can we confirm whether they should be included in NCCD reporting or deliberately left out?"
When the record is unclear: "A person outside this class needs to understand the support from the record. What detail should we add?"
The promise is simple: if the gap is visible early, the school can act before census week turns it into a scramble.
