How to Organise Case Notes for an NDIS Plan Reassessment

Months of case notes can contain useful observations about support, participant responses and changes over time. Preparing them for an NDIS plan reassessment starts with making that history understandable: which period does it cover, what support is represented, and where are the gaps?

A collection of notes is source material. A formal report brings relevant information together and explains it for its purpose. The NDIS guide to report writing describes reports in terms of supports delivered, outcomes, goals and challenges. Exporting notes does not create that report or guarantee a funding outcome.

Agree on the purpose and period

Before collecting records, confirm who is preparing the report, what information they need and the relevant date range. A request about changes in daily support may need a different selection from a review of one Service’s work.

Write down the participant, reporting period and Services covered. If the request includes records from other providers, identify those separately rather than assuming your own case note collection contains the full picture.

Support coordinators should also check their request for service and portal due dates. The NDIS support coordinator reporting guidance explains that requirements and timing depend on the participant’s circumstances and the request for service. Use the guidance relevant to your role rather than treating every provider’s report as interchangeable.

Build a chronology using session dates

Arrange notes by when the support occurred. A note written the next morning should still appear against its recorded session, rather than being treated as support delivered on the writing date.

In MyCaseNote, filter the case note list by participant, session dates and Service, then check other filters such as status. You can export all matching notes or selected notes to PDF. All matching results includes records across list pages, within export limits.

Check sessions that cross the beginning or end of the period. For example, support starting on 31 August and ending on 1 September overlaps both months. Our overnight and multi-day documentation guide explains how to record those boundaries clearly.

Review progress, variation and gaps

Read the chronology before drawing conclusions from it. Look for concrete observations, participant feedback and the assistance provided. Compare like situations where possible, and note changes in context that could affect the comparison.

For example, in a fictional set of community access notes, one entry might record a participant using a printed bus timetable with prompting. A later entry might record them choosing the route independently on a familiar journey. Those observations give a report writer specific records to consider; they do not establish that all journeys can now be made independently.

During review, ask:

• Are statements about change supported by dated examples?
• Does the selection represent difficulties and variation as well as positive experiences?
• Are participant comments clearly attributed?
• Are there unexplained gaps or missing session dates?
• Are draft or rejected notes included, and is their status understood?

An absence of notes is not proof that no support occurred. Identify the gap and follow your organisation’s process for investigating it. Do not fill missing historical details with estimates presented as facts. Keep corrections and amendments traceable through the note history.

Prepare supporting documents separately

MyCaseNote exports include saved note content, template responses, amendments and available metadata. They exclude attachments and attachment filename lists. Check the source records for supporting documents that may be needed, rather than assuming they appear in the PDF.

Keep a simple document list alongside your preparation work: document title, date, source and why it is relevant. Verify that each item belongs to the right participant and period, and confirm the authorised recipient and sharing process.

The export’s download expiry applies to the generated copy in MyCaseNote. It does not remove copies already saved to a device or sent elsewhere. Our guide to storing case notes securely covers related record-handling considerations.

Choose and check the export

A combined PDF is useful for reading a participant’s notes in sequence. A ZIP containing one PDF per participant helps separate records when an authorised internal review covers several people. Always check the participant scope before sharing a file.

MyCaseNote groups combined output by participant and offers oldest-first or newest-first order. It generates files in the background, so you can return to My exports when they are ready. Requests currently support up to 200 notes, with additional size and page limits; divide larger collections into clearly labelled periods when necessary and check for gaps or duplicates at the boundaries.

Review the downloaded file before using it: confirm its scope, status information and capture time. A new export is needed if you want changes made after the earlier content capture to be included.

A preparation checklist

• Confirm the purpose, participant, period and relevant Services.
• Check session-date boundaries and the applied status filters.
• Review the chronology for specific examples, variation and gaps.
• Gather relevant attachments and other reports separately.
• Check the export includes the intended notes and participant only.
• Record any limits or gaps the report writer needs to understand.
• Confirm the recipient and authorised sharing process.
• Keep the final report distinct from its supporting case note collection.

For future sessions, Service-specific case note templates can prompt staff to record support, responses and follow-up consistently. That creates clearer source material for the next review without asking workers to write a reassessment report after every session.