Can You Retake a Cubiks Assessment?

SEO title: Can You Retake the Cubiks Assessment?

Meta description: Whether you can retake a Cubiks (Talogy) test, why block timers leave no room to restart, what to do after a technical fault, and how reapplication works.

Suggested URL: /tests/can-you-retake-cubiks-assessment

Quick answer

Retakes are an employer decision, not a feature of the test. Cubiks supplies the assessment; the organisation that invited you decides whether anyone gets a second attempt, and most do not offer one simply because a candidate was disappointed.

Within the sitting itself there is no retake mechanic at all, and the block structure makes that unusually final. Logiks runs verbal, numerical and abstract as separately timed blocks, and when a block's countdown expires the test moves on. You cannot go back to a completed block, you cannot restart one, and on the commonly published Intermediate configuration a block may run only a few minutes — so there is very little margin between a small problem and a lost block. Whether you can revisit individual questions within a block varies by administration and is stated on the instruction screen, which is worth reading before you start rather than discovering at question twelve.

The realistic routes to another attempt are three: the employer offers a retest for reasons of their own, usually supervised confirmation or a later cycle; something fails technically and the employer reissues the assessment; or you apply again in a future round under whatever reapplication policy that employer publishes. Each is covered below. One practical note throughout — you may see either the Cubiks or Talogy name in your correspondence, since Cubiks came under the Talogy brand on 15 March 2022, and that inconsistency is not itself a fault.

Why the block structure leaves so little room

It is worth understanding why a Cubiks sitting is less forgiving than a single-timer test of the same total length.

Because each reasoning block carries its own countdown, a disruption does not cost you time in general — it costs you time in one specific block, and that block cannot be repaid from anywhere else. Finishing verbal with a minute spare does not create a minute for abstract. A two-minute interruption during a four-minute abstract block removes half of it.

That also means a partial failure is genuinely partial. If your connection dropped during the numerical block but verbal completed cleanly, those are separable events, and saying so precisely is what makes a request actionable. "The numerical block disconnected about three minutes in" is something a recruiter can act on; "the test went wrong" is not.

The same logic applies to any PAPI or situational judgement component, which typically sit outside the tightly timed Logiks blocks and are often untimed. A fault there is usually easier to recover from, because there is no countdown that has already been consumed.

So the practical instruction is to treat the Logiks blocks as unforgiving and prepare the environment accordingly, and to document precisely which block was affected if something does go wrong.

When an employer offers a retest

Where retests happen, they are almost always driven by the employer's process rather than granted on request.

Supervised confirmation is the most common reason. An employer who screens with an unsupervised online sitting may ask shortlisted candidates to re-sit an ability test under proctored conditions, to confirm the original result was genuinely theirs. If you receive that invitation, treat it as a routine stage rather than as suspicion of you specifically, prepare exactly as you did the first time, and expect equivalent but different questions rather than the same items.

A different role is a second route. Because employers set expectations per role and assign different combinations, a result that did not clear the bar for one position may be adequate for another, and some organisations will consider you elsewhere without retesting at all.

A new hiring cycle is the third. Employers running annual or seasonal intakes commonly retest returning applicants, since a result from a previous year is stale.

What is far rarer is a retest granted because a candidate felt they underperformed. Those requests are frequent and mostly declined, because giving one candidate a second attempt while others had one undermines the comparability the assessment exists to provide. Asking once is not unreasonable — expect a no, and do not let it delay the rest of your applications.

What to do when a block fails technically

This is where employers are most willing to act, so make acting easy for them.

Move immediately. Note the time, which block you were in, roughly how far through it you had got, and any error message, and take a screenshot if you can. On a block measured in minutes, evidence decays fast and vague accounts get vague responses.

Contact the recruitment contact named on your invitation the same day — not after the deadline — with a short factual account: the role and reference, which block failed, what happened, when, and a request for the assessment to be reissued. If your invitation includes an assessment support link, use that too, since it creates an independent record of the fault.

Do not reopen the link repeatedly or switch devices unless you have been told to. Multiple attempts against one invitation look like circumvention even when they are not, and they complicate the case you are trying to make.

Prevention costs far less than remedy here. Wired connection or close to the router, other applications closed, notifications silenced on computer and phone, phone out of reach, and the sitting scheduled a day or two before the deadline rather than in its final hours — so that a genuine fault leaves you time to get it resolved rather than turning into a lost application.

If the completion window closed

Employers set a completion window and state it in the invitation. Once it closes, the link usually stops working.

If you have missed it, contact the recruitment team quickly and plainly: name the role and reference, say that you missed the window, give the reason in one line if there was a real one, and ask whether a new invitation is possible. Recruiters do reissue links, particularly early in a cycle and particularly where the reason is genuine — illness, an emergency, or an invitation filtered into a spam folder.

If you completed some components but not others — the Logiks blocks but not PAPI, say — state exactly that. A request to reissue one outstanding component is smaller and more grantable than a request to start the whole process again.

What does not work is a long explanation, a request that reads as an entitlement, contact several weeks later, or starting a fresh application in the hope of resetting things; most applicant tracking systems will simply match it to your existing record.

Two habits prevent this entirely. Check your spam folder throughout any live application. And on the day the invitation arrives, put the sitting in your calendar with a couple of days of margin — remembering that if PAPI is included, the session runs considerably longer than the Logiks timings alone suggest.

Brand inconsistency is not a fault

Candidates working through a Cubiks process sometimes encounter more than one brand name and wonder whether something has gone wrong or whether they are on a legitimate site.

The background is straightforward. Cubiks was acquired by PSI Services, and on 15 March 2022 it was brought under the Talogy identity along with a large group of other assessment businesses — Caliper, a&dc, IPAT, Select International and PSI Talent Management among them. Depending on when your employer configured their process and how often they refresh their materials, your invitation email, the login page, the test interface and any resulting report may carry the Cubiks name, the Talogy name, or a mixture.

That is a reflection of a corporate rebrand rather than a technical problem, and it is not grounds for a retake request. The Logiks and PAPI material is the same either way.

What does warrant contacting the employer is a link that does not work, a test that will not load, a session that terminates unexpectedly, or an invitation that appears to be addressed to someone else. Those are real problems worth raising promptly. Unfamiliar branding on a working link is not, and raising it as one tends to slow down the response to anything genuine.

Reapplying in a future round

If you were rejected after a Cubiks stage, whether you can apply again is employer policy rather than anything to do with the assessment. Many organisations publish a waiting period on their careers pages — often measured in months for the same role — while others allow reapplication at the next cycle and some place no restriction at all. Check the specific employer rather than assuming a standard.

Where a waiting period applies, use it rather than simply waiting it out. Logiks responds well to targeted practice, and the block structure makes targeting easy: if the abstract block was the problem, that is a specific and trainable skill built on a finite set of transformation rules, not a general verdict on you. A candidate who spends a few weeks running a feature checklist until it is automatic is a materially different applicant.

Expect fresh assessments rather than reused results if you do reapply, and expect equivalent but different questions. That is good news — nothing carries over, and you are judged on what you produce this time.

Finally, a result at one employer does not follow you to another. Assessment records belong to the organisation that commissioned them, so applications elsewhere start fresh, including at other employers using Cubiks or Talogy material.

How TestSolve can help

TestSolve lets candidates practise realistic question types, see worked explanations, and review their mistakes before a real online assessment. Since there is no retake inside a Logiks block, the place for repeated attempts is beforehand, where they cost nothing: drilling verbal, numerical and abstract blocks separately under time pressure and reading the worked explanation for each item rather than only the answer.

That matters most to anyone facing a supervised retest or a reapplication after a disappointing first attempt. Because both the test and the practice are block-level, the mistake review points at something specific and fixable — data-reading errors in the numerical block, over-inferring in the verbal block, or no systematic method in abstract — rather than at a vague sense that the whole thing went badly. Working that out on practice material is what makes a second attempt genuinely different from the first.

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.