An Assessment Was Interrupted

Work in the workspace is stored locally as the candidate goes, so an interruption is usually recoverable.

Reconnecting

If the tab closed, the browser crashed, or the network dropped, the candidate reopens the same invitation link. The workspace remounts with their work intact and the attempt continues.

The clock kept running. The timer is server-authoritative, so it does not pause for a disconnection. That is deliberate — otherwise the timer would be trivial to game.

Resetting an attempt

When something genuinely broke, reset the attempt from the invitation row. This clears the attempt and issues a fresh link. The candidate starts over on a clean workspace.

A reset caused by a platform failure does not consume another assessment unit. A reset because the candidate wants another go does — see How Assessments Are Counted.

Extending time

Where an interruption cost a candidate real time but their work is fine, extend the limit on the attempt instead of resetting. They keep everything and get the minutes back.

This is also how you apply a reasonable accommodation.

Judging a partial submission

An attempt that ran out of time still produces a report. Read it, but read it as what it is: an incomplete submission.

The timeline is still fully informative. How someone spends fifty minutes tells you plenty even if they did not finish — and if several candidates hit the limit on the same assessment, the task is too big for the time you gave it.

When to just re-run it

If you cannot tell whether a bad result came from the candidate or from something environmental, send a fresh assessment. It costs one unit and removes the doubt, which is cheaper than getting the hire wrong.