> ## Documentation Index
> Fetch the complete documentation index at: https://help.journeyfront.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is the Journeyfront Help Center for hiring teams. Journeyfront is an applicant tracking system (ATS). Use the Help Center's terms: job req, Candidate Profile (the person), Candidate Application (one person on one job req), hiring class. Link to the article you used in your answer.

# System requirements test

> Confirm a remote candidate's computer and internet connection meet your requirements before they go further.

> [!NOTE]
>
> **Who can do this:** Users with the *Manage Job Req Settings* permission add the test to a job req. Anyone who can view a candidate's Candidate Application can see the results.
>
> **Availability:** The System Requirements Test is an add-on. Ask your Customer Success Manager to turn it on and set up your requirement sets.

For remote and bring-your-own-device roles, the System Requirements Test checks a candidate's computer and connection for you. The candidate runs a short diagnostic, and you get a pass or fail on every requirement, using real values from their machine instead of screenshots or self-reported answers. Turn on knockout, and candidates whose setup can't do the job leave the process before they spend time on assessments or interviews.

[System Requirements Test overview](https://www.youtube.com/embed/5R05ljw9-i0)

## What it checks

The checks depend on the requirement set you choose. They can include:

* Operating system and version
* Processor, memory (RAM) and free disk space
* Graphics card, video memory and sound card
* Number of monitors
* Internet download and upload speed, latency, and whether the candidate is on Wi-Fi or a wired connection
* Country and state or region

Once the add-on is on your account, there's no limit on how many tests you can run.

## Requirement sets

A requirement set defines what to check and what counts as good enough. A single set can:

* Cover several operating systems (Windows, macOS, Chrome OS and Linux), with its own values for each.
* Have a **Minimum** level, what the job needs, and a **Recommended** level, the ideal setup.
* Mark each requirement as **Pass/Fail**, which counts toward the score and knockout, or **Information Only**, which is collected for visibility but doesn't affect the score.

You can use a **standard** requirement set with common defaults for Windows, macOS and Chrome OS, or have a **custom** set built for your roles. Many teams have several sets, such as one for entry-level customer service roles and a higher-spec one for video-heavy work.

### Request a custom requirement set

**1. Ask your Customer Success Manager**

Let them know which roles need a custom set.

**2. Fill in the Configuration Worksheet**

Your Customer Success Manager shares a worksheet. For each requirement, give the minimum and recommended values and say whether it's **Pass/Fail** or **Information Only**.

**3. Wait for the set to go live**

Your Customer Success Manager lets you know when it's on your account. This usually takes one to two weeks.

**4. Add it to your job reqs**

Follow the steps below to start using it.

> [!TIP]
>
> Request custom sets early in your rollout so they're ready before your first hiring push. To change a set later, ask your Customer Success Manager. Changes apply to future tests only; candidates who already took the test keep their results.

## Add the test to a job req

**1. Open the workflow editor**

Open the job req and go to **Setup**, then **Workflow**. Click **Create New Version** (or **Edit Draft** if there's already a draft).

**2. Add the activity**

In the building blocks on the left, drag **System Requirements Test** into the step where you want to check candidates' tech. The **Choose a requirement set** panel slides out.

**3. Choose a requirement set**

Your account's requirement sets are listed on the left, with the operating systems each supports. Click a set to see its **Minimum** and **Recommended** values, using the tabs to switch between operating systems, then click **Use this set**. The draft can't be saved until you choose one.

Later, the activity's **Requirement Set** section shows the set you picked. Click **View or change** to open the panel again. Once a version is saved with the activity, you can view its set but not switch it; to use a different set, add a new System Requirements Test.

![The workflow editor with the Choose a requirement set panel open: the account's requirement sets listed on the left with the operating systems each supports, and the selected set's Minimum and Recommended values for Windows, with tabs for macOS and Chrome OS and the Use this set button highlighted](https://mintcdn.com/journeyfront/V546gE5TModFe50b/images/assessments/system-requirements/gen-requirement-set.png?fit=max\&auto=format\&n=V546gE5TModFe50b\&q=85\&s=a6bd8d2b87916b7b71a2004ed2e82af2)

**4. Set scoring and knockout**

Check the **Instructions** (click to expand) and the **Scoring** section, and adjust scoring and knockout (below).

**5. Save and publish**

Click **Save Draft**, then **Publish** when you're ready. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).

The default candidate instructions already tell candidates to take the test on a computer, not a phone. You can add anything specific to your process on the activity.

> [!TIP]
>
> Put the test early in the workflow, right after the application. Candidates whose setup won't work find out quickly, before they invest time in longer assessments or interviews.

## Set scoring and knockout

After you choose a requirement set, the activity's **Scoring** section shows a row for each result: **Requirements Not Met**, **Minimum Requirements Met** and **Recommended Requirements Met**. Each result gives the candidate a Job Adaptive Score on the 1 to 5 scale, so it sits alongside the rest of the workflow. You can change the score for **Minimum Requirements Met** if this job needs a different bar.

The **Knockout** checkbox on a row decides what happens to candidates with that result:

* **Checked:** they're rejected automatically, with the rejection reason **Auto rejected**.
* **Unchecked:** they're scored and stay in the process for your team to review.

> [!TIP]
>
> New to the test? Leave **Knockout** off for a few weeks and watch how candidates score. Turn it on once you're confident the requirements fit your roles.

The score counts toward the candidate's overall score and works with filters and automation rules, just like any other activity.

## Review a candidate's results

**1. Open the Assessments tab**

Open the candidate's Candidate Application and select the **Assessments** tab.

**2. Expand the test**

Expand the System Requirements Test. You'll see the overall result, **PASS RECOMMENDED**, **PASS MINIMUM** or **FAIL**, and the Job Adaptive Score.

**3. Check each requirement**

The table lists every requirement checked. The candidate's actual values, their raw results, appear under **Your System**, next to your minimum values (**Requirements**) and recommended values (**Recommendations**). The **Min** and **Rec** columns show a pass, fail or information-only mark for each level.

![The requirements table for a candidate's System Requirements Test, with a pass, fail or information mark for the minimum and recommended level of each requirement, and the candidate's actual values under Your System](https://mintcdn.com/journeyfront/61dBaB1hIRAsZpUl/images/assessments/system-requirements/gen-results-table.png?fit=max\&auto=format\&n=61dBaB1hIRAsZpUl\&q=85\&s=f0307d7093490ab80c873a1491ea0650)

> [!TIP]
>
> The breakdown makes follow-up easy. A candidate who failed only because they're on Wi-Fi when the role needs a wired connection may be one cable away from passing. **Information Only** requirements appear in the table but never affect the score.

If results don't come back right away, the test shows **Error Getting Results**. Journeyfront keeps trying automatically for 48 hours, and you can click **Retry** to fetch the results again at any time.

## What candidates see

* **Instructions first.** The test appears as an activity in their application, with instructions to use a computer rather than a phone.
* **A quick scan.** They click **Continue**, download and open a small file that checks their computer, and a short diagnostic runs, usually in under two minutes. There's nothing to type.
* **A clear finish.** They come back to Journeyfront, see the test marked complete, and can continue to the next step.
* **No waiting around.** If results are still processing, they're told their test was received and they can carry on. Journeyfront keeps checking for the results.
* **A way to retry.** If the score can't be calculated, they see a message asking them to try again, with a **Try Again** button.

![What the candidate sees: their application steps with the System Requirements Test as the next step, then the test instructions with the Continue button](https://mintcdn.com/journeyfront/61dBaB1hIRAsZpUl/images/assessments/system-requirements/gen-candidate-start-test.png?fit=max\&auto=format\&n=61dBaB1hIRAsZpUl\&q=85\&s=c2b38f940ab8bf605926bf3061f3882c)

## FAQ

> [accordion] Can candidates take the test on a phone or tablet?
>
> No. The test only runs on a computer with Windows, macOS, Chrome OS or Linux. The default instructions tell candidates this before they start.

> [accordion] A candidate sees "Failed to calculate score." What should they do?
>
> Ask them to click **Try Again** on the same computer and let the scan finish without closing the window. Until a scan completes, the activity stays **In Progress**, so they can retry as many times as they need. If it keeps failing, contact support with a link to the candidate's Candidate Application.

> [accordion] What if a candidate closes the window before the scan finishes?
>
> The activity stays **In Progress**. They can open it again and restart the test. Only a completed scan produces a score.

> [accordion] The results say Error Getting Results. What does that mean?
>
> The candidate finished the test, but the results haven't come back yet. Journeyfront retries automatically for 48 hours. If retries stop, click **Retry** on the Candidate Application.

> [accordion] How is this different from the Internet Speed Test?
>
> The Internet Speed Test only checks download and upload speed. The System Requirements Test checks the whole setup, hardware, software and network, against a requirement set. You can use both in the same workflow.

> [accordion] Can one requirement set cover several operating systems?
>
> Yes. One set can hold separate values for Windows, macOS, Chrome OS and Linux. Most teams keep all their supported systems in one set.

> [accordion] What happens if we change a requirement set after candidates have taken the test?
>
> Candidates who already took the test keep their results. The new values apply to tests taken after the change goes live.

> [accordion] Is there a limit on how many tests we can run?
>
> No. Once the add-on is on your account, run it on as many candidates and job reqs as you like.

## Related

> [card] [Add-ons](https://help.journeyfront.com/account-setup/add-ons.md)
>
> Turning on add-ons for your account.

> [card] [Workflows overview](https://help.journeyfront.com/workflows/overview.md)
>
> Where activities like this fit in a job req's workflow.

> [card] [How scoring works](https://help.journeyfront.com/scoring/how-scoring-works.md)
>
> Raw scores and the Job Adaptive Score.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.