Refusing well

An unsuccessful applicant should know exactly why and what would change it.

A refusal that says the evidence was insufficient tells the applicant nothing usable. They do not know whether they were close, which requirements failed, or whether more evidence would change the outcome, and they generally conclude the process was arbitrary.

A useful outcome statement identifies which requirements were met, which were not, and specifically what evidence would have been sufficient for each. That converts a refusal into a plan, and a proportion of applicants come back with what was asked for.

It also protects the provider. A documented judgement with reasons is defensible on appeal; a general statement of insufficiency is not, and appeals against recognition decisions are more common than against taught assessment because the applicant has a strong personal view of their own competence.

Every applicant should be told the appeals route at the point of the decision, in writing, as part of the outcome rather than on request. Where a provider's own process is exhausted, applicants in most systems have an external avenue, and it should be named.

There is a further reason to write a specific refusal, which is that the applicant may well be competent and poorly evidenced. Those two situations are indistinguishable from the file and entirely different in substance, and an outcome that identifies exactly what was missing gives a genuinely competent person a route rather than a verdict on their ability.