ChatGPT prompts for NDIS support workers

These ChatGPT prompts for NDIS support workers help with the writing that fills the end of every shift: progress notes, handovers, incident summaries and messages to families and support coordinators. Each prompt is ready to copy, with [placeholders] for your details. They work in any AI assistant your organisation approves, including ChatGPT, Claude and AusGPT.

Use these prompts safely#

Read this before you paste anything into an AI tool.

• Check your organisation's policy first. Only use AI tools your provider has approved, and only for the tasks it allows.
• De-identify everything. Use [Participant] instead of a name, and leave out NDIS numbers, Medicare numbers, dates of birth, addresses, phone numbers and photos. Unusual details can identify someone too, so generalise them.
• Respect privacy. The NDIS Code of Conduct requires everyone who delivers NDIS supports, including workers, to respect the privacy of people with disability.
• Know the regulator's position. The NDIS Commission's February 2026 position statement on AI in behaviour support plans expects that, if a provider uses AI, all information is appropriately de-identified and no personal information of participants is disclosed to AI systems. It also flags risks such as inaccurate content and information being processed or stored overseas.
• Keep personal information out of public AI tools. The OAIC recommends that organisations don't enter personal information, particularly sensitive information such as health and disability information, into publicly available generative AI tools.
• You own the record. AI drafts; you check every sentence against what actually happened, fix anything wrong, then add identifying details back in your organisation's system.
• Never let AI slow down reporting. Registered providers must notify the NDIS Commission of reportable incidents, most within 24 hours of becoming aware of them. Follow your incident procedure first.

Each prompt asks the AI to write in objective, person-centred language: describe what you saw and heard, use the person's own words where relevant, and avoid judgements or labels.

Progress notes#

Turn rough shift notes into a progress note#

You are helping an NDIS support worker write a progress note. Rewrite my rough shift notes below into a clear, objective, person-centred progress note.

Rules:
- Use [Participant] instead of any name.
- Describe what happened and what was observed or said. No assumptions, diagnoses or judgements.
- Write in past tense, plain English, first person ("I supported [Participant] to...").
- Use headings: Supports provided, Participant's choices and preferences, Observations, Progress towards goals, Follow-up needed.
- If something is unclear or missing, list it as a question at the end instead of guessing.

Shift: [date/time placeholder], [type of support, e.g. community access, personal care]
My notes: [paste de-identified notes]

Make my note more objective#

Review this de-identified progress note. Identify any wording that is judgemental, vague, or not person-centred (for example "was difficult", "refused", "behaved badly", "seemed happy"). For each one, suggest an objective alternative that describes what was actually seen or said. Then give me the full rewritten note. Don't add any facts that aren't in my note.

Note: [paste note]

Write a note that links to goals#

Write a short progress note that links today's activities to the participant's goals. Use [Participant] instead of a name.

Goals (de-identified): [e.g. "build confidence using public transport", "prepare simple meals independently"]
What happened today: [paste notes]

For each goal, write one or two sentences on what was worked on, the level of support given (prompting, modelling, hands-on, independent) and any change compared with previous shifts. If a goal wasn't worked on, say so.

Short note for a routine shift#

Turn these dot points into a concise progress note of no more than 120 words for a routine [type of shift]. Keep it factual and person-centred, use [Participant] instead of a name, and finish with "Follow-up:" followed by any action needed, or "Nil".

Dot points: [paste]

Check my note for missing details#

Act as a team leader reviewing a de-identified progress note. List anything a reader would need that is missing or unclear: times, who was present, what support was provided, the participant's choices, any concerns raised, and follow-up actions. Don't rewrite the note. Just give me a checklist of questions to answer.

Note: [paste note]

Shift handovers#

Handover summary for the next worker#

Write a shift handover for the next support worker from my de-identified notes. Use these headings: How [Participant] is today, What was done, Anything to watch for, Tasks for next shift, Who to contact if needed (use roles, not names). Keep it under 200 words and in plain English. Don't add anything that isn't in my notes.

Notes: [paste]

Turn a routine into a handover checklist#

Turn this de-identified description of a participant's evening routine into a step-by-step checklist a new support worker could follow. Keep the participant's preferences and choices in each step (for example "Ask [Participant] which...", "Offer..."). Add a final section called "Check with the team leader" for anything that needs clarifying.

Routine: [paste]

Handover between services#

Write a brief, respectful handover message from our service to [receiving service type, e.g. day program, respite provider] covering today's relevant information only. Use [Participant] instead of a name. Include: anything that affects support today, preferences to respect, and items being sent. Leave out anything not needed for this handover.

Information: [paste de-identified notes]

Incident summaries#

Organise my notes into a factual incident summary#

Help me organise my own de-identified notes into a factual incident summary for my organisation's incident form. This is a draft for me to check, not a final report.

Rules:
- Use roles or placeholders, not names ([Participant], [Worker 1], [Visitor]).
- Separate what I directly saw or heard from what I was told by others.
- Record times and sequence exactly as in my notes. Don't estimate or fill gaps.
- Include immediate actions taken and who was notified (by role).
- Don't speculate about causes or assign blame.
- At the end, list any information my form may need that's missing from my notes.

My notes: [paste]

Build a timeline of events#

From the de-identified notes below, build a timeline table with columns: Time, What happened, Who was involved (role only), Source (seen by me / reported to me). Keep the exact times from the notes. Where a time isn't given, write "time not recorded" instead of estimating.

Notes: [paste]

What should I check before submitting?#

I'm about to complete my organisation's incident form. Based on my de-identified summary below, list questions I should check the answers to before submitting, such as times, injuries observed, first aid given, who was notified and when, and follow-up. Don't tell me whether the incident is reportable. I'll follow my organisation's procedure for that.

Summary: [paste]

Reflective debrief questions#

After a difficult shift, I want to reflect for supervision. Based on this de-identified summary, write 8 open reflective questions about what happened, what worked, what I'd do differently, what support I need, and what the participant's experience might have been. Don't judge or draw conclusions.

Summary: [paste]

Routines and support information#

These prompts help you write everyday support information, such as routines and preferences, to discuss with the participant and your team. They're not for behaviour support plans, which are prepared by behaviour support practitioners under separate rules.

"About me" page for new workers#

Draft a one-page "About me" summary for new support workers, written from the participant's point of view ("I like...", "Please..."). Use [Participant] instead of a name. Base it only on the de-identified information below. Include: what's important to me, how to communicate with me, what a good day looks like, and things that upset me. Mark it "Draft: check with [Participant] and the team before use".

Information: [paste]

Step-by-step guide for a task#

Turn this de-identified description into a clear step-by-step guide for supporting [Participant] with [task, e.g. grocery shopping]. For each step, include how to offer choice and how much support to give. Use short sentences. Add a "Before you start" list and an "If plans change" section.

Description: [paste]

Easy Read version#

Rewrite the text below in an Easy Read style for [Participant]: short sentences, one idea per sentence, everyday words, and headings. Suggest where a picture would help, in square brackets, for example [picture: bus stop]. Keep the meaning exactly the same.

Text: [paste]

Goal tracking#

Break a goal into small steps#

A participant's goal is: "[de-identified goal]". Suggest 6 to 8 small, practical steps a support worker could work on with them over the next few months, from the most supported to the most independent. For each step, give an example activity and what "progress" might look like in a progress note. The participant should choose which steps to work on.

Monthly progress summary#

Summarise the participant's progress towards each goal over the past month, using only the de-identified progress note extracts below. For each goal, write: what was worked on, how often, changes in level of support, barriers noted, and the participant's own comments where recorded. Finish with "Suggested topics for the next team or plan review discussion". Don't invent progress that isn't in the notes.

Goals: [list]
Note extracts: [paste]

Activity ideas linked to a goal#

Suggest 10 activity ideas in [suburb type, e.g. a regional town / inner-city area] that could help a participant work towards this goal: "[de-identified goal]". The participant enjoys [interests] and prefers [quiet / busy / outdoor / indoor] settings. Include low-cost options and note any planning each activity needs.

Communication with participants, families and support coordinators#

Email to a support coordinator about a change in needs#

Draft a professional email to the participant's support coordinator about a change in support needs I've noticed. Use [Participant] and [Support coordinator] as placeholders. State the observations objectively with dates (as placeholders), explain why it may matter, and ask for a time to discuss. Keep it under 180 words. No diagnoses or assumptions.

Observations: [paste de-identified notes]

Update for a family member#

Write a warm, respectful update for [Participant]'s family member about today's shift. Share only what [Participant] is happy for their family to know: [list what was agreed]. Keep it positive and factual, under 100 words, and avoid jargon.

Explain a change of plans to a participant#

Write a short message explaining to [Participant] that [change, e.g. their usual worker is away next Tuesday and a new worker will come]. Use plain, friendly language, explain what will stay the same, and offer a choice where possible (for example rescheduling). Write it at a reading level suitable for [describe needs, e.g. Easy Read].

Respond to a concern raised by a family#

A family member has raised this concern: "[paste de-identified concern]". Draft a reply that thanks them, acknowledges the concern without being defensive, explains what happens next (I will pass it to [role] in line with our complaints process), and gives a timeframe placeholder. Don't admit fault or promise outcomes. Under 150 words.

Agenda for a team or case meeting#

Create an agenda for a 45-minute team meeting about supports for [Participant]. Topics: [list]. Include the participant's own priorities as the first item, time allocations, who should lead each item (by role), and a final item for agreed actions and who is responsible.

Save these prompts to a shared prompt library#

Prompts work best when everyone on the team uses the same wording. In AusGPT, you can save prompts to a shared prompt library with folders, for example "Progress notes", "Handovers" and "Incidents", so new workers start with prompts your team leaders have already checked.

To set it up, copy the prompts you use from this page, adjust the headings and rules to match your organisation's templates, and save them in your team workspace. Keep the [placeholders] so each person fills in their own de-identified details.

AusGPT stores and processes conversations in Australia and never uses them to train AI models. That doesn't change the de-identification steps above: follow your organisation's policy and the NDIS Commission's expectations in any AI tool. See how AusGPT works for NDIS providers.