Editorial policy
How this site is written
The rules we work to, including the ones that make our job harder.
Who writes the questions
Every question is written by someone who has sat GAMSAT and finished with it. That second condition is deliberate and it is not about credibility.
ACER’s conflict-of-interest terms allow it to “refuse or cancel a relevant registration” for anyone affiliated with a preparation provider. Commissioning a current candidate would put their own sitting at risk. So we only work with people who have completed their GAMSAT journey.
The clean-room rule
We never purchase ACER's practice materials.
Buying them binds the purchaser to a licence — personal, non-commercial, twelve months, no upload to third-party or AI platforms. Accepting that licence would compromise the clean-room position that makes our original questions defensible, and it would do so invisibly.
Everything needed to write good questions is in ACER’s free published material: the subject split, the assessed skills, the format and the timings. We write from that.
Copyright protects expression, not skills, format or structure. We can legitimately build a test that mirrors GAMSAT’s structure, timing, difficulty and reasoning demands, provided every word is ours. We do not reproduce, transcribe or paraphrase any real exam question.
How questions are built
To ACER's published specification, under the real exam's constraints.
| Constraint | How we apply it |
|---|---|
| Subject split | Section 3 is 40% chemistry, 40% biology, 20% physics — stated by ACER, not estimated by us |
| No calculator | Not permitted — every item is solvable by hand, and arithmetic is kept tractable |
| No formula sheet or periodic table | Every constant a question needs appears in that question’s own material |
| No ruler | No question requires measuring anything on a figure |
| Shared stimulus | Questions attach to a shared stimulus in units of 1–7, as in the real exam — not as isolated one-offs |
| Equal value | ACER states all questions carry the same value. Ours do too. |
Difficulty is authored rather than accidental. We tune it mainly through distractor spacing — how close the wrong answers sit to the right one — which lets us vary difficulty and time pressure independently. A static PDF cannot do this; an interactive test can.
Every question ships with a worked explanation that says why the answer is right and why the plausible wrong answer is wrong. A question without an explanation is not finished.
How facts are verified
- Primary sources only.Exam mechanics come from ACER’s own booklet and site. University requirements come from each institution’s own admissions pages — not from ACER’s summary list, which we found contains four errors.
- Everything is dated. Every figure carries the year it applies to and the date we checked it.
- Unverified means unverified. Where we cannot confirm something, we label it rather than publishing a plausible number. Four of our 33 course records currently carry that label.
- Conflicts are shown, not resolved silently.Where a university’s page and a central body disagree, we say so and explain which we treat as authoritative.
What we will not publish
- A predicted GAMSAT score from a practice test. No public raw-to-scaled conversion exists. Any site showing you one has invented it.
- A single-point percentile. ACER publishes no percentile table at all, and percentiles shift between sittings. We publish ranges and say they are estimates.
- Real ACER material. No past papers, no reproduced questions, no scanned booklets — regardless of how much traffic those pages would attract.
- A Section 2 marking weighting. No official weighting between the two criteria exists. The figure circulating online comes from a prep sheet whose own author concedes ACER has never revealed its criteria.
- Invented test dates. Where ACER has not published a sitting, we say so.
Corrections
We will get things wrong. When we do, we fix the page and note what changed rather than editing quietly. If you spot an error — a stale cutoff, a wrong fee, a flawed explanation — report it here.

