July 2026

How Accurate Are Our EOI Forecasts? We Tested — Here Are the Numbers

The Immitrend Forecast Engine, validated against nine models across thousands of blind tests on real SkillSelect data.

Latest evaluation: June 2026 snapshot · next update after the July verification run

Before showing you a single prediction, we made our forecasting engine compete against nine alternatives — including machine-learning and deep-learning models — across thousands of blind tests on real SkillSelect data. This page shows exactly how it performed, where it’s reliable, and where it isn’t.

6,795
blind-test folds at 1 month ahead
~830
occupation × visa series evaluated
19 mo
of out-of-sample test targets

Six months ahead, the engine’s error is roughly half the best ML model’s.

Immitrend Forecast Engine13.0%“Pool stays flat” baseline23.0%Best ML model27.6%Foundation model34.3%
Average error (MAPE) forecasting the total EOI pool six months ahead — every method evaluated on identical blind folds. Lower is better.

The result: pool-size forecasts

Immitrend Forecast Engine“Stays flat” baselineBest ML modelFoundation model
0%10%20%30%1 mo2 mo3 mo4 mo5 mo6 mo13%34%
Average forecast error by months ahead — lower is better. The engine's lead widens with horizon: at 6 months its error is roughly half the ML model's and a third of the foundation model's.
Average error (MAPE)1 mo3 mo6 mo
“Pool stays flat” baseline5.7%13.2%23.0%
Best machine-learning model5.0%14.2%27.6%
Foundation model (zero-shot)6.1%15.2%34.3%
Immitrend Forecast Engine4.9%8.6%13.0%

The Immitrend Forecast Engine beat every alternative at every horizon beyond one month — and the gap widens the further out you look. For the large occupations most users care about, production accuracy is better still: 3.2% at one month, 9.9% at six.

Why did the ML and deep-learning models lose? Interesting failure modes, all measured: decision trees can’t extrapolate a climb they’ve never seen; the foundation model’s pretraining makes it bet against trends persisting — but SkillSelect pools trend hard. With under three years of monthly history, structure beats brute force. We re-test every candidate as history grows.

How we test a forecast honestly

Any model looks good if you grade it on data it has already seen. We use rolling-origin backtesting — the standard from forecasting science:

  • Stand at a past month — say, December 2024 — and hide everything after it.
  • Fit the model only on what was known up to that month.
  • Predict 1 to 12 months ahead, then compare against what actually happened.
  • Step forward and repeat — across every occupation, every visa subclass, every month of history.

That produces thousands of genuinely blind predictions at every horizon. We score them with MAPE — mean absolute percentage error. A MAPE of 5% means our forecasts were, on average, within 5% of the real number.

What we tested the engine against

The Immitrend Forecast Engine competed against nine alternatives on identical data, under an identical protocol, with strict train/test separation:

  • Two naive baselines (the pool stays flat; the recent trend continues as a straight line)
  • Linear regression at every window length
  • Gradient-boosted decision trees trained across all occupations (the method that wins most tabular ML competitions)
  • A pretrained time-series foundation model — a 200-million-parameter transformer
  • Four neural network architectures trained on the pooled data, including residual networks and a transformer
  • Plus ensembles, hybrids, and per-occupation model-selection strategies

Three blind-test case studies

Numbers in aggregate can feel abstract, so here are three of the most accurate results among the ten largest 189 occupations, shown in full: the engine was trained only on data up to December 2025, predicted the next six months, and then we let reality arrive. The solid line is what actually happened — including the six months the engine never saw. The dashed line is what it predicted.

Engineering TechnologistANZSCO 233914 · 189 pool
6-month forecast: 6,069actual: 6,067within 0.1%
Actual poolForecastTypical range
Dec '24Jun '25Dec '25Jun '26
Civil EngineerANZSCO 233211 · 189 pool
6-month forecast: 9,699actual: 9,325within 4.0%
Dec '24Jun '25Dec '25Jun '26
Mechanical EngineerANZSCO 233512 · 189 pool
6-month forecast: 8,565actual: 8,126within 5.4%
Dec '24Jun '25Dec '25Jun '26

These are strong examples, chosen to show the engine at its best — the averages in the table above include every occupation, including the hard cases (one accelerated 18% past every model we tested; another was whipsawed by an invitation round). That spread is exactly why every forecast ships with a range.

How far ahead can we see? The 12-month test

We extended the blind protocol to a full year. Total-pool forecasts hold up: at 12 months the engine averages 17.9% error on 189 pools — against 39.7% for “nothing changes” — and its error curve flattens after month six rather than compounding.

A full hidden year: Biomedical EngineerANZSCO 233913 · 189 pool
12-month forecast: 535actual: 530within 0.9%
Aug '24Jun '25Dec '25Jun '26

Trained only on data through June 2025, then twelve hidden months. Pool-size outlooks run to 12 months; queue forecasts stop at 6 — beyond that their errors grow past the point where we consider them decision-grade, and we would rather cap the product than publish noise.

The harder problem: the queue above your score

For 189, what matters isn’t the total pool — it’s how many EOIs sit at or above your points, because invitations go top-down. These queues are smaller, faster-moving, and driven by human behaviour (people re-sitting English tests to jump bands), so errors are honestly larger:

Queue (189)1 mo3 mo6 mo
At/above 65 points4.7%7.0%13.1%
At/above 75 points7.8%13.7%24.9%
At/above 85 points9.4%17.2%27.8%
At/above 90 points low confidence10.0%17.8%36.0%
0%8%16%24%7%≥65 pts9.2%≥70 pts13.7%≥75 pts16%≥80 pts17.2%≥85 pts17.8%≥90 pts
Three-month forecast error by queue threshold, round-adjusted fit on round-free folds (invitation rounds are modelled separately by the round-aware projection). Higher thresholds are intrinsically harder — smaller, faster-moving queues driven by applicant behaviour — which is why the ≥90 queue carries a permanent low-confidence label.

We label the ≥90 queue low confidence everywhere it appears — no model we tested (including the neural networks) can reliably predict a small queue that doubles when a cohort re-sits an English test. We’d rather tell you that than pretend otherwise.

Queue case study: Systems Analyst — all three rank-critical queuesANZSCO 261112 · 189
The engine predicted all three queues at once, six months blind.
At/above 80: forecast 3,131 · actual 3,052 within 2.6%
Dec '24Jun '25Dec '25Jun '26
At/above 85: forecast 2,278 · actual 2,230 within 2.2%
Dec '24Jun '25Dec '25Jun '26
At/above 90: forecast 1,457 · actual 1,452 within 0.4%
Dec '24Jun '25Dec '25Jun '26

Worth noting why the ≥90 queue is predictable here: Systems Analyst’s pool is unusually top-heavy (nearly half its ≥80 queue already sits at 90+), so its ≥90 queue is large and stable — unlike the small, behaviour-driven ≥90 queues that earn the low-confidence label elsewhere.

8 in 10

outcomes land inside the published typical range — a calibration we validated before launch and re-measure every month.

Why every forecast ships with a range

Actual poolForecastTypical range
Jul '25Jan '26Jun '26Dec '26
A real forecast (Early Childhood Teacher, 189 pool): the range fan widens with horizon because uncertainty genuinely grows — a 6-month forecast should not pretend to 1-month precision.

A single number pretends to a precision no forecast has. Every Immitrend forecast comes with a typical range — calibrated so that roughly 8 times in 10, the real outcome lands inside it. We validated this the hard way: our first two range algorithms failed the calibration test and were rejected before launch. The one that ships is the one that passed. Ranges widen the further ahead you look, because that’s the truth.

The part most forecast products skip

Backtests grade the past. From launch, every forecast we publish is written down first and graded later: when the next month’s official data arrives, we score every stored prediction against reality — including whether it beat the “nothing changes” baseline and whether the actual landed inside our range. That verification runs automatically every month, on data that did not exist when the forecast was made. If the engine ever loses its edge, this page will show it.

What forecasts can't know: invitation-round dates and sizes before they’re announced, policy changes, and shifts in applicant behaviour. Our 189 projections state their round assumptions explicitly (“assumes a round around September inviting roughly N EOIs in this occupation”) so you can judge them — and adjust when reality differs.

Where you’ll see it

Forecasts appear on the EOI Trends page (a 6-month outlook per visa subclass), and on every occupation page: the pool trend forecast (up to 12 months) and, for 189, the Projected Pool Distribution — including the projected queue at or above each points band, with ranges, round assumptions, and confidence labels.

This is a living methodology — we’ve published the first version, not the last. Every month we grade our stored forecasts against the new official data and re-test challenger models as history grows, so the figures on this page move with the record — and we keep sharpening both the accuracy and how honestly we report it. Independent scrutiny makes it better: if something looks off, or you want a capability we don’t have yet, tell us. Immitrend is an independent community project, and your support helps us keep improving it — we’re glad to have you along for what’s next.

See the forecast for your occupation

Sign in to unlock occupation-specific projections — including the projected queue above your score.

Explore EOI forecasts

Methodology. Rolling-origin backtest on SkillSelect EOI data (Feb 2024 – Jun 2026 snapshots): ~830 occupation × subclass series, 6,795 folds at one month ahead (fewer at longer horizons as test targets run out), out-of-sample targets Dec 2024 – Jun 2026; horizons to 12 months for pool totals, 6 for point-threshold queues. MAPE = mean absolute percentage error against subsequently observed values.

The typical range targets 80% coverage, validated by the same blind protocol; achieved coverage is re-measured each month as stored forecasts mature against new official data, and the figures on this page refresh with it.

Forecasts are estimates, not advice; migration decisions should account for the stated ranges, round assumptions, and confidence labels.

Was this helpful?