How Long Does the Cubiks Assessment Take?

SEO title: How Long Does the Cubiks Assessment Take?

Meta description: How long Cubiks (Talogy) takes: Logiks General block timings, standalone Logiks Advanced tests, untimed PAPI, setup time and the invitation deadline.

Suggested URL: /tests/how-long-does-the-cubiks-assessment-take

Quick answer

The Logiks reasoning part is short — often surprisingly so. The commonly published Logiks General Intermediate configuration runs 50 questions in about 12 minutes total, and the commonly published Advanced configuration runs 30 questions in about 20 minutes. Those totals are not one continuous window, though: they are divided into verbal, numerical and abstract blocks, each with its own countdown, and the Advanced split is usually described as around eight minutes each for verbal and numerical and four for abstract.

That per-block structure is the number that actually governs your day. You never get the whole 12 or 20 minutes to allocate as you like. You get a few minutes for one ability, then a few for the next, and unused time in one block does not roll forward. The block budget — not the total — is what you should be pacing against.

The whole sitting is usually longer than the Logiks figures suggest. If your employer has also assigned PAPI, that is typically untimed and commonly takes somewhere around 25 to 35 minutes, which can easily double or triple the session. A situational judgement component adds more. And if you were assigned a standalone single-ability Logiks Advanced test instead of Logiks General, the shape changes again — these are commonly reported at around 25 minutes for verbal, 25 for numerical, and 15 for abstract, sat as one sustained test rather than three short blocks. Employers configure their own versions, so use your invitation and instruction screens for the real figures.

The block timers are the number that matters

Divide the total by the questions and you get an average, but averages mislead here because the blocks are not equally weighted.

On a commonly published Intermediate configuration the three blocks each take roughly a third of the 12 minutes, but the question counts differ — verbal typically carries the most items, numerical fewer, abstract fewer still. That produces genuinely different per-question budgets in each block: a handful of seconds per verbal item, a little more for numerical, and around twenty-odd seconds for each abstract item.

On a commonly published Advanced configuration the imbalance is sharper. Verbal and numerical get around eight minutes each while abstract gets around four, and because the numerical block carries relatively few questions, it works out at roughly a minute per item — a completely different rhythm from Intermediate, where you are recognising and moving rather than working.

Two practical consequences follow. Calculate the budget fresh for each block from its own instruction screen rather than carrying a rhythm over from the previous one. And set your abandonment threshold per block: thirty seconds on a stubborn item is catastrophic in a block running at a few seconds per question and entirely normal in the Advanced numerical block.

Check also whether you can revisit questions within a block, since that varies by administration and determines whether skipping is a viable tactic or has to mean answering something before moving on.

You cannot bank time between blocks

This is the single most misunderstood aspect of Cubiks timing, and it changes tactics more than any other fact on this page.

Because each block has its own countdown, finishing a block early does not create time for the next one. That minute simply disappears when the block closes. There is no pool of time to manage across the sitting and no advantage in rushing a block you are comfortable with in order to build a buffer, because the buffer cannot exist.

The corollary is that a disruption is contained but concentrated. An interruption does not eat into your whole assessment — it eats into whichever block you happen to be in. On a four-minute abstract block, two minutes lost to a doorbell is half the block gone, and there is no way to make it up elsewhere.

It also means each block deserves its own mental reset. Candidates who carry frustration from a block that went badly into the next one lose twice. When a block closes, it is finished and unrecoverable; the only useful response is to give the next one full attention.

Rehearsing this in practice matters more than it sounds. Run blocks back to back under their own timers so that the transitions, and the finality of each block closing, are familiar rather than discovered on the day.

Standalone Logiks Advanced tests are a different shape

Not everyone gets Logiks General. Some employers assign a standalone single-ability test, and the timing profile is quite different.

These are commonly reported at around 25 minutes for the verbal test, 25 minutes for the numerical test, and 15 minutes for the abstract test — one sustained assessment on one ability rather than three short blocks in sequence. The per-question budget is generally more generous and the questions are correspondingly harder.

That changes what you should prepare. Stamina and consistency matter more; the ability to switch quickly between question types matters not at all. Pacing is a single sustained plan rather than three separate short ones, and a mid-test checkpoint is genuinely useful in a way it is not in a four-minute block.

If your employer has assigned more than one of these, check whether they must be completed in one sitting or can be spread across the completion window. Where they can be separated, spreading them over two or three days usually produces better results, since each is sharper when you are fresh.

Your invitation names which assessment you have been given. Preparing for three fast blocks and then meeting a single 25-minute test — or the reverse — means arriving with the wrong instincts, and that is an avoidable problem.

PAPI and situational judgement add the real time

If your process includes PAPI, budget generously, because it typically dominates the session.

PAPI is untimed in the usual sense and commonly takes somewhere in the region of 25 to 35 minutes depending on the format. The normative version presents a large set of statements to rate on a scale; the ipsative version presents groups of statements and asks which is most and least like you, and many candidates find the forced choices slower going because several options feel partly true.

There is no advantage to hurrying an untimed questionnaire and no advantage to agonising either. First responses tend to be the more consistent ones, and over-deliberating usually produces a less coherent profile rather than a better one. Aim for a steady, unhurried pace and do not schedule it against a hard stop.

A situational judgement component adds further time. These are typically not timed as aggressively as the Logiks blocks, and they reward reading each scenario properly rather than skimming for keywords, so allow for that.

Add it all up from your invitation rather than from the Logiks figures alone. A candidate who budgets 20 minutes because they read that Logiks Advanced takes 20 minutes, and then meets PAPI immediately afterwards, is going to be rushing something that should not be rushed.

Setup, instructions and the completion deadline

Add fifteen to twenty minutes at the front that most candidates never plan for.

That covers the practical things that protect a session with almost no slack: a wired connection or a spot close to the router, other applications closed, notifications silenced on the computer and separately on the phone with the phone out of reach, water and any permitted paper or calculator on the desk, and anyone sharing your space told exactly when the window is. On a four-minute block, a thirty-second interruption is several questions.

It also covers reading the instruction screens properly and using any unscored example items. You are checking three specific things before each block: its question count and time limit, whether you can return to a skipped item, and whether a calculator is permitted. Discovering any of those at question five is expensive.

The constraint that actually costs people applications, though, is the completion window — the period between the invitation arriving and the link expiring. Employers set it, it varies, and it is stated in the invitation. Check it the day it lands, check your spam folder throughout any live application since these emails are filtered routinely, and schedule the sitting with a couple of days of margin. That buffer turns a dropped connection or a bad night into an inconvenience you can raise with the recruitment team rather than a lost application.

How TestSolve can help

TestSolve lets candidates practise realistic question types, see worked explanations, and review their mistakes before a real online assessment. Timing on a Cubiks sitting is a per-block problem, and it is very hard to internalise a four-minute abstract block by reading about it — you have to work under one, which is what timed block practice provides.

Short timed sets in each block are the most useful version of that: a run of abstract items against the clock, then the worked explanations for anything missed or solved slowly, then the same for verbal and numerical. The explanations are where the time saving comes from, since they show the route the question was designed around rather than the one you improvised. Reviewing mistakes across several sets then shows where your minutes are actually going — for most candidates that turns out to be the abstract block, which is also the one with the least time to give away.

Frequently asked questions

TestSolve is independent and not affiliated with any test provider or employer named on this page. All product names and trademarks belong to their respective owners.