Support Availability

What a waitlist number actually means

Families treat a stated wait as a delivery date. It is almost never one, and understanding why changes what you do with it.

Related: direct service or referral, why capacity changes faster than directories do, and the whole definition of Support Availability.

Three different things called a waitlist

An ordered queue. Names in sequence, served in order. This is what everyone pictures and it is the least common of the three.

A prioritised pool. Everyone waiting is assessed against need criteria and the most urgent are served first. A person can join today and be served before someone who joined last year. This is the most common arrangement in senior services and it is almost never explained on the phone.

A record of interest. A list kept so the organization can demonstrate demand to a funder. Being on it may have no relationship to being served at all.

The question that separates them. "If someone with greater need applies tomorrow, do they go ahead of me?" A yes means it is a pool, not a queue, and your stated wait is an average rather than a countdown.

Why the number is usually an average of the past

A stated wait of eight months normally means recent entrants waited about eight months. It is a historical figure, not a forecast, and it moves with funding cycles, staffing, and how many people applied last quarter.

So a long stated wait is a weak reason not to apply. Applying costs an afternoon, the clock only starts when you are on the list, and the figure that mattered was measured before your application existed.

Closed is rarely permanent

A closed list usually means closed to new entries right now, and reopening is frequently tied to a funding date rather than to capacity freeing up. The useful question is not whether it is closed but when it reopens and whether anyone will tell you.

Almost nobody is notified. Support Availability treats a closed list with a known reopening date as a materially different finding from one with no date, because the first is something a family can act on and the second is not.

What we will and will not say

We report the status a provider gave us and the date they gave it. We do not convert a stated wait into an expected start date, because that would be a forecast built on an average we did not produce.

Where the type of list is known, it is stated. Where it is not, that is reported as unknown rather than assumed to be a queue, since assuming a queue is the specific error that leads families to wait quietly instead of asking about priority criteria.

What to do with a long wait

Apply anyway, and ask three things: is this a queue or a prioritised pool, what would move someone up it, and will anyone contact me if my situation changes. The last question matters most, because almost every prioritised pool has a route to reassessment and almost nobody uses it.

Related: direct service or referral, why capacity changes faster than directories do, and the whole definition of Support Availability.