A participant's family wants to know how many support hours per week they can realistically book without blowing the plan before the next review — a quick, defensible number beats a guess.
Max weekly hours = Core supports budget ÷ (hourly rate × weeks remaining)
This divides the remaining Core Supports budget evenly across the remaining weeks of the plan, at the quoted hourly rate — giving the maximum weekly hours the budget can sustain without running out early.
1 What this calculator does
Converts a Core Supports dollar budget into a maximum sustainable number of support worker hours per week (and per day), based on the hourly rate charged and the number of weeks left in the plan. Helps participants, families and support coordinators set realistic rosters.
2 Formula & professional reasoning
Max weekly hours = Core supports budget / (Hourly rate x Weeks remaining)
Max daily hours = Max weekly hours / 7
NDIS Core Supports funding for support work is consumed at the provider's hourly rate (up to the NDIS Price Limit for that support item and region). Dividing the remaining budget by the product of rate and weeks remaining spreads the funding evenly across the rest of the plan. This is a planning estimate, not an entitlement calculation — actual rosters also need to account for public holiday loading, travel time/costs, cancellation policies and non-labour charges which can all reduce the effective hours the budget stretches to.
3 Worked examples
⚠️ Illustrative example only — not clinical or professional instruction.
10400/(68.50x26) = 10400/1781 = 5.84 hrs/week36000/(72x52) = 36000/3744 = 9.62 hrs/week58000/(85x20) = 58000/1700 = 34.1 hrs/week4 Sanity check
5 Common errors
| Error | Cause | Consequence | Fix |
|---|---|---|---|
| Using the wrong price limit item | Applying a standard weekday rate when most support will be delivered on weekends or public holidays | Overestimates sustainable hours since actual invoices will be higher | Check the current NDIS Pricing Arrangements and Price Limits document for the correct item number and time-of-day rate |
| Forgetting travel and non-labour costs | Assuming 100% of the Core Supports budget converts directly to face-to-face hours | Real sustainable hours are lower than calculated, especially in regional areas with more travel | Reduce the effective budget by an estimated travel/non-labour allowance before calculating, or treat the result as an upper bound |
| Not separating Core Supports sub-categories | Entering the whole Core Supports budget when some of it may already be committed to consumables or transport | Overstates hours available for support worker time specifically | Check how much of Core Supports is already allocated elsewhere before running the calculation |
| Ignoring cancellation policy exposure | Not accounting for the possibility of short-notice cancellations being charged at up to 100% | Actual spend can run ahead of the calculated sustainable rate if cancellations occur | Build a small buffer into the weekly hours estimate to absorb occasional cancellation charges |
6 Reference & regulatory links
7 Professional workflow
Common tools used alongside this one: