The quality assurance TEQSA expects from every institution is not a document but a system: courses are approved by an academic body with real authority, every course is monitored while it runs and comprehensively reviewed on a cycle, anything delivered with another party stays under the provider's control, and the results of all of that flow back into decisions. That system is described in Domain 5 of the Threshold Standards, and since TEQSA moved to a self-assurance model it is the thing assessors most want to see operating.
This article explains Domain 5 as a connected whole rather than four separate standards, what a quality assurance cycle actually looks like inside a provider with a few hundred students, and how the self-assurance model changes what you have to prove. It draws on fifteen years of TEQSA registration and renewal work with private providers.
What does Domain 5 of the Threshold Standards require?
Domain 5 of the Higher Education Standards Framework (Threshold Standards) 2021 is titled Institutional Quality Assurance and has four sections. Standard 5.1 covers course approval and accreditation, 5.2 academic and research integrity, 5.3 monitoring, review and improvement, and 5.4 delivery with other parties. Read in isolation, each looks like a discrete compliance task. Read together, they describe a loop.
The loop runs like this. A course is designed and approved through a process that tests it against the standards before anyone enrols (5.1), and while it runs the provider watches its performance and reviews it periodically, acting on what it finds (5.3). Where any part of it is delivered by someone else, the provider remains accountable for the same standards (5.4), and throughout, integrity of assessment and of academic work is protected (5.2). TEQSA assesses whether the loop closes, not whether each document exists.
Why course approval is the entry point
Standard 5.1 requires that courses are approved by the provider's academic governance processes before they are offered, and that the approval considers the course against the Threshold Standards. In practice this means an academic board, or a committee reporting to it, that can decline to approve a course and has on at least one occasion sent one back.
In my experience the weakest course approvals are the ones where the academic board saw a finished course for the first time at the meeting that approved it. Assessors read the approval papers. They look for an external review by a discipline expert, a mapping of learning outcomes to AQF level descriptors, a staffing plan naming real people, and minutes recording questions and conditions. Course approval that leaves no such trail is not the quality assurance TEQSA can rely on, and every course that passed through it carries the same doubt. Our article on what TEQSA looks for in a new course sets out the approval evidence in more detail.
Monitoring, review and improvement: where most providers are thin
Standard 5.3 is the heart of Domain 5 and the section I see failed most often at renewal. It requires that all courses are subject to periodic comprehensive review, that performance is monitored in between, that review draws on external referencing and student outcomes, and that findings are acted on. The standard is written in the present tense: courses are reviewed, findings are used. Evidence that a review policy exists does not satisfy it.
A working 5.3 system in a small provider has two speeds. Annual monitoring looks at each course every year against a short set of indicators: progression, attrition, grade distributions, student feedback, complaints and integrity cases. Comprehensive review happens on a cycle, typically every five years or before re-accreditation, and brings in external benchmarking, an external reviewer's report and a full look at currency and outcomes. Both produce a report to the academic board, and the academic board decides what happens next. The design of that cycle is the subject of our article on designing a continuous improvement framework for course reviews.
The part that separates a functioning system from a filing cabinet is action tracking. Every review generates recommendations. TEQSA asks what happened to them. A register of actions with owners, dates and a closure column, reported to the academic board until each item is closed, is the single most persuasive piece of Domain 5 evidence a provider can produce. Providers increasingly use learning analytics to meet TEQSA's continuous improvement expectations, which helps with the monitoring speed but does not replace the decision-making that follows.
Third-party delivery is still your quality assurance
Standard 5.4 says that where a course, or part of one, is delivered through another party, the provider remains responsible for meeting the standards and must have arrangements to assure that. Assessors treat this section with particular care because third-party delivery is where problems most often escape notice.
The evidence set is a written agreement that allocates responsibility for admission, teaching, assessment, records and student support, a schedule of what the provider checks and how often, and the results of those checks. In my experience a provider that cannot produce a moderation record or a site visit report for a partner-delivered unit will be asked, quite reasonably, how it knows the unit meets the standard at all. TEQSA's material change policy also lists new third-party arrangements as notifiable, so the governance side runs alongside the quality side.
What changes under the self-assurance model?
TEQSA retired the Confirmed Evidence Table for higher education registration and now asks for a self-assurance report, capped at ten pages, with an evidence index behind it. The renewal application guide makes clear that TEQSA does not require evidence against every standard and assesses on a risk basis, informed by compliance history and annual data.
Providers sometimes read that as a lighter touch. It is the reverse. Under a Confirmed Evidence Table you could list a document against each standard and let the assessor form the view. Under self-assurance the provider must state, in its own words, how it knows it is compliant, and then point to the evidence that shows it.
That is a harder question, and it is a question about Domain 5, because Domain 5 is the machinery by which a provider knows anything about its own quality. A self-assurance report that describes policies rather than findings tells TEQSA the machinery is not running. Our guide to preparing re-registration evidence explains how to build the index that sits behind the report.
What the quality assurance TEQSA accepts looks like in a small provider
Consider an anonymised composite: a provider with three accredited courses, about four hundred students and a single campus. Its academic board meets six times a year. At each meeting it receives a standing quality report covering enrolments, progression, grade distributions by unit, and any integrity cases or complaints since the last meeting. Twice a year it receives the annual course monitoring reports, one per course, each ending with a short list of actions.
Once a year it receives an internal audit of one policy area chosen by risk, a practice described in our article on the role of internal audit in meeting TEQSA's quality assurance standards. Once every five years, or ahead of re-accreditation, each course goes through comprehensive review with an external reviewer. The action register is a standing item until every line is closed. The chair of the academic board reports to the corporate board after every meeting. That is the whole system, and it fits on one page and it satisfies Domain 5 because it produces evidence of operation as a by-product of running.
My view: build the loop before you need it
The quality assurance TEQSA rewards is unglamorous. It is the same short reports, produced on the same schedule, read by the same board, with the same action register slowly closing. Providers that try to assemble that record in the six months before renewal find they cannot, because the standard asks for evidence that the system operated, and operation cannot be back-dated.
Guidance notes will help you interpret each section of Domain 5, with the usual caveat that guidance notes are not themselves Threshold Standards. The standard itself is short enough to read in an afternoon. If your academic board can show course approvals it debated, monitoring reports it received, reviews it commissioned and actions it closed, you have met it. If it cannot, no volume of policy will substitute.
Download the Re-registration Evidence Index Template
— a working index for mapping Domain 5 evidence to the self-assurance report, drawn from our TEQSA registration and governance work with private providers. Get the template
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
What does TEQSA mean by quality assurance?
TEQSA uses the term as Domain 5 of the Threshold Standards does: the provider's own system for approving courses, monitoring and reviewing them, protecting academic integrity and controlling delivery by other parties. It assesses whether that system operates, not whether the policies exist.
How often must courses be reviewed under Standard 5.3?
The standard requires periodic comprehensive review and ongoing monitoring but does not fix a period. Most providers review each course comprehensively every five years or before re-accreditation and monitor every course annually.
Does the self-assurance model mean less evidence?
No. TEQSA no longer requires evidence against every standard and assesses on risk, but the provider must state how it knows it is compliant and back that with an indexed evidence set showing the quality system in operation.
Who is responsible for quality assurance in a private provider?
The academic board holds responsibility for academic quality under Standard 6.3, and the corporate governing body remains accountable for the provider's compliance overall. Neither can delegate that responsibility to management or to a consultant.
Dr Brendan Moloney is CEO of Darlo Higher Education, Australia's largest specialist TEQSA consultancy. He holds a PhD from the University of Melbourne, is a Cambridge University Press author on governance in higher education, and has advised private providers on registration and course accreditation for more than fifteen years.