Why map the whole participant journey?
In disability support, a completed intake is not the same as support received. Between plan activation and the first agreed shift, information moves between participants, coordinators, administrators and support workers. Consent, risk screening, funding checks, worker availability, travel and participant preferences all affect how reliably that journey flows.
Value stream mapping (VSM) makes the end-to-end process visible. It captures both information and work: each activity, handoff, touch time, queue, rework loop and outcome. The aim is not simply to move faster. It is to help participants receive the agreed support safely, with choice and continuity, while making work more predictable for support teams.
NDIS workflows can include a request for service and, where applicable, service-booking requirements. Confirm the current rules for the particular support and funding arrangement using the NDIS request-for-service guidance and service-booking guidance. For support coordinators, the NDIS states that a request for service must be accepted or declined within four business days. Treat this as a relevant process requirement, not a substitute for measuring the provider’s full participant journey.
Scope the value stream around the participant
Set boundaries before gathering data. For this worked example, the participant is the person choosing and receiving disability support, with their chosen supporters involved as they wish.
- Start: the provider receives a referral or plan-related request with enough information to begin intake.
- Finish: the participant receives the first agreed support from a suitably matched worker.
- Include: referral review, participant contact, consent, service agreement, risk checks, required funding administration, worker matching, rostering, confirmation and first delivery.
- Exclude: the external plan-approval process and ongoing support after the first service, unless a later improvement project deliberately includes them.
Agree with participants what “timely” and “acceptable” mean for the service. A fast start that ignores communication preferences, worker suitability, safeguarding or the participant’s schedule is not a successful outcome. A project scope boundary calculator can help a team document the boundaries.
Current state: follow the request to the first shift
The following hypothetical provider example illustrates how to build a baseline. It is not an industry benchmark. Times are average business days, and touch time is active staff effort per request. Queue time is time waiting between steps; elapsed lead time is approximately the queue time for each step, plus active work.
| Current-state step | Touch time | Queue / elapsed time | First-time-right rate |
|---|---|---|---|
| Referral received and triaged | 20 min | 1.5 days | 97% |
| Request reviewed and capacity decision made | 30 min | 2.0 days | 95% |
| Participant contacted; needs and preferences discussed | 90 min | 2.5 days | 93% |
| Agreement, consent and risk screening completed | 75 min | 3.0 days | 94% |
| Funding and required booking details checked | 30 min | 2.0 days | 98% |
| Worker matched and roster prepared | 60 min | 5.0 days | 90% |
| First shift confirmed and prepared | 30 min | 2.0 days | 97% |
| First agreed support delivered | 120 min | 0 days | 99% |
| Total | 7 hr 35 min | 18 business days | 68.2% rolled throughput yield |
The rolled throughput yield (RTY) is the probability of completing every step correctly the first time: multiply the step yields (0.97 × 0.95 × 0.93 × 0.94 × 0.98 × 0.90 × 0.97 × 0.99 ≈ 0.682). In this example, about 68 of every 100 requests pass through all steps without a correction or repeat.
Add workforce and queue data to the map, not just process boxes. Suppose the provider has 46 open service requests, receives first contact within 2.3 business days on average, and has 120 qualified, requested recurring shifts per week, of which 96 are filled. That is 80% shift availability. Sampled staff utilisation is 82% of available paid hours. Interpret utilisation carefully: a high figure may leave too little room for travel, documentation, leave or urgent changes. Segment results by service type, location, complexity and participant preference.
For applicable support-coordinator requests, also measure the share accepted or declined within the NDIS four-business-day requirement. The average alone can conceal a long-waiting tail, so report median and 90th-percentile times too.
Identify DOWNTIME across the journey
Use the eight-waste framework to connect observations with causes:
- Defects: missing intake details, incorrect funding information or incomplete consent create corrections and repeat contact.
- Overproduction: collecting forms or assessments before they are needed adds work without advancing a suitable start.
- Waiting: participants wait for contact, checks, an appropriate worker or a roster slot.
- Non-utilisation of talent: support workers’ and coordinators’ practical knowledge is left out of process redesign or scheduling decisions.
- Transportation: information is transferred between disconnected systems or teams instead of moving with the request.
- Inventory: the 46 open requests are work in process; a growing queue can hide which requests need action.
- Motion: staff search across emails, spreadsheets and systems for availability, preferences or approvals.
- Extra processing: the same details are entered repeatedly or checked by several people without a clear control purpose.
Build a future state that balances demand, capacity and choice
Design countermeasures around safe, reliable flow, not speed in isolation.
- Make intake ready for a decision. Use one standard checklist for essential referral information, participant preferences, location, funding pathway and risk-screening needs. Assign a named owner and acknowledge referrals within one business day.
- Visualise the queue. Review a shared daily board showing request age, next action, owner, capacity status and escalation needs. Make a documented capacity decision promptly and, for applicable support-coordinator requests, before the four-business-day deadline.
- Reduce repeated handling. Keep a single participant record where feasible, with controlled access and appropriate privacy safeguards. Standardise agreement, consent and booking steps, while preserving time for individual discussion and informed choice.
- Match on suitability, not availability alone. Maintain a current skills, location, travel and shift-availability matrix. Confirm worker qualifications and participant preferences before offering a start date.
- Level demand and protect capacity. Forecast likely starts by support type and time band. Reserve a small, controlled number of onboarding and first-shift slots; review them daily and release unused capacity according to agreed rules. Avoid filling every available hour: retain practical capacity for travel, leave and unexpected changes.
- Create standard work with clear exceptions. Define handoffs, required checks, response expectations and escalation routes. Complex or urgent needs should receive a human review rather than being forced through a standard pathway.
A takt-style calculation can help set a planning rhythm. If demand is 24 suitable first starts per week and the team operates over five days, the average requirement is 4.8 starts per day, roughly one start every 1.67 working hours across an eight-hour service day. If the provider can sustainably offer 30 qualified, travel-feasible start slots per week, planned capacity is six per day. This is a team-level planning signal, not a quota for individual workers or a reason to compromise participant choice or safe matching.
Compare current and designed performance
The future-state figures below are 90-day improvement targets for the hypothetical example, to validate through a pilot and participant feedback, not promised outcomes.
| Measure | Current state | Future-state target |
|---|---|---|
| Referral-to-first-support lead time | 18 business days | 7 business days |
| Active touch time per request | 7 hr 35 min | 6 hr 50 min |
| Initial acknowledgement | 2.3 business days | Within 1 business day |
| Open service requests (WIP) | 46 | 18 or fewer |
| Requested recurring shifts filled | 80% | 95% |
| Staff utilisation of available paid hours | 82% | 80–85%, monitored with wellbeing and travel |
| First-time-right rolled throughput yield | 68.2% | 90% |
| Applicable support-coordinator RFS decisions within 4 business days | 88% | 100% |
A 90-day kaizen sequence
Days 1–30: Define and measure. Form a team that includes participant perspectives, support workers, coordinators and administration. Confirm scope and measures; map actual work through observation and request sampling. Establish baseline median and 90th-percentile lead times, WIP, rework, shift fill and participant-reported timeliness. Use the process cycle efficiency calculator to distinguish touch from waiting.
Days 31–60: Analyse and pilot. Review the longest queues and repeat-work causes. Pilot the intake checklist, visual request board and skills-and-availability view in one service line. Test roster levelling with a small, controlled capacity buffer. Ask participants and staff what improved and what created new friction; adjust before expanding.
Days 61–90: Standardise and sustain. Extend proven changes, document standard work and assign process owners. Review a weekly dashboard with lead time, RTY, roster fill, cancellations, WIP, overtime and participant feedback. Set trigger limits for overdue requests and uncovered shifts, and use regular audits to confirm that privacy, consent, safeguarding and choice remain intact.
Develop the capability to lead improvement
A well-run VSM project combines Lean flow thinking with DMAIC measurement and root-cause analysis. For practitioners ready to lead cross-functional improvement, Lean 6 Sigma Hub offers self-paced, CSSC-accredited Green Belt training and Black Belt training, with practical case studies and worked examples. Explore the full course range to choose a pathway suited to your role.
Build the skills to map, measure and improve participant-centred services: pursue Lean Six Sigma Green Belt or Black Belt certification.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma.
