About
Why Verantrix exists
Preparation is full of ways to accumulate content. What is harder to find is something that notices why the same mistake keeps happening.
The gap shows up most clearly for repeat sitters. They have often already covered the content. What keeps costing them marks is a reasoning pattern that more content cannot fix, because content was never designed to find it.
So Verantrix is built around one distinction: whether an answer was correct and whether the reasoning behind it was sound are different questions. A right answer can come from an unreliable shortcut, and a wrong one can come from a sound reading that went one step too far. Keeping the two apart is what makes the advice specific enough to act on.
It is written for candidates sitting the GAMSAT in Australia.
Who runs it
Verantrix is built for candidates sitting the GAMSAT in Australia. The operating entity is named in the Terms of Use.
The full operating terms, including what happens to your work during the beta, are in the Terms of Use.
How the content is made
Every question, answer and explanation is written for Verantrix and reviewed by a person before it reaches you. Correctness is not decided by a model: the approved answer and the reasoning behind it are human-authored and human-reviewed, and the coach works from that reviewed content rather than deciding for itself.
No examination material is used. ACER’s own questions are not ingested, reproduced or paraphrased here, for any purpose, and every worked example on this site is invented. Verantrix is independent of the Australian Council for Educational Research and is not a source of official information about the examination.
Content about the examination itself -- rules, dates, structure -- is sourced from ACER’s published materials and attributed, or it is not published.
What we do not claim
We have no outcome data, so we do not say what results candidates get. No score improvement is promised, no percentile, no admission outcome, and nothing here is described as typical, because we have nothing establishing what typical is.
Feedback can be wrong. It is a study aid, produced in part by a model, and it is not a marker. Where the evidence behind an observation is thin, the product is built to say so rather than to sound confident.
When something is wrong, tell us. Corrections to published content are made promptly, and where a correction changes the meaning of advice we have given, the change is noted rather than quietly applied.
How the pieces fit together is on the method page, and contact is open before you register.