A successful TEQSA registration application shows an assessor four things: that the provider's governance, courses, staffing and systems are operating rather than merely existing, that the evidence in one domain agrees with the evidence in every other, that each claim is specific to this provider and not to a model one, and that nothing in the application would surprise the assessor if they visited. Assessors read for those four qualities before they read for anything else, and an application that has them rarely needs more than a light request for further information.
This article is written from the assessor's side of the desk. It explains how an application is actually read, what patterns draw scrutiny, and how to write to that reading, drawing on fifteen years of TEQSA registration work. For the sequence of stages, see our step-by-step guide to the TEQSA registration application process.
How an assessor actually reads an application
An application for initial registration is assessed against the Higher Education Standards Framework (Threshold Standards) 2021, and TEQSA's application guide sets out what must be submitted. But the guide describes the inputs, not the reading. In my experience an assessor does not read the application front to back like a book. They read the governance evidence first, because it tells them whether anything else in the application can be trusted, then the courses, then the financial material, and then they go looking for the places where those three do not agree.
That reading has two consequences for the writer. The first is that the governance section carries the whole application: if the board minutes are thin or the academic board is advisory, every later claim is discounted. The second is that the application is read as a single document, even though it is usually written by several people over many months, and its internal consistency is itself evidence. The preliminary assessment, due within thirty days of lodgement under TEQSA's indicative timeframes, is largely a check for completeness; the substantive assessment, due within nine months and extendable by up to a further nine, is where the reading described here happens.
Operation, not existence: the Standards are in the present tense
The Threshold Standards say that a provider "has" an academic board, that admission "is" based on published criteria, that assessment "is" monitored. They do not say that a provider has a policy which says those things. The most common failure I see in applications is a description of arrangements that exist on paper and have not yet operated: a risk register never reviewed, a grievance process never used, a delegations schedule the CEO has never consulted.
A successful TEQSA registration application answers the present-tense question with present-tense evidence. Minutes showing the academic board declining or conditioning a course approval. A conflicts register with entries. A risk register whose ratings have changed between meetings. Where the provider has not yet enrolled students, the standard cannot be evidenced through student outcomes, and the honest approach is to say so and show the arrangements operating in the ways they can, through governance, staffing, course approval and the readiness of systems, rather than to imply an operating history that does not exist.
Cross-domain reading: where inconsistency is found
Assessors compare. The staffing profile in Domain 3 is checked against the course delivery plan in Domain 3.1, the financial projections in Domain 6 and the organisational chart. The student support arrangements in Domain 2 are checked against the cohort described in the business plan and against the admission criteria in Standard 1.1. The academic board's terms of reference in Standard 6.3 are checked against the course approval minutes in Standard 5.1.
The inconsistencies that draw scrutiny are ordinary. Enrolment projections that require more teaching staff than the staffing plan funds. A course described as work-integrated whose placement agreements do not appear. Independent directors named in the governance section who do not appear in the attendance record. Policy dates that precede the board meeting at which the policy was supposedly adopted.
None of these is fatal on its own, but each one tells the assessor that the application was assembled rather than written, and the questions that follow are about whether the organisation is as coherent as its description. Our article on common mistakes in TEQSA applications and how to avoid them catalogues the ones I see most.
Specificity: why generic applications draw more scrutiny now
When TEQSA retired the Confirmed Evidence Tables for higher education registration and moved to self-assurance, it raised the evidentiary bar. The provider now decides what demonstrates compliance and must present it coherently, rather than ticking documents against a list. That change coincided with the arrival of generative AI, and the regulator has since received a wave of applications whose narrative is fluent, well-structured and interchangeable. Assessors have learned to read for that.
The tell is a paragraph that could describe any provider. "The academic board provides rigorous oversight of academic quality in accordance with Standard 6.3" is not evidence; it is a restatement of the standard. "The academic board met seven times in the past year, declined one course proposal in March pending revised assessment and approved it in June with two conditions, recorded at minute 6.2" is evidence, and it can be checked. A successful TEQSA registration application is specific at that level of detail throughout, and the specificity is easy to produce if the organisation has actually been operating, because the facts exist to be reported. Our companion piece on what TEQSA expects in key evidence and documentation sets out the documents that carry this detail.
Writing a successful TEQSA registration application to that reading
The practical method follows from the four qualities. Build the evidence index before the narrative, standard by standard, and for each standard ask whether the document listed shows the arrangement operating or merely existing. Write the governance section first and best, and have it read by someone who was not involved in building the governance. Then write the rest of the application to the evidence, not the other way around: if the index has no minute showing the academic board approving a course, the narrative must not say it did.
Cross-check as an assessor would. Take the staffing plan, the financial model and the course delivery plan and reconcile them line by line; take every named person and confirm they appear consistently across governance, staffing and fit and proper declarations; take every policy and confirm its adoption date sits after the meeting that adopted it. Then remove every sentence that restates a standard without adding a fact. In my experience that last step shortens an application by a fifth and strengthens it considerably.
The non-delegation principle in the finished application
One further thing assessors look for, quietly, is who wrote the application. A consultant may draft, and most providers use one, but the governing body is non-delegably responsible for the application and for the provider's compliance. The application should read as the board's own account, and the record should show the board considering it, questioning it and resolving to lodge it. A cover resolution passed at a meeting that lasted twenty minutes, with no papers, tells the assessor that the board delegated what it could not delegate.
The fastest path to registration remains a complete, specific and true application from a provider that is already governing itself. An assessor who finds operation rather than existence, consistency across domains, specificity throughout and a board that plainly owns the document has little left to ask, and an application that draws no substantive request for further information is decided inside the statutory period far more often than not.
Download the Threshold Standards Map
— a one-page cross-reference from each part of a registration application to the standards it must evidence and the questions assessors ask of each, drawn from our TEQSA registration and governance work with private providers. Get the map
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 look for first in a registration application?
Governance. Assessors read the governing body and academic board evidence first, because it determines whether the rest of the application can be trusted, and an application with weak governance evidence is discounted throughout.
What does "operation, not existence" mean?
The Threshold Standards are written in the present tense and require arrangements that are operating, not policies that describe them. Evidence of operation includes minutes showing decisions, registers with entries and reviews that changed something.
Why do generic applications attract more scrutiny?
Since TEQSA moved from Confirmed Evidence Tables to self-assurance, the provider must decide and present its own evidence, and assessors have seen many fluent, AI-drafted narratives that restate the Standards without provider-specific facts. Specific, checkable detail is what distinguishes evidence from description.
Can a consultant write our TEQSA application?
A consultant can draft and advise, but the governing body is non-delegably responsible for the application. The board must consider, question and resolve to lodge it, and the minutes must show that it did, or the assessor will conclude the board delegated a responsibility it cannot delegate.
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.