Submit an outcomes-focused progress or plan reassessment report that links every moving support you delivered to the participant’s actual NDIS goals, backs each claim with a current functional measure, and lodge it well before the review meeting. That’s the whole game. NDIS guidance recommends submitting these reports at least eight weeks before the scheduled plan reassessment meeting, giving the NDIA planner time to actually read and act on your evidence rather than skim it the night before.
Before you write a word, park these basics in your head:
- Link every support to a specific goal, using the participant’s own goal wording.
- Use at least one objective, dated assessment measure, not just narrative description.
- Attach supporting documents (incident reports, shift notes, allied health reports).
- Quantify your recommendation (hours, frequency, line item) rather than describing it in general terms.
Pro Tip: Set a calendar reminder for eight weeks out from every plan reassessment date the moment a new plan starts. Report writing always takes longer than you think, and NDIA and NDIS both use the same eight-week benchmark for a reason.
Key Takeaways
Reports that link goal-specific, dated evidence to quantified support recommendations and land eight weeks before the review consistently outperform vague, late submissions.
| Point | Details |
|---|---|
| Lead with a summary | Open the report with a two-line summary of the headline outcome and recommendation. |
| Submit eight weeks early | Lodge reports at least eight weeks before the plan reassessment meeting for full planner review time. |
| Quantify every recommendation | State hours, frequency, and line items rather than describing supports in general terms. |
| Attach objective evidence | Include assessment scores, incident reports, and shift notes, not narrative alone. |
| Use EasyMove Services for evidence | Live tracking and NDIS-aware moving logs from EasyMove Services generate dated, attachable proof of supports delivered. |
Where to go for official templates and guidance
- Guide to report writing | NDIS
- Plan reassessment report guidance | NDIS allied health
- NDIS progress report templates | SecondShift
Table of Contents
- What do NDIA planners actually look for in outcome evidence?
- What should a plan reassessment report include?
- How do you show outcomes with objective measures?
- What does the research say about timing and planner behaviour?
- How and where do you submit the report and attachments?
- What mistakes commonly weaken these reports?
- How EasyMove Services helps you build the evidence pack
- Sources
- FAQ
What do NDIA planners actually look for in outcome evidence?
Planners aren’t grading your writing style. They’re deciding whether a support is reasonable and necessary, and that decision rests on functional impact, not diagnosis. A report that states “participant has a spinal cord injury” tells a planner nothing actionable. A report that states “participant cannot lift boxes above shoulder height without pain flare and requires two support workers for any relocation task” gives them something to fund.
Under the PACE system, planners work through evidence packs under real time pressure, which means clarity beats cleverness every time. Short headings, scannable evidence blocks, and a summary up top all increase the odds your report gets read properly rather than triaged.
What planners consistently prioritise:
- Recent, objective measures over vague clinical opinion.
- Concrete examples of daily functioning, not abstract descriptions of impairment.
- A clear, explicit line between the support delivered and the goal it serves.
- Recommendations tied to reasonable and necessary criteria under the NDIS Act, not just clinical preference.
What should a plan reassessment report include?
A reassessment or progress report needs a predictable shape so a planner can find the decision-critical parts fast. Structure yours in this order:
- Two-line summary — the headline outcome and the headline recommendation, before anything else.
- Service details — provider name, service type, dates of service.
- Participant goals — copied verbatim from the current plan, not paraphrased.
- Baseline functional capacity — what the participant could and couldn’t do at plan start.
- Assessment tools used — name, date, and score for each measure applied.
- Supports provided — dates, frequency, and hours delivered.
- Progress by goal — objective, dated statements against each goal individually.
- Barriers and mitigating actions — what got in the way, and what you did about it.
- Risks and incident summary — anything safety-relevant that occurred during service delivery.
- Recommendations — quantified supports for the next period (hours, frequency, line item).
- Community and mainstream links — any non-NDIS supports connected during the period.
- Consent and privacy statement — confirming the participant agreed to this information being shared.
Attach whatever backs the narrative: allied health reports, a Functional Capacity Assessment, incident reports, support worker observations, and shift notes. If the participant’s moving supports are already written into their plan, reference that wording directly rather than inventing new language for the same support.
How do you show outcomes with objective measures?
Vague praise convinces nobody. “Participant has made good progress with the move” is the kind of sentence a planner has read a thousand times and trusts less each time. What works instead is a dated, measurable statement: task, support level, and change, in that order.
A few validated tools worth referencing when they suit the goal:
- Timed Up and Go (TUG) for mobility-related goals, particularly relevant when a relocation involved stairs, uneven access, or a change in home layout.
- Modified Barthel Index for activities-of-daily-living goals affected by the move, such as independent access to a new bathroom or kitchen.
- Goal Attainment Scaling for tracking progress on a participant-defined outcome across the reporting period.
Sample sentence template: “As of [date], [participant] completed [task] with [level of support], compared to [baseline level of support] at [plan start date] — a reduction of [X] support hours per week.”
| Baseline (plan start) | Intervention | Objective result | Recommended next support |
|---|---|---|---|
| Required two support workers for all packing and lifting tasks | Structured packing plan with specialty handling for fragile items over 8-week move | Independently managed light packing tasks; two-worker support needed only for heavy furniture | One support worker, 4 hours per fortnight for heavy-item assistance |
| Unable to navigate new home layout without prompts | Guided orientation sessions during and after move-in | Navigates kitchen and bathroom independently after 3 weeks | Reduce orientation support from weekly to as-needed |
What does the research say about timing and planner behaviour?
The single highest-leverage move you can make is timing. NDIS guidance is explicit: lodge reassessment evidence at least eight weeks before the meeting. Miss that window and even excellent evidence risks being skimmed rather than properly weighed.
Under PACE, planners lean more heavily on written packs than on interview impressions, which means a well-structured report often carries more weight in the outcome than anything said in the room. Practitioner experience also suggests plan reassessments are frequently won or lost on how clearly the written evidence links clinical findings to everyday functional need, rather than on the strength of the clinical findings alone.
Pro Tip: Confirm every attachment is uploaded and named correctly before you submit, then send a short note to the participant’s support coordinator flagging that the report has gone in. A dropped attachment is the single most avoidable delay in this whole process.
How and where do you submit the report and attachments?
Getting the content right only matters if it lands in the right place, in the right format, on time. Follow this sequence:
- Assemble the full report plus every attachment (assessments, incident reports, shift notes, allied health letters).
- Confirm the participant has given consent for this information to be shared, and record that consent in writing.
- Upload everything through the my NDIS provider portal, or send it via whatever method the request for service specifies.
- Notify the participant’s planner and support coordinator directly that the report has been submitted, rather than assuming the portal upload alone will flag it.
Support coordinators already work to a defined reporting rhythm: an initial implementation report around eight weeks into the plan, regular mid-term updates, and the plan reassessment report itself. Adapting an existing progress-report template for moving-specific outcomes is far faster than writing from a blank page, and it keeps your formatting consistent with what planners already expect to see.
Before you hit submit, run a final sweep:
- File names should identify the participant, report type, and date, not “Document1.pdf”.
- Every goal in the current plan should have a matching progress block, even if the update is brief.
- PDF format for the final report avoids formatting shifts across devices.
What mistakes commonly weaken these reports?
A handful of avoidable errors show up constantly, and each one gives a planner a reason to pause or request clarification rather than approve.
- Vague language. “Doing well” tells a planner nothing. Replace it with dated, measurable statements every time.
- Missing dates or scores. An assessment without a date is unverifiable; always attach both.
- An outdated Functional Capacity Assessment. An FCA older than 12 months reads as stale evidence and often prompts a request for an updated one.
- Unquantified recommendations. “More support with moving tasks” won’t get funded the way “4 hours per fortnight of specialist packing assistance” will.
- Missing attachments. A report that references an incident but doesn’t attach the incident report invites a clarification request, which slows everything down.
Each of these is exactly the kind of gap that triggers an internal review request later, and successful reviews almost always need new, gap-specific evidence rather than a resubmission of what was already knocked back.
A provider’s note on getting this right
Consistency beats brilliance here. Providers who save goal-linked shift notes in the same format every time, dated and tied to a specific plan goal, cut report preparation time dramatically and produce stronger evidence without extra effort. You don’t need to attend the review meeting to influence its outcome. A well-timed written report does most of the work on its own.
How EasyMove Services helps you build the evidence pack
Good reporting depends on good records, and that’s where most of the manual effort goes. EasyMove Services builds NDIS-compliant moving and packing support around exactly the documentation a reassessment report needs, so you’re not reconstructing a timeline from memory three weeks before a deadline.
Our specialised NDIS moving supports come with live tracking that timestamps every stage of a relocation, giving you objective, dated evidence you can attach directly to a progress report. Coordinators get reporting tools built for exactly this kind of documentation, including shift-style logs, delivery confirmations, and incident records that slot straight into the checklist above. If you’re already working out how the NDIS covers home transition costs for a participant, our team can talk you through what documentation to request before the move even starts.
If you’re a support coordinator or allied health professional preparing for an upcoming plan reassessment, get in touch with EasyMove Services’ NDIS removalist team to plan a move that generates the evidence your report needs, not just a completed job.
Sources
- Guide to report writing | NDIS
- How to write a plan reassessment report | NDIS allied health guidance
FAQ
How early should I submit an NDIS reassessment report?
Submit at least eight weeks before the scheduled plan reassessment meeting, following NDIS guidance, so the planner has full time to review your evidence.
What’s the difference between a progress report and a reassessment report?
A progress report tracks goal-by-goal status during the plan, while a plan reassessment report summarises outcomes, barriers, and recommendations ahead of the next plan period.
Do I need a Functional Capacity Assessment for every review?
Not always, but if you have one, it should be no older than 12 months; an outdated FCA is a common trigger for clarification requests.
Can EasyMove Services provide evidence for my report?
Yes. EasyMove Services offers live tracking, timestamps, and NDIS-aware moving documentation that coordinators can attach directly to progress and reassessment reports.
What happens if my report is missing attachments?
Missing attachments often prompt a clarification request or delay, and can weaken the case for the recommended supports even when the narrative itself is strong.
Recommended
- Moving Service Reporting Tools For NDIS Coordinators
- The Role Of Feedback In NDIS Moving Services, Explained
- Coordinating SDA Moves: Best Practices For NDIS Participants
- Why Support Coordinators Arrange Moving Services For NDIS Participants