The most common mistakes TEQSA applications contain are substantive rather than clerical. They are a staffing profile that describes people not yet hired, learning outcomes pitched at the wrong AQF level, an academic board that can only recommend, text that reads as if a language model wrote it, evidence that proves a document exists but not that it operates, and vocational language carried across from the RTO world. Each one tells an assessor something about the provider, and each one produces a request for further information.
This article works through those six errors in turn and explains what the assessor sees when they appear. It draws on fifteen years of TEQSA registration and accreditation work with private providers, and it is deliberately narrow: governance failures have their own article, and so does the broader question of compliance after registration. Here I am concerned with what is on the page when the application is lodged.
Which common mistakes TEQSA applications reveal most often?
Assessors read an application against the Higher Education Standards Framework (Threshold Standards) 2021, and the standards are written in the present tense. A provider "has" qualified staff, "maintains" academic governance, "monitors" student outcomes. The application is therefore read as a description of a functioning institution, not a plan for one, and most of the errors below come from writing a plan and calling it a description.
The other thing to understand is that assessors read for internal consistency. A staffing table, a course structure, a set of learning outcomes and a budget all describe the same institution, and when they disagree the assessor does not pick the most favourable version. They ask which one is true. Most of the common mistakes TEQSA applications make are, at root, consistency failures between sections written by different people at different times.
Mistake 1: a staffing profile made of intentions
Standard 3.2 requires academic staff who are qualified to at least one AQF level above the course they teach, or with equivalent professional experience, and who are active in scholarship relevant to their field. The most frequent error I see is a staffing schedule populated with roles, salary bands and a note that recruitment will follow registration.
TEQSA does not register an intention to employ. Assessors expect to see named people, signed contracts or letters of offer, CVs that show the qualification and the scholarship, and a workload model that shows those people can actually deliver the course as designed. Where a provider has one full-time academic and a list of sessional staff "to be confirmed", the assessor concludes that the course cannot yet be delivered, and the application stalls until it can. In my experience, this single issue accounts for more delay in initial registration than any other.
Mistake 2: learning outcomes at the wrong AQF level
The Australian Qualifications Framework sets out what a graduate at each level should know, be able to do, and be able to apply. A bachelor degree is level 7; a coursework masters is level 9. The mistake is writing course learning outcomes that describe level 7 capability in a course badged as level 9, or the reverse, and then building assessment that does not test what the outcomes promise.
Assessors check this carefully because it goes to whether the qualification is what it claims to be. The tell-tale signs are outcomes that begin with "understand" or "be aware of" in a masters program, an absence of anything resembling independent judgment or research at level 9, or a level 7 course whose outcomes read as if lifted from a level 5 diploma. Standard 1.4 requires outcomes consistent with the AQF level and field, and Standard 3.1 requires the course design to deliver them. An outcome at the wrong level fails both.
Mistake 3: an academic board that only advises
I have written about this at length in the governance mistakes that stall TEQSA applications, so I will keep it short here. Standard 6.3 requires academic governance with authority over academic matters. An "academic advisory committee" whose recommendations the CEO may accept or reject does not have that authority, and every course approval that passed through it is compromised as evidence.
The reason it belongs on this list is that it shows up in the application document itself, not only in the governance annexures. Course approval sections that say "approved by the CEO on the recommendation of the academic advisory committee" tell an assessor exactly how the provider is run. The fix is structural, not textual, and it needs to happen before the board approves the course, not before the application is lodged.
Mistake 4: text that a language model wrote
This is the newest of the common mistakes TEQSA applications now contain, and it has grown quickly. TEQSA's move away from Confirmed Evidence Tables towards self-assurance coincided with the arrival of generative AI, and the two together produced a wave of applications that read fluently, cite the standards correctly, and say nothing specific about the provider at all.
Assessors have learned to recognise the pattern: the paragraphs are the same length, every standard is "fully addressed through a robust framework", and no policy is named, no meeting is dated, no number appears. In my experience this kind of text draws more scrutiny rather than less, because the assessor cannot tell whether the provider has understood the standard or merely described it. Self-assurance raised the evidentiary bar: TEQSA is asking the provider to show its own judgment about where it is strong and where it is not, and generic prose cannot do that.
Mistake 5: evidence of existence rather than operation
An application can include a hundred policies and still fail on evidence. The question the assessor asks is not whether the provider has a moderation policy but whether moderation happened, who did it, what it found, and what changed. A policy proves that a document exists. Minutes, reports, registers and reviews prove that it operates.
This distinction runs through the whole framework and I have set it out in detail in the difficulty of providing evidence for TEQSA registration. For a prospective provider with no students, the operational evidence is necessarily thinner, but it is not absent: the academic board has met, the course was externally reviewed, the risk register has been discussed and revised, the benchmarking partner has been engaged. An application that cannot show any of that is asking TEQSA to take the policies on trust, and assessors do not.
Mistake 6: VET language in a higher education application
Many new providers come from the vocational sector, and the vocabulary follows them. The application refers to "units of competency", "trainers and assessors", "RPL against performance criteria", "continuous improvement registers" and "audits". None of those terms belongs in higher education, and their presence tells an assessor that the provider has not yet understood the sector it is entering.
The deeper problem is that the language reflects a model. VET compliance governance is designed to demonstrate that training meets a package; higher education academic governance is designed to exercise judgment about knowledge, scholarship and assessment at AQF levels 5 to 10. A provider that describes its academic integrity arrangements as "compliance monitoring" or its course design as "mapping to the training package" has imported the wrong model, and TEQSA reads the vocabulary as evidence of that.
How the mistakes compound
None of these errors is fatal on its own. An RFI is issued, the provider responds, and the assessment continues. What stalls an application is the combination. An assessor who finds aspirational staffing and generic text and an advisory academic board no longer reads the rest of the application charitably. Every section is now checked for the same pattern, and the assessment timeline, which TEQSA's own indicative timeframes already put at up to nine months from commencement with possible extension, stretches accordingly.
I have set out the practical corrections in a companion article on common mistakes and how to avoid them, and the post-registration equivalents in common TEQSA compliance mistakes. The short version is this: the fastest path through TEQSA is a complete, specific, true application that gives the assessor no reason to ask a second question.
What I tell providers before they lodge
Read the draft as the assessor will. For every claim, ask whether the evidence shows the thing operating or merely existing. For every staff member, ask whether the person is real, contracted and qualified. For every learning outcome, ask which AQF level descriptor it maps to and whether the assessment tests it. For every paragraph, ask whether it could have been written about any provider in the country, and if it could, rewrite it until it could not.
Then ask the governing body to do the same, and record that it did. The board is non-delegably responsible for the application, and an application the board has actually read and challenged is, in my experience, a noticeably better document than one it has merely approved.
Download the Darlo TEQSA Registration Guide
— a plain-language walk through each section of an initial registration application and the evidence that belongs in it, drawn from our TEQSA registration and governance work with private providers. Get the guide
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 is the single most common mistake in a TEQSA registration application?
In my experience it is the staffing profile: describing roles to be recruited rather than named, contracted, qualified people. TEQSA registers a provider that can deliver its courses now, and a schedule of intended hires does not demonstrate that.
Does TEQSA penalise applications written with AI?
There is no rule against it, but generic AI-drafted text that names no policy, meeting or figure draws closer scrutiny because the assessor cannot tell whether the provider understands the standards. Specific, evidenced prose is safer regardless of how it was drafted.
How does TEQSA check AQF level in course learning outcomes?
Assessors compare the course learning outcomes with the AQF level descriptors for knowledge, skills and application, then check that the assessment tasks test those outcomes. Outcomes that describe a lower level than the badged qualification are a Standard 1.4 and 3.1 problem.
Can a former RTO reuse its ASQA compliance documents for TEQSA?
Some corporate documents transfer, but academic governance, course design, assessment and integrity arrangements must be rebuilt for higher education. VET terminology and compliance-style governance in a TEQSA application signal that the provider has not yet made the shift.
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.