Novida logoNovida

Winning Work Through the NDIS Request for Service Process

How support coordinators win referrals through the NDIS request for service process: channels, fast responses, conflict rules and what changes by 2028.

What a request for service actually is

A request for service is a referral document sent to a support coordination provider asking them to take on a specific participant. It typically includes the participant's first name or initials, their NDIS plan dates, the level and amount of support coordination funded, the reason coordination was included, and a contact pathway. It is not a contract. It is…

Where RFS referrals come from

There is no single national button that sends every request for service. The channel is fragmented, which is exactly why coordinators who understand it win more work. In practice, referrals arrive through several routes: LAC / Partners in the Community: The Local Area Coordinator organisations (contracted partners like APM, Feros Care, Mission Australia and…

Getting on the radar so referrals reach you

You cannot respond to a request for service you never receive. Getting into the flow is deliberate work: List on the NDIS Provider Finder if you are registered, and keep your service area, capacity and contact details current — an out-of-date listing sends referrals to a dead inbox.. Introduce yourself to the LAC partner organisations in your catchment. Ask…

How to read and triage an incoming RFS

Before you accept, read the request for service properly. A fast yes to the wrong referral costs you more than a slow no. Check: Plan dates: How long is left on the plan? A referral with six weeks remaining is very different from one with eleven months.. Funded hours: Divide the funded support coordination dollars by the relevant price limit to see how many…

Responding fast: the acceptance mechanics

Speed wins RFS work. Referrers often send the same request to several coordinators and allocate to whoever confirms capacity first and makes contact with the participant. A realistic sequence: Acknowledge the RFS the same day, even if only to say you are reviewing capacity and will confirm within 24 hours.. Confirm you can take the participant, or decline…

How this plays out: a worked example

An LAC partner emails you an RFS on a Monday. The participant, 'J', has a first plan with $5,000 of Level 2 Coordination of Supports, the plan started three weeks ago and runs twelve months, and the reason given is 'first plan, needs help connecting to supports and finding a therapy provider.' You reply the same morning confirming capacity and asking for the…

Conflict of interest when accepting RFS work

The NDIA is actively scrutinising support coordination invoicing right now, especially where coordination sits alongside brokerage or where the same organisation delivers multiple supports to one participant. When you accept an RFS, you must be able to show that your coordination decisions serve the participant's choice, not your own or a related provider's…

Common mistakes that cost coordinators RFS work

Slow replies: Sitting on a request for service for three days almost always loses it. The referrer allocates to a faster responder.. Accepting beyond capacity: Saying yes to every RFS and then failing to make timely contact damages your standing with the referring LAC — the exact source you depend on.. Taking Level 3 without 0132 registration: Accepting a…

Frequently asked questions

What is a request for service in the NDIS?

It is the referral a Local Area Coordinator, NDIA planner or other party sends to a support coordination provider asking them to take on a specific participant whose plan includes support coordination funding. It names the participant, plan dates, funded level and the reason coordination was included. It is an invitation to make contact and agree a service, not a binding contract.

How do support coordinators receive requests for service?

Mostly through the regional LAC / Partners in the Community organisations, NDIA planners for complex plans, hospital and health discharge teams, and direct participant or provider referrals. There is no single national RFS portal, so the practical step is knowing which LAC partner covers your area and how they prefer to send referrals.

How fast should I respond to an NDIS request for service?

Same day where possible. Referrers often send the same request to multiple coordinators and allocate to whoever confirms capacity and contacts the participant first. Acknowledge immediately, confirm or decline within 24 hours, and make first participant contact within about two business days.

Do I need to be registered to accept a request for service?

For standard support coordination (group 0106), mandatory registration was paused in December 2025, so registration is not currently forced. For Level 3 Specialist Support Coordination (group 0132), registration remains mandatory, so you cannot accept a Level 3 RFS without it. Confirm both positions at ndiscommission.gov.au.

Will the request for service process still exist after the 2028 reforms?

The open-market RFS model is scheduled to be replaced by a commissioned support coordination panel from 1 July 2028 under the Securing the NDIS for Future Generations Bill 2026, subject to passage and the Senate inquiry reporting on 14 August 2026. If it proceeds, panel selection rather than open referral will largely determine who receives work. Verify against health.gov.au before relying on the dates.

Related guides

Browse NDIS providers on Novida