ILP Progress Monitoring in NT Schools: How to Track What's Actually Working

An Individual Learning Plan is a live document, not a once-a-year administrative exercise. Yet in many NT schools, the ILP is reviewed formally at semester intervals—and between those reviews, parents often have no visibility into whether the adjustments are being implemented or whether the goals are being met. By the time the review arrives, months of potential learning time have passed with no accountability.

Effective progress monitoring doesn't require complex systems. It requires clear goals with measurable targets, an agreed method for collecting data, and a commitment from both school and parent to review it at regular intervals.

What the NT DoE Requires

Under the NT DoE's Students with Disability Guidelines, ILPs must be reviewed at minimum once per semester. Schools are required to upload agreed adjustment plans and medical evidence to the Support Services Information Database (SSID) or the Student Achievement Information System (SAIS) after each review. This documentation is used both to maintain continuity when staff turn over and to validate the school's NCCD classification for funding purposes.

The formal review process should include:

• Review of goal progress (were targets met, partially met, or not met?)
• Updated NCCD classification if the student's needs have changed
• Revision of goals for the next period
• Parental consent re-signed if SWIPS or external practitioners remain involved

In practice, many NT schools treat the semester review as a brief administrative checkpoint rather than a genuine progress conversation. Knowing what to bring to these reviews—and what data to request—makes a significant difference.

What Good Progress Data Looks Like

A goal written without a measurement method has no progress data. This is why every ILP goal should specify how progress will be measured. Common measurement methods in NT schools include:

Teacher observation records: A daily or weekly tally of specific behaviours or skill demonstrations. Simple and practical for classroom teachers. Example: tracking how many times per day the student successfully uses their break card (the replacement behaviour) versus swiping materials off the desk (the challenging behaviour).

PM Benchmark and standardised reading assessments: Provides objective, norm-referenced data on reading progress at regular intervals. Useful for literacy goals.

Skill checklists: Structured observation of specific adaptive or academic skills. A checklist of the five steps in the morning routine, for example, with the number of steps completed independently recorded each day.

Speech pathology session notes: If a SWIPS speech pathologist or NDIS-funded therapist is providing sessions, their session notes are progress data. Request copies of these notes at the semester review.

Attendance records: For anxiety or school refusal, attendance data is a meaningful progress measure.

How to Monitor Progress Between Formal Reviews

You don't have to wait until the semester review to know if the plan is working. Build informal monitoring into your routine:

Weekly parent-teacher communication: Even a brief weekly note or app message ("How many times did Jake use his break card this week?") gives you real-time data without demanding a formal meeting.

Parent observation log: Keep your own dated record of what you observe at home. Changes in stress levels before school, homework completion patterns, social engagement, sleep quality. This data is relevant context at the review meeting.

Threshold triggers: Agree with the school in advance on what would trigger an unscheduled early review—for example, if the challenging behaviour frequency increases by 50% over a two-week period, or if the student's reading benchmark drops a level.

NDIS therapist liaison: If your child has NDIS-funded therapy, maintain communication with the therapist between reviews. They'll flag if they're seeing skill regression that's inconsistent with what the school is reporting.

A Simple Progress Monitoring Template

This is the minimum structure for tracking a single ILP goal:

Goal: [Student] will correctly identify and label their emotional state using the Zones of Regulation framework, choosing the appropriate zone in 4 out of 5 prompted opportunities, as measured by teacher daily observation record—up from current baseline of 1 out of 5 (Term 1).

Review date: End of Term 2

Data collected: Teacher observation tally — dates and results

• Week 1: 2/5
• Week 2: 2/5
• Week 3: 3/5
• Week 4: 3/5
• Week 5: 4/5

Review outcome: Goal met. New goal to be set for independent (unprompted) emotional identification in Term 3.

Not every goal will be this straightforward, but this structure provides a clear record that can be shared at the formal review, compared against the baseline, and used to justify a new goal or a change in strategy.

When Goals Aren't Being Met

If you arrive at a review meeting and goal progress is minimal, the question to ask is: why?

Common reasons goals aren't met in NT schools:

The adjustment wasn't implemented consistently: The strategy was agreed but the classroom teacher changed mid-term (common in NT), the substitute teacher didn't know the plan, or the ES worker supporting the student was pulled to another classroom. This is a resourcing and accountability failure, not evidence that the goal was wrong.

The goal was set too high: The baseline wasn't properly established or the target was ambitious. The goal needs to be revised with a more accurate current baseline.

The function of the behaviour changed: Common in developmental stages. A strategy built around one behavioural function may stop working when the underlying need changes.

SWIPS or specialist involvement didn't happen: The ILP listed fortnightly SWIPS visits, but the SWIPS team's schedule changed and visits reduced to once a term. The support reduction needs to be explicitly documented.

In each case, the response is different. The key is to diagnose the reason before revising the goal or the strategy—not to simply write a lower target.

Progress Monitoring and NT Staff Turnover

NT schools have some of the highest teacher turnover rates in Australia. When a teacher who knows your child's ILP leaves mid-year, progress monitoring data is often lost or reset.

Protect against this by:

• Requesting that all ILP progress data be uploaded to SSID/SAIS at the end of each term, not just each semester
• Asking the school how it briefs incoming teachers on existing ILPs
• Providing a one-page student summary document directly to any new teacher—teacher change doesn't suspend your right to have the ILP implemented

What to Ask for at the Semester Review

Bring these questions to every formal review:

1. What data was collected against each goal, and can I see it?
2. Were all adjustments implemented as documented? If not, why?
3. Based on progress data, do any goals need to be revised?
4. Has my child's NCCD classification changed? If so, what evidence supports the change?
5. What are the goals and strategies for next semester?
6. Are all staff who interact with my child briefed on the current ILP?
7. What's the plan if the classroom teacher or ES worker changes next term?

Asking these questions—and receiving documented answers—is what turns an ILP review from a formality into an accountability mechanism.

The Northern Territory Disability Support Blueprint includes a complete ILP progress monitoring framework for NT schools—with goal review templates, data collection tools, and a checklist for the semester ILP review meeting.

See more Australia homeschool guides →