Regulators expect an appeals and complaints process that is published, easy to use, fair, timed, and independently reviewed at the final stage, with every case recorded from start to finish. The record is what proves the process is real, because a policy nobody follows is worth nothing. Build it so a learner knows how to raise an issue, knows how long it will take, and can be sure the final decision is not made by the person the complaint is about.
What regulators actually expect
Regulators expect a process that is published, easy for a learner to use, fair, timed, and independently reviewed at the final stage, with every case recorded. Those five things are the test: a process can be well written, but if learners cannot find it, if timescales drift, or if the final decision is made by the person being complained about, it will not stand up.
The record proves the rest. When a quality assurance visit or an awarding organisation asks whether your process works, they want to see cases. Set out your policy on a complaints and appeals page so learners can find it.
Separate complaints from appeals: they are different things
A complaint and an appeal are different things and your process must treat them separately. A complaint is about how you were treated: the service, the delivery, the conduct of staff, a facility. An appeal is about an academic or assessment decision the learner disputes: a mark, a grade, a competence judgement.
Blurring the two causes real problems: an assessment appeal handled as a service complaint may never reach someone qualified to review the academic judgement. Say clearly, in the policy, which is which, and give each its own steps.
Build in independence
Independence means the person who makes the final decision is not the person whose decision or conduct is being questioned. This is the feature regulators look for hardest, because without it the process is just the provider marking its own work.
In a small provider this is a challenge but solvable. You can name a senior person with no involvement in the original decision, bring in an external reviewer, or use a panel. What matters is that you can show the final reviewer had no stake in the original outcome.
Set and keep timescales
Set clear timescales for each stage, tell the learner what they are, and keep to them. A process with no timescale leaves a learner in limbo and gives a regulator nothing to check you against. The point is not a particular number of days, which depends on your context and any awarding organisation requirement, but that you commit to timescales, publish them, and meet them.
Where you cannot meet a timescale, tell the learner, explain why, and give a new date, then record that you did. Verify any timescales an awarding organisation or regulator sets for you and build your process around the tightest of them.
Record every case
Record every complaint and every appeal from the moment it is raised to the moment it is closed, in one place, with dates against each step. The record should show what was raised, who handled each stage, what was decided, who decided it, when, and what changed. This is not bureaucracy; it is the evidence that the process is real.
- What was raised, by whom, and the date received
- Which route it took, complaint or appeal, and why
- Each stage, who handled it, and the date
- The final decision, the independent reviewer, and the date
- Any change to practice that followed
Use complaints as improvement data
Treat complaints and appeals as improvement data, not just problems to close, because a pattern in them tells you where your provision is weak. One complaint about an assessment brief might be a one-off; five complaints about the same brief is a design fault you should fix.
This is also what a self-assessment report is for. Pull the themes out of your case records, show what you changed, and whether it worked. A provider that can point to an improvement it made because of a complaint has a quality system that is clearly alive.
Common questions
What is the difference between a complaint and an appeal?
A complaint is about how a learner was treated: the service, the delivery, the conduct of staff or a facility. An appeal is about an academic or assessment decision the learner disputes, such as a mark, grade or competence judgement. They need separate routes because they need different expertise to resolve.
Does an appeals process need to be independent?
Yes, at the final stage. The person who makes the final decision must not be the person whose decision or conduct is being questioned, or the process is just the provider marking its own work. In a small provider you can achieve this with a senior person who had no involvement, an external reviewer, or a panel.
How fast must we respond to a complaint?
There is no single number that applies to everyone. What regulators expect is that you set clear timescales for each stage, publish them, tell the learner what they are, and keep to them, communicating and recording any exception. Verify any timescales an awarding organisation or regulator sets for you.
Do we have to keep records of complaints?
Yes. Recording every complaint and appeal from the moment it is raised to the moment it is closed is what proves the process is real, and it is the first thing a quality assurance visit will ask to see. The record should show what was raised, who handled it, what was decided, by whom, when, and what changed.
Can Apollo write our appeals policy?
Yes. Apollo Accreditation helps training providers in the UK and Malta build appeals and complaints processes that are published, fair, timed, independently reviewed and properly recorded, and that meet awarding organisation and regulator expectations. Book a scoping call and we will map what you have against what a regulator expects.
Planning a programme, an accreditation route or a quality system?
Book a 30 minute scoping call. We will map the route, the standards that apply and a realistic timeline. No preparation needed.
Book a 30 minute scoping callPrefer to write first? Contact us.