Most applications fail at the front end

Not at assessment. At gathering.

The dropout point in most recognition processes is before any assessment occurs. An applicant receives a kit, discovers it asks for evidence against dozens of requirements in language they do not recognise, attempts it, and stops. The provider records a withdrawal and concludes that recognition demand is low.

The kit is usually the problem. Written in the language of the standard, organised by unit, and running to many pages, it asks a person to translate their working life into a framework they have never seen. That translation is the assessor's expertise, not the applicant's.

Processes that work invert this. An initial conversation establishes what the person has done, an adviser maps that to the requirements and tells them what to collect, and the collection request is specific and short. The applicant is asked for eleven identified items rather than for evidence against forty requirements.

This costs staff time at the front end and is the difference between a process that produces completed applications and one that produces enquiries. It also produces much better evidence, because it was requested rather than guessed at.

The other front-end improvement worth making is to give applicants examples. Showing what an acceptable piece of evidence looks like, in their field, resolves more confusion than any amount of explanation, and it can be assembled once from previous files with identifying details removed.