What happens to student complaints intelligence inside the OfS?
The Office for Students (OfS) is a risk-based regulator – it gathers intelligence and targets regulatory attention where it’s most needed.
Student complaints are an obvious source of that intelligence. The Office of the Independent Adjudicator for Higher Education (OIA) runs the student complaints scheme in England and Wales, and through its casework, identifies problems across providers.
Since 2018, a formal Collaboration Agreement has governed how the two bodies “share information and intelligence in a timely and effective manner,” including information that “identifies systemic issues and broad themes” arising from complaints.
OfS has made complaints intelligence central to its published regulatory architecture. Its own regulatory framework – Securing student success – states that general monitoring will “make use of wider strategic intelligence relating to the sector and/or individual providers, where appropriate, including whistleblowing and student complaints.” That’s paragraph 132, the core description of how general monitoring works.
Paragraph 136 lists the lead indicators OfS uses to flag changes in provider risk. Among them – alongside continuation rates, entry qualifications, and financial sustainability indicators – is “the number, nature or pattern of student complaints to the OIA.” A named, specific data stream that OfS committed to using as a risk signal.
So what happens once that information actually reaches OfS?
The agreement
The 2018 Collaboration Agreement anticipates that the OIA will share information arising from complaints where it may be relevant to regulatory oversight, referring to clusters of complaints and outcomes, instances of provider non-compliance with the OIA, and emerging trends within the OfS’s remit.
What it doesn’t do is prescribe how that intelligence should be handled once received – it’s silent on how information should be captured, brought together, or escalated internally. The effectiveness of the information flow depends entirely on internal OfS governance arrangements rather than any formal requirement set out in the agreement itself.
The OIA’s newly published Operating report 2025 describes regular engagement with the OfS on live regulatory issues, and its Operating plan 2025 commits to improving how the OIA identifies, records, and reports on complaints intelligence.
If the OIA is sharpening its own process, the next question is straightforward – what ensures that intelligence is captured and usable once it reaches OfS?
Into a black hole?
In response to Freedom of Information requests, the OfS confirmed that it doesn’t maintain any dedicated mechanism for capturing or managing information received from the OIA under the Collaboration Agreement.
The OfS does not maintain a dedicated mechanism – such as a register, mailbox, SharePoint site or tracking tool – for capturing or managing information received under this agreement.
Information from the OIA is handled within “standard operational processes”, but there’s no standalone system or dataset recording it as a distinct intelligence stream.
Consider what this means against the OfS’s own commitments. The regulatory framework doesn’t just mention complaints intelligence in passing – it names OIA complaints data as one of its lead indicators for monitoring all registered providers.
Paragraph 146 states that the OfS “will seek input from students – this may be insights from lead indicators from the national student surveys, complaints raised with the OIA, or by inviting information from individual students and student bodies.”
The framework overview at paragraph 19 summarises it as – all providers will be monitored using “lead indicators, reportable events and other intelligence such as complaints.”
And yet there’s no system for capturing this intelligence when it arrives.
No aggregation for the board
OfS also confirmed that it doesn’t produce any document whose primary purpose is to aggregate or summarise OIA-derived intelligence for senior management or the board.
We do not hold any documents whose primary purpose is to aggregate, summarise or collate stakeholder-derived intelligence for senior management or the Board.
While stakeholder information may be considered during routine operational work, the OfS says it doesn’t create or maintain an aggregated report, dashboard, or intelligence product of this kind.
OfS’s quality assessment process states that the regulator “continually monitors the regulatory intelligence we gather relating to quality for areas of potential concern” and uses that intelligence to select providers for assessment.
During its blended learning review, it conducted “a thematic analysis” of notifications related to course quality – the kind of structured work with intelligence that doesn’t appear to happen for OIA complaints data.
Its strategy for 2022–25 commits to using “the data and regulatory intelligence we hold” to identify providers where there may be concerns, and to becoming “increasingly risk-based in the way we monitor compliance.” How OIA complaints intelligence feeds into that remains unclear.
No record
The Collaboration Agreement requires at least one annual meeting between the chief executives of the two bodies. On this point, OfS confirmed that it doesn’t maintain a complete or consistent set of records evidencing those meetings over time.
We do not maintain a dedicated repository or formal series of documents created solely for the purpose of evidencing annual meetings under this agreement.
Ad-hoc records – emails or calendar entries, say – may exist for particular meetings, but there’s no auditable record covering the full period.
I asked OfS to confirm what these statements amounted to in practice – my reading was that they describe complaints intelligence entering the regulator without a defined governance pathway. OfS said it stood by its wording but didn’t want to endorse that characterisation.
The underlying points weren’t disputed. What OfS wouldn’t do was join them up into a view about what they collectively imply for governance once complaints intelligence is received.
Why it matters
None of this shows that the OfS ignores student complaints, or that information from the OIA is never discussed – the OfS is careful to emphasise that stakeholder information is considered as part of routine operational work.
But risk-based regulation depends on more than ad-hoc consideration. Information has to be drawn together so that patterns become visible beyond individual cases, and carried to senior decision-makers in a way that allows the regulator to explain, later, how its judgement was formed.
OfS’s own regulatory architecture makes the case. OIA complaints are named as a lead indicator. The regulatory framework commits to using complaints intelligence in general monitoring. Condition C1 on consumer protection law lists “student complaints, whether to the OIA or elsewhere” as material the OfS may consider when assessing compliance.
Condition C2 requires providers to cooperate with the OIA scheme, creating a regulatory loop in which the OfS is supposed to use OIA data to monitor whether providers are meeting that obligation.
The Collaboration Agreement anticipates that complaints can “suggest an underlying issue within the sector,” and that sharing this intelligence will support regulatory oversight.
Yet OfS’s own description of its arrangements suggests that information is shared but not structurally captured, that issues may be identified but not systematically brought together, and that meetings take place without any consistent record over time.
That leaves a real design question for a regulator that places so much emphasis on being evidence-led and risk-based.
If complaints intelligence is meant to contribute to oversight, what’s the pathway by which it becomes visible, legible, and usable at the points where regulatory judgement is actually made?
