Updated April 2026 · 9 min read · Saville Assessment · Adaptive combined cognitive
| Provider | Saville Assessment |
|---|---|
| Test family | Swift Assessments (combined adaptive) |
| Format | ~20-25 minutes · adaptive · numerical + verbal + diagrammatic |
| Variants | Swift Analysis Aptitude, Swift Comprehension Aptitude, Swift Apprentice, Swift Executive |
| Used by | Aon (some pipelines), Centrica, Capita, Babcock, Network Rail, Lloyds Banking Group |
Saville's Swift Assessments are adaptive cognitive batteries that combine multiple reasoning domains into one efficient test. Where Saville's Standalone tests dedicate a full session to a single domain (numerical or verbal alone), Swift tests bundle the domains and use adaptive item delivery to triangulate ability faster.
| Variant | Combines | Used for |
|---|---|---|
| Swift Analysis Aptitude | Numerical analysis + verbal analysis + diagrammatic analysis | Senior analyst, manager, leadership roles |
| Swift Comprehension Aptitude | Numerical comprehension + verbal comprehension + error checking | Operational, administrative, customer-facing roles |
| Swift Apprentice | Numerical + verbal + checking · school-leaver level | Apprenticeship and school-leaver schemes |
| Swift Executive | Higher-order numerical, verbal, diagrammatic | Director / partner-level selection |
Swift uses an item-response-theory engine: difficulty calibrates to your responses. Initial questions are medium-difficulty; correct answers escalate difficulty, wrong answers de-escalate. Score is your demonstrated ability level, not raw item count. This means two candidates can answer the same number of questions correctly but receive very different percentile scores.
Sten scores (1-10) and percentiles relative to graduate or professional norm groups. Most graduate cutoffs sit at sten 7+ (top third), with senior roles requiring sten 8+.
Centrica, Capita, Babcock International, Network Rail, Lloyds Banking Group (selected pipelines), Severn Trent, Anglian Water, and several UK public sector recruitments use Saville Swift across graduate and operational tiers.
Practice across all three modes. Swift's combined nature means you can't rely on one strong area to compensate for a weak one. The adaptive engine evaluates each domain semi-independently.
Early questions matter more. Adaptive engines weight early items because they determine the entry difficulty for subsequent items. Take 5-10 extra seconds on questions 1-3.
Don't gamble. On adaptive tests, gambling that you'll guess right and unlock harder questions doesn't work — wrong answers de-escalate difficulty and your score drops. Answer only when reasonably confident.
Practise across a range of difficulty levels, not just your comfort zone. Because Swift adapts to your demonstrated ability, strong candidates will genuinely see harder items than weaker candidates during the same test — this is by design, not a sign anything has gone wrong. Practising exclusively on easier practice material won't prepare you for the harder items an adaptive engine will serve you once you've demonstrated strong early performance, so deliberately including some genuinely difficult practice items in your preparation, not just items at your current comfortable level, better reflects what a strong performance on the real test actually looks like.
Manage the psychological effect of increasing difficulty. A specific and common source of anxiety on adaptive tests is noticing that questions are getting harder partway through — some candidates interpret this as a sign they're doing badly, when it's actually the opposite: the engine only escalates difficulty in response to correct answers. Understanding this in advance, so that increasing difficulty reads as a positive signal rather than a source of doubt, helps maintain confidence and pacing through the back half of the test rather than second-guessing a strong performance.
Numerical reasoning on Swift tests is almost always table-based: two or three small tables of financial, sales, or operational data, followed by a question that requires a multi-step calculation and a unit conversion.
Q. A retail chain sells three product lines. Units sold last quarter were 660 (Line A), 1,140 (Line B) and 310 (Line C). Average selling price was £1.00, £1.00 and £1.00 respectively. Total revenue to the nearest £ was:
A) £1,780 B) £1,950 C) £2,048 D) £2,110
A. Sum the units: 660 + 1,140 + 310 = 2,110. Answer: D.
The actual Swift question adds distractors: prices in pence rather than pounds, mixed currencies, unit ambiguity (per pack vs per item). Candidates who rush the unit check pick C or B despite nailing the arithmetic.
Standard Swift numerical assessments give 18 questions in 18 minutes — about 60 seconds per question. That sounds generous but each question has 3–5 numbers to read, a calculation (often multi-step), and a unit conversion.
If you're past 75 seconds and still unsure, flag and move on — you can't recover four lost minutes from one stubborn question.
Your invitation email or the job description is the most reliable source — Saville and the employer will usually name the specific variant (Analysis, Comprehension, Apprentice, or Executive) rather than just "Saville Swift" generically. If the level isn't explicit, the seniority of the role is the next-best signal: graduate and entry-level roles most commonly use Comprehension or Apprentice, since these variants pair straightforward numerical and verbal comprehension with error-checking rather than the more demanding analytical reasoning the Analysis and Executive variants require. Manager and senior-analyst roles more commonly use Analysis Aptitude, which adds diagrammatic reasoning to the numerical and verbal components. Director and partner-level selection processes use Executive, the hardest variant, which tests the same three domains at a noticeably higher difficulty ceiling given the adaptive engine's difficulty range extends further for this variant.
If you're still unsure after checking your invitation and role level, a safe general strategy is to prepare broadly across numerical, verbal, and diagrammatic reasoning rather than betting everything on one specific variant — since all four Swift variants draw from the same underlying domains, general practice across all three transfers reasonably well regardless of which specific variant you end up facing.
Because Swift's item-response-theory engine adjusts difficulty based on your responses in real time, the test doesn't have a single fixed set of questions the way a traditional linear test does — two candidates of different ability levels will see meaningfully different item difficulty even within the same section, and the total number of items you see can vary somewhat between candidates depending on how quickly the engine converges on a reliable ability estimate. This has a direct practical implication: your score reflects the difficulty level you demonstrated you could handle, not simply how many questions you got right in absolute terms, which is why two candidates who both answer, say, 15 questions correctly out of 20 attempted can still receive noticeably different final sten scores if one of them was working through harder items than the other by that point in the test.
The practical takeaway for preparation: since early questions disproportionately set your difficulty trajectory for the rest of the section, treating the opening few items of each section with extra care — rather than rushing through them at the same pace you'd use once you're mid-section and warmed up — has an outsized effect on your eventual score compared to the same extra care applied to a later question.
A second, less obvious implication of the adaptive format: since the engine specifically targets items near the edge of your demonstrated ability, you should expect to feel like you're struggling for much of the test even if you're performing well. This is normal and by design — a well-calibrated adaptive test converges toward roughly a 50/50 hit rate for a candidate performing at their true ability level, which feels noticeably harder in the moment than a fixed-difficulty test where you'd comfortably answer most items correctly. Candidates unfamiliar with this dynamic sometimes mistake the felt difficulty for evidence they're underperforming, which can dent confidence and pacing on later items for no real reason — knowing in advance that persistent difficulty is a sign the engine is working correctly, not a sign of poor performance, is itself a useful piece of preparation.
Use TestSolve to crack the Saville Swift Assessments
AI-powered answers and reasoning sent to your phone in seconds. Free first solve, no signup.
Try it free →See pricing