The reliable way to avoid TEQSA application mistakes is to treat the application as a build with five stages, each with its own gate: sequence the work so that governance and course design come before the writing, index every piece of evidence as it is created, run an internal review that reads the application as an assessor would, hold a mock assessment before lodgement, and prepare for a request for further information before it arrives. Most of the errors I have catalogued elsewhere are not failures of knowledge. They are failures of process, and a process fixes them.
This article sets out that method stage by stage. It draws on fifteen years of TEQSA registration work with private providers, and it is the companion to my catalogue of the common mistakes in TEQSA applications, which describes the errors themselves rather than how to stop them occurring.
Why a method to avoid TEQSA application mistakes beats a list of errors
A list of mistakes is useful once, when you check a finished application against it. By then the expensive errors have already been made, because they were baked into the order in which the work was done. A provider that wrote its policies before it appointed its academic board has an academic board that has never made a decision, and no amount of proofreading will fix that.
TEQSA's own application guide for prospective providers is organised by the Threshold Standards, not by the order in which a sensible provider would build the evidence. That is the regulator's job. Sequencing is yours. In my experience the providers who avoid TEQSA application mistakes are the ones who decide the order of work first and the content of the application second.
Stage one: sequence the build so evidence has time to exist
The Higher Education Standards Framework (Threshold Standards) 2021 is written in the present tense. It asks whether a governing body monitors, whether an academic board oversees, whether a provider reviews its courses. Evidence of a thing that exists is not evidence of a thing that operates, and operation takes time. The first stage of prevention is therefore a calendar that puts the slow-maturing items first.
In my practice the sequence is governance, then people, then courses, then policies, then writing. The corporate board and academic board are constituted and meet on a real cycle from month one, because six months of minutes showing genuine decisions is worth more than any narrative. Key academic staff are recruited early enough to contribute to course design rather than being named after the fact. Courses go through design, external review and academic board approval, a cycle that in my experience takes three to four months. Policies are written to reflect how those bodies actually work, and the application is drafted last, describing something that already exists.
TEQSA's indicative timeframes assume you engage with the regulator at least six months before applying, and that engagement is far more productive when the governance is already running.
Stage two: index the evidence as it is created
The second most common failure I see is an application whose evidence was collected at the end, in a hurry, from whoever still had the files. Documents are missing, versions conflict, and the evidence index is a spreadsheet built in the final week that nobody has reconciled against the narrative. TEQSA reads the index before it reads anything else, and an index that does not match the submission tells the assessor the provider does not know its own material.
The prevention is dull and effective. From the first board meeting, every document that might be evidence is filed with a unique identifier, a date, a version number and the standard it speaks to. Minutes are indexed the week they are approved, and policies carry their approval date and the body that approved them on the front page. When the writing stage begins, the index already exists and the narrative is written to it, not the other way around. Our TEQSA registration checklist for new providers lists what that index typically needs to hold.
Stage three: an internal review that reads like an assessor
An internal review is not a proofread. The reviewer's task is to pick a standard at random, read the narrative for it, open every document the narrative cites, and ask whether the documents prove the claim. Then repeat for another standard. In my experience a competent reviewer doing this for a day finds a dozen places where the narrative asserts something the evidence does not show, and each one is an RFI avoided.
The reviewer should be someone who did not write the application. Where the provider is small, that is often a board member with higher education experience, and that is appropriate because the board is non-delegably responsible for the application in any case. Consultants advise, boards decide, and the record must show the board reviewed and adopted the submission as its own. A board resolution that says "the application was received and approved" without any evidence of reading is a governance mistake sitting inside the process meant to prevent them. My article on what TEQSA looks for in a successful registration application describes the assessor's reading habits the reviewer should imitate.
Stage four: a mock assessment before lodgement
A mock assessment goes one step further than internal review. Someone plays TEQSA. They receive the application cold, with the evidence index and nothing else, and they produce a written list of the questions they would ask. In my experience the exercise takes two to three weeks and produces a document that looks uncomfortably like a real request for further information, which is the point.
The mock assessment should also rehearse the site visit and the interviews. Assessors talk to board members, academic board members, the CEO and academic staff, and they ask each of them the same questions to see whether the answers agree. A board chair who cannot describe how the academic board reports to the corporate board, or an academic board member who has never seen the risk register, is a finding regardless of what the paperwork says. Preparing people for those conversations is not coaching them to say the right thing. It is checking that the governance the application describes is the governance they actually experience.
Stage five: RFI readiness
Even a strong application can attract a request for further information, because TEQSA's assessment is risk-based and it will probe wherever the evidence is thinnest. The mistake is treating an RFI as a crisis. The prevention is to have already decided who answers, how quickly, and from what material.
Before lodgement I ask providers to nominate one person who owns the RFI response, to agree that the board will meet within a week of any RFI arriving, and to keep the evidence index live so that any additional document can be located and cited in a day. An RFI answered in ten days with precise references to indexed evidence reads very differently from one answered on the deadline with new documents that did not exist when the application was lodged. The regulator notices when evidence is created in response to a question, and it draws the obvious conclusion.
Where the method fits in the overall process
The five stages sit inside the formal sequence that TEQSA runs: preliminary assessment within thirty days of lodgement, then a substantive assessment with a decision due within nine months of commencement, extendable by up to a further nine. The provider controls nothing after lodgement except the quality of its responses. Everything the provider does control happens before, which is why the step-by-step application process is worth reading alongside this method.
Since TEQSA retired Confirmed Evidence Tables in favour of self-assurance, the evidentiary bar has risen rather than fallen. A self-assurance report asks the provider to make its own judgment and to prove it, and generic, AI-drafted narratives that assert compliance without specific evidence now attract more scrutiny, not less. A method built around evidence that exists, is indexed and has been tested by someone playing the assessor is the direct answer to that shift.
What I tell providers who want to get it right first time
The fastest path to registration is a complete, specific, true application that avoids RFIs. Nobody achieves that by being clever in the writing. They achieve it by building the provider in the right order, keeping the evidence tidy from the start, and testing the whole thing against a sceptical reader before TEQSA does. The method costs some months at the front of the project. In my experience it saves more months at the back, and it produces a provider that can actually do what its application says.
If you take one thing from this article, take the sequence. Governance first, people second, courses third, policies fourth, writing last. Providers who follow it avoid TEQSA application mistakes almost by default, because the mistakes have nowhere to hide.
Download the TEQSA Registration Timeline Planner
— a month-by-month build sequence with evidence-indexing and review gates, drawn from our TEQSA registration work with private providers. Get the planner
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
How early should a provider start building evidence before a TEQSA application?
In my experience twelve to eighteen months before lodgement for governance and course design, because TEQSA reads the Threshold Standards in the present tense and expects to see governing bodies that have actually met, decided and monitored over a sustained period.
Who should conduct the internal review of a TEQSA application?
Someone who did not write it, ideally a board member or external academic with higher education experience. The review tests whether each cited document proves the claim made in the narrative, and the board should record that it considered and adopted the application as its own.
What does a mock TEQSA assessment involve?
A reviewer receives the application cold, drafts the questions an assessor would ask, and rehearses interviews with board members, academic board members and staff to check that their accounts of governance match the documents.
Does a strong application still receive a request for further information?
It can, because TEQSA's assessment is risk-based and it probes wherever evidence is thinnest. The aim is to make any RFI narrow and to answer it quickly from evidence that already exists and is indexed.
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.